aw-spec-cli 0.1.5 → 0.1.6

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

@@ -1,293 +0,0 @@
-# =============================================================================
-# aw-spec-parity (orchestrator) — the CUTOVER GATE of the Brownfield Pipeline
-#
-# The migration-grade oracle. Once a slice has a new (candidate) implementation
-# (forward pipeline) and a green characterization fence, PARITY runs every case
-# in a manifest against BOTH the running LEGACY system and the new CANDIDATE and
-# diffs observable output (response status + body, and optional resulting-state
-# probes). The seam cuts over to the candidate ONLY when parity HOLDS — the
-# running legacy system is the oracle, not a written spec.
-#
-#   inventory → adopt → characterize → [ forward pipeline ] → PARITY → cutover   ← you are here
-#
-# Parity is what analyze-slice/characterize can't be: it compares against a LIVE oracle,
-# so it catches behaviour no static test captured. Approved intended differences
-# are whitelisted in the manifest's `expected_deviations` — and each MUST be
-# recorded as a MODIFIED spec item via the CR loop, so behaviour never drifts
-# silently.
-#
-# Two things the operator supplies (the pipeline cannot guess them): WHERE the
-# legacy and candidate systems are running (the two `sides` in the manifest).
-# parity AUTHORS the input corpus from the spec + source-map, then STOPS for you
-# to fill the endpoints, then diffs on re-run.
-#
-# On a mismatch: triage — a REGRESSION is fixed in the CANDIDATE code (to match
-# legacy); an INTENDED difference is added to expected_deviations (+ recorded as a
-# MODIFIED spec item via /aw-spec-orch specify). parity never changes the spec here and
-# never forces a match by breaking the candidate.
-#
-# Launch:  /aw-spec-orch parity [strategy] [focus/guidance]
-# Prereq:  /aw-spec-orch adopt (spec.md + design.md + source-map.md) + a running
-#          candidate, and the legacy system reachable.
-# =============================================================================
-
-name: aw-spec-parity
-description: Run a parity manifest's cases against the running legacy system and the new candidate, diff observable output, and gate cutover on parity holding. Authors the corpus from the spec + source-map; the operator supplies the two endpoints. Mismatches are triaged (fix the candidate, or whitelist an intended deviation that must become a MODIFIED spec item). The live legacy system is the oracle.
-version: 1.0.0
-agent_agnostic: true
-dialect: aw-spec.orchestrator/v1
-
-inputs:
-  user_input:
-    description: Optional focus / guidance (an area or extra input cases to cover).
-    required: false
-    bind: USER_INPUT
-
-scripts:
-  parity:
-    sh:  .aw-spec/scripts/bash/aw-parity.sh
-    ps1: .aw-spec/scripts/powershell/aw-parity.ps1
-  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 code-generation
-# set (triage may fix the CANDIDATE code to match legacy) is no longer hardcoded here — it is
-# now CONFIGURATION, loaded per-command from docs/domainspecs/<domain>/commandtechrulemap.md
-# under "## /aw-spec-parity" by the tech-select module (see the tech_select step below). No
-# domain files: the target behaviour is defined by the running legacy system, not domain rules —
-# the tech map lists only technical files. (parity does not reference constitution.technical.md.)
-standards:
-  - { path: docs/glossary/ai-rules.md, optional: true }
-
-vars:
-  parity_ok: "false"
-  case_count: "0"
-  sides_configured: "false"
-
-workflow:
-
-  # 0. TECHNICAL rule files → sticky standards (configuration, not hardcoded). tech-select
-  #    reads docs/domainspecs/<domain>/commandtechrulemap.md under "## /aw-spec-parity" and
-  #    loads that code-generation set into the sticky standards the agent_generate triage step
-  #    ALWAYS prepends. No domain rule file is loaded here — the tech map lists only technical
-  #    files. No blocking gate: an unconfigured project soft-continues (the target behaviour is
-  #    the running legacy system, not any rule file).
-  - id: tech_select
-    action: include
-    module: .aw-spec/orchestrator/modules/tech-select.orch.yaml
-    with: { command: aw-spec-parity }
-
-  # 1. Resolve the feature + require the adopted artifacts (spec/design/source-map).
-  - 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: design_file,   from: "$.design_file" }
-      - { name: spec_exists,   from: "$.spec_exists" }
-      - { name: design_exists, from: "$.design_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 parity."
-
-  - id: verify_spec
-    action: verify_context
-    require_true: spec_exists
-    on_false: stop
-    on_false_message: "No spec.md for the current feature. Adopt the slice first: /aw-spec-orch adopt <Aggregate>."
-
-  - id: verify_design
-    action: verify_context
-    require_true: design_exists
-    on_false: stop
-    on_false_message: "No design.md for the current feature. Run /aw-spec-orch adopt <Aggregate> (or /aw-spec-orch design) first."
-
-  - id: set_source_map
-    action: set
-    vars:
-      source_map: "{{feature_dir}}/source-map.md"
-  # required_files raises a fixed Stop naming the missing file → run adopt first.
-  - id: require_source_map
-    action: verify_context
-    required_files: ["{{source_map}}"]
-
-  # 2. Scaffold the parity manifest (idempotent — keeps an existing one, incl. the
-  #    operator's endpoints and any cases already authored).
-  - id: scaffold_parity
-    action: execute_script
-    script: { ref: parity }
-    subcommand: scaffold
-    args: ["--feature-dir", "{{feature_dir}}"]
-    outputs:
-      - { name: manifest_path, from: "$.manifest_path" }
-
-  # 3. Read current manifest readiness BEFORE authoring, so cases are only authored
-  #    once (a re-run after the operator fills endpoints skips authoring).
-  - id: check_initial
-    action: execute_script
-    script: { ref: parity }
-    subcommand: check
-    args: ["--manifest", "{{manifest_path}}"]
-    outputs:
-      - { name: case_count,       from: "$.case_count" }
-      - { name: sides_configured, from: "$.sides_configured" }
-
-  # 4. Pre-execution hooks.
-  - id: resolve_pre_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "before_parity"]
-    outputs:
-      - { name: before_hooks, from: "$.hooks" }
-  - id: dispatch_pre_hooks
-    action: dispatch_hooks
-    hooks_from_variable: before_hooks
-
-  # 5. AUTHOR the parity corpus (only when no real cases exist yet). Derive cases
-  #    from the spec's US/FR and the source-map's as-built quirks. Edits ONLY the
-  #    `cases` array — the operator owns `sides`.
-  - id: ctx_author_cases
-    condition: "{{case_count}} == 0"
-    action: build_context
-    context:
-      - { path: "{{manifest_path}}" }             # the manifest to edit (cases only)
-      - { path: "{{spec_file}}" }                 # US / FR / SC — the observable surface
-      - { path: "{{source_map}}" }                # as-built quirks (each MUST get a case)
-      - { path: "{{design_file}}" }               # endpoints / handlers / events
-  - id: author_cases
-    condition: "{{case_count}} == 0"
-    action: agent_generate
-    tools: "Read,Write,Edit"
-    permission_mode: acceptEdits
-    task: |
-      Author the PARITY CORPUS by editing the `cases` array of the parity manifest
-      (in context) — the inputs whose outputs must match between the running legacy
-      system and the new candidate. Guidance: {{USER_INPUT}}
-      Rules:
-      - Derive cases from the spec's User Stories / FR / Success Criteria (in context)
-        and the design's endpoints/handlers: one case per observable behaviour, with
-        representative inputs — the happy path, boundaries, and error paths.
-      - Every AS-BUILT QUIRK recorded in source-map.md (in context) MUST get a case
-        that will confirm the candidate REPRODUCES it (parity fails if the new code
-        "fixes" a quirk that was not turned into an intended deviation).
-      - Each case: a stable `id` (PC-002, PC-003, …), a `description`, `spec_ids`, a
-        `request` (method/path/headers/body — compared on status + body), and — where
-        resulting STATE matters — an optional `state_probe` request (a follow-up
-        read compared on body). Use the routes/fields the design + code actually use.
-      - Edit ONLY the `cases` array. Preserve `sides`, `compare`, `expected_deviations`
-        and every other key BYTE-FOR-BYTE (the operator owns the two `sides`
-        endpoints). Remove the PC-001-EXAMPLE placeholder. Emit VALID JSON.
-    outputs:
-      - { name: authored, from: "$.files" }
-
-  # 6. Re-read readiness after authoring.
-  - id: check_ready
-    action: execute_script
-    script: { ref: parity }
-    subcommand: check
-    args: ["--manifest", "{{manifest_path}}"]
-    outputs:
-      - { name: case_count,       from: "$.case_count" }
-      - { name: sides_configured, from: "$.sides_configured" }
-      - { name: check_error,      from: "$.error" }
-
-  - id: cases_gate
-    action: verify_context
-    require_true: case_count
-    on_false: stop
-    on_false_message: "No parity cases in {{manifest_path}} (check error: {{check_error}}). Authoring produced none or the JSON is invalid — add cases by hand (derived from the spec + source-map) and re-run."
-
-  # 7. OPERATOR HANDOFF: the two `sides` endpoints cannot be guessed. Stop here until
-  #    they are filled (where the legacy + candidate systems are running).
-  - id: sides_gate
-    action: verify_context
-    require_true: sides_configured
-    on_false: stop
-    on_false_message: "Parity corpus is ready ({{case_count}} case(s)), but the endpoints are not set. Edit {{manifest_path}} → set sides.legacy and sides.candidate to where your LEGACY and NEW systems are running (kind:http base_url, or kind:shell command), then re-run /aw-spec-orch parity."
-
-  # 8. PARITY + TRIAGE loop: run both sides + diff; on mismatch, fix the CANDIDATE
-  #    (regression) or whitelist an INTENDED deviation, then re-run. Bounded (3×).
-  - id: parity_loop
-    action: loop
-    while: "{{parity_ok}} != true"
-    max_iterations: 3
-    steps:
-      - id: run_parity
-        action: execute_script
-        on_error: continue
-        script: { ref: parity }
-        subcommand: run
-        args: ["--manifest", "{{manifest_path}}"]
-        outputs:
-          - { name: parity_ok,   from: "$.ok" }
-          - { name: mismatched,  from: "$.mismatched" }
-          - { name: matched,     from: "$.matched" }
-          - { name: par_errors,  from: "$.errors" }
-          - { name: report_path, from: "$.report_path" }
-      - id: hold_break
-        action: break
-        condition: "{{parity_ok}} == true"
-      - id: ctx_triage
-        action: build_context
-        context:
-          - { path: "{{report_path}}" }           # the unaccepted diffs + accepted deviations
-          - { path: "{{manifest_path}}" }         # to add expected_deviations
-          - { path: "{{spec_file}}" }
-          - { path: "{{source_map}}" }
-      - id: triage
-        action: agent_generate
-        tools: "Read,Write,Edit,Bash"
-        permission_mode: acceptEdits
-        task: |
-          Parity did not hold. Triage EACH unaccepted diff in the report (in context)
-          — the LEGACY output is the oracle:
-          - REGRESSION (the candidate is wrong): fix the CANDIDATE (new) code so its
-            observable output matches legacy. Read the candidate code, correct it, and
-            keep behaviour aligned with the legacy value shown in the report. Never
-            change the legacy side, and never edit a test just to hide the diff.
-          - INTENDED difference (a deliberate modernization): add an entry to the
-            manifest's `expected_deviations` ({case, path, reason}) so parity accepts
-            it — AND state in the reason that it must be recorded as a MODIFIED spec
-            item via /aw-spec-orch specify (do NOT edit spec.md here, and do NOT change code
-            to force a match). An as-built quirk the candidate dropped is a REGRESSION
-            unless it is a reviewed intended change.
-          - INVOKE ERROR (a side unreachable / bad request): report it — the operator
-            must make both systems reachable / fix the case; do not fake a pass.
-          Change ONLY candidate code and/or the manifest's expected_deviations.
-          Report:
-          {{report_path}}
-        outputs:
-          - { name: triaged_files, from: "$.files" }
-
-  - id: parity_gate
-    action: verify_context
-    require_true: parity_ok
-    on_false: stop
-    on_false_message: "Parity does NOT hold after 3 attempts ({{mismatched}} mismatch(es), {{par_errors}} error(s)). See {{report_path}}. Resolve each unaccepted diff — fix the candidate to match legacy, or whitelist an intended deviation (and record it as a MODIFIED spec item via /aw-spec-orch specify) — then re-run. Do NOT cut over until parity holds."
-
-  # 9. Post-execution hooks.
-  - id: resolve_post_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "after_parity"]
-    outputs:
-      - { name: after_hooks, from: "$.hooks" }
-  - id: dispatch_post_hooks
-    action: dispatch_hooks
-    hooks_from_variable: after_hooks
-
-outputs:
-  feature_dir: "{{feature_dir}}"
-  manifest_path: "{{manifest_path}}"
-  report_path: "{{report_path}}"
-  matched: "{{matched}}"
-  next: "PARITY HOLDS — the slice is cutover-ready. Route the seam to the candidate (Run/Deploy); the legacy path goes dark and roll back = re-route. Fold every accepted deviation into spec.md as a MODIFIED item via /aw-spec-orch specify. Repeat inventory→adopt→characterize→parity for the next slice."

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

@@ -1,177 +0,0 @@
-# =============================================================================
-# aw-spec-run (orchestrator) — migrate + prepare to run
-#
-# Apply database migrations; on failure fix (up to 3×) and record the touched files
-# in the slice's OKF concept; then surface the launch command. A live server is not
-# held by the batch engine — the launch hint is reported for the user/agent to start.
-# Run after /aw-spec-orch analyze-slice.
-#
-# 1.1.0 — the fix loop's file list now comes from the OKF concept's `source_files`
-# (`aw-xref concept-paths`) instead of the retired `design-paths` scan for
-# ```lang path=… fences, and the tail step records fix-loop files in that concept
-# instead of copying file bodies back into design fences (`design-reconcile`).
-#
-# Launch:  /aw-spec-orch run [strategy]
-# =============================================================================
-
-name: aw-spec-run
-description: Apply migrations, fix migration/runtime errors, record the touched files in the slice's knowledge concept, and report the launch command.
-version: 1.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
-  xref:
-    sh:  .aw-spec/scripts/bash/aw-xref.sh
-    ps1: .aw-spec/scripts/powershell/aw-xref.ps1
-
-# No hardcoded technical standards seed (run never had ai-rules). The technical rule file
-# the migration step works against (persistence) is now CONFIGURATION, loaded per-command from
-# docs/domainspecs/<domain>/commandtechrulemap.md under "## /aw-spec-run" by the tech-select
-# module (see the tech_select step below). No domain files; run does not reference
-# constitution.technical.md. (missing files skipped at assembly time)
-standards: []
-
-vars:
-  migrate_ok: "false"
-
-workflow:
-
-  # 0. TECHNICAL rule files → sticky standards (configuration, not hardcoded). tech-select
-  #    reads docs/domainspecs/<domain>/commandtechrulemap.md under "## /aw-spec-run" and loads
-  #    that set (persistence) into the sticky standards the agent_generate migration step ALWAYS
-  #    prepends. No domain rule file here. No blocking gate: an unconfigured project soft-continues.
-  - id: tech_select
-    action: include
-    module: .aw-spec/orchestrator/modules/tech-select.orch.yaml
-    with: { command: aw-spec-run }
-
-  - 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 run."
-
-  # The slice's source files, from its OKF concept — what the migration fix loop below is
-  # handed. Replaces the retired `design-paths` fence scan (the tech-agnostic design.md
-  # carries no ```lang path=… code blocks, so it returned nothing and the fixer got an
-  # EMPTY context). Read-only, exits 0 with paths=[] when there is no concept yet, and
-  # on_error: continue so a missing bundle can never block a migration.
-  - id: concept_paths
-    action: execute_script
-    on_error: continue
-    script: { ref: xref }
-    subcommand: concept-paths
-    args: ["--feature-dir", "{{feature_dir}}"]
-    outputs:
-      - { name: all_paths,     from: "$.paths" }
-      - { name: paths_missing, from: "$.missing" }
-
-  - id: resolve_pre_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "before_run"]
-    outputs:
-      - { name: before_hooks, from: "$.hooks" }
-  - id: dispatch_pre_hooks
-    action: dispatch_hooks
-    hooks_from_variable: before_hooks
-
-  # Migrate → (if red) fix → re-migrate, up to 3×.
-  - id: migrate_loop
-    action: loop
-    while: "{{migrate_ok}} != true"
-    max_iterations: 3
-    steps:
-      - id: migrate
-        action: execute_script
-        on_error: continue
-        script: { ref: actions }
-        subcommand: run-migrate
-        args: ["--feature-dir", "{{feature_dir}}"]
-        outputs:
-          - { name: migrate_ok,   from: "$.ok" }
-          - { name: migrate_tool, from: "$.tool" }
-          - { name: migrate_log,  from: "$.log_tail" }
-      - id: green_break
-        action: break
-        condition: "{{migrate_ok}} == true"
-      - id: ctx_fix
-        action: build_context
-        vars:
-          migrate_log: "{{migrate_log}}"
-        context_from: all_paths
-      - id: fix
-        action: agent_generate
-        tools: "Read,Write,Edit,Bash"
-        permission_mode: acceptEdits
-        task: |
-          A migration/runtime step failed. Fix the migration or configuration in
-          the files in context (usually the Infra layer), preserving intent. Log:
-          {{migrate_log}}
-        outputs:
-          - { name: fixed_files, from: "$.files" }
-
-  - id: run_gate
-    action: verify_context
-    require_true: migrate_ok
-    on_false: stop
-    on_false_message: "Migration still failing after 3 fix attempts. Last log: {{migrate_log}}"
-
-  # Record what the migration fix loop touched in the slice's OKF concept. Replaces the
-  # retired `design-reconcile` (which copied file bodies back into design fences — a
-  # silent no-op since design.md stopped carrying code). The fix loop can CREATE files
-  # (a new migration, a config) that implement never recorded. UNION (--merge), never
-  # replace. Advisory: conditioned + on_error: continue, never gated.
-  - id: okf_merge_run_fixes
-    action: execute_script
-    condition: "{{fixed_files}}"
-    on_error: continue
-    script: { ref: xref }
-    subcommand: concept-upsert
-    args: ["--feature-dir", "{{feature_dir}}", "--source-files", "{{fixed_files}}", "--merge"]
-    outputs:
-      - { name: okf_concept, from: "$.concept" }
-
-  # Surface the launch command (does not start a long-lived server).
-  - id: locate_host
-    action: execute_script
-    on_error: continue
-    script: { ref: actions }
-    subcommand: find-host-project
-    outputs:
-      - { name: host_found,   from: "$.found" }
-      - { name: host_project, from: "$.project_dir" }
-
-  - id: resolve_post_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "after_run"]
-    outputs:
-      - { name: after_hooks, from: "$.hooks" }
-  - id: dispatch_post_hooks
-    action: dispatch_hooks
-    hooks_from_variable: after_hooks
-
-outputs:
-  feature_dir: "{{feature_dir}}"
-  migrate_tool: "{{migrate_tool}}"
-  okf_concept: "{{okf_concept}}"
-  # Declared in the concept but absent on disk — advisory index drift, never gated.
-  stale_source_files: "{{paths_missing}}"
-  host_project: "{{host_project}}"
-  launch_hint: "dotnet run --project {{host_project}} (if .NET)"
-  next: "/aw-spec-orch deploy"

package/assets/.aw-spec/orchestrator/workflows/aw-spec-select-domain.orch.yaml

@@ -1,79 +0,0 @@
-# =============================================================================
-# aw-spec-select-domain (orchestrator) — select the active domain-specs folder
-#
-# Pure orchestration/governance, NO generation: scripts + one gate + one HITL select.
-# Exercises the D1 interaction channel: under ANY strategy the `user_select`
-# step suspends via --checkpoint (kind 'select') so the LAUNCHING agent asks
-# the user; headless runs prefill with --input, --select select_domain=<name>,
-# or --non-interactive.
-#
-# Run (interactive via launcher):
-#   python3 .aw-spec/orchestrator/orchestrator.py \
-#     .aw-spec/orchestrator/workflows/aw-spec-select-domain.orch.yaml \
-#     --checkpoint .aw-spec/orchestrator/.state/select-domain.state.json --json
-# =============================================================================
-
-name: aw-spec-select-domain
-description: Select the active domain-specs folder and store it in .aw-spec/domain.json so all AW-Spec commands load the right domain rule files.
-version: 1.0.0
-agent_agnostic: true
-dialect: aw-spec.orchestrator/v1
-
-inputs:
-  user_input:
-    description: Optional domain folder name to set directly (e.g. healthcare).
-    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
-
-workflow:
-
-  # 1. Discover candidate domains = immediate subdirs of docs/domainspecs.
-  - id: list_domains
-    action: execute_script
-    script: { ref: actions }
-    subcommand: list-domains
-    outputs:
-      - { name: domains, from: "$.domains" }
-
-  # 2. Stop early if there are no domains to choose from.
-  - id: guard_no_domains
-    action: verify_context
-    require_non_empty: domains
-    on_empty_message: >
-      No domains found. Create docs/domainspecs/<name>/comandrulemap.md
-      (laid out like the healthcare one), then re-run.
-    on_empty: stop
-
-  # 3. Choose the domain. If USER_INPUT names a valid domain it is used directly;
-  #    otherwise the launcher relays the choice to the user. One option => confirm.
-  - id: select_domain
-    action: user_select
-    prompt: "Select the active domain:"
-    options_from_variable: domains
-    preselect_from: USER_INPUT     # direct-argument fast path
-    single_option_confirm: true
-    outputs:
-      - { name: chosen, from: selection }
-
-  # 4. Persist the choice to .aw-spec/domain.json and report map status.
-  - id: set_domain
-    action: execute_script
-    script: { ref: actions }
-    subcommand: set-domain
-    args: ["--domain", "{{chosen}}"]
-    outputs:
-      - { name: domain,     from: "$.domain" }
-      - { name: map_path,   from: "$.map_path" }
-      - { name: map_exists, from: "$.map_exists" }
-
-outputs:
-  domain: "{{domain}}"
-  comandrulemap: "{{map_path}}"
-  comandrulemap_exists: "{{map_exists}}"
-  note: "Active domain '{{domain}}' persisted to .aw-spec/domain.json. It selects TWO rule maps under docs/domainspecs/{{domain}}/ — comandrulemap.md (DOMAIN rules; read by constitution + specify only, because the spec is the pivot) and commandtechrulemap.md (TECHNICAL rules; read by 10 workflows incl. design, implement, build and run). comandrulemap_exists reports the domain half only. A map that is absent, or a command with no heading in one, loads nothing for that class and SOFT-CONTINUES — an absent heading is a valid state, never a failure."
-  next: "/aw-spec-orch select-feature   (then specify — the per-feature path). Re-run /aw-spec-orch select-domain any time to switch domains; it rebinds both maps at once."

package/assets/.aw-spec/orchestrator/workflows/aw-spec-select-feature.orch.yaml

@@ -1,128 +0,0 @@
-# =============================================================================
-# aw-spec-select-feature (orchestrator) — pick or create the active FEATURE
-#
-# feature = AGGREGATE (e.g. Order). This is the FIRST step of the spec-anchored
-# pipeline: it fixes the aggregate boundary BEFORE any spec/design exists, so the
-# feature's single spec.md + design.md and every command (CreateOrder/UpdateOrder =
-# user stories) hang off one directory. It replaces guessing the aggregate out of prose in
-# `specify` — that is why finding #1 (feature=aggregate) is enforced here, not hoped for.
-#
-# The pickable list is TWO merged sources (deduped by name): specs/ sub-folders
-# (features already scaffolded/adopted) AND the OKF bundle's Aggregate concepts —
-# the brownfield feature map `/aw-spec-orch onboard` reverse-engineers. So in a
-# brownfield repo you pick a real discovered code feature BEFORE anything is under
-# specs/; on greenfield (no bundle) the list is specs-only, exactly as before.
-#
-# ZERO LLM: only scripts + one select + (conditionally) one ask. No generation,
-# no standards, no domain-select. Pure, deterministic orchestration/governance.
-#
-#   list-features (specs/ ∪ OKF aggregates) → user_select (existing | "+ create new") → [ask name] → set-feature
-#
-# Persists .aw-spec/feature.json {"feature_directory":"specs/<Feature>"} so every
-# later command operates on it: the forward loop (specify/design/analyze-design/implement/
-# build/analyze-slice/run/deploy) and the CR loop (analyze-delta-design/implement-delta/
-# finalize-delta/close-delta — the standalone `cr` is retired; specify and design author
-# the delta docs themselves).
-#
-# Launch:
-#   /aw-spec-orch select-feature                 # interactive: list + add-new
-#   /aw-spec-orch select-feature Order           # direct: create-or-select Order
-# =============================================================================
-
-name: aw-spec-select-feature
-description: Pick an existing feature (aggregate) or create a new one, and store it in .aw-spec/feature.json so every AW-Spec command operates on it. Zero LLM — scripts + one selection only.
-version: 1.0.0
-agent_agnostic: true
-dialect: aw-spec.orchestrator/v1
-
-inputs:
-  user_input:
-    description: Optional feature (aggregate) name to create or select directly, e.g. Order.
-    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
-
-vars:
-  new_sentinel: "+ Create a new feature"   # source of truth is list-features $.sentinel; overwritten below
-  typed_name: ""
-  target_name: ""
-  bundle_dir: "knowledge"                   # where /aw-spec-orch onboard writes the OKF feature map (repo-root default)
-
-workflow:
-
-  # 1. Enumerate selectable aggregates from TWO merged sources (deduped by name):
-  #    specs/ sub-folders (already scaffolded/adopted) AND the OKF bundle's
-  #    Aggregate concepts — the brownfield feature map onboard reverse-engineers,
-  #    so a not-yet-adopted code feature is pickable before its specs/ dir exists.
-  #    On greenfield (no bundle) the OKF source is empty → specs-only, as before.
-  #    `select_options` carries the "+ create new" sentinel and (when USER_INPUT
-  #    names a not-yet feature) that name injected — a direct arg is one-list select.
-  - id: list_features
-    action: execute_script
-    script: { ref: actions }
-    subcommand: list-features
-    args: ["--preselect", "{{USER_INPUT}}", "--bundle", "{{bundle_dir}}"]
-    outputs:
-      - { name: features,       from: "$.features" }
-      - { name: feature_names,  from: "$.names" }
-      - { name: feature_count,  from: "$.count" }
-      - { name: select_options, from: "$.select_options" }
-      - { name: new_sentinel,   from: "$.sentinel" }
-
-  # 2. Choose. A matching USER_INPUT auto-selects (existing OR injected-new) with
-  #    no prompt; the lone sentinel at bootstrap (no features yet) auto-confirms.
-  - id: pick
-    action: user_select
-    prompt: "Select a feature (the aggregate, e.g. Order) — or create a new one:"
-    options_from_variable: select_options
-    preselect_from: USER_INPUT
-    single_option_confirm: true
-    outputs:
-      - { name: chosen, from: selection }
-
-  # 3. Only when the user chose "+ create new" (or bootstrapped) do we ask a name.
-  - id: ask_new_name
-    action: ask
-    condition: "{{chosen}} == {{new_sentinel}}"
-    prompt: >
-      Name the new feature — this is the AGGREGATE root (e.g. Order, Invoice,
-      Customer), NOT a single command. Operations like CreateOrder / UpdateOrder
-      become user stories inside it:
-    answer_var: typed_name
-
-  # 4. Coalesce the target name. The engine has no compound conditions, so this
-  #    is two ordered sets: default to the pick, then override with the typed
-  #    name only on the "create new" branch.
-  - id: name_from_pick
-    action: set
-    vars: { target_name: "{{chosen}}" }
-  - id: name_from_new
-    action: set
-    condition: "{{chosen}} == {{new_sentinel}}"
-    vars: { target_name: "{{typed_name}}" }
-
-  # 5. Create-or-select the aggregate dir + persist it as the active feature.
-  - id: set_feature
-    action: execute_script
-    script: { ref: actions }
-    subcommand: set-feature
-    args: ["--feature", "{{target_name}}"]
-    outputs:
-      - { name: feature,     from: "$.feature" }
-      - { name: feature_dir, from: "$.feature_dir" }
-      - { name: spec_file,   from: "$.spec_file" }
-      - { name: existed,     from: "$.existed" }
-      - { name: created,     from: "$.created" }
-      - { name: spec_exists, from: "$.spec_exists" }
-
-outputs:
-  feature: "{{feature}}"
-  feature_dir: "{{feature_dir}}"
-  created: "{{created}}"
-  spec_exists: "{{spec_exists}}"
-  note: "Active feature set in .aw-spec/feature.json — the aggregate boundary for its single spec.md + design.md."
-  next: "/aw-spec-orch specify <what this feature does>   (authors {{feature_dir}}/spec.md; each operation = a user story)"