v2 self hosting direction

[briansrls]

Auto-opened by session-dashboard for session fierce-lark-661.
Pushing to roadmap/wind-down-position-2026-09-14 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[gunbai-bot]

Review 66382 — both findings verified against the head and fixed in 1 commit (now $(git rev-parse --short HEAD)):

• Meaning fork on first_slice — agreed. first_slice is consumed as the next executable slice (current_state derives from it; the dispatch brief reads it). Both slices are restored verbatim.
• Unclassified prose / typed carrier — the carrier for a dated position already exists in this model: gunbc.roadmap_status TicketFields.updates: List<TicketUpdate { on, note }>, declared precisely so "every update [stops] concatenat[ing] into the blob because no time axis exists", and rendered by gunbc.roadmap_page disclosure_updates_block. Both positions now land as one TicketUpdate { on: "2026-09-14", note } each, via a new updated(t, on, note) constructor beside fields(). The note still names the standing carriers (gunbc.namespace.namespace_cut_stage, gunbc.compiler_frontend_program_interlock) rather than restating their rows; what the note carries that no carrier does is the per-PR disposition at wind-down and the resume order — which is what an update on the ticket's time axis is for.

Verified on srv1 with a gunbc built from this branch: the authority parses and typechecks; roadmap_ticket_brief_violations reports only the pre-existing cardinality-vertical-slice (119 words), untouched here.