epic(os): Agent OS roadmap 2026-06 — Stage 0 stabilize + Stage 1 friction telemetry

[ArchonVII]

Summary

Tracking epic for the approved Agent OS roadmap (owner approved 2026-06-12). Roadmap doc in-repo at docs/plans/2026-06-12-os-roadmap.md; single active-lane map at docs/CURRENT_WORK.md.

Organizing insight: the visual workflow graph is a rendering of the OS, not the OS — manifests first (Stage 2), RPC second (#212 lane 3), graph tab third (Stage 3). Stages 0–1 filed; Stages 2–4 are filed after Stage 1 friction data ranks priorities.

HARD RULE (owner, 2026-06-12): Stage 1 telemetry does not start at #233/#234. It starts when #238's post-apply verification passes in the existing fleet and the timestamp is recorded.

Capability ladder

Stage	The OS becomes aware of	Status
0 — Stabilize & Decide	its own current state	COMPLETE (all 7 lanes merged)
1 — Friction telemetry	its own friction	source merged; #233/#234 dispatchable; #238 starts the clock
2 — Process layer	its own shape (manifests)	not yet filed
3 — See it	showing itself (process-graph tab, rides #212 lanes 3–5)	not yet filed
4 — Touch it	being steered (edit-in-place + policy registry)	not yet filed

Dispatch order (owner-confirmed 2026-06-12)

1. chore(snapshots): refresh provider snapshots once Stage 0 repo-template lanes merge (OS Stage 0) #232 — snapshot refresh DONE (PR chore(snapshots): refresh provider snapshots #237)
2. feat(friction): collect .claude/friction.md ledgers into events and maintenance signals (OS Stage 1) #233 + feat(registry): friction-ledger feature entry + snapshot wiring (OS Stage 1) #234 — DISPATCH NOW, parallel or same batch (feat(friction): collect .claude/friction.md ledgers into events and maintenance signals (OS Stage 1) #233: missing ledger reads as "no ledger", never "no friction"; feat(registry): friction-ledger feature entry + snapshot wiring (OS Stage 1) #234: new-repo coverage ONLY)
3. feat(distribution): owner-gated friction-ledger rollout to existing OS repos — starts the Stage 1 telemetry clock #238 — owner-gated fleet distribution pass → records the telemetry-window start timestamp

Stage 0 lanes — COMPLETE 2026-06-12

• fix(anomaly): align anomaly ledger path and install the anomaly-triage caller (OS Stage 0) repo-template#75 — anomaly path + triage caller (PR fix(anomaly): install anomaly triage caller repo-template#80)
• feat(docs): wire the doc-orphan-detector cron backstop caller (OS Stage 0) repo-template#76 — doc-orphan-detector backstop (PR feat(docs): wire doc orphan detector repo-template#79)
• fix(hooks): respect checkout_default_branch in the owner-lane gate; scrub dangling docs/phase2 refs (OS Stage 0) repo-template#77 — hooks default-branch + authority refs (PR fix(hooks): honor default branch in owner-lane gate repo-template#81)
• Add local close-scan and CI guard commands repo-template#28 — close-scan local guard (PR feat(close-scan): add local delivery guard repo-template#82)
• docs(status): refresh ecosystem-status, add CURRENT_WORK.md convention, land the OS roadmap doc (OS Stage 0) #230 — CURRENT_WORK.md + status refresh + roadmap doc (PR docs(status): add current work map and os roadmap #236)
• feat(ecosystem-map): add jma-skill-review to the ecosystem map and overview (OS Stage 0) #231 — skill-router in ecosystem map (PR feat(ecosystem-map): expose skill router in overview #235)
• chore(snapshots): refresh provider snapshots once Stage 0 repo-template lanes merge (OS Stage 0) #232 — snapshot refresh (PR chore(snapshots): refresh provider snapshots #237; gw snapshot at v1@ae00ba3, repo-template at 7853175, orgDefaults at 3187457)

Stage 0/1 follow-ups (from PR #237 review-bot findings + lane report)

• fix(close-scan): include deleted files in scope derivation; bash -n every hook script repo-template#84 — close-scan: deletions in scope derivation + bash -n every hook script
• chore(integrator): cover new template baseline files in snapshots and audit plan; reconcile check-map gate name #239 — snapshot completeness (.gitignore/.claude/friction.md), auditPlan covers anomaly-triage.yml, check-map ci-success reconcile

Stage 1 lanes

• feat(friction): .claude/friction.md append-log ledger contract + AGENTS.md instruction (OS Stage 1) repo-template#78 — friction ledger contract (PR feat(friction): add append-log ledger contract repo-template#83, merged by owner)
• feat(friction): collect .claude/friction.md ledgers into events and maintenance signals (OS Stage 1) #233 — friction collector — DISPATCHABLE NOW
• feat(registry): friction-ledger feature entry + snapshot wiring (OS Stage 1) #234 — registry feature foundation.frictionLedger — DISPATCHABLE NOW
• feat(distribution): owner-gated friction-ledger rollout to existing OS repos — starts the Stage 1 telemetry clock #238 — owner-gated distribution to existing OS repos — starts the two-week telemetry clock (blocked by feat(friction): collect .claude/friction.md ledgers into events and maintenance signals (OS Stage 1) #233/feat(registry): friction-ledger feature entry + snapshot wiring (OS Stage 1) #234)
• Ritual (no code): weekly page-gm digest over the friction aggregate

Decisions executed 2026-06-12

• docs(specs): document policy charters, vision layer, doc-health spec #224 document-policy spec MERGED → epic Epic: document policy — charters, vision layer, doc-health #223 lanes unblocked
• docs(readme): refresh workflow provider guide github-workflows#66 README refresh rebased + MERGED
• chore(deps): bump the actions group across 1 directory with 13 updates github-workflows#68 Dependabot group HELD (decision comment on PR)
• @v1 RETAGGED: af0ac6e → ae00ba3 (annotated evidence tag; decoupled from gw#68)
• docs(profile): refresh public profile .github#29 profile refresh: copy tweaks applied, MERGED
• jma-skill-review#183/chore(snapshot): propagate safe agent prune behavior #184 already merged; feat(prlane): add rollback verification cleanup #180 remains (CONFLICTING — its Codex lane owns the rebase)

Operational notes

• repo-template lane PRs serialize on docs/repo-update-log.md append-conflicts: merge one, sync main into the next (keep-both), repeat.
• archon-setup main has required_conversation_resolution enabled: unresolved review-bot threads produce mergeStateStatus: BLOCKED even with green checks and zero required reviews — check gh api repos/.../branches/main/protection (classic), not just rulesets. Disposition pattern: route findings to issues, reply + resolve threads, merge.

Related

#212 (ecosystem registry + dashboard), #223 (document policy — unblocked), #154 (e2e ecosystem), #198 (silent failure/success search).