docs: audit project readiness and streamline contributor context

[TusanHomichi]

Problem

Project guidance had drifted behind the implementation: README described an
unusable scaffold, architecture treated implemented features as plans, and
the roadmap omitted completed Milestone 5 slices. The first documentation
refresh also overstated snapshot-bound authorization. A fresh contributor
needs concise entrypoints that route to source and decision authority, an
accurate workflow, and evidence of the current continuation state.

Outcome and acceptance criteria

• README, roadmap, architecture, domain model, and integrity guide distinguish
  current implementation from remaining work through Milestone 5 slice 2.
• AGENTS.md remains concise and preserves the repository contract, while a
  task index maps work to source, ADRs, formats, and relevant tests.
• CONTRIBUTING.md owns build/verification and contribution detail; tool
  entrypoints stay thin and consistent.
• Document local versus deployed preview behavior without credentials.
• Audit current repository/CI readiness, run web/Rust/browser checks, and
  record material gaps with exact evidence and follow-up ownership.
• Add the existing browser scenarios to CI; correct the PR chore(project): audit readiness and consolidate browser fixtures #55 review finding
  without claiming unimplemented service guarantees.
• Consolidate duplicated browser process lifecycle into a shared fixture,
  prove startup/refusal/cleanup behavior, and typecheck browser code.

Primary PR: #55, also addressing #57 (browser fixture ownership). Separate
repair found by the audit: #56 (doctor changes persisted journal mode).
Existing work remains in #27, #34, #47, #49, #51, #52, and #54; #44 owns
Milestone 5.

[TusanHomichi]

Fresh-session handoff — 2026-09-05

PR #55 merged as dc898443d3ff215959043e48698734d456fdadb7. Local checkout /data/dev/src/consolebook is clean on main, identical to origin/main; push reports everything up to date. No open PRs remain at handoff. #53 and #57 closed through the merge.

The PR branch and three stale claude/ remote branches were deleted after confirming their history was retained in main. Only main remains locally and remotely (plus origin/HEAD). Recheck live state at session start rather than treating this snapshot as permanent.

Verification

Full CI passed at final PR head 424f01e0540265c5216d009ea62dacc38ef52e41: https://github.com/FieldmouseWorks/consolebook/actions/runs/33928869139. The merge tree is identical to that tested head. Gates include web install/check/build, Rust fmt/clippy/test (118 integration tests), explicit binary build, and browser tests (8). Prior review feedback is resolved. This is not production-readiness or recovery-drill proof.

Next work

Recommended first issue: #56, the read-only doctor repair. Its reproduction and acceptance criteria are in the issue; use invented scratch installations, not the preview database.

Before extending retention/disposition, address #52 (packet pin timeline verification) and #51 (enrollment-event schema shape). Coordinate concurrent-write fixes in #27 with the paths the new work touches.

All other audit follow-ups are tracked:

• Draft workspace: keep the losing writer's text visible after a stale-save reload #34: stale-save recovery; Trainees cannot view their own task signoff history in the web interface #49: trainee signoff UI.
• Stream installation exports instead of assembling the archive in memory #47: streaming exports; web(deps): resolve SvelteKit cookie audit advisory #54: existing dependency advisory.
• New refactor(rust): separate program and draft workspace ownership #58: Rust program/draft workspace decomposition.
• New refactor(web): split large workflow pages and domain API contracts #59: large web workflow/API decomposition.

#58/#59 specify proposed owners, preserved contracts, and regression proof; they are scoped maintenance to coordinate with work in those owners, not approved broad rewrites. The audit now links both issues.

Milestone 5 slices 1–2 remain complete. Slice 3 (retention policy, holds, lawful disposition, tombstones, explicit authority) is the next feature under #44; this audit did not implement it.

Minimum context

Read AGENTS.md, then the selected issue and CONTRIBUTING.md. Use docs/development.md for task-to-source/ADR/test routing; docs/roadmap.md and docs/audits/2026-09-05.md provide continuation context. Do not preload every ADR. Start any implementation on a new issue-linked codex/ branch and use a PR; never push changes directly to main.

The live preview at https://consolebook-preview.conary.io is unchanged and runs a separately installed release binary. Repository merges do not deploy it. Follow docs/preview.md for host work; no deployment, migration, credentials, or production data were changed during this task.