aw-spec-cli 0.1.3 → 0.1.5

package/assets/.aw-spec/orchestrator/workflows/aw-spec-analyze-delta-design.orch.yaml

@@ -0,0 +1,248 @@
+# =============================================================================
+# aw-spec-analyze-delta-design (orchestrator) — the delta-spec↔delta-design GATE
+#
+# The CR analog of analyze-design, scoped to the OPEN change. The delta spec is the
+# ANCHOR: confirm delta-design.md STRICTLY realises delta-spec.md (+ the domain gate
+# overlays as a backstop), and that every MODIFIED element names a real element in
+# the master design.md. On drift, REPORT the gaps and ASK whether to repair, then
+# UPDATE delta-design.md to conform (the delta spec wins). This stage VALIDATES the
+# delta only — it does NOT touch spec.md / design.md and does NOT close the change
+# (finalize-delta merges the delta later; close-delta closes it at the very end).
+#
+#   specify → design → ⟨review⟩ → analyze-delta-design   ← you are here
+#       → implement-delta → build → finalize-delta → analyze-slice → close-delta
+#
+# Launch:  /aw-spec-orch analyze-delta-design [strategy]
+# Prereq:  /aw-spec-orch specify (delta-spec) + design (delta-design) — an OPEN change with both delta docs.
+# =============================================================================
+
+name: aw-spec-analyze-delta-design
+description: The delta-spec↔delta-design conformance gate for an open change — confirm delta-design.md realises delta-spec.md (delta spec is the anchor; domain overlays are a backstop; MODIFIED elements must exist in the master design) and, with approval, repair it. Does not modify the master docs or close the change.
+version: 1.0.0
+agent_agnostic: true
+dialect: aw-spec.orchestrator/v1
+
+scripts:
+  actions:
+    sh:  .aw-spec/scripts/bash/aw-spec-actions.sh
+    ps1: .aw-spec/scripts/powershell/aw-spec-actions.ps1
+
+vars:
+  analyze_ok: "false"
+  active_change: ""
+  has_change: "false"
+
+workflow:
+
+  # 1. Resolve the current feature + its spec; require the spec (delta context base).
+  - id: feature_paths
+    action: execute_script
+    on_error: continue      # never crash raw on 'no feature set' — the gate below explains it
+    script: { ref: actions }
+    subcommand: feature-paths
+    outputs:
+      - { name: feature_dir, from: "$.feature_dir" }
+      - { name: spec_file,   from: "$.spec_file" }
+      - { name: spec_exists, from: "$.spec_exists" }
+
+  - id: require_feature
+    action: verify_context
+    require_non_empty: feature_dir
+    on_empty: stop
+    on_empty_message: "No active feature. Run /aw-spec-orch select-feature first (pick or create the aggregate, e.g. Order), then re-run analyze-delta-design."
+
+  - id: verify_spec
+    action: verify_context
+    require_true: spec_exists
+    on_false: stop
+    on_false_message: "No spec.md for the current feature. Run /aw-spec-orch specify (and design) first."
+
+  # 1b. Read the OPEN change (opened by cr). A CR gate needs a change to gate.
+  - id: read_change
+    action: execute_script
+    script: { ref: actions }
+    subcommand: version-read
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: active_change, from: "$.active_change" }
+      - { name: has_change,    from: "$.has_change" }
+
+  - id: require_change
+    action: verify_context
+    require_true: has_change
+    on_false: stop
+    on_false_message: "No open change on this feature. Run /aw-spec-orch specify <change> (opens the change + delta-spec) then /aw-spec-orch design (delta-design) first — analyze-delta-design gates an open change's delta docs."
+
+  # 2. Ensure the master design.md exists (idempotent) — the base the delta MODIFIED
+  #    elements must refer to. Delta doc paths are derived from the open change id.
+  - id: design_scaffold
+    action: execute_script
+    script: { ref: actions }
+    subcommand: design-scaffold
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: design_doc, from: "$.design_doc" }
+
+  # 2b. Load the domain GATE overlays (the comandrulemap `/aw-spec-gate` checklist) as
+  #     the conformance checklist — VALIDATION input only, NEVER authoring. analyze sees
+  #     them (include_standards: true); reconcile does NOT (the delta conforms to the
+  #     delta SPEC, not to the overlays). Empty/no-op for a non-domain project.
+  - id: resolve_gate_overlays
+    action: execute_script
+    script: { ref: actions }
+    subcommand: resolve-domain
+    args: ["--command", "aw-spec-gate"]
+    outputs:
+      - { name: gate_overlays, from: "$.candidates" }
+  - id: load_gate_overlays
+    action: load_standards
+    files_from_variable: gate_overlays
+    optional: true
+
+  # 3. Pre-execution hooks.
+  - id: resolve_pre_hooks
+    action: execute_script
+    script: { ref: actions }
+    subcommand: resolve-hooks
+    args: ["--phase", "before_analyze_cr"]
+    outputs:
+      - { name: before_hooks, from: "$.hooks" }
+  - id: dispatch_pre_hooks
+    action: dispatch_hooks
+    hooks_from_variable: before_hooks
+
+  # 4. Conformance + REPAIR loop (the delta spec is the anchor): check → REPORT gaps +
+  #    ASK → Repair on approval → re-check; "Report and Skip" writes the report + stops.
+  #    Bounded (3×). Delta docs live under changes/<open change>/.
+  - id: analyze_loop
+    action: loop
+    while: "{{analyze_ok}} != true"
+    max_iterations: 3
+    steps:
+      - id: analyze
+        action: agent_query
+        context:
+          - "{{feature_dir}}/changes/{{active_change}}/delta-spec.md"
+          - "{{feature_dir}}/changes/{{active_change}}/delta-design.md"
+          - "{{spec_file}}"
+          - "{{design_doc}}"
+        include_standards: true            # the gate overlays (checklist) are in the standards
+        schema: { ok: true, gaps: [ { severity: "high", spec_ref: "<delta FR/BR/CN/DC/IC/US or overlay or —>", where: "<delta-design section>", gap: "<how it drifts>" } ] }
+        mock: { ok: true, gaps: [] }
+        task: |
+          delta-spec.md is the ANCHOR for this change. Check that delta-design.md
+          (in context) STRICTLY realises the delta spec (in context) and list EVERY
+          drift as a gap:
+          (1) every ADDED / MODIFIED delta-spec item — FR / BR / CN- / DC- / IC- /
+          user story — has a home in the delta design (an ADDED or MODIFIED design
+          element that serves it). A delta-spec item with no delta-design element is
+          a HIGH gap;
+          (2) every MODIFIED delta-design element names a REAL element that exists in
+          the master design.md (also in context) — you cannot MODIFY what the master
+          does not define (that would be an ADD). A dangling MODIFIED reference is a
+          HIGH gap;
+          (3) the delta design introduces NOTHING beyond the delta spec — any design
+          element with no delta-spec basis is a drift (unless logged as a delta DA-n);
+          (4) shared elements have ONE owning definition (no duplicate path=/element);
+          the layers stay coherent (Application→Domain, API→Application, Infra→ports)
+          and technology-agnostic;
+          (5) OVERLAY BACKSTOP — the domain gate checklist is loaded in the standards.
+          For each constraint it states (retention, immutability, append-only audit,
+          data-exposure, interop obligation, etc.) that this CHANGE touches, confirm
+          the delta realises it via a delta CN-/DC-/IC-. If the change touches such a
+          constraint but it is in NEITHER the delta spec nor the delta design, it is a
+          HIGH gap — set spec_ref to the overlay name and PREFIX the gap text with
+          "LIFT-FAILURE:" (re-run /aw-spec-orch specify to lift it into the delta spec; do
+          NOT fabricate it in the delta design).
+          (If delta-design.md is still the empty template, treat the WHOLE delta spec
+          as gaps.) Set ok=true ONLY when delta-design.md fully realises the delta spec
+          AND no touched checklist constraint is unaccounted for.
+        outputs:
+          - { name: analyze_ok,   from: "$.ok" }
+          - { name: analyze_gaps, from: "$.gaps" }
+      - id: conform_break
+        action: break
+        condition: "{{analyze_ok}} == true"
+      - id: ask_repair
+        action: ask
+        prompt: |
+          analyze-delta-design found delta-spec↔delta-design gaps (the delta spec is the anchor):
+          {{analyze_gaps}}
+          Repair delta-design.md to conform to the delta spec now, or report the gaps and stop?
+        options: ["Repair", "Report and Skip"]
+        answer_var: repair_choice
+      - id: write_report
+        condition: "{{repair_choice}} == Report and Skip"
+        action: agent_author
+        context: ["{{feature_dir}}/changes/{{active_change}}/delta-design.md"]
+        include_standards: false
+        output_target: { type: file, path: "{{feature_dir}}/changes/{{active_change}}/delta-design-analyze-report.md" }
+        task: |
+          Write a Delta Design Analyze Report to the output from these
+          delta-spec↔delta-design conformance gaps (the delta spec is the ANCHOR; the
+          user chose to skip repair):
+          {{analyze_gaps}}
+          Markdown format:
+          - "# Delta Design Analyze Report — {{active_change}}" plus today's date.
+          - A verdict line: "verdict: GAPS ✗ · <n> gap(s)".
+          - "## Gaps" as a table: | # | severity | delta-spec ref | delta-design location | gap |.
+          - "## How to resolve": the delta spec is the anchor — update delta-design.md
+            to realise it for each gap (out of band; a "LIFT-FAILURE:" gap means re-run
+            /aw-spec-orch specify to lift the constraint into the delta spec), then re-run
+            /aw-spec-orch analyze-delta-design to clear the report.
+          Return the complete report markdown only.
+      - id: skip_break
+        action: break
+        condition: "{{repair_choice}} == Report and Skip"
+      - id: reconcile
+        action: agent_author
+        context:
+          - "{{feature_dir}}/changes/{{active_change}}/delta-spec.md"
+          - "{{feature_dir}}/changes/{{active_change}}/delta-design.md"
+          - "{{design_doc}}"
+        include_standards: false           # rewrite-in-place: the delta spec anchors — NOT the overlays
+        output_target: { type: file, path: "{{feature_dir}}/changes/{{active_change}}/delta-design.md" }
+        task: |
+          delta-spec.md is the ANCHOR — update delta-design.md (in context) to REALISE
+          it, closing these gaps (the delta spec WINS every time):
+          {{analyze_gaps}}
+          - Add a delta-design element for each uncovered ADDED/MODIFIED delta-spec
+            FR/BR/CN/DC/IC/US, in the correct layer section, serving that spec id.
+          - Ensure every MODIFIED element names a REAL element from the master
+            design.md (in context); if the master does not define it, make it an ADDED
+            element instead.
+          - REMOVE, or move to a delta DA-n note, any delta-design element with no
+            delta-spec basis — never keep design that exceeds the delta spec.
+          - A "LIFT-FAILURE:" gap you CANNOT close — the constraint is not in the delta
+            spec, and you must NOT invent a domain rule it omits. Leave it open and add
+            a note "lift-failure: <constraint> — re-run /aw-spec-orch specify to lift it into
+            the delta spec". (The gate will stop and direct the user to cr.)
+          - Keep the technology-agnostic form (signatures + pre/post/invariant, field
+            shapes — NO code). Preserve every already-conformant section VERBATIM. Do
+            NOT change the delta spec or the master design.md.
+          Return the COMPLETE updated delta-design.md content only.
+
+  - id: analyze_gate
+    action: verify_context
+    require_true: analyze_ok
+    on_false: stop
+    on_false_message: "delta-design.md does not realise the delta spec (gaps: {{analyze_gaps}}) — repair was skipped (see changes/{{active_change}}/delta-design-analyze-report.md), or it could not be reconciled in 3 passes. A 'LIFT-FAILURE:' gap means a domain constraint from the gate checklist was never lifted into the delta spec — re-run /aw-spec-orch specify to add it (CN-/DC-/IC-). Otherwise fix out of band, or re-run and choose Repair."
+
+  # 5. Post-execution hooks.
+  - id: resolve_post_hooks
+    action: execute_script
+    script: { ref: actions }
+    subcommand: resolve-hooks
+    args: ["--phase", "after_analyze_cr"]
+    outputs:
+      - { name: after_hooks, from: "$.hooks" }
+  - id: dispatch_post_hooks
+    action: dispatch_hooks
+    hooks_from_variable: after_hooks
+
+outputs:
+  feature_dir: "{{feature_dir}}"
+  cr_id: "{{active_change}}"
+  conformant: "{{analyze_ok}}"
+  gaps: "{{analyze_gaps}}"
+  next: "/aw-spec-orch implement-delta → build → finalize-delta → analyze-slice → close-delta   (the delta design realises the delta spec; the change stays OPEN through finalize-delta's merge and analyze-slice's verification, and only close-delta archives it and bumps the version)"

package/assets/.aw-spec/orchestrator/workflows/aw-spec-analyze-design.orch.yaml

@@ -0,0 +1,261 @@
+# =============================================================================
+# aw-spec-analyze-design (orchestrator) — the spec↔design conformance GATE
+#
+# The single, discrete conformance gate on the forward path:
+#   specify → design → analyze-design → implement.
+# spec.md is the ANCHOR. Confirm design.md STRICTLY follows the spec (+ the domain
+# gate overlays as a backstop); on drift, REPORT the gaps and ASK whether to repair,
+# then UPDATE design.md to conform (spec wins). Design AUTHORS; this stage VALIDATES.
+#
+# BOOTSTRAP-ONLY, and it NEVER opens, merges or closes a change. It gates a feature
+# whose spec.md + design.md ARE the masters. With a change OPEN the delta docs are the
+# authoritative in-flight edit and the master pair must not be rewritten under them, so
+# the run STOPS and routes to /aw-spec-orch analyze-delta-design (the delta's own gate).
+# The change is closed by close-delta, the SINGLE cr-archive caller, and only after
+# finalize-delta has merged the delta into the masters. Also runnable on demand to
+# re-anchor a hand-edited spec — again, only when no change is open.
+#
+# Launch:  /aw-spec-orch analyze-design [strategy]
+# Prereq:  /aw-spec-orch design   (a spec.md + design.md for the active feature).
+# =============================================================================
+
+name: aw-spec-analyze-design
+description: The spec↔design conformance gate — confirm design.md conforms to spec.md (spec is the anchor; domain overlays are a backstop) and, with approval, repair it. Bootstrap-only — with a change open it stops and routes to analyze-delta-design; it never closes a change.
+version: 2.1.0
+agent_agnostic: true
+dialect: aw-spec.orchestrator/v1
+
+scripts:
+  actions:
+    sh:  .aw-spec/scripts/bash/aw-spec-actions.sh
+    ps1: .aw-spec/scripts/powershell/aw-spec-actions.ps1
+
+vars:
+  analyze_ok: "false"
+  active_change: ""
+  has_change: "false"
+  version: ""
+  no_open_change: "true"   # NOT has_change ⇒ the masters are authoritative ⇒ this gate applies
+
+workflow:
+
+  # 1. Resolve the current feature + its spec; require the spec (the anchor).
+  - id: feature_paths
+    action: execute_script
+    on_error: continue      # never crash raw on 'no feature set' — the gate below explains it
+    script: { ref: actions }
+    subcommand: feature-paths
+    outputs:
+      - { name: feature_dir, from: "$.feature_dir" }
+      - { name: spec_file,   from: "$.spec_file" }
+      - { name: spec_exists, from: "$.spec_exists" }
+
+  - id: require_feature
+    action: verify_context
+    require_non_empty: feature_dir
+    on_empty: stop
+    on_empty_message: "No active feature. Run /aw-spec-orch select-feature first (pick or create the aggregate, e.g. Order), then re-run analyze-design."
+
+  - id: verify_spec
+    action: verify_context
+    require_true: spec_exists
+    on_false: stop
+    on_false_message: "No spec.md for the current feature. Run /aw-spec-orch specify (and design) first."
+
+  # 1b. Read the open change (opened by specify, or by design on a design-only change).
+  #     has_change drives the BOOTSTRAP-ONLY guard below — it closes nothing.
+  - id: read_change
+    action: execute_script
+    script: { ref: actions }
+    subcommand: version-read
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: active_change, from: "$.active_change" }
+      - { name: has_change,    from: "$.has_change" }
+      - { name: version,       from: "$.version" }
+
+  # 1c. BOOTSTRAP-ONLY GUARD. A change open ⇒ delta-spec/delta-design are the
+  #     authoritative in-flight edit and this stage is the WRONG gate: its repair loop
+  #     rewrites the MASTER design.md, which would drift the masters out from under the
+  #     delta before finalize-delta merges it. Stop BEFORE any scaffold/authoring so the
+  #     wrong-stage run has zero side effects, and route to the delta's own gate.
+  - id: flag_change_open
+    condition: "{{has_change}} == true"
+    action: set
+    vars: { no_open_change: "false" }
+
+  - id: require_no_change
+    action: verify_context
+    require_true: no_open_change
+    on_false: stop
+    on_false_message: "Change {{active_change}} is OPEN on this feature — analyze-design is the BOOTSTRAP gate and must not rewrite the master design.md while a delta is in flight. Gate the delta instead: /aw-spec-orch analyze-delta-design → implement-delta → build → finalize-delta (merges the delta into spec.md + design.md) → analyze-slice → close-delta (archives the change + bumps the version). Re-run analyze-design once the change is closed, to re-anchor the masters."
+
+  # 2. Ensure design.md exists (idempotent scaffold — returns the existing path, or
+  #    a fresh template the repair loop will author to conform to the spec).
+  - id: design_scaffold
+    action: execute_script
+    script: { ref: actions }
+    subcommand: design-scaffold
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: design_doc, from: "$.design_doc" }
+
+  # 2b. Load the domain GATE overlays (the comandrulemap `/aw-spec-gate` checklist) as
+  #     the conformance checklist — VALIDATION input only, NEVER authoring. The analyze
+  #     step sees them (include_standards: true); reconcile does NOT (design conforms to
+  #     the SPEC, not to the overlays). Empty/no-op for a non-domain project.
+  - id: resolve_gate_overlays
+    action: execute_script
+    script: { ref: actions }
+    subcommand: resolve-domain
+    args: ["--command", "aw-spec-gate"]
+    outputs:
+      - { name: gate_overlays, from: "$.candidates" }
+  - id: load_gate_overlays
+    action: load_standards
+    files_from_variable: gate_overlays
+    optional: true
+
+  # 3. Pre-execution hooks.
+  - id: resolve_pre_hooks
+    action: execute_script
+    script: { ref: actions }
+    subcommand: resolve-hooks
+    args: ["--phase", "before_analyze"]
+    outputs:
+      - { name: before_hooks, from: "$.hooks" }
+  - id: dispatch_pre_hooks
+    action: dispatch_hooks
+    hooks_from_variable: before_hooks
+
+  # 4. Conformance + REPAIR loop (spec is the anchor): check → REPORT gaps + ASK →
+  #    Repair on approval → re-check; "Report and Skip" writes design-analyze-report.md
+  #    and stops. Bounded (3×).
+  - id: analyze_loop
+    action: loop
+    while: "{{analyze_ok}} != true"
+    max_iterations: 3
+    steps:
+      - id: analyze
+        action: agent_query
+        context: ["{{spec_file}}", "{{design_doc}}"]
+        include_standards: true            # the gate overlays (checklist) are in the standards
+        schema: { ok: true, gaps: [ { severity: "high", spec_ref: "<FR/BR/CN/DC/IC/US/SC or overlay or —>", where: "<design section>", gap: "<how it drifts>" } ] }
+        mock: { ok: true, gaps: [] }
+        task: |
+          spec.md is the ANCHOR. Check that design.md (in context) STRICTLY follows
+          the spec (in context) and list EVERY drift as a gap:
+          (1) every spec item — FR / Business Rule / Constraint (CN-) / Data
+          Classification (DC-) / Integration Contract (IC-) / user story / success
+          criterion — has a design home (§6 Traceability complete). A lifted CN-/DC-/IC-
+          with no design row is a HIGH gap;
+          (2) the DOMAIN model matches the spec EXACTLY — entities/value objects are
+          the spec's Key Entities (same names), invariants are the spec's Business
+          Rules, and the boundary is the spec's Aggregate Boundary;
+          (3) NO design element exceeds or contradicts the spec — anything without a
+          spec basis is a drift unless already logged as a §7 DA-n assumption;
+          (4) the layers are coherent (Application→Domain, API→Application, Infra
+          implements the declared ports) and it stays high-level + technology-agnostic.
+          (5) OVERLAY BACKSTOP — the domain gate checklist is loaded in the standards.
+          For each constraint it states (retention, immutability, append-only audit,
+          data-exposure, interop obligation, etc.), confirm design.md realises it via a
+          spec CN-/DC-/IC-. If a checklist constraint is present in NEITHER the spec nor
+          the design, it is a HIGH gap — set spec_ref to the overlay name and PREFIX the
+          gap text with "LIFT-FAILURE:" (it was never lifted into the spec; the fix is
+          /aw-spec-orch specify, not design — do not fabricate it in the design).
+          (If design.md is still the empty template, treat the WHOLE spec as gaps.)
+          Set ok=true ONLY when design.md fully conforms to the spec AND no checklist
+          constraint is unaccounted for.
+        outputs:
+          - { name: analyze_ok,   from: "$.ok" }
+          - { name: analyze_gaps, from: "$.gaps" }
+      - id: conform_break
+        action: break
+        condition: "{{analyze_ok}} == true"
+      - id: ask_repair
+        action: ask
+        prompt: |
+          Analyze found spec↔design gaps (spec.md is the anchor):
+          {{analyze_gaps}}
+          Repair design.md to conform to the spec now, or report the gaps and stop?
+        options: ["Repair", "Report and Skip"]
+        answer_var: repair_choice
+      - id: write_report
+        condition: "{{repair_choice}} == Report and Skip"
+        action: agent_author
+        context: ["{{design_doc}}"]
+        include_standards: false
+        output_target: { type: file, path: "{{feature_dir}}/design-analyze-report.md" }
+        task: |
+          Write a Design Analyze Report to the output from these spec↔design
+          conformance gaps (spec.md is the ANCHOR; the user chose to skip repair):
+          {{analyze_gaps}}
+          Markdown format:
+          - "# Design Analyze Report — <aggregate>" plus today's date.
+          - A verdict line: "verdict: GAPS ✗ · <n> gap(s)".
+          - "## Gaps" as a table: | # | severity | spec ref | design location | gap |.
+          - "## How to resolve": the spec is the anchor — update design.md to follow
+            the spec for each gap (out of band), then re-run /aw-spec-orch analyze-design
+            to clear the report.
+          Return the complete report markdown only.
+      - id: skip_break
+        action: break
+        condition: "{{repair_choice}} == Report and Skip"
+      - id: reconcile
+        action: agent_author
+        context: ["{{spec_file}}", "{{design_doc}}"]
+        include_standards: false           # rewrite-in-place: spec anchors — NOT the overlays
+        output_target: { type: file, path: "{{design_doc}}" }
+        task: |
+          spec.md is the ANCHOR — update design.md (in context) to CONFORM to it,
+          closing these gaps (the spec WINS every time):
+          {{analyze_gaps}}
+          - Add a design home for each uncovered spec FR/BR/CN/DC/IC/US/SC (a lifted
+            CN-/DC-/IC- lands in §1 invariant · §4 persistence/§4.2 adapter · §5 row).
+          - Realign the DOMAIN model to the spec: entity/value-object names = the
+            spec's Key Entities, invariants = the spec's Business Rules, boundary =
+            the spec's Aggregate Boundary.
+          - REMOVE, or move to a §7 DA-n assumption, any design element with no spec
+            basis — never keep design that exceeds or contradicts the spec. EXCEPTION:
+            do NOT remove a cross-cutting element that is (or may be) mandated by the
+            technical constitution — it cites a principle as its basis ("per Const.
+            §<n>"), or it is standing technical/infrastructure machinery rather than
+            invented domain logic. MOVE such an element to a §7 DA-n citing the mandating
+            principle; removing it could violate the constitution. Reserve REMOVE for
+            genuine over-reach — invented domain entities/rules/behaviour the spec omits.
+          - A "LIFT-FAILURE:" gap you CANNOT close — the constraint is not in the spec,
+            and you must NOT invent a domain rule the spec omits. Leave it open and add a
+            §7 DA-n note "lift-failure: <constraint> — re-run /aw-spec-orch specify to lift
+            it into CN-/DC-/IC-". (The gate will stop and direct the user to specify.)
+          - Keep §6 Traceability in sync. Preserve every already-conformant section
+            VERBATIM. Do NOT change the spec.
+          Return the COMPLETE updated design.md content only.
+
+  - id: analyze_gate
+    action: verify_context
+    require_true: analyze_ok
+    on_false: stop
+    on_false_message: "design.md does not conform to the spec (gaps: {{analyze_gaps}}) — repair was skipped (see design-analyze-report.md), or it could not be reconciled in 3 passes. A 'LIFT-FAILURE:' gap means a domain constraint from the gate checklist was never lifted into the spec — re-run /aw-spec-orch specify to add it (CN-/DC-/IC-). Otherwise fix out of band, or re-run and choose Repair; resolve an ambiguous spec via /aw-spec-orch specify."
+
+  # (No change-close here by design — this stage only ever runs with NO change open,
+  #  and cr-archive belongs to close-delta, which runs after finalize-delta's merge.)
+
+  # 5. Post-execution hooks.
+  - id: resolve_post_hooks
+    action: execute_script
+    script: { ref: actions }
+    subcommand: resolve-hooks
+    args: ["--phase", "after_analyze"]
+    outputs:
+      - { name: after_hooks, from: "$.hooks" }
+  - id: dispatch_post_hooks
+    action: dispatch_hooks
+    hooks_from_variable: after_hooks
+
+outputs:
+  feature_dir: "{{feature_dir}}"
+  design_doc: "{{design_doc}}"
+  conformant: "{{analyze_ok}}"
+  gaps: "{{analyze_gaps}}"
+  version: "{{version}}"
+  next: "/aw-spec-orch implement   (design conforms to the spec; version unchanged — this gate closes nothing)"