v2 release-readiness capstone - aggregate compliance runner + readiness dashboard #93
Reference in New Issue
Block a user
Delete Branch "v2-release-readiness-capstone"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes out Phase 6 with the two pieces a release engineer needs before tagging v2 GA.
Summary
scripts/compliance/phase-6-all.ps1— meta-runner that invokes each Phase 6.N script in its own powershell.exe child + aggregates PASS/FAIL. Locally: all four phases PASS.docs/v2/v2-release-readiness.md— dashboard: what’s shipped, what’s deferred, three release blockers (6.2 dispatch wiring #143, 6.1 cache wiring #136, 6.3 coordinator + UA-node + interop #145/#147/#150), release exit criteria (all compliance scripts exit 0 + dotnet test ≤ 1 known flake + blockers closed + Fleet Admin signoff + live-Galaxy smoke + CTT pass + redundancy cutover validated).Test plan
pwsh ./scripts/compliance/phase-6-all.ps1exit 0, aggregate PASS.🤖 Generated with Claude Code
Closes out Phase 6 with the two pieces a release engineer needs before tagging v2 GA: 1. scripts/compliance/phase-6-all.ps1 — meta-runner that invokes every per-phase Phase 6.N compliance script in sequence + aggregates results. Each sub-script runs in its own powershell.exe child process so per-script $ErrorActionPreference + exit semantics can't interfere with the parent. Exit 0 = every phase passes; exit 1 = one or more phases failed. Prints a PASS/FAIL summary matrix at the end. 2. docs/v2/v2-release-readiness.md — single-view dashboard of everything shipped + everything still deferred + release exit criteria. Called out explicitly: - Three release BLOCKERS (must close before v2 GA): * Phase 6.2 Stream C dispatch wiring — AuthorizationGate exists but no DriverNodeManager Read/Write/etc. path calls it (task #143). * Phase 6.1 Stream D follow-up — ResilientConfigReader + sealed-cache hook not yet consumed by any read path (task #136). * Phase 6.3 Streams A/C/F — coordinator + UA-node wiring + client interop still deferred (tasks #145, #147, #150). - Three nice-to-haves (not release-blocking) — Admin UI polish, background services, multi-host dispatch. - Release exit criteria: all 4 compliance scripts exit 0, dotnet test ≤ 1 known flake, blockers closed or v2.1-deferred with written decision, Fleet Admin signoff on deployment checklist, live-Galaxy smoke test, OPC UA CTT pass, redundancy cutover validated with at least one production client. - Change log at the bottom so future ships of deferred follow-ups just append dates + close out dashboard rows. Meta-runner verified locally: Phase 6.1 — PASS Phase 6.2 — PASS Phase 6.3 — PASS Phase 6.4 — PASS Aggregate: PASS (elapsed 340 s — most of that is the full solution `dotnet test` each phase runs). Net counts at capstone time: 906 baseline → 1159 passing across Phase 6 (+253). 15 deferred follow-up tasks tracked with IDs (#134-137, #143-144, #145, #147, #149-150, #153, #155-157). v2 is NOT YET release-ready — capstone makes that explicit rather than letting the "shipped" label on each phase imply full readiness. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>