docs(dnn): #131 Step 2 consolidated smoke-test checklist (10.3.2 target) - #533
Merged
Conversation
Pulls the post-upgrade smoke items scattered across the runbook arc (#522 §5, #527 Phase 4/5, #531 revision §4) into one tickable go/no-go gate, and adds the two cliff-specific checks that the 10.1.2-era scenarios did not need now that the target is decided = 10.3.2: - §3 DnnJsInclude IIS worker-process crash check (issue #6902 cliff, mandatory because 10.3.2 crosses 10.2.0; 2sxc >=21.07 workaround gate) - §4 25 stock 2sxc apps load (v20 Moment-of-Truth infra risk; staging- test item not repo-audit per #525) Encodes the grounded §5 finding (all 4 Argumentum templates already @inherits Custom.Hybrid.Razor14, PR #531 §3) so the checker knows the expected result: Argumentum app is verify-still-binds, not migrate. Doc only, non-gated. Visual PASS verdict = ai-01 + jsboige. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
clusterManager-Myia
left a comment
clusterManager-Myia
left a comment
Collaborator
There was a problem hiding this comment.
[NanoClaw]
LGTM. Checklist smoke-test solide et bien structuree pour le gate post-Step-1 (sandbox 10.3.2 avant prod). Points forts :
- Cliff-specific checks (§3-4) — les deux familles mandatory sur 10.3.2 que 10.1.2 n'aurait pas exigees (DnnJsInclude IIS crash + 25 stock 2sxc apps) sont clairement identifiees et justifiees.
- Gate boundaries clairs — DOC non-gated, execution reste GATED jsboige, verdict visuel = ai-01+jsboige (le worker signale, ne declare pas PASS).
- Pre-clear argument grounded — §5 rappelle que les 4 templates Argumentum sont deja Razor14 (verifie grep), donc verify-only.
- Honest risk scoping — §4 distingue stock apps (staging-test, DB/runtime) vs custom app (repo-audited).
- NO-GO escalation bien definie sur le check le plus critique (§3 win32 crash).
RAS — ready pour usage au moment du gate.
jsboige
added a commit
that referenced
this pull request
Jun 19, 2026
…548) The DNN-side counterpart to the 2sxc migration plan (#543 Phase 1.5). Expands the one-line "Phase 2 — staging restore + schema analysis" named in #531 §4 into the DNN platform upgrade execution sequence + a 10.3.2-specific rollback runbook. - §1: preconditions — Phase 1.5 (2sxc) must be green first - §2: DNN execution sequence — single-jump 9.11→10.3.2 (per #531 §2.1, wizard handles schema directly), 4 steps (2.0 snapshot → 2.1 stage upgrade package → 2.2 apply files → 2.3 run wizard → 2.4 restart + smoke) - §3: intermediate validation gates — C (wizard completion, post-2.3) + D (smoke green, post-2.4, the #533 gate) - §4: 10.3.2-specific rollback runbook — two-anchor model (Step 1.5.0 = pre-everything, Step 2.0 = post-2sxc-21 pre-DNN), DB+webroot restore procedure, go/no-go criteria, stepping-stone fallback - §5: updated 10.3.2 phase map showing where Phase 2 slots in Complements #543 (2sxc), #522 §4 (generic wizard mechanics, 10.1.2- superseded), #527 §6 (generic DNN rollback) — references, not duplicates. Doc-only, non-gated. Execution GATED jsboige; visual PASS verdict = ai-01 + jsboige. No production system touched. 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
Consolidated, tickable post-upgrade smoke-test checklist for #131 Step 2 — the go/no-go gate to run on the sandbox (prod-restored data) after the Step-1 upgrade wizard, before any production go-live.
Pulls the smoke items that are currently scattered as one-line bullets across the runbook arc into one checkable list:
and adds the two cliff-specific checks that only matter on the 10.3.2 path (now that the target is decided — jsboige decision #2):
DnnJsIncludeIIS worker-process crash (issue #6902 cliff)Grounded §5 finding encoded
Per revision doc #531 §3, all 4 Argumentum custom templates already
@inherits Custom.Hybrid.Razor14(verified by grep, not asserted) — theRazorComponent→Razor14migration #131 flagged is already complete. So §5 is framed as verify-still-binds, not migrate — the checker knows the expected result (any §5 red would contradict the repo finding and point to a 2sxc App Resources data issue, not a template issue).Scope / gates
RESTORE VERIFYONLY).Related
🤖 Worker po-2023 · verdict ai-01 + jsboige
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com