aw-spec-cli 0.1.20 → 0.1.21

package/assets/.appweaver/orchestrator/workflows/aw-spec-onboard.orch.yaml

@@ -137,7 +137,7 @@
 
 name: aw-spec-onboard
 description: Onboard an existing codebase for brownfield DEVELOPMENT — a deterministic whole-repo scan produces a high-level OKF feature map (folders/concepts) PLUS the project-level governance scaffold (split constitution + guardrails/projects/brf-<domain>/ with its DOMAIN rule files at domain/ + domain-rule-bindings + code-derived TECHNICAL rule files at service/ + tech-rule-bindings + activated domain), all provisional-from-scan and refined per slice by adopt. Where the scan finds a frontend lane in the CODE, it also authors that lane's half — constitution.ui.md (UX-*) — and its code-derived rule files at brf-<domain>/frontend/, mapped under `## /aw-spec-ui-constitution`; a backend-only repo gets none of it. Every rule tier is reverse-engineered from the CODE alone (never a greenfield rule file), evidenced-only, and WIRED per-workflow so the whole forward pipeline AND adopt govern against THIS codebase — never a greenfield fallback. It also reverse-engineers the repo's own technical structure into a project-specific design + delta-design template pair, installed as the project template overrides, and — where the lane exists — the frontend lane's own pair from the UI source. Every authoring step is shaped by a NEUTRAL rev-templates skeleton; no greenfield constitution, rule file or document template is ever placed in context. Accepts an optional concerns list to look for (onboard decides which are actually present). Reads any declared lane, never writes one. No migration content; never modifies source.
-version: 2.0.0
+version: 2.1.0
 agent_agnostic: true
 dialect: aw-spec.orchestrator/v1
 
@@ -1270,8 +1270,8 @@ workflow:
         numeral is whatever the code supported — never a value carried over from another
         constitution. If it mandates no modelling methodology, say so plainly rather than
         supplying one.
-      - Author ONLY the domain layer: domain principles, domain folder additions,
-        regulatory/security posture, domain governance — from the project + charter. NUMBER
+      - Author ONLY the domain layer: project identity, domain principles, domain folder
+        additions, regulatory/security posture, domain governance — from the project + charter. NUMBER
         them by CONTINUING the technical half's roman numerals: READ
         constitution.technical.md (in context), find its LAST numeral N, start the first
         domain principle at N+1 (do NOT assume it ends at XV). TITLE each by DOMAIN

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

@@ -14,8 +14,13 @@
 # evidence sits in, and both are only ever proposals — an operator selects from the
 # list or types a path the kit has never seen.
 #
-#   stack-list --suggest backend  → select stack → ask source path → lane-declare
-#   stack-list --suggest frontend → select stack → ask source path → lane-declare
+#   stack-list --suggest backend  → select stack → stack-list --profile → ask source path → lane-declare
+#   stack-list --suggest frontend → select stack → stack-list --profile → ask source path → lane-declare
+#
+# THE SOURCE-PATH OPTIONS ARE BUILT AFTER THE STACK IS CHOSEN. Most profiles of a kind
+# share a default root (six frontend stacks default to web/), so a list built before the
+# choice cannot say which stack an option belongs to. The second stack-list call answers
+# for the chosen stack alone.
 #
 # (none) IS A REAL ANSWER FOR EITHER LANE, and it is how a project says "I do not
 # have one of these". A backend-only project answers (none) to the UI lane; a
@@ -56,7 +61,7 @@
 
 name: aw-spec-select-stack
 description: Declare the project's lanes — each lane's STACK and its SOURCE PATH — and persist them to .appweaver/stacks.json, the single channel every later workflow resolves and gates on. The first command of both the greenfield and the brownfield sequence, and the sole writer of the lane model.
-version: 2.0.0
+version: 2.3.0
 agent_agnostic: true
 dialect: aw-spec.orchestrator/v1
 
@@ -93,9 +98,7 @@ workflow:
       - { name: api_options,       from: "$.select_options" }
       - { name: api_ids,           from: "$.ids" }
       - { name: api_preselect,     from: "$.preselect" }
-      - { name: api_root_options,  from: "$.root_options" }
-      - { name: api_detected,      from: "$.detected_profile" }
-      - { name: api_detected_root, from: "$.detected_root" }
+      - { name: api_detected,      from: "$.detected_summary" }
       - { name: api_none_sentinel, from: "$.none_sentinel" }
 
   # 2. No profiles installed is a setup error, not an empty menu. Gated on the
@@ -114,7 +117,7 @@ workflow:
   #    does a detected stack; a project with exactly one candidate auto-confirms.
   - id: select_api_stack
     action: user_select
-    prompt: "Select the API (backend) stack — it owns the service lane. This repo's own files point at: {{api_detected}} (leading the list). (none) declares a project with no service lane at all, and stops the technical constitution half and the service rule files being authored:"
+    prompt: "Select the API (backend) stack — it owns the service lane. This repo's own files point at: {{api_detected}}. A detected stack leads the list. (none) declares a project with no service lane at all, and stops the technical constitution half and the service rule files being authored:"
     options_from_variable: api_options
     preselect_from: api_preselect
     single_option_confirm: true
@@ -133,14 +136,24 @@ workflow:
     condition: "{{chosen_api}} == {{api_none_sentinel}}"
     vars: { api_selected: "" }
 
-  # 5. WHERE the service lane's source lives. Offered best-first — where the
-  #    evidence actually sits, then each profile's own default — and free text is
-  #    accepted, because a repo that matches no profile still has a source path.
-  #    The label after the path says why it is offered and is stripped on the way in.
+  # 5. WHERE the service lane's source lives. Offered best-first for the CHOSEN stack —
+  #    where its evidence sits, then its own default, then where another stack's
+  #    evidence sits — and free text is accepted, because a repo that matches no
+  #    profile still has a source path. The label after the path says why it is
+  #    offered and is stripped on the way in.
+  - id: list_api_roots
+    action: execute_script
+    condition: "{{api_selected}}"
+    script: { ref: actions }
+    subcommand: stack-list
+    args: ["--kind", "backend", "--suggest", "--profile", "{{chosen_api}}"]
+    outputs:
+      - { name: api_root_options, from: "$.root_options" }
+
   - id: ask_api_source_path
     action: ask
     condition: "{{api_selected}}"
-    prompt: "Service lane SOURCE PATH — the subtree this lane owns, the only place implement may write, and the directory build/test/run act on. Pick one or type your own:"
+    prompt: "Service lane SOURCE PATH — the subtree this lane owns, where implement writes its code, and the directory build/test/run act on. Its tests go to the stack's test path beside it (tests/ next to src/ for .NET), shown in the summary. Pick one or type your own:"
     options_from_variable: api_root_options
     answer_var: api_source_path
 
@@ -159,6 +172,7 @@ workflow:
       - { name: api_lane_id,     from: "$.lane_id" }
       - { name: api_profile,     from: "$.profile" }
       - { name: api_root,        from: "$.source_path" }
+      - { name: api_test_path,   from: "$.test_path" }
       - { name: api_root_exists, from: "$.root_exists" }
 
   # ═══════════════ UI LANE ════════════════════════════════════════════════════
@@ -176,15 +190,13 @@ workflow:
       - { name: ui_options,       from: "$.select_options" }
       - { name: ui_ids,           from: "$.ids" }
       - { name: ui_preselect,     from: "$.preselect" }
-      - { name: ui_root_options,  from: "$.root_options" }
-      - { name: ui_detected,      from: "$.detected_profile" }
-      - { name: ui_detected_root, from: "$.detected_root" }
+      - { name: ui_detected,      from: "$.detected_summary" }
       - { name: ui_none_sentinel, from: "$.none_sentinel" }
 
   # 8. Choose the UI stack.
   - id: select_ui_stack
     action: user_select
-    prompt: "Select the UI (frontend) stack — it owns the web lane, and its root must not overlap the service lane's. This repo's own files point at: {{ui_detected}} (leading the list). (none) declares a backend-only project, and stops the UI constitution half and the frontend rule files being authored:"
+    prompt: "Select the UI (frontend) stack — it owns the web lane, and its root must not overlap the service lane's. This repo's own files point at: {{ui_detected}}. A detected stack leads the list. (none) declares a backend-only project, and stops the UI constitution half and the frontend rule files being authored:"
     options_from_variable: ui_options
     preselect_from: ui_preselect
     single_option_confirm: true
@@ -199,7 +211,16 @@ workflow:
     condition: "{{chosen_ui}} == {{ui_none_sentinel}}"
     vars: { ui_selected: "" }
 
-  # 9. WHERE the UI lane's source lives.
+  # 9. WHERE the UI lane's source lives, offered for the chosen UI stack.
+  - id: list_ui_roots
+    action: execute_script
+    condition: "{{ui_selected}}"
+    script: { ref: actions }
+    subcommand: stack-list
+    args: ["--kind", "frontend", "--suggest", "--profile", "{{chosen_ui}}"]
+    outputs:
+      - { name: ui_root_options, from: "$.root_options" }
+
   - id: ask_ui_source_path
     action: ask
     condition: "{{ui_selected}}"
@@ -217,6 +238,7 @@ workflow:
       - { name: ui_lane_id,     from: "$.lane_id" }
       - { name: ui_profile,     from: "$.profile" }
       - { name: ui_root,        from: "$.source_path" }
+      - { name: ui_test_path,   from: "$.test_path" }
       - { name: ui_root_exists, from: "$.root_exists" }
 
   # ═══════════════ CHECK + REPORT ═════════════════════════════════════════════
@@ -257,7 +279,7 @@ workflow:
   - id: api_summary_lane
     action: set
     condition: "{{api_declared}}"
-    vars: { api_summary: "{{api_lane_id}} ({{api_profile}}) at {{api_root}} — source path exists: {{api_root_exists}}" }
+    vars: { api_summary: "{{api_lane_id}} ({{api_profile}}) at {{api_root}}, tests at {{api_test_path}} — source path exists: {{api_root_exists}}" }
 
   - id: ui_summary_none
     action: set
@@ -265,7 +287,7 @@ workflow:
   - id: ui_summary_lane
     action: set
     condition: "{{ui_declared}}"
-    vars: { ui_summary: "{{ui_lane_id}} ({{ui_profile}}) at {{ui_root}} — source path exists: {{ui_root_exists}}" }
+    vars: { ui_summary: "{{ui_lane_id}} ({{ui_profile}}) at {{ui_root}}, tests at {{ui_test_path}} — source path exists: {{ui_root_exists}}" }
 
   # 12. Read the finished declaration back through the reader every later workflow
   #     uses, so what this run reports is what they will resolve.
@@ -287,10 +309,12 @@ outputs:
   ui_lane: "{{ui_summary}}"
   api_source_path: "{{api_root}}"
   ui_source_path: "{{ui_root}}"
+  api_test_path: "{{api_test_path}}"
+  ui_test_path: "{{ui_test_path}}"
   api_source_path_exists: "{{be_root_exists}}"
   ui_source_path_exists: "{{fe_root_exists}}"
-  api_detected: "{{api_detected}} at {{api_detected_root}}"
-  ui_detected: "{{ui_detected}} at {{ui_detected_root}}"
+  api_detected: "{{api_detected}}"
+  ui_detected: "{{ui_detected}}"
   prototype: "{{prototype}}"
-  note: "Lanes persisted to .appweaver/stacks.json. Each lane carries a STACK and a SOURCE PATH, and both are load-bearing. The SOURCE PATH is ownership: implement's service lane writes only under the service lane's and its frontend lane only under the UI lane's, build/test/run act on it, and onboard reverse-engineers out of it — overlapping paths are refused here rather than discovered later as two generators writing one file. The build/test/run commands are project-supplied strings the engine shells out to, which is how it stays stdlib-only and stack-ignorant. api_detected / ui_detected report what this repo's own files pointed at, whether or not it was chosen — empty on a greenfield repo with nothing to detect. A source path that does not exist yet is NORMAL here and reported rather than refused: greenfield declares src/ before implement creates it. The on-disk check runs in the phases that read the subtree — implement, build, run and onboard all call lane-verify and STOP with the fix named. Declining a lane with (none) is a real declaration and removes any lane of that kind a previous run left behind; it is also what stops that lane's constitution half and rule files being authored. `prototype` is not a lane — it has a root and a run command so an operator can open it, and nothing else. Re-run this workflow any time to re-stack a lane, move a source path, or drop a lane with (none); it is the only workflow that may write this file."
-  next: "GREENFIELD: /appweaver select-domain → constitution → select-feature → specify. BROWNFIELD: /appweaver onboard — it reverse-engineers out of the source paths declared here and generates the project (no select-domain; onboard derives and activates it from the code). Run this workflow FIRST in either sequence: constitution reads the declaration to decide which halves to author, and onboard reads it to decide what to scan."
+  note: "Lanes persisted to .appweaver/stacks.json. Each lane carries a STACK and a SOURCE PATH, and both are load-bearing. The SOURCE PATH is ownership: implement's service lane writes its code only under the service lane's and its frontend lane only under the UI lane's, build/test/run act on it, and onboard reverse-engineers out of it. Each lane also owns a TEST PATH, taken from its stack profile — tests/ beside a .NET src/, the source path itself for a stack that keeps its tests inside — and implement writes the lane's tests there. Overlapping paths of either kind are refused here rather than discovered later as two generators writing one file. The build/test/run commands are project-supplied strings the engine shells out to, which is how it stays stdlib-only and stack-ignorant. api_detected / ui_detected report what this repo's own files pointed at, whether or not it was chosen, as "<stack> at <path>" — or "nothing detected" on a greenfield repo with nothing to detect. A source path that does not exist yet is NORMAL here and reported rather than refused: greenfield declares src/ before implement creates it. The on-disk check runs in the phases that read the subtree — implement, build, run and onboard all call lane-verify and STOP with the fix named. Declining a lane with (none) is a real declaration and removes any lane of that kind a previous run left behind; it is also what stops that lane's constitution half and rule files being authored. `prototype` is not a lane — it has a root and a run command so an operator can open it, and nothing else. Re-run this workflow any time to re-stack a lane, move a source path, or drop a lane with (none); it is the only workflow that may write this file."
+  next: "GREENFIELD: /appweaver foundation — once per lane, to scaffold a compiling project into each source path declared here (skip it for a lane whose code already exists, or scaffold with the stack's own tooling) — then /appweaver select-domain → constitution → select-feature → specify. BROWNFIELD: /appweaver onboard — it reverse-engineers out of the source paths declared here and generates the project (no select-domain; onboard derives and activates it from the code). Run this workflow FIRST in either sequence: foundation unpacks into the source paths declared here, constitution reads the declaration to decide which halves to author, and onboard reads it to decide what to scan."

package/assets/.appweaver/orchestrator/workflows/aw-spec-specify.orch.yaml

@@ -670,5 +670,5 @@ outputs:
   authored_document: "{{quality_target}}"   # spec.md (bootstrap) | delta-spec.md (delta)
   checklist_file: "{{checklist_file}}"
   checklist_quality: "{{checklist_passed}}/{{checklist_total}} items passing"
-  note: "Behaviour and structure were authored together: the spec says what the system must do, {{domain_model}} says what the domain IS. The aggregate root, its entities and its invariants (BR-n) live in the model and are cited from the spec by id — never restated there, because several specs act on one aggregate and a per-spec copy drifts. On the DELTA path neither master was touched: this run wrote changes/{{cr_id}}/delta-spec.md and {{delta_model}}, and that model delta sits BESIDE the master where every other open delta can see it while being authored. WAVE {{wave}} is its parallel-development level — deltas sharing a wave are independent, a higher wave is implemented only after the lower ones land; `cr-wave --cr-id {{cr_id}} --wave <n>` moves it. {{open_count}} change(s) are open on this feature."
+  note: "Behaviour and structure were authored together: the spec says what the system must do, {{domain_model}} says what the domain IS. The aggregate root, its entities and its invariants (BR-n) live in the model and are cited from the spec by id — never restated there, because several specs act on one aggregate and a per-spec copy drifts. On the DELTA path neither master was touched: this run wrote changes/{{cr_id}}/delta-spec.md and {{delta_model}}, and that model delta sits BESIDE the master where every other open delta can see it while being authored. WAVE {{wave}} is its parallel-development level — deltas sharing a wave are independent, a higher wave is implemented only after the lower ones land. The wave is DERIVED from the model delta's `## Depends on`: one above the highest delta named there, stamped into both halves as soon as it was authored ({{wave_message}}). To move it, correct that section and re-run `.appweaver/scripts/bash/aw-spec-actions.sh cr-wave-derive --cr-id {{cr_id}} --stamp`; finalize-delta refuses a change whose wave contradicts it. {{open_count}} change(s) are open on this feature."
   next: "/appweaver plan — BOOTSTRAP authors backend-plan.md from the spec + the domain model; a DELTA (this run opened change {{cr_id}}, wave {{wave}}) authors the delta plans for it. A change then flows: analyze-plan-delta → implement → build → analyze-slice-delta → finalize-delta → analyze-slice → close-delta (finalize-delta merges the delta into spec.md + domain-model.md — not the lane plans, which are derived from those two — but leaves the change open; analyze-slice verifies the slice against the merged master; close-delta archives the change and bumps the version). ⚠️ With more than one change open, plan, analyze-plan-delta and implement ASK which one they are for (pass the id as the argument to skip the prompt) and activate the answer; finalize-delta and close-delta still act on whichever change is active — so finish or close the others deliberately."