Context
Narrow authoring leaf of #14475 (v13.1 release cut), split per close-target discipline: the notes-document PR must not Resolves the cut ticket while its prepare-validation, operator publish-handoff, and #14327-notify ACs remain open ticket-side. This leaf is fully delivered by the document PR; #14475 stays the coordination anchor.
Live latest-open sweep: checked latest 8 open issues at 2026-07-02T14:42:00Z (full latest-20 at 14:27:19Z) — no equivalent authoring ticket. A2A: no competing claim; the parent lane is mine (self-assigned, lane-claim broadcast d8e3fc3d).
The Problem / The Fix
publish.mjs:83 requires a hand-authored resources/content/release-notes/v13.1.0.md at the flat directory root before the cut can execute (it parses title+body for gh release create; the ReleaseNotesSyncer then re-mirrors the published release into chunk-N/ with sync frontmatter — the flat file is the authoring surface, the chunks are mirrors). Author the document to the narrative bar: TL;DR → the window stat (663 PRs / 748 issues / 8 epics in 20 days) → hero (the four-layer immune system + #14046 single-shot + #14165 24-cycle soak gates) → War Story (#13999: ~60% silent vector loss, green health checks, backup-failure discovery → detect/diagnose/heal/prevent) → window highlights → continuity. Every external claim sourced to tickets/commits verified this session.
Acceptance Criteria
Out of Scope
Everything else on #14475: scope re-enumeration at cut boundary, prepare.mjs validation, the operator publish handoff, #14327 notification.
Related
Related: #14475 (parent cut ticket), #14039 (the release epic), #13999 (War-Story source)
Origin Session ID: 8cf234b7-e698-47ca-99e2-bf865196b6aa
Retrieval Hint: v13.1.0 release notes document narrative flat-root publish.mjs authoring surface
Context
Narrow authoring leaf of #14475 (v13.1 release cut), split per close-target discipline: the notes-document PR must not
Resolvesthe cut ticket while its prepare-validation, operator publish-handoff, and #14327-notify ACs remain open ticket-side. This leaf is fully delivered by the document PR; #14475 stays the coordination anchor.Live latest-open sweep: checked latest 8 open issues at 2026-07-02T14:42:00Z (full latest-20 at 14:27:19Z) — no equivalent authoring ticket. A2A: no competing claim; the parent lane is mine (self-assigned, lane-claim broadcast d8e3fc3d).
The Problem / The Fix
publish.mjs:83requires a hand-authoredresources/content/release-notes/v13.1.0.mdat the flat directory root before the cut can execute (it parses title+body forgh release create; the ReleaseNotesSyncer then re-mirrors the published release intochunk-N/with sync frontmatter — the flat file is the authoring surface, the chunks are mirrors). Author the document to the narrative bar: TL;DR → the window stat (663 PRs / 748 issues / 8 epics in 20 days) → hero (the four-layer immune system + #14046 single-shot + #14165 24-cycle soak gates) → War Story (#13999: ~60% silent vector loss, green health checks, backup-failure discovery → detect/diagnose/heal/prevent) → window highlights → continuity. Every external claim sourced to tickets/commits verified this session.Acceptance Criteria
resources/content/release-notes/v13.1.0.mdmerged on dev at the flat root (not chunk-N)--no-verifyper publish-pipeline precedent: publish.mjs's own internal commit + v13.0.0 flat-file PR lineage #12697/#13276) documented in the PR's DeltasOut of Scope
Everything else on #14475: scope re-enumeration at cut boundary,
prepare.mjsvalidation, the operator publish handoff, #14327 notification.Related
Related: #14475 (parent cut ticket), #14039 (the release epic), #13999 (War-Story source)
Origin Session ID: 8cf234b7-e698-47ca-99e2-bf865196b6aa
Retrieval Hint:
v13.1.0 release notes document narrative flat-root publish.mjs authoring surface