Phase 6 reconcile - merge adjustments into plan bodies, add decisions #143-162, scaffold compliance stubs #77
Reference in New Issue
Block a user
Delete Branch "phase-6-reconcile"
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?
Summary
Test plan
?? Generated with Claude Code
After shipping the four Phase 6 plan drafts (PRs 77-80), the adversarial-review adjustments lived only as trailing "Review" sections. An implementer reading Stream A would find the original unadjusted guidance, then have to cross-reference the review to reconcile. This PR makes the plans genuinely executable: 1. Merges every ACCEPTed review finding into the actual Scope / Stream / Compliance sections of each phase plan: - phase-6-1: Scope table rewrite (per-capability retry, (instance,host) pipeline key, MemoryTracking vs MemoryRecycle split, hybrid watchdog formula, demand-aware wedge detector, generation-sealed LiteDB). Streams A/B/D + Compliance rewritten. - phase-6-2: AuthorizationDecision tri-state, control/data-plane separation, MembershipFreshnessInterval (15 min), AuthCacheMaxStaleness (5 min), subscription stamp-and-reevaluate. Stream C widened to 11 OPC UA operations. - phase-6-3: 8-state ServiceLevel matrix (OPC UA Part 5 §6.3.34-compliant), two-layer peer probe (/healthz + UaHealthProbe), apply-lease via await using, publish-generation fencing, InvalidTopology runtime state, ServerUriArray self-first + peers. New Stream F (interop matrix + Galaxy failover). - phase-6-4: DraftRevisionToken concurrency control, staged-import via EquipmentImportBatch with user-scoped visibility, CSV header version marker, decision-#117-aligned identifier columns, 1000-row diff cap, decision-#139 OPC 40010 fields, Identification inherits Equipment ACL. 2. Appends decisions #143 through #162 to docs/v2/plan.md capturing the architectural commitments the adjustments created. Each decision carries its dated rationale so future readers know why the choice was made. 3. Scaffolds scripts/compliance/phase-6-{1,2,3,4}-compliance.ps1 — PowerShell stubs with Assert-Todo / Assert-Pass / Assert-Fail helpers. Every check maps to a Stream task ID from the corresponding phase plan. Currently all checks are TODO and scripts exit 0; each implementation task is responsible for replacing its TODO with a real check before closing that task. Saved as UTF-8 with BOM so Windows PowerShell 5.1 parses em-dash characters without breaking. Net result: the Phase 6.1 plan is genuinely ready to execute. Stream A.3 can start tomorrow without reconciling Streams vs. Review on every task; the compliance script is wired to the Stream IDs; plan.md has the architectural commitments that justify the Stream choices. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>