Docs: refresh pre-merge roadmap

[mchwang]

Summary

• advance the architecture snapshot to merged main commit d77eabc
• record the completed foreign- and owned-conflict engine plus production sandbox adapter from PRs 138, 140 and 144
• identify the remaining issue 22 ownership: F5 admission/refresh/head-bound checks and F6 push/required-check/guarded-merge handoff, with rewritten heads pushed before review state is recomputed and head-bound checks run, followed by fresh required GitHub checks

Initial validation (historical)\n\nInitial validated head: b9939fa50ca826ed504e23451391f6e903b7ba44\nInitial baseline: cb69e50d6f7d92f6e1d2e897c45db3f8152bb36c

• npm run typecheck — passed
• git diff --check — passed
• documentation-only change; product, browser, full-suite, and real-Docker tests were not run locally

Review rounds

Self-review 1

• reviewer: author
• exact base/head: cb69e50d6f7d92f6e1d2e897c45db3f8152bb36c / 2ed2f375e10b7d3ed36a7ed7ad7bccdc82a9dee8
• findings: none
• changed or declined: none
• evidence: complete documentation diff reread; typecheck and diff check passed

Independent-agent review 1

• exact base/head: cb69e50d6f7d92f6e1d2e897c45db3f8152bb36c / 2ed2f375e10b7d3ed36a7ed7ad7bccdc82a9dee8
• finding: the next-work sequence omitted the still-required owned-commit conflict resolver
• changed: added owned-conflict resolution to the summary, not-built inventory, roadmap, and known limits
• declined: no other hypotheses; F3/F4 delivery and F5/F6 sequencing were otherwise accurate
• evidence: the detailed design requires the owned resolver, the implementation document says it is absent, and current rebase code refuses owned conflicts

Independent-agent review 2

• exact base/head: cb69e50d6f7d92f6e1d2e897c45db3f8152bb36c / 52e2235e567d88979e22b4bd7069007315742af7
• finding: owned-conflict resolution was incorrectly classified as unfinished F4 even though F4 is the completed foreign-conflict lane
• changed: listed owned-conflict resolution as a separate issue 22 prerequisite before F5
• declined: no other hypotheses; the prior omission was otherwise fully resolved
• evidence: compared the roadmap lane definition, detailed owned-conflict protocol, and current code

Independent-agent review 3 — clean; authorizes Copilot request

• exact base/head: cb69e50d6f7d92f6e1d2e897c45db3f8152bb36c / b9939fa50ca826ed504e23451391f6e903b7ba44
• findings: none
• changed or declined: none
• evidence: complete three-dot diff reread; all milestone, implementation, and next-work claims checked against current code, design, merged PRs, and issue 22

Pre-Copilot request status

• exact base/head: cb69e50d6f7d92f6e1d2e897c45db3f8152bb36c / b9939fa50ca826ed504e23451391f6e903b7ba44
• CI: both test jobs in progress
• mergeability: MERGEABLE; merge state UNSTABLE because CI is pending
• unresolved review threads: 0
• deferred follow-up issues: none beyond existing issue 22
• latest clean independent-agent review: round 3 on this exact base/head pair

Review-lesson classification

• The omitted owned resolver and incorrect F4 label are one-off roadmap synthesis errors now corrected against the authoritative design and current implementation. The existing Review readiness rules already require full-diff rereads and verification of every behavioral claim, so no new repository rule is warranted.
• No findings were declined.

Deferred follow-ups

• Existing issue 22 owns all identified remaining pre-merge work; no new issue is needed.

Copilot review round 1 — clean

• reviewer: copilot-pull-request-reviewer
• exact base/head: cb69e50d6f7d92f6e1d2e897c45db3f8152bb36c / b9939fa50ca826ed504e23451391f6e903b7ba44
• findings: none; approval recommended with 0 open findings
• changed or declined: none
• evidence: review completed on the independently reviewed exact head

Final validation

• validated head: b9939fa50ca826ed504e23451391f6e903b7ba44
• local npm run typecheck — passed against the exact pushed head
• local git diff --check origin/main...HEAD — passed
• CI: 2 of 2 test jobs passed
• mergeability: MERGEABLE; merge state CLEAN
• unresolved review threads: 0
• product, browser, full-suite, and real-Docker tests were not run locally because this is documentation-only

Final review-lesson audit

• Independent round 1 omitted-owned-resolver finding and round 2 F4-taxonomy finding are one-off roadmap synthesis errors covered by existing full-diff and claim-verification rules.
• Independent round 3 and Copilot round 1 were clean on the final exact base/head pair.
• No findings were declined, no new repository rule is needed, and existing issue 22 owns the remaining implementation.

Base integration and status refresh

• current baseline: d77eabc8f0061e29f5b152911241f01f692ca71b after merged PRs 144 and 147
• current reviewed head: 24169775475906d0b519cbfdefd948d332f5e464
• prior exact-pair review and CI evidence is historical and does not authorize this updated head
• changed: integrated current main, recorded owned-conflict support as merged, removed it from remaining work, and advanced F5 to the next issue 22 step

Self-review 2

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 24169775475906d0b519cbfdefd948d332f5e464
• findings: none
• changed or declined: none
• evidence: full current documentation diff reread; main integration inspected; typecheck and diff check passed

Independent-agent review 4 — clean; authorizes Copilot request 2

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 24169775475906d0b519cbfdefd948d332f5e464
• findings: none
• changed or declined: none
• evidence: full three-dot diff, merged conflict implementations, production reachability, F5/F6 sequencing, and preservation of PR 147 checked

Pre-Copilot request status 2

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 24169775475906d0b519cbfdefd948d332f5e464
• CI: both test jobs queued
• mergeability: MERGEABLE; merge state UNSTABLE because CI is pending
• unresolved review threads: 0
• deferred follow-up issues: none beyond existing issue 22
• latest clean independent-agent review: round 4 on this exact base/head pair

Copilot review round 2 — findings

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 24169775475906d0b519cbfdefd948d332f5e464
• findings: the top summary retained the old baseline/scope; the F5/F6 wording implied head-bound commands ran before the rewritten head was pushed
• changed: updated the summary, labeled the initial evidence historical, and made the integrated runtime order explicit
• declined: none
• regression evidence: authoritative design and pre-merge implementation ordering reread; both threads replied to and resolved

Independent-agent review 5 — finding

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / d411c4de921370ea0268578e07d6768189325290
• finding: saying checks were accepted after push still allowed them to run before push
• changed: now explicitly states push, recompute review state, run/accept head-bound commands, then fresh required GitHub checks
• declined: none

Independent-agent review 6 — clean; authorizes Copilot request 3

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 190c813c5fddc6610683be8b05866f7dce44f3e8
• findings: none
• changed or declined: none
• evidence: complete three-dot diff and all changed paragraphs reread; both Copilot findings and the prior incomplete remediation verified resolved

Pre-Copilot request status 3

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 190c813c5fddc6610683be8b05866f7dce44f3e8
• CI: both test jobs in progress
• mergeability: MERGEABLE; merge state UNSTABLE because CI is pending
• unresolved review threads: 0
• deferred follow-up issues: none beyond existing issue 22
• latest clean independent-agent review: round 6 on this exact base/head pair

Review-lesson classification addendum

• The stale-summary finding is covered by the existing exact-head evidence and external-status rules; the body now distinguishes historical evidence from the current pair.
• The push/check-order finding and incomplete first remediation are covered by the existing requirement to verify every behavioral claim against every path that can break it. The final wording is source-checked and unambiguous.
• Both were documentation-specific synthesis errors; no new repository rule or follow-up issue is warranted.

Copilot review round 3 — finding

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 190c813c5fddc6610683be8b05866f7dce44f3e8
• finding: “runs or accepts” could permit stale pre-rebase command evidence instead of requiring every check to rerun
• changed: the architecture now requires rerunning every plan item’s head-bound cmd: checks after push and review-state recomputation
• declined: none
• regression evidence: authoritative design ordering reread; thread replied to and resolved

Independent-agent review 7 — clean; authorizes Copilot request 4

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 6deaee8058fd9b44baa278ef1190a9c941802894
• findings: none
• changed or declined: none
• evidence: complete three-dot diff reread; stale evidence cannot satisfy the documented gate; all prior findings verified resolved

Pre-Copilot request status 4

• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 6deaee8058fd9b44baa278ef1190a9c941802894
• CI: both test jobs in progress
• mergeability: MERGEABLE; merge state UNSTABLE because CI is pending
• unresolved review threads: 0
• deferred follow-up issues: none beyond existing issue 22
• latest clean independent-agent review: round 7 on this exact base/head pair

Review-lesson classification addendum 2

• The stale-command-evidence ambiguity is covered by the existing rule that behavioral claims must be traced through every breaking path and by the head-bound evidence rules. It was a documentation-specific wording defect and now requires exact-head reruns.
• No new repository rule or follow-up issue is warranted.

Copilot review round 4 — clean

• reviewer: copilot-pull-request-reviewer
• exact base/head: d77eabc8f0061e29f5b152911241f01f692ca71b / 6deaee8058fd9b44baa278ef1190a9c941802894
• findings: none; approval recommended with 0 open findings and all earlier findings resolved
• changed or declined: none
• evidence: review completed on the independently reviewed exact head

Final exact-head validation

• validated head: 6deaee8058fd9b44baa278ef1190a9c941802894
• baseline: d77eabc8f0061e29f5b152911241f01f692ca71b
• local npm run typecheck — passed
• local git diff --check origin/main...HEAD — passed
• CI: 2 of 2 test jobs passed
• mergeability: MERGEABLE; merge state CLEAN
• unresolved review threads: 0
• product, browser, full-suite, and real-Docker tests were not run locally because this is documentation-only

Final review-lesson audit for current pair

• all three Copilot findings are classified above and covered by existing exact-head, behavioral-claim, and external-status rules
• independent round 7 and Copilot round 4 are clean on the final exact base/head pair
• no findings were declined, no new repository rule is needed, and existing issue 22 owns the remaining implementation

[Copilot]

🟢 Approval recommended

The documentation accurately reflects the current implementation and remaining roadmap.

0 open findings

What changed in this PR

Refreshes the architecture roadmap to reflect completed rebase infrastructure and clarify remaining pre-merge work.

Changes:

• Advances the documented main snapshot.
• Records completed foreign-conflict handling.
• Clarifies the owned-conflict, F5, and F6 sequence.

File	Description
docs/​architecture.md	Updates pre-merge status, roadmap, and known limitations.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟡 Changes recommended

The F5/F6 sequence conflicts with authoritative documentation, and the PR summary references an outdated baseline.

2 open findings

• Update stale PR summary with final baseline and delivered scope · New
• Correct roadmap ordering of push and head-bound checks · New

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

The roadmap ambiguously permits accepting stale cmd: evidence instead of rerunning every check after rebase.

1 open finding

• Require rerunning every plan check after rebase · New

2 resolved since last review

• Correct roadmap ordering of push and head-bound checks
• Update stale PR summary with final baseline and delivered scope

🧠 Review effort: Balanced

[Copilot]

🟢 Approval recommended

The documentation accurately reflects the current implementation and required pre-merge sequence.

0 open findings

1 resolved since last review

• Require rerunning every plan check after rebase

🧠 Review effort: Balanced