Reconcile roadmap and release docs with current main

[Joncallim]

Part of epic #61 (Make live-state claims evidence-backed). One slice per PR.

Goal

Update repository roadmap/testing/product docs so completed August work is no longer listed as future work, and the next epics reflect current main (the filed epic sequence #61-#70) rather than older June Notion snapshots.

Scope

• ROADMAP.md (or equivalent): mark shipped epics (Add parser-level provider fixtures for expanded host collectors #31-Responsive and accessibility coverage pass #35 era: runtime providers, ui-navigation, hardening) as done; point next work at the filed epic issues Epic: Make live-state claims evidence-backed #61-Epic: Add observed change history and bounded operational telemetry #70 with their documented sequence.
• Testing/product docs: correct any "planned"/"future" language for features already shipped and verified on main.
• Keep changes doc-only and accurate to live repo state (main @ head, verify claims against the code).

Acceptance criteria

• Roadmap/testing docs describe the actual current implementation; no shipped feature listed as future work.
• Epic sequence Epic: Make live-state claims evidence-backed #61-Epic: Add observed change history and bounded operational telemetry #70 visible to a new contributor; no contradiction with AGENTS.md.
• npm run check green if docs touch code-adjacent files (otherwise doc-only PR review).

Non-goals

• Rewriting AGENTS.md; Notion edits (Notion stays planning-side; this slice is repo docs only).

Validation

Doc build/links if applicable; manual review of accuracy against main.

Closure evidence

## Resolution Evidence comment (What changed / Why this resolves / How I checked / Remaining risk). Never self-close.

[Joncallim]

Resolution Evidence

Issue #77 — reconcile roadmap and release docs with current main resolved by PR #88 (merged 9747b71).

• README: start-order framing replaces failure-prediction language; status example mode corrected to the contract's docker|mock values (verified against packages/contracts RuntimeMode); browser Demo Mode distinguished from the Node API mock fallback.
• ROADMAP: active priority updated to the filed Epic: Make live-state claims evidence-backed #61-Epic: Add observed change history and bounded operational telemetry #70 epic sequence; done work (Python/native providers Implement Python provider for runtime map #32/[codex] Implement Python provider for runtime map (#32) #38/[codex] Harden python provider per review (omit raw args, token detection, pipe drain) #39+Implement native-process provider for runtime map #33, detail pages Improve container, network, volume, and image detail pages #34, responsive/a11y Responsive and accessibility coverage pass #35, OpenAPI 5fcadd3) marked complete with merge SHAs.
• ARCHITECTURE: shipped UI work no longer described as deferred; Python/native providers described as implemented; update-status wording no longer references merged Remove synthetic update-available claims from live mode #72 as future.
• TESTING_PLAN: web vitest suite noted; /api/health auth reconciled with the route manifest (auth: "authenticated" — verified apps/api/src/routes.ts); Python/native fixture tests described as shipped; OpenAPI gap closed with drift-check note.
• RELEASE_CHECKLIST: evidence-gated items reconciled against live deploy and recorded runs while genuinely unproven gates stay open (smoke-deploy.sh as a script, external daemon-port confirmation, full Authentik route matrix); later work linked to epics Epic: Certify v0.1 private alpha and establish release supply-chain baseline #63/Epic: Decompose backend monoliths into reviewable security and provider boundaries #64/Epic: Establish one canonical contract, route and schema authority #65.

Docs-only change; no deployment required. Recommend closure.

[Joncallim]

Resolution Evidence

• What changed: Reconciled docs/planning/ROADMAP.md and docs/README.md with current main: shipped Python/native-process providers, route/versioning work, UI work, Epic: Make live-state claims evidence-backed #61 live-truth progress, Epic: Isolate Docker authority and define host-inspection profiles #62 deployment, and the real Epic: Certify v0.1 private alpha and establish release supply-chain baseline #63 release gap.
• Why this resolves the issue: A new contributor now sees the actual implementation and filed epic sequence rather than June-era planned work.
• How I checked it: Reviewed the live source modules/routes and open issue states; PR docs: reconcile roadmap with shipped work #103 passed Rust, TypeScript, Docker-image, Playwright-smoke, production-image, and security CI checks.
• Remaining risk or follow-up: Epic: Certify v0.1 private alpha and establish release supply-chain baseline #63 intentionally remains open for clean-host and host-reboot recovery evidence; later epics remain listed as future work.

Recommendation: This issue appears resolved and can be closed by a maintainer.