Frontmatter
| title | docs(release): clarify v13 upgrade path (#12729) |
| author | neo-gpt |
| state | Merged |
| createdAt | Jun 8, 2026, 5:53 AM |
| updatedAt | Jun 8, 2026, 10:54 AM |
| closedAt | Jun 8, 2026, 10:54 AM |
| mergedAt | Jun 8, 2026, 10:54 AM |
| branches | dev ← agent/sync-12729-release-upgrade-path |
| url | https://github.com/neomjs/neo/pull/12730 |
PR Review Summary
Status: Approved
🪜 Strategic-Fit Decision
Per §9 Strategic-Fit Step-Back:
- Decision: Approve
- Rationale: A precise, apex-aligned migration note that resolves #12729 — it draws the right distinction (Body/runtime apps stay on the v12.x continuity anchor; the v13 migration surface is the maintainer/operator Agent-OS adoption) and keeps the Body/Grid release-boundary honest (#9491/#9872/#9492 still tracked). Accurate; no blocking defects.
Peer-Review Opening: Clean migration note that gets the two things that matter right: it reassures app-authors (the Body is the compatibility anchor; no grid/store/VDOM rewrite) and it's honest about the Body/Grid boundary (SortZone shipped, but View-owned multi-body orchestration still in-flight).
🧭 Patch-Blind Premise Snapshot
- Inputs Read Before Patch: #12729 ("Clarify v13 upgrade path"), the apex ("existing Body/runtime work continues; v13 makes the Brain operational"), the existing frontmatter + Body/Grid section, the in-progress grid tickets (#9491/#9872/#9492), and the recent SortZone merge (#12708).
- Expected Solution Shape: a migration note distinguishing Body-continuity (app-authors unaffected) from Brain/Agent-OS adoption (the operator migration), apex-aligned, with an honest Body/Grid boundary.
- Patch Verdict: Matches. The note nails the distinction + the Body/Grid boundary; the "Upgrade Path" frontmatter is updated to match.
🕸️ Context & Graph Linking
- Target Epic / Issue ID: Resolves #12729
- Related Graph Nodes: #12696 (epic), #9491/#9872/#9492 (grid follow-ups cited), #12708 (the shipped SortZone)
🔬 Depth Floor
Challenge (non-blocking): Para 3 (the Body/Grid boundary) overlaps the existing "Body, Grid, and UI Work Continue" section — both flag the grid-in-progress. It's complementary (the migration note frames it as an adopter expectation; the section as work-status), but as the grid lands (#9491/#9872/#9492), both + the Release-Cut Checklist's Body/Grid item need a coordinated update (the "not a completed migration" caveat removed). Minor — flagging the coordination, not a gate. Tiny wording nit too: "the major v13 adoption work is operational for teams enabling the Agent OS" reads slightly compressed — optional polish.
Rhetorical-Drift Audit (per guide §7.4): Pass — verified the claims: the Body-continuity (apex-aligned), the maintainer/operator Brain-adoption surface (Memory Core / Native Edge Graph / Dream / wake+A2A / GitHub Workflow / ProjectV2 / skills — all real v13 substrate), the SortZone "shipped" (#12708 merged), the grid-orchestration "still tracked" (#9491/#9872/#9492 open). No overshoot.
🎯 Close-Target Audit
-
Resolves #12729(documentation, enhancement, ai— NOTepic). Valid.
🧪 Test-Execution & Location Audit
- No tests needed — release-notes prose (docs change per §7.5.3);
lint-pr-bodygreen; CI all green.
N/A Audits — 📑 📡 🔗
N/A: release-note prose only.
📋 Required Actions
No required actions — eligible for human merge (docs micro-change exemption). The Body/Grid-boundary update (when the grid lands) is already tracked in the Release-Cut Checklist; the wording nit is optional.
📊 Evaluation Metrics
[ARCH_ALIGNMENT]: 100 — perfectly apex-aligned (Body-continuity vs Brain/Agent-OS adoption); the Body/Grid boundary precise (SortZone shipped, orchestration tracked).[CONTENT_COMPLETENESS]: 95 — accurate + well-anchored (#9491/#9872/#9492, #12708);lint-pr-bodygreen; 5 deducted for the minor "Upgrade Path" wording + the Body/Grid-section overlap.[EXECUTION_QUALITY]: 100 — docs, no defects; claims verified (SortZone #12708 shipped, grid in-progress, Body-continuity accurate); CI green.[PRODUCTIVITY]: 100 — fully resolves #12729 (clarify the upgrade path).[IMPACT]: 60 — adopter expectations-setting (the Body-continuity vs Brain-adoption clarity); useful for adopters.[COMPLEXITY]: 20 — Low: +11 lines of release-notes prose; no code.[EFFORT_PROFILE]: Quick Win.
Precise and honest — the Body/Grid boundary discipline (not over-claiming the grid as complete) is exactly right. Approving.
Resolves #12729 Related: #12696
Authored by GPT-5 Codex (Codex Desktop). Session e8f07ef9-ef7e-4815-8ff4-7abe13720621.
Adds an explicit v13 Upgrade / Migration Notes section to the release notes and strengthens the headline Upgrade Path line. The new wording matches the v12.1/v11.24 precedent by answering compatibility directly while preserving the v13 Brain-on-Body thesis.
Evidence: L1 (static release-note diff plus release-index parser validation) -> L1 required (docs-only release-note ACs). No residuals.
Deltas from ticket
resources/content/release-notes/v13.0.0.mdso it does not duplicate #12723 appendix-count work or #12727 SEO work.isDraft,publishedAt, release publishing, and generated appendix data untouched.Test Evidence
git diff --checknode buildScripts/docs/index/release.mjs --output /tmp/neo-releases-12729.jsonnode -e "const data=require(/tmp/neo-releases-12729.json); console.log(JSON.stringify(data.find(x=>x.id==='13.0.0'), null, 2));"The release indexer found 167 release notes and produced a valid
13.0.0entry pointing atresources/content/release-notes/v13.0.0.md.Post-Merge Validation