4 Commits

Include renames

Author	SHA1	Message	Date
Bendik LynghaugandClaude Opus 5	44c7ee6870	Render an Apple configuration profile from the server's PACC document ... iOS is the one client none of the mail autoconfiguration reaches: Apple Mail reads neither Mozilla autoconfig nor Autodiscover for IMAP, so adding an account means the device probing for ports - and a probe that meets a filtered port waits out a TCP timeout and reports the account as unverifiable, which the person reads as a wrong password. A profile states the hosts and the ports instead, and carries mail, calendars and contacts in one install. It invents none of them: site.yaml names a PACC document - the standard defined to be fetched from the mail domain itself - and every host, port and collection path comes from there, so the server is described in one place and the profile follows it. The document holds no address, username or password. iOS asks for those at install, which means one profile serves everyone with an account and it can be fetched by anyone: it says no more than PACC already says in public. Identifiers are derived from the site and the payload rather than drawn at random, because iOS replaces a profile whose ids it knows and stacks a duplicate when they differ. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015GeH3y8fwTaTudaD88P57o	2026-10-07 11:18:46 +02:00
Bendik Aagaard LynghaugandClaude Fable 5.1	f395ace556	Storylines: the same site told several ways, one per visitor, counted ... Any text a person reads may be a list, one entry per storyline, every list the same length. A visitor is given one storyline for the whole site and reads it on every page and in every mail about their case. Records and events carry the storyline; GET /report gives counts per bucket, storyline and state, and nothing else. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt	2026-09-30 15:11:27 +02:00
Bendik Aagaard LynghaugandClaude Fable 5	8229dbf4c2	Announce sweeper: refresh open records from content ... A date or place corrected after first announce never reached the portal_events record, so the followup fired on the stale schedule. While a record is still in its initial state, content is the source of truth: differing responses are written back on each sweep. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y42TyF8Zu7NGRR2893vNcZ	2026-08-30 23:13:29 +02:00
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