docs(release): v13.1 notes cut-prep — banner out, TD diagrams, stamped counts (#14555) (#14556)

* docs(release): v13.1 notes cut-prep — banner out, TD diagrams, stamped counts (#14555)

* docs(release): stat carries live-GitHub counts for the true window — v13.0 cut was 2026-06-12 (#14555)

Author: neo-opus-vega

resources/content/release-notes/v13.1.0.md

@@ -4,8 +4,6 @@
 **Stability:** Stable
 **Upgrade Path:** Body/runtime applications continue on the v12.x/v13 continuity path. v13.1's headline is the Agent OS immune system; the window's full breadth spans engine, portal, and tooling work well beyond it.
 
-> **Status: iteration 2 of N — still a deliberately-early draft.** These notes grow through mining-driven iterations (epic #14483) until the cut; chapters, scope, and designations are living. Do not read as final.
-
 > **TL;DR:** v13 turned Neo's solo-agent operating layer into a cross-family engineering institution. v13.1 answers the question every autonomous system eventually faces: **what happens when the institution's own memory silently corrupts and there is no human at the keyboard?** The answer shipped: the Agent OS now autonomously **detects, diagnoses, and heals** its own data-integrity failures — built for operator-less cloud environments, active locally too; no operator, no pager, no "escalate to a human" terminal. The concept was proven the hard way: against a real incident that had silently destroyed ~60% of the Memory Core's vectors while every health check reported green.
 
 ---
@@ -14,7 +12,7 @@
 
 **The one line:** the Agent OS grew an immune system — and `escalate-to-a-human` was deleted from its vocabulary, because in a cloud deployment there is no human to escalate to. Fittingly, the incident that proved the need happened in the LOCAL deployment: self-healing is cloud-motivated, not cloud-limited.
 
-**The stat:** current draft scope since v13.0.0 — **roughly 700 merged PRs, roughly 780 closed issues, 8 epics closed**, produced and reviewed by the cross-family swarm v13 introduced. And the ticket record trails the shipped reality: a substantial share of the window's work is still being filed retroactively, so this stays intentionally rounded while the cut remains open.
+**The stat:** the v13.1 window — everything resolved since the v13.0 release cut of 2026-06-12 — counts **717 merged PRs, 816 closed issues, 9 epics closed** (live GitHub search, 2026-07-03; the queries are one-liners: `is:pr is:merged merged:>=2026-06-12`, `is:issue closed:>=2026-06-12`, `+label:epic`), produced and reviewed by the cross-family swarm v13 introduced. And the ticket record trails the shipped reality: a substantial share of the window's work was filed retroactively, so treat the count as the tracker's floor, not the window's ceiling.
 
 **The release gate (proven, not promised):** a corruption injected in test is auto-detected → classified → **healed end-to-end with no human in the loop**, twice over:
 
@@ -45,7 +43,7 @@ Every layer of v13.1 exists because of one real failure.
 The four layers are one loop, and it exists to catch what the old container-scoped watch could not — a green health check sitting on top of a gutted store:
 
 ```mermaid
-flowchart LR
+flowchart TD
     Green["Container watch, ADR 0025/0026<br/>liveness, resources, config: all green"] -. "healthy while ~60% data-gutted, #13999" .-> Blind["no data-integrity signal<br/>a stopped heart is visible, internal bleeding is not"]
     Blind --> Detect["Detect<br/>coverage drift, monotonicity, canaries<br/>#14026, #14024"]
     Detect --> Diagnose["Diagnose<br/>WAL-stall vs index-desync vs wipe<br/>#14043, #14027"]
@@ -83,7 +81,7 @@ v13.1 turned that into a dataset. The #14454 route-attribution leaf, merged thro
 The whole route, captured in that single synthesis run:
 
 ```mermaid
-flowchart LR
+flowchart TD
     Cand["semantic candidate"] --> G1["open / state gate"]
     G1 --> G2["type gate"]
     G2 --> G3["label / actionability gate"]
@@ -114,20 +112,20 @@ The apex proof is #14313 / PR #14370, the new "What Is Neo?" front door. Session
 
 ## 🧬 Other shipped slices in the window
 
-The same draft window carried several additional slices whose conclusions continue into the next release:
+The same window carried several additional slices whose conclusions continue into the next release:
 
 - **Observability:** the durable heal-event ledger and queryable immune-status surface (#14163) — the immune system writes its own audit trail in addition to healing, never instead of it.
 - **Backpressure:** the throttle-shed actuation primitive (#14284) gave the healing layer its load-shedding valve; Chroma PID adoption now rejects process-alive-but-service-dead states (#14297).
 - **Docs and Agent OS guide work:** `docs(agentos)` accounts for 45 merged PRs in the cut-window scope report, with #14310 carrying the ongoing comprehension-first learning experience.
 - **Golden Path v2 consumers:** #14472 is open by design; its leaves are now executable against measurements, not impressions.
 
-**Changelog shape of the window:** `feat(ai)` 187 · `fix(ai)` 142 · `docs(agentos)` 45 · `fix(memory-core)` 24 · `feat(agentos)` 20 — the full grouped appendix (roughly 700 PRs, roughly 780 issues, by author, scope, label, and epic) ships as the release-appendix artifact generated by `buildScripts/release/analyzeClosedSinceRelease.mjs` at the cut boundary.
+**Changelog shape of the window:** `feat(ai)` 187 · `fix(ai)` 143 · `docs(agentos)` 46 · `fix(memory-core)` 24 · `feat(agentos)` 21 (`analyzeClosedSinceRelease.mjs` over the active mirror, 2026-07-03 — the mirror trails live GitHub by ~15 PRs at stamp time, which is why the headline uses the live queries) — the full grouped appendix (by author, scope, label, and epic) ships as the release-appendix artifact the same analyzer regenerates at the cut boundary.
 
 ---
 
 ## 🧭 Continuity
 
-- **Body/runtime:** the window carries engine, portal, and tooling work alongside the Agent OS arc; the appendix enumerates the ticketed share, and later iterations narrate the rest.
+- **Body/runtime:** the window carries engine, portal, and tooling work alongside the Agent OS arc; the appendix enumerates the ticketed share, and the v14 notes pick up the narration.
 - **Agent OS deployments:** the immune system is on by default in cloud topology; ADR 0025/0026/0027 describe the detect/act/jurisdiction model, including the operator-less design premise.
 - **Next:** v13.2 planning opens post-cut — the harness PoC (Epic #13012) returns to scope per the #14038 re-scope, alongside the Fleet-Manager cornerstone (#13015) and the immune system's next jurisdiction.