aw-spec-cli 0.1.5 → 0.1.7

package/assets/.aw-spec/orchestrator/workflows/aw-spec-constitution.orch.yaml

@@ -1,284 +0,0 @@
-# =============================================================================
-# aw-spec-constitution (orchestrator) — create/update the SPLIT project constitution
-#
-# Authors TWO composed files, each from its own source, so the forward loop can
-# load them per the rule-partition (.aw-spec/RULE-PARTITION.md):
-#   .aw-spec/memory/constitution.technical.md  ← technology base (I–XV) + ai-rules.
-#       Domain-agnostic. STANDING input to DESIGN + IMPLEMENT (not specify).
-#   .aw-spec/memory/constitution.domain.md     ← the active domain addenda
-#       (docs/<domain>-constitution.md + domain rule files). Domain principles XVI+.
-#       SPECIFY-only + gate checklist; deliberately NOT loaded by design/implement.
-# A deterministic `compose-constitution` then concatenates them into the composed
-# .aw-spec/memory/constitution.md (human/compat view only; the pipeline loads the
-# halves directly).
-#
-# WHY SPLIT: the old single constitution embedded the domain (principles XVI–XX)
-# and was standing input to every phase — a domain side-channel into design that
-# broke "design's only domain input is the spec." Splitting keeps design/implement
-# domain-free while specify still gets the full picture.
-#
-# The seam is enforced by ORDER: the technical half is authored BEFORE domain-select
-# runs, so its context can never contain a domain file. The domain half is authored
-# after, from the domain addenda (and may reference the technical base it extends).
-#
-# Each half is authored and then linted by the deterministic `constitution-verify`
-# SCRIPT (residual [ALL_CAPS] placeholders, body-vs-report version, ISO dates) with
-# a bounded self-correction loop (max 3) — so the whole skill works under every
-# strategy (sdk/sdk-apply/spawn/agent), --checkpoint, or headless.
-#
-# NOT part of the per-feature pipeline. Project-level, run-once / amend-on-change.
-#
-# Launch:  /aw-spec-orch constitution [strategy] [principles or values…]
-# Action semantics: .aw-spec/ORCH-DIALECT.md
-# =============================================================================
-
-name: aw-spec-constitution
-description: Create or update the split project constitution — constitution.technical.md (technology base) + constitution.domain.md (active domain addenda), each version-bumped with a Sync Impact Report, then composed into constitution.md. Project-level, run-once/amend — not a per-feature phase.
-version: 2.0.0
-agent_agnostic: true
-dialect: aw-spec.orchestrator/v1
-
-inputs:
-  user_input:
-    description: Principles or values for the project constitution (optional).
-    required: false
-    bind: USER_INPUT
-
-scripts:
-  actions:
-    sh:  .aw-spec/scripts/bash/aw-spec-actions.sh
-    ps1: .aw-spec/scripts/powershell/aw-spec-actions.ps1
-
-# Sticky standards seed = the UNIVERSAL always-on rule only (ai-rules). The technology-
-# constitution base the TECHNICAL half ratifies is no longer hardcoded here — it is now
-# CONFIGURATION, loaded per-command from docs/domainspecs/<domain>/commandtechrulemap.md
-# under "## /aw-spec-constitution" by the tech-select module (see the tech_select step
-# below). tech_select runs BEFORE the technical half AND before domain-select, so the
-# technical author still sees only the technology base + ai-rules — NO domain file: the
-# seam is preserved. The constitution OUTPUT files (constitution.technical.md /
-# constitution.domain.md) are referred to directly elsewhere, never mapped. (missing skipped)
-standards:
-  - { path: docs/glossary/ai-rules.md, optional: true }
-
-vars:
-  technical_ok: "false"   # technical-half validation-loop guard, flipped by constitution-verify
-  domain_ok: "false"      # domain-half validation-loop guard, flipped by constitution-verify
-
-workflow:
-
-  # 0. TECHNICAL rule files → sticky standards (configuration, not hardcoded). tech-select
-  #    reads docs/domainspecs/<domain>/commandtechrulemap.md under "## /aw-spec-constitution"
-  #    and loads the technology-constitution base into the sticky standards the TECHNICAL
-  #    half ratifies. Placed FIRST — before the technical half AND before domain-select — so
-  #    the technical author sees only technical files: the seam that keeps it domain-free is
-  #    preserved. No blocking gate: an unconfigured project soft-continues (ai-rules seed only).
-  - id: tech_select
-    action: include
-    module: .aw-spec/orchestrator/modules/tech-select.orch.yaml
-    with: { command: aw-spec-constitution }
-
-  # 1. Ensure both halves exist (copy each template in if missing). Rewrite-in-place
-  #    only — never creates a second template. Composed constitution.md is produced
-  #    later by compose-constitution.
-  - id: setup_constitution
-    action: execute_script
-    script: { ref: actions }
-    subcommand: setup-constitution
-    outputs:
-      - { name: constitution_technical_file, from: "$.constitution_technical_file" }
-      - { name: constitution_domain_file,    from: "$.constitution_domain_file" }
-      - { name: technical_created,           from: "$.technical_created" }
-      - { name: domain_created,              from: "$.domain_created" }
-
-  # 2. Pre-execution hooks: resolve (script) then dispatch (invoking agent).
-  - id: resolve_pre_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "before_constitution"]
-    outputs:
-      - { name: before_hooks, from: "$.hooks" }
-  - id: dispatch_pre_hooks
-    action: dispatch_hooks
-    hooks_from_variable: before_hooks
-
-  # ── TECHNICAL HALF ─────────────────────────────────────────────────────────
-  # Authored FIRST, while the sticky set holds only the technology base + ai-rules
-  # (domain-select has not run yet). This ordering is what guarantees the technical
-  # constitution is domain-free.
-
-  # 3. Context: the technical half (template being filled / file being amended) +
-  #    the spec template for Sync-Impact-Report propagation awareness.
-  - id: gen_technical_ctx
-    action: build_context
-    context:
-      - { path: "{{constitution_technical_file}}" }
-      - { path: .aw-spec/templates/spec-template.md, optional: true }
-
-  # 4. Author the TECHNICAL constitution (rewrite-in-place).
-  - id: gen_technical
-    action: agent_author
-    output_target: { type: file, path: "{{constitution_technical_file}}" }
-    task: |
-      Update the TECHNICAL project constitution (the target file in context). It is
-      a TEMPLATE with [ALL_CAPS] placeholder tokens. This is the domain-AGNOSTIC half.
-      Principles/values supplied by the user: {{USER_INPUT}}
-      Steps:
-      - Fill EVERY placeholder with concrete text; leave no unexplained [BRACKET]
-        tokens (justify any intentionally deferred as TODO(<FIELD>): reason).
-      - Derive values from the user input, the technology-constitution base + ai-rules
-        (in the standards), and repo context — do NOT invent principles.
-      - Author ONLY technology-base principles (the I–XV set) + base folder structure,
-        base conventions/AI rules, and base governance. Do NOT add any domain-specific
-        principle, identifier, terminology, regulatory, or interoperability rule — those
-        belong to the paired constitution.domain.md and MUST NOT appear here.
-      - Bump CONSTITUTION_VERSION by semver (MAJOR incompatible; MINOR new/expanded;
-        PATCH clarifications). This half versions independently of the domain half.
-      - Dates ISO YYYY-MM-DD: RATIFICATION_DATE = original adoption (TODO if unknown);
-        LAST_AMENDED_DATE = today when changed.
-      - Preserve heading hierarchy exactly. Principles declarative and testable.
-      - PREPEND a "Sync Impact Report" as an HTML comment at the very top: version
-        old→new, modified/added/removed principles, dependent artifacts (✅/⚠) + TODOs.
-      Return the complete updated technical constitution content only.
-
-  # 5. Deterministic validation loop for the technical half (max 3 patch passes).
-  - id: technical_validation_loop
-    action: loop
-    while: "{{technical_ok}} != true"
-    max_iterations: 3
-    steps:
-      - id: tech_lint
-        action: execute_script
-        script: { ref: actions }
-        subcommand: constitution-verify
-        args: ["--file", "{{constitution_technical_file}}"]
-        outputs:
-          - { name: technical_ok,     from: "$.ok" }
-          - { name: technical_issues, from: "$.issues" }
-      - id: tech_lint_break
-        action: break
-        condition: "{{technical_ok}} == true"
-      - id: patch_technical
-        action: agent_author
-        context: ["{{constitution_technical_file}}"]
-        include_standards: false        # rewrite-in-place: only the technical half
-        output_target: { type: file, path: "{{constitution_technical_file}}" }
-        task: |
-          Fix these mechanical defects in the technical constitution (target file in
-          context), changing NOTHING else — preserve every principle, the heading
-          hierarchy, and the Sync Impact Report. Fill any listed [ALL_CAPS] placeholder
-          with concrete text (or a justified TODO(<FIELD>): reason); make the body's
-          version line AGREE with the Sync Impact Report's new version; ISO YYYY-MM-DD dates.
-          Defects: {{technical_issues}}
-          Return the complete updated technical constitution content only.
-
-  # ── DOMAIN HALF ────────────────────────────────────────────────────────────
-  # 6. Resolve the active domain + load its rule files into the sticky set (D3).
-  #    Gate Continue/Exit when no domain/comandrulemap; then Select all/subset/none.
-  #    Runs AFTER the technical half is done, so it cannot leak into it.
-  - id: domain_select
-    action: include
-    module: .aw-spec/orchestrator/modules/domain-select.orch.yaml
-    with: { command: aw-spec-constitution }
-
-  # 7. Context for the domain half: the domain template/file + the domain addenda
-  #    source (docs/<domain>-constitution.md). Sticky now also carries the domain
-  #    rule files loaded by domain-select. Skipped when no active domain.
-  - id: gen_domain_ctx
-    action: build_context
-    condition: "{{dg_rulemap_exists}} == true"
-    context:
-      - { path: "{{constitution_domain_file}}" }
-      - { path: "docs/{{domain}}-constitution.my-ref.md", optional: true }
-      - { path: "docs/{{domain}}-constitution.md", optional: true }
-
-  # 8. Author the DOMAIN addenda (rewrite-in-place). Only when a domain is active.
-  - id: gen_domain
-    action: agent_author
-    condition: "{{dg_rulemap_exists}} == true"
-    output_target: { type: file, path: "{{constitution_domain_file}}" }
-    task: |
-      Update the DOMAIN ADDENDA constitution for domain '{{domain}}' (the target file
-      in context). It is a TEMPLATE with [ALL_CAPS] placeholder tokens. This half carries
-      ONLY domain-specific material. Principles/values supplied by the user: {{USER_INPUT}}
-      Steps:
-      - Fill EVERY placeholder with concrete text; leave no unexplained [BRACKET] tokens
-        (justify deferrals as TODO(<FIELD>): reason). NO residual placeholder may remain.
-      - Derive values from the domain addenda source (docs/{{domain}}-constitution.*) and
-        the domain rule files (in the standards) — do NOT invent principles.
-      - Author ONLY the domain layer: domain principles NUMBERED XVI+ (continuing the
-        technical base which ends at XV), domain folder additions, regulatory posture &
-        security addenda, and domain governance overrides. For each domain principle,
-        state which technical principle it EXTENDS. Do NOT restate the technical
-        principles I–XV or the base governance — reference them.
-      - Bump CONSTITUTION_VERSION by semver; this half versions independently of the
-        technical half. Dates ISO YYYY-MM-DD.
-      - Preserve heading hierarchy exactly. PREPEND a "Sync Impact Report" HTML comment:
-        version old→new, changed domain principles, dependent artifacts (✅/⚠) + TODOs.
-      Return the complete updated domain addenda content only.
-
-  # 9. Deterministic validation loop for the domain half (max 3). Skipped if no domain.
-  - id: domain_validation_loop
-    action: loop
-    condition: "{{dg_rulemap_exists}} == true"
-    while: "{{domain_ok}} != true"
-    max_iterations: 3
-    steps:
-      - id: dom_lint
-        action: execute_script
-        script: { ref: actions }
-        subcommand: constitution-verify
-        args: ["--file", "{{constitution_domain_file}}"]
-        outputs:
-          - { name: domain_ok,     from: "$.ok" }
-          - { name: domain_issues, from: "$.issues" }
-      - id: dom_lint_break
-        action: break
-        condition: "{{domain_ok}} == true"
-      - id: patch_domain
-        action: agent_author
-        context: ["{{constitution_domain_file}}"]
-        include_standards: false        # rewrite-in-place: only the domain half
-        output_target: { type: file, path: "{{constitution_domain_file}}" }
-        task: |
-          Fix these mechanical defects in the domain addenda constitution (target file in
-          context), changing NOTHING else — preserve every principle, the heading hierarchy,
-          and the Sync Impact Report. Fill any listed [ALL_CAPS] placeholder (or a justified
-          TODO(<FIELD>): reason); make the body version AGREE with the Sync Impact Report;
-          ISO YYYY-MM-DD dates.
-          Defects: {{domain_issues}}
-          Return the complete updated domain addenda content only.
-
-  # 10. Compose the two halves into the human/compat constitution.md (deterministic).
-  #     Skips the domain half automatically if it is an unauthored template.
-  - id: compose_constitution
-    action: execute_script
-    script: { ref: actions }
-    subcommand: compose-constitution
-    outputs:
-      - { name: composed_file,   from: "$.composed_file" }
-      - { name: domain_included, from: "$.domain_included" }
-
-  # 11. Post-execution hooks.
-  - id: resolve_post_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "after_constitution"]
-    outputs:
-      - { name: after_hooks, from: "$.hooks" }
-  - id: dispatch_post_hooks
-    action: dispatch_hooks
-    hooks_from_variable: after_hooks
-
-outputs:
-  constitution_technical_file: "{{constitution_technical_file}}"
-  constitution_domain_file: "{{constitution_domain_file}}"
-  composed_file: "{{composed_file}}"
-  domain_included: "{{domain_included}}"
-  technical_validation_ok: "{{technical_ok}}"
-  technical_validation_issues: "{{technical_issues}}"
-  domain_validation_ok: "{{domain_ok}}"
-  domain_validation_issues: "{{domain_issues}}"
-  note: "Split constitution authored: constitution.technical.md (technology base, standing input to design + implement) + constitution.domain.md (domain addenda, standing input to specify + a gate checklist), composed into constitution.md. If a validation_ok is false, the matching validation_issues lists what still needs a manual touch. See each half's Sync Impact Report for its version bump. Suggested commit: 'docs: amend split constitution'."
-  next: "Loaded per concern — /aw-spec-orch specify loads constitution.domain.md; design + implement load constitution.technical.md. Re-run /aw-spec-orch constitution to amend."

package/assets/.aw-spec/orchestrator/workflows/aw-spec-demo.orch.yaml

@@ -1,103 +0,0 @@
-# =============================================================================
-# aw-spec-demo.orch.yaml — a runnable demo workflow for the aw-orchestrator.
-# Launch via the parametric skill:  /aw-spec-orch demo [strategy]
-#
-# It walks the exact loop from the diagram:
-#   build_context → agent_generate (fresh) → agent_review (fresh) → repeat
-#
-# Run it (safe, no model calls — prints the assembled payloads):
-#   python3 .aw-spec/orchestrator/orchestrator.py .aw-spec/orchestrator/workflows/aw-spec-demo.orch.yaml
-#
-# Run it for real (spawns fresh `claude -p --bare` per generation):
-#   python3 .aw-spec/orchestrator/orchestrator.py .aw-spec/orchestrator/workflows/aw-spec-demo.orch.yaml \
-#       --transport claude --model opus --budget 0.50
-# =============================================================================
-
-dialect: aw-spec.orchestrator/v1
-name: demo-fresh-generation
-
-vars:
-  out_dir: .aw-spec/orchestrator/.demo-out
-  review_pass: "false"          # loop guard, flipped by agent_review
-
-workflow:
-
-  # 1. Builds Complete Context — the interpreter reads standards (→ system) and
-  #    any prior artifacts (→ user context). Optional files are tolerated so the
-  #    demo runs even if the docs/ tree isn't present.
-  - id: ctx_generate
-    action: build_context
-    system:
-      - { path: docs/architecture/clean-architecture.md, optional: true }
-      - { path: docs/architecture/cqrs.md, optional: true }
-      - { path: docs/glossary/ai-rules.md, optional: true }
-    context:
-      - { path: "{{out_dir}}/spec.md", optional: true }
-
-  # 2. Invoke Claude Code (FRESH generation) — it decides the file path(s) itself
-  #    (per the loaded folder-structure/architecture standards), writes them with
-  #    its tools, and REPORTS the paths back. The interpreter binds that list.
-  - id: gen_handler
-    action: agent_generate
-    tools: "Read,Write,Edit,Bash"
-    permission_mode: acceptEdits
-    task: |
-      Implement a CQRS command handler `CreateOrderHandler` for a "Create Order"
-      feature, following the loaded Clean Architecture + CQRS standards. Keep it
-      compilable C#; no TODOs.
-    outputs:
-      - { name: gen_status,  from: "$.status" }
-      - { name: gen_summary, from: "$.summary" }
-      - { name: gen_files,   from: "$.files" }    # the paths the agent chose
-
-  # 3. Review the current output — a SECOND fresh generation, read-only, that
-  #    judges the files the generation reported and returns pass/issues.
-  - id: review_handler
-    action: agent_review
-    review_of_var: gen_files
-    task: |
-      Review the handler for compliance with the loaded standards (naming, layer
-      boundaries, CQRS separation). Decide pass/fail.
-    outputs:
-      - { name: review_pass,   from: "$.pass" }
-      - { name: review_issues, from: "$.issues" }
-
-  # 4. If review failed, rebuild context (now including the issues) and
-  #    regenerate — up to 3 times. This is the "…continues" cycle.
-  - id: revise
-    action: loop
-    while: "{{review_pass}} != true"
-    max_iterations: 3
-    steps:
-      - id: ctx_revise
-        action: build_context
-        vars:
-          issues: "{{review_issues}}"
-        system:
-          - { path: docs/architecture/clean-architecture.md, optional: true }
-          - { path: docs/architecture/cqrs.md, optional: true }
-        context_from: gen_files            # the files the agent chose last round
-      - id: regen
-        action: agent_generate
-        tools: "Read,Write,Edit"
-        task: |
-          Fix these review issues in the file(s) provided in context, preserving
-          everything already correct: {{issues}}
-        outputs:
-          - { name: gen_files, from: "$.files" }
-      - id: rereview
-        action: agent_review
-        review_of_var: gen_files
-        task: Re-review after the fix. Decide pass/fail.
-        outputs:
-          - { name: review_pass,   from: "$.pass" }
-          - { name: review_issues, from: "$.issues" }
-      - id: stop_when_pass
-        action: break
-        condition: "{{review_pass}} == true"
-
-outputs:
-  generated: "{{gen_summary}}"
-  review_pass: "{{review_pass}}"
-  files: "{{gen_files}}"          # decided by the fresh agent, not the interpreter
-  next: "interpreter continues to the next workflow step"

package/assets/.aw-spec/orchestrator/workflows/aw-spec-dependency-tree.orch.yaml

@@ -1,69 +0,0 @@
-# =============================================================================
-# aw-spec-dependency-tree (orchestrator) — MR-0.1 of the Migration Pipeline
-#
-# Scans OKF knowledge bundles (knowledge/) and specs/ across all aggregates,
-# parses Depends-On and Cross-References relationships, runs deterministic
-# topological wave sorting, traps circular dependency deadlocks, and emits the
-# final migration hierarchy tree (specs/migration-tree.md + specs/migration-sequence.json).
-#
-# Zero LLM for tree calculation: pure deterministic script orchestration via aw-xref.py.
-#
-# Launch:
-#   /aw-spec-orch dependency-tree
-#   /aw-spec-orch tree
-# =============================================================================
-
-name: aw-spec-dependency-tree
-description: Scan OKF knowledge bundles and specs across all aggregates, parse Depends-On and Cross-References relationships, run topological wave sorting, trap circular dependency deadlocks, and emit the final migration hierarchy tree (specs/migration-tree.md + specs/migration-sequence.json).
-version: 1.0.0
-agent_agnostic: true
-dialect: aw-spec.orchestrator/v1
-
-inputs:
-  user_input:
-    description: Optional path hints or focus scope.
-    required: false
-    bind: USER_INPUT
-
-scripts:
-  xref:
-    sh:  .aw-spec/scripts/bash/aw-xref.sh
-    ps1: .aw-spec/scripts/powershell/aw-xref.ps1
-
-vars:
-  aggregate_count: "0"
-  wave_count: "0"
-  has_cycles: "false"
-  tree_file: ""
-  sequence_file: ""
-
-workflow:
-
-  # 1. Deterministic graph construction & topological wave sorting via aw-xref.py tree
-  - id: generate_tree
-    action: execute_script
-    script: { ref: xref }
-    subcommand: tree
-    outputs:
-      - { name: aggregate_count, from: "$.aggregate_count" }
-      - { name: wave_count,      from: "$.wave_count" }
-      - { name: has_cycles,      from: "$.has_cycles" }
-      - { name: tree_file,       from: "$.tree_file" }
-      - { name: sequence_file,   from: "$.sequence_file" }
-
-  # 2. Cycle warning gate
-  - id: check_cycles
-    action: verify_context
-    require_value: has_cycles
-    equals: "false"
-    on_mismatch: stop
-    on_mismatch_message: "Circular dependency detected among aggregates (see {{tree_file}}). Seam refactoring is required to break circular dependencies before executing the migration sequence."
-
-outputs:
-  aggregate_count: "{{aggregate_count}}"
-  wave_count: "{{wave_count}}"
-  has_cycles: "{{has_cycles}}"
-  tree_file: "{{tree_file}}"
-  sequence_file: "{{sequence_file}}"
-  note: "Migration Hierarchy Tree generated in {{tree_file}} and {{sequence_file}}."
-  next: "Human Gate H0.1: Review specs/migration-tree.md and proceed to /aw-spec-orch mr per slice."

package/assets/.aw-spec/orchestrator/workflows/aw-spec-deploy.orch.yaml

@@ -1,85 +0,0 @@
-# =============================================================================
-# aw-spec-deploy (orchestrator) — push to the deployment pipeline
-#
-# Config-driven: runs the command in .aw-spec/deploy.json {"command": "..."}.
-# Unconfigured = a clear no-op that reports how to wire it (never a false
-# success claim of an actual deploy). Post-deploy hooks carry smoke/rollback.
-#
-# Launch:  /aw-spec-orch deploy [strategy]
-# =============================================================================
-
-name: aw-spec-deploy
-description: Push the feature to the configured deployment pipeline (.aw-spec/deploy.json), with pre/post hooks for smoke checks and rollback.
-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:
-  deploy_ok: "false"
-
-workflow:
-
-  - 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" }
-
-  - 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 deploy."
-
-  # Pre-deploy hooks (e.g. a final smoke/build gate configured by the project).
-  - id: resolve_pre_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "before_deploy"]
-    outputs:
-      - { name: before_hooks, from: "$.hooks" }
-  - id: dispatch_pre_hooks
-    action: dispatch_hooks
-    hooks_from_variable: before_hooks
-
-  - id: deploy
-    action: execute_script
-    on_error: continue
-    script: { ref: actions }
-    subcommand: deploy-dispatch
-    outputs:
-      - { name: deploy_ok,   from: "$.ok" }
-      - { name: configured,  from: "$.configured" }
-      - { name: deploy_log,  from: "$.log_tail" }
-
-  - id: deploy_gate
-    action: verify_context
-    require_true: deploy_ok
-    on_false: stop
-    on_false_message: "Deploy command failed. Log: {{deploy_log}}"
-
-  # Post-deploy hooks: smoke checks and, on failure, rollback (project-configured).
-  - id: resolve_post_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "after_deploy"]
-    outputs:
-      - { name: after_hooks, from: "$.hooks" }
-  - id: dispatch_post_hooks
-    action: dispatch_hooks
-    hooks_from_variable: after_hooks
-
-outputs:
-  feature_dir: "{{feature_dir}}"
-  deployed: "{{configured}}"
-  note: "Set .aw-spec/deploy.json {\"command\": \"...\"} to enable an actual deploy; add smoke/rollback via before_deploy/after_deploy hooks."
-  next: "done"