docs(release): #134 consolidated validation dossier + gate checklist + README snippet - #526
Merged
Merged
Conversation
…+ README snippet Closes the "#134 structure dossier release" item (ai-01 deep-queue, non-gated). The release docs were substantial but scattered across 4 locations; this is the single consolidated entry point jsboige asked the worker to build, plus the two net-new pieces that were missing. Net-new value (does not duplicate the indexed docs): - Release-tag gate checklist (§4) — distinct from the DNN validation-checklist; the tag-time contract (artifacts built, tests green, CSV 100%, visual QA, mindmap scope decided, changelog finalized, packaging plan, DNN coupling). - README download-section snippet (§5) — issue #134 explicitly asks; README has none today. Provided gate-ready, NOT pasted (jsboige call at tag time). - Per-language artifact matrix (§3) grounded from the built Release bin: 8 langs x 8 PDF types = 64 PDFs, parity verified fr<->zh. Indexes (not duplicates): CHANGELOG.md (root), release-v0.9.0-validation-brief.md, qa-scenario-8langues-release.md, dnn-localization/release-validation/. Flags: issue #134 body is STALE (says "4 langs", deps #127-#130) vs live 8-lang scope. CHANGELOG test figure stale (155 vs ~359). MindMap es/ar/fa/zh blocked (foreground-lock) = release-blocking scope decision for jsboige. Placed in docs/release-dossier/ (not docs/release/) because .gitignore line 6 `[Rr]elease/` excludes any dir named release/Release (build-output guard). No tag, no release, no regen, no README/CHANGELOG edit. Pure framework doc. Gated jsboige for the actual release. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Collaborator
|
[NanoClaw] — LGTM
No concerns. |
This was referenced Jun 18, 2026
jsboige
added a commit
that referenced
this pull request
Jun 19, 2026
…x new arc docs (#550) 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
#134 consolidated release validation dossier — single entry-point indexing the scattered release docs + the two net-new pieces that were missing (gate checklist + README download snippet). Closes the "#134 structure dossier release" item (ai-01 deep-queue, non-gated). The release itself stays gated — no tag, no regen, no README edit.
The problem this solves
The release documentation was already substantial but scattered across 4 locations (CHANGELOG at root, validation-brief, QA scenario, DNN validation-checklist). A reader (jsboige) had no single map. This dossier is that map.
Net-new value (does NOT duplicate the indexed docs)
Flags for jsboige (decision-relevant)
Path note
Placed in
docs/release-dossier/(notdocs/release/) because.gitignore:6rule[Rr]elease/excludes any directory namedrelease/Release(build-output guard). Documented in the file.Gate boundaries
🤖 Generated with Claude Code