docs: reconcile north-star map with shipped reality

[marcusrbrown]

What

Reconciles the north-star architecture map (docs/brainstorms/2026-06-15-...) with verified live state as of 2026-07-10. A full grounding pass — control-plane state plus a cross-repo verification sweep (fro-bot/agent, fro-bot/dashboard, marcusrbrown/infra) — found the map stale in one consistent direction: every capability is further along than the 2026-06-21 rebaseline claimed.

Adds a Reconciliation (2026-07-10) note and updates the Tier 0/1/2 capability entries:

• S1 (web control surface) — shipped in source, fro-bot/agent#907 closed, contract v1.6.0; deploy-verification the one open item.
• S2 (operator web auth) — live in production (OAuth/PKCE/session/CSRF/origin binding); logout bug fro-bot/dashboard#156 fixed.
• R1 (dashboard PWA) — Phase 1 deployed live; interactive surface substantially built, flag-gated; mock client retired.
• R2 (push notifications) — was "not started"; now in-progress (transport shipped end-to-end, inline notification actions remain).
• R3 (web wiki) — confirmed still not started.
• A2 — bounded-PR correction machinery graduated (plan-consistency active).
• A3 — shipped and proven in production.
• C4 / O8 — two control-plane loops not in the original map, now added.

Strategic read: the Tier-2 control-plane autonomy arc is essentially complete; the genuinely-open threads now live in the other repos and the Tier-3 frontier.

Verification

Every factual claim grounded against live GitHub state (releases, issue/PR state, source, live dashboard.fro.bot auth redirect) or this repo's own code. pnpm lint clean. Docs-only; no behavior change.

[fro-bot]

The map was drifting from reality in one direction only — everything shipped ahead of what the 2026-06-21 rebaseline admitted. This pass drags it back into alignment cleanly, and the claims hold under grounding.

Verdict: PASS

Blocking issues

None.

Non-blocking concerns

• Cross-referenced facts verified live — every external anchor checks out: fro-bot/agent#907 CLOSED, fro-bot/dashboard#156 CLOSED (logout fix), fro-bot/.github#3512 OPEN (deploy-verification), and dashboard.fro.bot returns 302 → /operator/auth/github/start, corroborating the S2 "OAuth/PKCE, not shared-secret HMAC, live in production" claim. Grounded, not aspirational.
• New entries lack the effort/risk signal the section defines (line ~152: "effort/risk signal (L/M/H)"). The C4 and O8 additions carry _Owner:_ but no Effort/risk: — a minor schema drift from every sibling entry. Since both are marked SHIPPED, effort/risk is arguably moot, but for consistency either add the field or note it's inapplicable for already-landed loops. Non-blocking; docs-only.
• A2 status now split across two sections — the Rebaseline note (line 57) still says "shipped fully disarmed; graduation pending accepted-outcome signal," while the new Reconciliation (line ~85) and the A2 entry say it graduated with plan-consistency active. That's the intended supersession pattern (dated notes preserving history), and the Reconciliation header makes the direction explicit, so it reads correctly — flagging only so a future reader doesn't mistake the older note for current truth.

Missing tests

None — docs-only change to a brainstorm/north-star map. No behavior, no code path, no CI surface. Tests are not applicable; the correctness bar here is factual accuracy against live state, which is met.

Risk assessment: LOW

Single-file Markdown edit (+66/-12) to a non-authoritative planning doc. No workflow, dependency, permission, or executable surface touched. No injection, secret, or automation-safety exposure. Worst case of an error is a stale doc line, and the verifiable anchors all resolved correctly. Ship it.

---

Run Summary

Field	Value
Event	pull_request
Repository	fro-bot/.github
Run ID	29122694355
Cache	hit
Session	ses_0b235086affeMxyNzJXHZBwOPg

[fro-bot]

Re-review after the main merge (e0e2a17). The contributed diff is still one file, still +67/-12, still the clean reconciliation I approved on 10a17d3 — nothing in the north-star edits regressed. But the merge dragged a fresh contradiction into the branch, and this doc's entire job is to not contradict reality.

Verdict: CONDITIONAL

Blocking issues

• R3 is now stale within your own branch. docs/brainstorms/2026-06-15-fro-bot-personal-agent-north-star-requirements.md:88 (and the strategic read at :104) says R3 web wiki is "confirmed still not started — the only capability matching its original status." That was true at your 13:48 grounding pass. But #3677 ("publish knowledge wiki as a Quartz digital garden") landed on main at 19:40, and your 20:00 merge pulled it into this branch. The branch you're asking to merge now contains quartz-site/, .github/workflows/publish-wiki.yaml, and a wiki runbook — R3's read-only path shipped. A reconciliation PR that ships a doc claiming R3 hasn't started, in a tree that visibly contains R3, reintroduces exactly the drift this PR exists to kill. Update the R3 entry (line 88 and the line ~178 Tier-1 Status:) to reflect that the read-only web wiki shipped (#3677), with the editable/data-branch write path as the remaining open thread. The strategic-read line at :104 that lists "R3 web wiki" among genuinely-open frontier threads needs the same correction.

Non-blocking concerns

• Prior findings still stand, still non-blocking: C4/O8 lack the Effort/risk: field every sibling entry carries (moot for SHIPPED loops, but inconsistent); and the 2026-06-21 Rebaseline A2 note (line ~57) is superseded by the Reconciliation — correct supersession pattern, just don't let a future reader mistake the older line for current truth.
• Merge hygiene: e0e2a17 is a plain main catch-up, no conflicts, and touches nothing in the PR's effective diff. Fine.

Missing tests

None — docs-only. The correctness bar is factual accuracy against live state; that bar is what the R3 line now fails post-merge.

Risk assessment: LOW

Single-file Markdown edit to a non-authoritative planning doc. No workflow, dependency, permission, or executable surface in the contributed diff. The only defect is an internal factual contradiction — worst case is a reader trusting a stale "not started" line while the wiki publishes beside it. One-line fix, then this goes back to the clean PASS it was.

---

Run Summary

Field	Value
Event	pull_request
Repository	fro-bot/.github
Run ID	29137270671
Cache	hit
Session	ses_0b235086affeMxyNzJXHZBwOPg

[fro-bot]

The R3 contradiction is closed. 74761dc rewrites all three spots I flagged — the Reconciliation entry (:88), the strategic-read line (:104), and the Tier-1 Status: (:181) — and the new claims hold under grounding, not just internally. The doc and the tree it ships in now tell the same story.

Verdict: PASS

Blocking issues

None. The prior blocker is resolved: R3 now reads "read-only half SHIPPED, editable data-branch path open" instead of "not started." Verified live —

• fro.bot/.github returns 200: the Quartz garden is actually serving.
• #3677 seeded it; #3682 pointed baseUrl at the fro.bot custom domain; #3684 migrated to Quartz v5 with the pinned plugin lockfile. The doc's "Quartz v5, fail-closed plugin-lockfile gate, emergency unpublish" line maps cleanly onto shipped commits, not aspiration.

The split framing is also the correct reconciliation, not a hand-wave: read-only shipped, editable write-back through the data-branch authority model is the genuinely-open half. That's the honest seam.

Non-blocking concerns

• C4/O8 still lack the Effort/risk: field every sibling entry carries (line ~152 defines the L/M/H convention). Moot for SHIPPED loops, cosmetic schema drift. Not worth another round.
• A2 supersession — the 2026-06-21 Rebaseline note (line ~57) still reads "shipped disarmed," superseded by the Reconciliation's GRADUATED. Correct dated-supersession pattern; flagged only so no future reader mistakes the older line for current truth.

Missing tests

None — docs-only. The bar is factual accuracy against live state, and every anchor (#907, #156, #3512, dashboard.fro.bot 302, fro.bot/.github 200, #3677/#3682/#3684) resolves.

Risk assessment: LOW

Single-file Markdown edit (+72/-12) to a non-authoritative planning doc. No workflow, dependency, permission, or executable surface in the contributed diff. The one defect that mattered — an internal contradiction against the branch's own tree — is gone. Ship it.

---

Run Summary

Field	Value
Event	pull_request
Repository	fro-bot/.github
Run ID	29166528769
Cache	hit
Session	ses_0b235086affeMxyNzJXHZBwOPg