3 Commits

Include renames

Author	SHA1	Message	Date
Bendik Aagaard LynghaugandClaude Fable 5	0154f6c8c0	Announced pages: event windows, header announcements, summary tasks ... A question may carry event: {starts, duration, place}. While the window is open the page is announced in a strip at the top of every header (name, when, 'in 3 days'), soonest first, and kept out of the footer nav; when it closes the page becomes a followup - only a visitor carrying an answer chain still sees it. announce.rs keeps one record per event page in the runtime-owned portal_events bucket (built-in state graph: announced -> awaiting_summary -> summarized, content may override) and, on a one-minute idempotent sweep, moves ended windows to awaiting_summary, publishing the transition on portal.answers.submitted as 'Summary due' - the post-what-happened task a review desk picks up. Lint warns when event pages exist but nothing reads portal_events. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-30 12:34:34 +02:00
Bendik Aagaard LynghaugandClaude Sonnet 5	ebf4bf91b3	Event-sourced applicant/subscriber/project aggregates, generalized resources ... Replaces the free-string, direct-KV-mutate state model in answers.rs with a proper event log (events/store.rs, JetStream-backed, CAS via expected_last_subject_sequence) and three pure state machines (aggregates/{applicant,subscriber,project}.rs). Closes a real lost-update race in the old transition_answer (concurrent decisions on the same item could both win, publishing contradictory events). KV buckets become best-effort read-model projections, not the source of truth. Content-declared transition targets are now validated at load/reload time against the real compiled transition tables, not accepted as arbitrary strings. Buckets renamed to describe their content, not their relation to the app (portal_applicants -> applicants, etc); "inquiry" folded into a richer "project" concept. ResourceSpec generalized beyond a single KV bucket: Kv | GiteaStarred | GiteaOrgRepos | Url sources, with an optional jq filter (via the jaq crate) to shape live data for the frontend. Url source is SSRF-guarded (https-only, rejects loopback/private/link-local, real DNS resolve). New headless question_lint binary (validates content against compiled transition tables with no NATS/OIDC/server involved) and a one-time backfill_events binary (dry-run by default) for migrating existing KV data onto the new event log. Questions get an optional `responsible` contact plus a lightweight "report this question" action. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-06 08:52:29 +02:00
Bendik Aagaard Lynghaug	aa1a7fa572	Initial commit: content-driven onboarding portal ... Leptos/Axum app that renders a Question/Alternative/Feature schema loaded from a sibling content repo (portal-content). Kanidm OIDC login, content-driven authorization (Question.qualifies), a generic NATS KV-backed resource + state-transition mechanism (no bespoke "applicant" concept baked into the runtime - it's all content), a SHA-256 DAG chain tying submissions and decisions together, and the "YES - Rasterized Lines" piece (ported from the live uhhm.no site) as the landing hero.	2026-07-29 19:38:40 +02:00