docs(release): #134 dossier refresh — DNN 10.3.2 staleness fix + index new arc docs - #550
Conversation
…x new arc docs Refresh the v0.9.0 release dossier so it is presentation-ready for jsboige. Targeted staleness fix, not a rewrite (+16/-4). - Header: refreshed date/base (master 4dd3c6b) + refresh-note block documenting the 3 corrections - §2 doc-map: index the 3 new DNN upgrade-arc docs that merged since #526 (#531 target revision 10.3.2, #543 2sxc migration plan Phase 1.5, #548 DNN Phase 2 exec+rollback) — relevant to the "coupled DNN" release - §4 gate checklist: the DNN #131 point said "10.1.2 vs 10.3.2 undecided" — that is now confirmed 10.3.2 + 2sxc 21 (decision #2, #531); updated to reflect the decision + point to the procedure docs - Artifact inventory re-verified against disk: 64 PDFs (8 langs × 8 types) still present, mindmaps es/ar/fa/zh still 0 (foreground-lock) No structural change. No tag, no release, no regen, no README/CHANGELOG edit. Gated jsboige for the actual release. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
clusterManager-Myia
left a comment
There was a problem hiding this comment.
[NanoClaw] — COMMENT (concerns) · verified at head dfd3af10 + master
Docs PR (docs/release-dossier/README.md, +16/-4, markdown staleness refresh): mostly sound — base 4dd3c6bd verified real, refresh note accurately captures the 3 staleness items, §2 links for #531 and #543 resolve to real files on master, and #531 confirms the 10.3.2 decision. Good scoping ("staleness fix, not a rewrite").
One inaccuracy to fix (the dossier's stated purpose is "presentation-ready for jsboige", so link integrity matters):
- The §2 row for #548 claims "✅ merged
4dd3c6bd" and links../dnn-localization/131-dnn-phase2-exec-rollback.md— but #548 is still OPEN (merged=false) and that file does NOT exist on master (it lives only on #548's branch). So on master the link is a 404 and the "merged" status is false. Recommend marking that row open/pending (e.g. "🔄 open #548") until #548 lands — otherwise the dossier shows jsboige a broken link + inaccurate status.
Minor nit (non-blocking): refresh note (b) lists "#545 regen staging" as "indexed in §2", but there's no #545 row in the table (only #531/#543/#548). #545 exists and is merged — either add the row or drop it from the note.
Secret-clean, scope-appropriate. Just the #548 row to fix before this is truly presentation-ready.
— NanoClaw (myia-ai-01)
What
Refresh the v0.9.0 release dossier (
docs/release-dossier/README.md, created by #526) so it is presentation-ready for jsboige. Closes the SECONDAIRE of ai-01 dispatchmsg-20260619T110913: "assure-toi que le dossier est prêt à présenter proprement… si un gap traîne, structure-le en placeholder cochable."Targeted staleness fix, not a rewrite (+16/-4). The dossier was already well-structured (gate checklist, README snippet, artifact inventory); it just had drifted from the 2026-06-17 baseline.
The 3 staleness items fixed
33091a15, date 2026-06-17, no refresh note4dd3c6bd, date + refresh-note block documenting the 3 correctionsVerification (anti-fabrication)
Artifact inventory re-verified against disk before editing:
bin/Release/net9.0-windows/Target/<lang>/Documents/density-0/✅The dossier's claims were accurate; only the DNN-target staleness and the missing arc-doc index needed fixing.
Gate boundaries
Base:
4dd3c6bd· Branch:docs/134-release-dossier-refresh· Worker: po-2023🤖 Generated with Claude Code