aw-spec-cli 0.1.5 → 0.1.6

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

@@ -1,382 +0,0 @@
-# =============================================================================
-# aw-spec-finalize-delta (orchestrator) — MERGE the delta into the master docs
-#
-# The fourth of the five CR stages. Fold the open change's delta docs into the single
-# master spec.md + design.md (doc-first merge) and refresh the cross-slice edges from
-# the now-merged design. After this the master docs describe the shipped-plus-change
-# state — but THE CHANGE REMAINS OPEN.
-#
-#   specify → design → analyze-delta-design → implement-delta → build
-#       → finalize-delta   ← you are here
-#       → analyze-slice → close-delta
-#
-# MERGE HERE, CLOSE LATER. Archiving the change + bumping the version used to happen in
-# this stage; both moved to close-delta, which runs AFTER analyze-slice. The split buys
-# two things:
-#   1. analyze-slice reads a master spec.md that ALREADY carries the change, so its fix
-#      loops repair code against the true current requirements — no delta-awareness, no
-#      risk of "fixing" the change's new tests back toward pre-change behaviour.
-#   2. A red analyze-slice still lands on an OPEN change, so the remedy is "fix and
-#      re-run" rather than a NEW change to repair the one already shipped.
-# The downstream fence below still guards the MERGE (a change that breaks a dependent
-# must not reach the master docs); close-delta guards nothing — it is the bookkeeping.
-#
-# Prereqs: run /aw-spec-orch implement-delta then build first (the delta's code is
-# generated and compiles), so after the merge the master docs and the code agree.
-# finalize-delta edits ONLY the two master docs; it does not generate code.
-#
-# Launch:  /aw-spec-orch finalize-delta [strategy]
-# Prereq:  an OPEN change whose delta was implemented.
-# =============================================================================
-
-name: aw-spec-finalize-delta
-description: Merge the open change's delta-spec into spec.md and delta-design into design.md (doc-first), append the Change History, and refresh the cross-slice edges from the merged design. Gated first by a SCOPED downstream fence over the transitive blast radius (fence_green), which writes a triage report and asks Abort/Override on red. Leaves the change OPEN — analyze-slice runs next against the merged master, and close-delta archives the change and bumps the version.
-version: 1.2.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
-
-vars:
-  active_change: ""
-  has_change: "false"
-  version: ""           # the CURRENT version — unchanged by this stage
-  next_version: ""      # what close-delta will bump to; the number the Change History rows carry
-  downstream_count: "0"    # transitive + placeholder-filtered dependents (blast radius); drives the gate
-  downstream_csv: ""       # the blast-radius names, fed to the scoped fence's --also and shown to the human
-  fence_ok: "true"         # default green so the gate is a no-op when nothing downstream
-  gate_decision: "clean"   # audit: 'clean' unless a RED fence was deliberately overridden
-
-workflow:
-
-  # 1. Resolve the current feature + its spec; require the spec (a merge target).
-  - 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 finalize-delta."
-
-  - 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 + design first."
-
-  # 1b. Read the OPEN change (opened by cr). finalize-delta needs a change to close.
-  - 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" }
-      - { name: next_version,  from: "$.next_version" }
-
-  - id: require_change
-    action: verify_context
-    require_true: has_change
-    on_false: stop
-    on_false_message: "No open change on this feature — nothing to finalize. Run /aw-spec-orch specify → design → analyze-delta-design → implement-delta first."
-
-  # 1c. DOWNSTREAM GATE (hard, with a REVIEWED override). Who depends on this aggregate —
-  #     its OKF Cross-References, TRANSITIVELY (C→B→A all count) and placeholder-filtered
-  #     (the "_(none observed)_" row is NOT a dependent) = the real blast radius. If any
-  #     slice does, this change could ripple into it, so run a SCOPED regression fence over
-  #     this feature + its downstream closure (--scope slice --also <closure>) BEFORE the
-  #     doc merge, so a block leaves the repo untouched. The fence binds fence_GREEN (ran
-  #     AND matched >=1), not raw ok, so an empty / zero-match run is RED, never a vacuous
-  #     pass. If RED we do NOT hard-stop blindly: we WRITE a triage report, then surface the
-  #     failing log + dependent slices and ASK the developer — Abort (a real downstream
-  #     break: fix it first) or, having reviewed the log (pre-existing / flaky / unrelated),
-  #     deliberately Override and close anyway. Non-interactive / CI runs take the FIRST
-  #     option (Abort), so automation never silently overrides. Skipped when nothing depends
-  #     on this slice (count 0) or the fence is green.
-  - id: xref_impact
-    action: execute_script
-    on_error: continue
-    script: { ref: xref }
-    subcommand: list
-    args: ["--feature-dir", "{{feature_dir}}"]
-    outputs:
-      - { name: downstream_count, from: "$.referrer_closure_count" }   # transitive + placeholder-filtered
-      - { name: downstream_csv,   from: "$.referrer_closure_csv" }     # blast-radius names → --also + display
-
-  - id: run_downstream_fence
-    condition: "{{downstream_count}} != 0"
-    action: execute_script
-    on_error: continue
-    script: { ref: actions }
-    subcommand: test-run
-    args: ["--feature-dir", "{{feature_dir}}", "--scope", "slice", "--also", "{{downstream_csv}}"]
-    outputs:
-      - { name: fence_ok,   from: "$.fence_green" }
-      - { name: fence_tool, from: "$.tool" }
-      - { name: fence_log,  from: "$.log_tail" }
-
-  # Whenever the fence RAN (there are dependents), write a durable report BEFORE asking /
-  # stopping — written green OR red, mirroring characterize's drifted-tests.md, so a later green
-  # close never archives a STALE red report. On red it is the triage a developer reads while
-  # deciding Abort vs Override and, if Overridden, is ARCHIVED with the change as the "closed over
-  # red" record; on green it is a short all-clear that overwrites any prior red report. Skipped
-  # only when nothing depends on this slice (no fence ran, nothing to report).
-  - id: ctx_broken_downstream
-    action: build_context
-    condition: "{{downstream_count}} != 0"
-    vars:
-      active_change: "{{active_change}}"
-      downstream_count: "{{downstream_count}}"
-      downstream_csv: "{{downstream_csv}}"
-      fence_ok: "{{fence_ok}}"
-      fence_log: "{{fence_log}}"
-    context:
-      - { path: "{{spec_file}}" }
-      - { path: "{{feature_dir}}/changes/{{active_change}}/delta-design.md" }
-  - id: write_broken_downstream
-    action: agent_author
-    condition: "{{downstream_count}} != 0"
-    include_standards: false                       # a triage report, not generated code
-    output_target: { type: file, path: "{{feature_dir}}/changes/{{active_change}}/broken-downstream.md" }
-    task: |
-      Author the DOWNSTREAM report for change {{active_change}}: the result of re-running this
-      change against the aggregates that DEPEND ON this feature. finalize-delta does NOT fix a
-      downstream slice (that is the downstream slice's own job). Downstream blast radius
-      ({{downstream_count}}): {{downstream_csv}}. The fence result was fence_green={{fence_ok}}
-      (true = every downstream test passed; false = at least one failed). Test log:
-      {{fence_log}}
-      Always write the file (it is regenerated on every finalize-delta run so a green close never
-      leaves a stale red report standing). Stamp when it was generated in both cases.
-
-      IF fence_green is TRUE (all passed): write a SHORT all-clear — the heading
-      `# Broken Downstream — change {{active_change}}`, then a few lines stating that the
-      {{downstream_count}} slice(s) that use this feature ({{downstream_csv}}) were re-run against
-      this change and all passed, so nothing downstream broke. No per-slice sections; invent nothing.
-
-      IF fence_green is FALSE (something failed): write the triage record —
-      - `# Broken Downstream — change {{active_change}}` and a one-line statement: aggregates that
-        USE this feature and whose tests went red when this change was run against them, found by
-        finalize-delta's downstream gate. Note it is the record a human reads while deciding Abort vs
-        Override, and if the change is Overridden it is archived with the change as the record of
-        what was knowingly closed over.
-      - A SUMMARY line: total downstream slices in the blast radius, and how many have a failing test.
-      - One `##` section per DOWNSTREAM slice that has a failing test — attribute a failure to a
-        slice by matching the failing test names in the log to the slice's name. Under it, on their
-        own labelled lines: the downstream aggregate, the failing test(s) named in the log, what
-        broke (as far as the log shows), and a RESOLUTION line — either this change broke the
-        downstream slice's expected contract (fix it in the downstream slice's OWN CR, or re-baseline
-        its golden-master) or the failure is pre-existing / flaky / unrelated (a candidate for a
-        reviewed Override). Recommend one; do not claim certainty the log does not support.
-      - A closing `## How to use this file`: if you Abort, resolve each finding in the downstream
-        slice (or re-baseline its golden-master via a CR) then re-run /aw-spec-orch finalize-delta; if
-        you Override, this is the archived record of what was knowingly closed over. Do not edit in place.
-      Attribute only what the log supports; invent no failures. Do NOT propose an edit to THIS
-      feature's code or docs to silence a downstream failure — that would hide a real contract break.
-    outputs:
-      - { name: broken_downstream_file, from: "$.files" }
-
-  # Fires ONLY when the fence is RED — a failed test-run binds fence_ok=false, which renders
-  # as the string 'false' (json.dumps), so this condition is exactly "the fence is red".
-  # A green fence or no downstream users leaves fence_ok truthy and skips both this and the
-  # gate. The FIRST option is the safe default (non-interactive / CI → Abort). The chosen
-  # label is bound to gate_decision and later written into the OKF log for an audit trail.
-  - id: ask_override
-    condition: "{{fence_ok}} == false"
-    action: ask
-    prompt: |
-      DOWNSTREAM REGRESSION FENCE RED after change {{active_change}}.
-      {{downstream_count}} slice(s) depend on this aggregate: {{downstream_csv}}
-      Triage report: {{feature_dir}}/changes/{{active_change}}/broken-downstream.md
-      -- last test log ------------------------------------------------------------
-      {{fence_log}}
-      -----------------------------------------------------------------------------
-      Review the failing test(s) and the triage report. Is this break caused by THIS
-      change, or is it unrelated (a pre-existing / flaky / different-slice failure)?
-        - Abort    = a real downstream break: stop, fix the downstream slice (or open
-                     a CR on it to re-baseline its golden-master), then re-run finalize-delta.
-        - Override = you have reviewed the log and are DELIBERATELY closing X anyway.
-    options:
-      - "Abort (fix downstream first)"
-      - "Override (reviewed; close X anyway)"
-    answer_var: gate_decision
-
-  - id: downstream_gate
-    condition: "{{fence_ok}} == false"
-    action: verify_context
-    require_value: gate_decision
-    equals: "Override (reviewed; close X anyway)"
-    on_mismatch: stop
-    on_mismatch_message: "finalize-delta ABORTED — downstream fence RED after change {{active_change}} and the override was declined. {{downstream_count}} slice(s) depend on this aggregate ({{downstream_csv}}): the change would break a slice that USES this one. Triage: {{feature_dir}}/changes/{{active_change}}/broken-downstream.md. Fix the downstream break; or, if the behaviour change is intended, open a CR on the affected slice to re-baseline its golden-master. Then re-run /aw-spec-orch finalize-delta. Last log: {{fence_log}}"
-
-  # 2. Ensure the master design.md exists (idempotent) — the second merge target.
-  - id: design_scaffold
-    action: execute_script
-    script: { ref: actions }
-    subcommand: design-scaffold
-    args: ["--feature-dir", "{{feature_dir}}"]
-    outputs:
-      - { name: design_doc, from: "$.design_doc" }
-
-  # 3. Pre-execution hooks.
-  - id: resolve_pre_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "before_finalize_cr"]
-    outputs:
-      - { name: before_hooks, from: "$.hooks" }
-  - id: dispatch_pre_hooks
-    action: dispatch_hooks
-    hooks_from_variable: before_hooks
-
-  # 4. DOC-FIRST merge: fold the two delta docs into the two master docs in place.
-  # Context is fed via build_context — agent_generate reads the ENVELOPE, not a
-  # step-level context: key (unlike agent_author/agent_query which read both).
-  - id: ctx_merge
-    action: build_context
-    context:
-      - { path: "{{feature_dir}}/changes/{{active_change}}/delta-spec.md" }
-      - { path: "{{feature_dir}}/changes/{{active_change}}/delta-design.md" }
-      - { path: "{{spec_file}}" }
-      - { path: "{{design_doc}}" }
-  - id: merge_delta
-    action: agent_generate
-    tools: "Read,Write,Edit"
-    permission_mode: acceptEdits
-    task: |
-      Merge the open change {{active_change}} into the two MASTER docs (both in
-      context), DOC-FIRST. The delta docs (in context) are the source of the change;
-      apply them and change nothing else.
-      To spec.md:
-      - Add each ADDED user story as a US-n tagged `Added: {{active_change}}`, and fold
-        the ADDED / MODIFIED / REMOVED FR / BR / CN- / DC- / IC- items into their
-        sections using the master's vocabulary (EARS FR, BR invariants, etc.).
-      - Apply every MODIFIED item as an in-place edit of the existing item; apply every
-        REMOVED item by removing it. Keep the rest of spec.md VERBATIM.
-      - Append a Change History row for {{active_change}} (date + one-line summary).
-        Its Version cell is {{next_version}} — the version this change ships as.
-      To design.md:
-      - ADD each new design element in its layer section; apply each MODIFIED element as
-        an in-place edit of the existing element; remove each REMOVED element.
-      - Fold the delta's new DA-n / WA-n into the design's §7 / §8 ledgers, and keep §6
-        Traceability in sync (every new spec id has a design home). Keep the rest of
-        design.md VERBATIM.
-      - Append a Change History row for {{active_change}} (date + one-line summary),
-        Version cell {{next_version}}, in lockstep with the spec's row.
-      Leave the `**Version**:` HEADER of BOTH documents exactly as it is — it still reads
-      {{version}} and does not move here. close-delta stamps both headers to
-      {{next_version}} at the moment it bumps active_version.json, so all three carriers
-      of the number change in one step by one mechanism. Do not invent a version anywhere.
-      Preserve every unrelated section of BOTH docs byte-for-byte. Do NOT touch the
-      delta docs (close-delta archives them later) and do NOT touch any source code.
-      Report the two files you changed.
-    outputs:
-      - { name: merged_docs, from: "$.files" }
-
-  - id: verify_merged
-    action: verify_context
-    require_non_empty: merged_docs
-    on_empty: stop
-    on_empty_message: "The merge produced no changes — expected edits to spec.md and design.md. Ensure the delta docs are filled (not the empty template) and re-run."
-
-  # 4b. Refresh the cross-slice EDGES from the NOW-MERGED master design.md — the delta's
-  #     added / removed references have just landed, so this is the first point they are
-  #     authoritative. Reconcile-on-write: new deps appear in the used slices'
-  #     Cross-References, dropped deps are pruned. `--origin auto` keeps the slice's
-  #     provenance (greenfield vs reverse-engineered) from its design.md, so this works
-  #     identically for a greenfield CR and a brownfield CR. Best-effort (never blocks close).
-  - id: xref_record
-    action: execute_script
-    on_error: continue
-    script: { ref: xref }
-    subcommand: record
-    args: ["--feature-dir", "{{feature_dir}}", "--design", "{{design_doc}}", "--origin", "auto"]
-    outputs:
-      - { name: xref_edge_count, from: "$.edge_count" }
-      - { name: xref_origin,     from: "$.origin" }
-
-  # 4b-ii. Re-author the concept's Overview from the NOW-MERGED master design.md — the
-  #     change may have moved the aggregate's boundary or invariants, and this is the
-  #     first point the master states them. Section-scoped splice (the Cross-References
-  #     rows other slices own are untouched). Best-effort; an empty answer is a no-op.
-  - id: okf_overview
-    action: agent_query
-    context: ["{{design_doc}}"]
-    include_standards: false
-    schema: { overview: "<2-4 sentences of prose>" }
-    mock: { overview: "" }
-    task: |
-      Write the OKF knowledge-concept Overview for the aggregate that the merged
-      design.md (in context) describes. 2-4 sentences of PROSE, distilled from §1
-      Domain Model: name the aggregate ROOT and what the aggregate IS; state the
-      INVARIANTS it guards; state its TRANSACTION BOUNDARY — what it OWNS inside the
-      boundary vs what it only REFERENCES by id. Plain prose only: no headings, no
-      bullets, no code fences, no file paths, and no restating of the dependency edges
-      (those live in the Depends-On / Cross-References tables). Describe only what the
-      design states — invent nothing.
-    outputs:
-      - { name: okf_overview, from: "$.overview" }
-
-  - id: okf_overview_write
-    action: execute_script
-    on_error: continue
-    script: { ref: xref }
-    subcommand: concept-overview
-    args: ["--feature-dir", "{{feature_dir}}", "--text", "{{okf_overview}}"]
-
-  # 4c. Anchor the OKF bundle's freshness journal to the current commit (log.md, OKF §7).
-  #     Best-effort + git-aware: a no-op when there is no bundle or no commit, so it never
-  #     writes a non-conformant block. Records that this CR refreshed the cross-references.
-  - id: xref_log
-    action: execute_script
-    on_error: continue
-    script: { ref: xref }
-    subcommand: log
-    args: ["--note", "CR {{active_change}} merged (downstream gate: {{gate_decision}}) — OKF cross-references refreshed"]
-    outputs:
-      - { name: xref_log, from: "$.log" }
-
-  # 5. NO ARCHIVE, NO VERSION BUMP HERE. Both moved to close-delta, which runs after
-  #    analyze-slice — see the header. The change stays OPEN past this stage on purpose:
-  #    it is what keeps a red analyze-slice recoverable ("fix and re-run") instead of
-  #    landing on an already-shipped version. The delta docs therefore remain in
-  #    changes/{{active_change}}/ even though their content is now merged; close-delta
-  #    moves them to changes/archive/.
-
-  # 6. Post-execution hooks.
-  - id: resolve_post_hooks
-    action: execute_script
-    script: { ref: actions }
-    subcommand: resolve-hooks
-    args: ["--phase", "after_finalize_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}}"
-  merged_docs: "{{merged_docs}}"
-  version: "{{version}}"
-  downstream_count: "{{downstream_count}}"
-  gate_decision: "{{gate_decision}}"
-  xref_edge_count: "{{xref_edge_count}}"
-  next: "Delta MERGED into spec.md + design.md; OKF edges refreshed ({{xref_edge_count}} dep(s)), {{downstream_count}} downstream slice(s) fenced (gate: {{gate_decision}}). Change {{active_change}} is STILL OPEN and the version is still {{version}}. Next: /aw-spec-orch analyze-slice — it now reads a master spec that carries this change, and a red result is still recoverable because nothing has been archived. Then /aw-spec-orch close-delta archives the change and bumps the version."

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

@@ -1,246 +0,0 @@
-# =============================================================================
-# aw-spec-foundation (orchestrator) — scaffold a project from a foundation bundle
-#
-# Almost entirely deterministic script orchestration (unpack the verified
-# byte-for-byte bundle, rename the sentinel); the model is used ONLY for the
-# optional DbContext merge when the reference sample is included. That merge
-# is an `agent_author` (decl `llm_generate` port): generation is READ-ONLY
-# under every strategy and the ENGINE writes the merged file, so sdk-apply
-# degrades to sdk. No standards/domain/hooks — pure scaffolding, so the merge
-# runs with include_standards: false and a narrow two-file context.
-#
-# Interactive confirmations (proceed / overwrite / reference sample) ride the
-# checkpoint channel under EVERY strategy.
-#
-# Launch via the parametric skill:  /aw-spec-orch foundation [strategy]
-#   Interactive (no args): LISTS the available foundations to pick from, then ASKS
-#   for the app (project) name — both deterministic, no LLM. Fast path still works:
-#     /aw-spec-orch foundation agent VerticalSlice AppWeaver.Health
-#
-# Headless:
-#   python3 .aw-spec/orchestrator/orchestrator.py \
-#     .aw-spec/orchestrator/workflows/aw-spec-foundation.orch.yaml \
-#     --checkpoint .aw-spec/orchestrator/.state/foundation.state.json \
-#     --input "VerticalSlice AppWeaver.Health" --json
-# =============================================================================
-
-name: aw-spec-foundation
-description: Scaffold a complete, compiling project — pick from the available foundation bundles and enter the app name, then unpack the verified bundle and rename its sentinel to your app name. Selection is zero-LLM (list + pick + ask).
-version: 1.1.0
-agent_agnostic: true
-dialect: aw-spec.orchestrator/v1
-
-inputs:
-  user_input:
-    description: "Optional fast path: FoundationName [AppName] [OutputDirectory]. Omit to pick a foundation from the list and be asked for the app name."
-    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:
-  overwrite: "no"        # flipped by ask_overwrite only when the dry run finds collisions
-  ref_written: "0"       # stays 0 when the reference sample is declined
-  stash_found: "false"   # true only when the reference flow stashed a DbContext
-  app: ""                # resolved app name: fast-path 2nd token, else the ask below
-  app_typed: ""          # app name entered interactively (empty on the fast path)
-
-workflow:
-
-  # 1a. LIST the available foundations (deterministic docs/<Name>/<Name>.pack.txt
-  #     scan — no LLM). A direct "Foundation App [out]" argument is parsed here too
-  #     as an optional fast path (preselect_name / preselect_app / out_dir).
-  - id: list_foundations
-    action: execute_script
-    script: { ref: actions }
-    subcommand: foundation-list
-    args: ["--args", "{{USER_INPUT}}"]
-    outputs:
-      - { name: foundations,      from: "$.foundations" }
-      - { name: foundation_count, from: "$.count" }
-      - { name: preselect_name,   from: "$.preselect_name" }
-      - { name: preselect_app,    from: "$.preselect_app" }
-      - { name: out_dir,          from: "$.out_dir" }
-
-  - id: have_foundations
-    action: verify_context
-    require_non_empty: foundations
-    on_empty: stop
-    on_empty_message: "No foundations found under docs/<Name>/<Name>.pack.txt. Add a foundation bundle (see docs/<Name>/PACKAGING.md) and re-run."
-
-  # 1b. PICK the foundation. A matching fast-path arg auto-selects; a lone
-  #     foundation auto-confirms; otherwise the user chooses from the list.
-  - id: pick_foundation
-    action: user_select
-    prompt: "Select a foundation to scaffold from:"
-    options_from_variable: foundations
-    preselect_from: preselect_name
-    single_option_confirm: true
-    outputs:
-      - { name: fname, from: selection }
-
-  # 1c. ASK for the app (project) name — deterministic free-text, no LLM. Skipped
-  #     when the fast-path arg already supplied it (preselect_app non-empty).
-  - id: ask_app
-    action: ask
-    condition: "{{preselect_app}} == "
-    prompt: >
-      Enter the project (application) name — it replaces the foundation's sentinel
-      across the generated tree (dotted / underscored / hyphen / lower forms),
-      e.g. AppWeaver.Health:
-    answer_var: app_typed
-
-  # 1d. Coalesce the app name (engine has no compound conditions → two ordered
-  #     sets): default to the typed answer, then override with the fast-path token.
-  - id: app_from_typed
-    action: set
-    vars: { app: "{{app_typed}}" }
-  - id: app_from_arg
-    action: set
-    condition: "{{preselect_app}} != "
-    vars: { app: "{{preselect_app}}" }
-
-  # 1e. Locate the bundle/unpacker for the CHOSEN foundation + read the (bounded)
-  #     pack header (sentinel + file_count shown in the confirm below).
-  - id: locate
-    action: execute_script
-    script: { ref: actions }
-    subcommand: foundation-locate
-    args: ["--name", "{{fname}}", "--app", "{{app}}", "--out", "{{out_dir}}"]
-    outputs:
-      - { name: locate_ok,  from: "$.ok" }
-      - { name: locate_msg, from: "$.reason" }
-      - { name: available,  from: "$.available" }
-      - { name: fname,      from: "$.name" }
-      - { name: app,        from: "$.app" }
-      - { name: out_dir,    from: "$.out_dir" }
-      - { name: sentinel,   from: "$.sentinel" }
-      - { name: file_count, from: "$.file_count" }
-
-  - id: locate_gate
-    action: verify_context
-    require_true: locate_ok
-    on_false: stop
-    on_false_message: "{{locate_msg}}  (available foundations: {{available}})"
-
-  # 2. Confirm the scaffold plan (checkpoint kind 'ask' under every strategy).
-  - id: confirm
-    action: ask
-    prompt: |
-      Foundation: {{fname}} (sentinel {{sentinel}}, {{file_count}} files)
-      App Name:   {{app}}
-      Output:     {{out_dir}}
-      Rename {{sentinel}} -> {{app}} (dotted/underscored/hyphen/lower forms).
-      Unchanged: 'Projects' sample domain + AppWeaver.* framework packages. Proceed?
-    options: ["yes", "no"]
-    answer_var: proceed
-
-  - id: confirm_gate
-    action: verify_context
-    require_value: proceed
-    equals: "yes"
-    on_mismatch: stop
-    on_mismatch_message: "Cancelled by user."
-
-  # 3. Dry-run to surface collisions, then confirm overwrite if needed.
-  - id: dry_run
-    action: execute_script
-    script: { ref: actions }
-    subcommand: foundation-unpack
-    args: ["--name", "{{fname}}", "--app", "{{app}}", "--out", "{{out_dir}}", "--dry-run"]
-    outputs:
-      - { name: has_collisions, from: "$.has_collisions" }
-
-  - id: ask_overwrite
-    action: ask
-    condition: "{{has_collisions}} == true"
-    prompt: "Output files already exist. Overwrite them?"
-    options: ["yes", "no"]
-    answer_var: overwrite
-
-  - id: overwrite_gate
-    action: verify_context
-    condition: "{{has_collisions}} == true"
-    require_value: overwrite
-    equals: "yes"
-    on_mismatch: stop
-    on_mismatch_message: "Aborted — output files exist and overwrite was declined."
-
-  # 4. Unpack for real.
-  - id: unpack
-    action: execute_script
-    script: { ref: actions }
-    subcommand: foundation-unpack
-    args: ["--name", "{{fname}}", "--app", "{{app}}", "--out", "{{out_dir}}", "--force", "{{overwrite}}"]
-    outputs:
-      - { name: written, from: "$.written" }
-
-  # 5. Optional reference sample.
-  - id: ask_reference
-    action: ask
-    prompt: "Include the reference sample project (Projects, Users, Reports slices)?"
-    options: ["yes", "no"]
-    answer_var: want_reference
-
-  - id: stash_dbcontext
-    action: execute_script
-    condition: "{{want_reference}} == yes"
-    script: { ref: actions }
-    subcommand: foundation-stash-dbcontext
-    args: ["--out", "{{out_dir}}"]
-    outputs:
-      - { name: stash_found, from: "$.found" }
-      - { name: db_context,  from: "$.dbcontext" }
-      - { name: db_backup,   from: "$.backup" }
-
-  - id: reference_unpack
-    action: execute_script
-    condition: "{{want_reference}} == yes"
-    script: { ref: actions }
-    subcommand: foundation-unpack
-    args: ["--name", "{{fname}}", "--app", "{{app}}", "--out", "{{out_dir}}", "--reference"]
-    outputs:
-      - { name: ref_written, from: "$.written" }
-
-  # 6. Merge the foundation DbContext (usings + DbSet<>) back over the reference
-  #    one. agent_author: read-only generation, the ENGINE writes the target.
-  - id: merge_dbcontext
-    action: agent_author
-    condition: "{{stash_found}} == true"
-    context: ["{{db_backup}}", "{{db_context}}"]
-    include_standards: false
-    task: |
-      The target file ({{db_context}}) currently holds the REFERENCE DbContext
-      (sample DbSet<> properties, no OnModelCreating). The backup ({{db_backup}})
-      holds the FOUNDATION DbContext (full OnModelCreating, no DbSet<>). Produce a
-      single merged ApplicationDbContext:
-        - Base = the FOUNDATION file (backup).
-        - Add any `using` directives from the reference that are missing.
-        - Insert every reference `public DbSet<…>` line as a block right after the
-          class opening brace (before OnModelCreating), preserving any comment above them.
-        - Keep everything else in the foundation file unchanged.
-    output_target: { type: file, path: "{{db_context}}" }
-
-  # 7. Verify (sentinel residue must be zero in the generated tree).
-  - id: verify
-    action: execute_script
-    script: { ref: actions }
-    subcommand: foundation-verify
-    args: ["--out", "{{out_dir}}", "--sentinel", "{{sentinel}}"]
-    outputs:
-      - { name: clean,   from: "$.clean" }
-      - { name: residue, from: "$.residue" }
-
-outputs:
-  foundation: "{{fname}}"
-  app: "{{app}}"
-  output_dir: "{{out_dir}}"
-  files_written: "{{written}}"
-  reference_files: "{{ref_written}}"
-  sentinel_clean: "{{clean}}"
-  sentinel_residue: "{{residue}}"
-  note: "Foundation scaffolded into {{out_dir}} ({{written}} file(s), sentinel renamed to {{app}}). Configure your AppWeaver.* NuGet feed and run the AppHost to confirm the scaffold starts before building on it."
-  next: "/aw-spec-orch select-feature   (pick the feature to build; every stage from specify onward reads that active feature and stops without it. If this project has domain rule packs under docs/domainspecs/, run /aw-spec-orch select-domain first — it is one-time and optional.)"