docs(dnn): #131 navigation index for the DNN upgrade arc - #554
Conversation
docs(dnn): #131 navigation index for the DNN upgrade arc The docs/dnn-localization/ folder had 15 markdown docs covering the #131/#132/#457 DNN upgrade arc but no single entry point. A reader landing here had no map: which doc is authoritative, which is superseded, what order to execute, what is still gated on jsboige. Add a navigation-only README that: - sequences the 7 spine docs in 10.3.2 go-live execution order (Step 0 runtime fact -> target decision -> CVE reconciliation -> 2sxc Phase 1.5 -> DNN Phase 2 exec/rollback -> sandbox smoke gate -> prod go-live) - lists 5 supporting/scope docs - flags 3 superseded docs (9.13 plan, 10.1.2 step1, 10.1.2 deployment title) so they are not executed by mistake - surfaces the 2 pending jsboige gates (#445 Stripe, #525 typo) that block prod go-live - restates the hard constraints (sandbox/doc only, no csv touch, gated exec) Pure navigation/references — no content rewritten from the detailed docs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> @
clusterManager-Myia
left a comment
clusterManager-Myia
left a comment
There was a problem hiding this comment.
[NanoClaw] — #554 (docs(dnn): #131 navigation index for the DNN upgrade arc)
Clean docs-only navigation index (+67/-0, new file docs/dnn-localization/README.md). It does what it says: sequences the 15 existing DNN-upgrade docs (#131/#132/#457 arc) in go-live execution order and flags what's superseded. No content rewrite, no code, no execution.
✅ No dangling links — verified the targets exist. I listed docs/dnn-localization/ at the PR head: all referenced docs are present (131-step0-runtime-verification.md, 131-target-revision-10.3.2-full-upgrade.md, 131-cve-correction-..., 131-2sxc-migration-plan.md, 131-dnn-phase2-exec-rollback.md, 131-step2-smoke-test-checklist.md, 132-deployment-runbook.md, the §2 supporting docs, plus release-validation/). The superseded-docs table (§3) and pending-gates table (§4) point at real issues/docs.
✅ Properly gated — the right posture for a production DNN upgrade arc. §6 hard constraints are explicit and correct: "DNN = sandbox/research/doc only. NO deploy, NO content mutation, NO live sandbox upgrade without explicit jsboige GO", "NEVER touch dnn-ui-strings.csv (merged via #490)", "Doc execution gated step-by-step on jsboige go/no-go." This defers every business/version decision (target DNN 10.3.2 + 2sxc 21.07; #445 Stripe vs OpenStore; #525 typo) to jsboige. Consistent with the #552 §4.2 RESTORE-order fix I reviewed earlier (referenced accurately in §1 row 4).
Secrets: clean (only issue numbers, version strings, public filenames — no credentials, tokens, or sensitive URLs). The "@body.md" PR description is a placeholder, but the actual README content is fully present in the diff and checks out. Comment-only (self-review cap).
docs(dnn): #457 document-tier translation workflow (Phase 2-4 design) The Phase 1 inventory (457-site-content-type-inventory.md) named WHAT to translate but deferred the HOW for content-type C (the 2 standalone FR HTML pages, ~37k chars of prose). The string-tier toolchain (tools/dnn_i18n/, PRs #524/#487) handles ui.*/res.* keys but does not fit prose. This doc designs the document-tier lane: extraction -> DatasetUpdater -> re-import. Scope: DNNPlatform/fallacies/fallacies.html (81 KB, structured charte) + MariagePourTous.html (38 KB, prose). Design: - Phase 2 CSV schema: segment-oriented (segment_id = file#element-index), source_path + selector for deterministic re-import, inner-text fields per language. NOT the key->value string-tier dialect. - Phase 2 DatasetUpdater task shape: document-tier variant vs string-tier (prose prompt, char-budget chunking, gpt-5.5, reasoning effort low, max_output_tokens >=7000, Enabled=false until GO). - Phase 1.5 extractor: the net-new gating tool (html.parser stdlib, file-specific selectors h2/h3/li vs p/h2/h3, inner-text extract + selector store for re-wrap). Nothing translates until this exists. - Phase 4 re-import: selector-based patch, dry-run verifier (same DoD as string-tier round-trip), localized HTML files per language. - RTL/CJK (ar/fa/zh): reuse PR #359 font stacks at page level (dir=rtl/lang), template variant decision for jsboige. - Sequencing: extractor is critical path. - 4 open questions for jsboige (inner-text vs outer-HTML, one-template vs per-lang, are pages still served, GO to build extractor). Index README #554 updated to reference the new doc in supporting-docs table. Pure design/references -- no prod mutation, no extraction executed, no DatasetUpdater enabled. @ Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2 participants
@body.md