SuperBizAgent-java/openspec/changes/archive/2026-07-17-chat-diagnosis-stategraph-design-freeze/tasks.md

1. Freeze Source Documents

• 1.1 Compare ISS-011 sections 3–14 against the committed state, routing, retry, fallback, audit, and test-migration design; resolve every drift without editing runtime code.
• 1.2 Verify devflow/glossary/CONTEXT.md defines Diagnosis Orchestration Trace and the Verifier verified-evidence boundary without implementation-detail leakage.

2. Record Durable Architecture Decisions

• 2.1 Create a project ADR that records the StateGraph control boundary, explicit Gatekeeper Node, run-scoped orchestration trace, rejected alternatives, compatibility, migration, and rollback decisions.
• 2.2 Record the six independent sm-flow handoff boundaries and require stages 1–5 to reference the archived stage 0 baseline.

3. Validate The Design Freeze

• 3.1 Run strict OpenSpec validation and cross-artifact checks for proposal, design, specs, and tasks; resolve every validation or alignment gap.
• 3.2 Verify the stage 0 diff contains no Java, SQL, Prompt, configuration, or runtime behavior changes.
• 3.3 Record that unit tests and Maven E2E are intentionally not run because stage 0 changes only design artifacts; reserve Maven E2E, logs, and database evidence for stage 5.