aw-spec-cli 0.1.16 → 0.1.17

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

@@ -7,14 +7,14 @@
 #
 # 1.1.0 — the slice'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, a convention the tech-agnostic design.md no longer carries;
+# ```lang path=… fences, a convention the tech-agnostic backend-plan.md no longer carries;
 # and the tail step records fix-loop files in that concept instead of copying file
 # bodies back into design fences (`design-reconcile`, likewise retired).
 #
 # 1.2.0 — TECHNICAL RULES ONLY: the `domain-select` include is REMOVED. Build repairs
 # compile errors against design intent — a purely technical job — and the domain never
 # reaches this stage anyway (specify is the domain's sole carrier into the pipeline;
-# build reads code and design.md, never the spec or the domain docs). The include was
+# build reads code and backend-plan.md, never the spec or the domain docs). The include was
 # also inert: no shipped domain-rule-bindings.md carries a "## /aw-spec-build" heading, so
 # `resolve-domain` — which keys `rulemap_exists` off the FILE, not the heading —
 # returned `candidates: []` and every load step skipped. On a CONFIGURED project it was
@@ -87,7 +87,7 @@ workflow:
     with: { require: backend, command: "/appweaver build" }
 
   # The slice's source files, from its OKF concept — what the fix loop below is handed.
-  # This replaces the retired `design-paths` fence scan: the tech-agnostic design.md
+  # This replaces the retired `design-paths` fence scan: the tech-agnostic backend-plan.md
   # carries no ```lang path=… code blocks, so that scan returned nothing and the fixer
   # was told to "fix the source files in context" with an EMPTY context. `source_files`
   # is the maintained answer (implement writes it, analyze-slice merges fixes into it).
@@ -158,7 +158,7 @@ workflow:
 
   # Record what the fix loop touched in the slice's OKF concept. This replaces the retired
   # `design-reconcile` step, which copied on-disk file bodies back into the design doc's
-  # path-tagged fences — meaningless now that design.md describes contracts, not code (and
+  # path-tagged fences — meaningless now that backend-plan.md describes contracts, not code (and
   # a silent no-op for as long as that has been true). The fix loop can CREATE files that
   # implement never recorded, so the knowledge index, not the design prose, is what has to
   # be caught up. UNION (--merge), never replace: fixed_files holds only what this loop

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

@@ -1,7 +1,7 @@
 # =============================================================================
 # aw-spec-characterize (orchestrator) — B2 of the Brownfield Pipeline
 #
-# The REGRESSION FENCE. After a slice is adopted (spec.md + design.md +
+# The REGRESSION FENCE. After a slice is adopted (spec.md + backend-plan.md +
 # source-map.md), pin what the legacy code CURRENTLY DOES as golden-master /
 # characterization tests — observed behaviour asserted AS-IS, bugs and quirks
 # included. These are NOT correctness claims; they are the missing behaviour
@@ -18,7 +18,7 @@
 # item via the CR delta loop — never a silent drift.
 #
 # Characterize GENERATES tests only; it does NOT modify production code and does
-# NOT change spec.md / design.md.
+# NOT change spec.md / backend-plan.md.
 #
 # EXISTING TESTS. A legacy repo usually already has some. They are not a fence — they
 # assert INTENDED behaviour, which is exactly what brownfield cannot assume. So before
@@ -34,7 +34,7 @@
 # every run (never appended), so it always reflects the CURRENT scan and can never go stale.
 #
 # Launch:  /appweaver characterize [strategy] [focus/guidance]
-# Prereq:  /appweaver adopt <Aggregate>  (spec.md + design.md + source-map.md),
+# Prereq:  /appweaver adopt <Aggregate>  (spec.md + backend-plan.md + source-map.md),
 #          and a scaffolded project (/appweaver foundation) to host + run tests.
 # =============================================================================
 
@@ -118,7 +118,7 @@ workflow:
     action: verify_context
     require_true: design_exists
     on_false: stop
-    on_false_message: "No design.md for the current feature. Run /appweaver adopt <Aggregate> (or /appweaver design) first."
+    on_false_message: "No backend-plan.md for the current feature. Run /appweaver adopt <Aggregate> (or /appweaver plan) first."
 
   # 1b. Require the ADOPT source-map sidecar — characterize fences an ADOPTED
   #     legacy slice (its as-built quirks + owned source files live here).
@@ -188,8 +188,8 @@ workflow:
       - { path: "{{design_file}}" }
   - id: scan_existing_tests
     action: agent_query
-    tools: Read,Glob,Grep   # no test list is supplied — it globs the tree; empty results make characterize write duplicate golden-masters
     include_standards: false
+    tools: Read,Glob,Grep   # no test list is supplied — it globs the tree; empty results make characterize write duplicate golden-masters
     schema:
       duplicates: [ { behaviour: "<observable behaviour>", spec_id: "<US-/FR-/BR- id>", existing_test: "<file:test-name>", seam: "<endpoint|handler|domain|persistence>", source_file: "<production file it covers>" } ]
       drift: [ { existing_test: "<file:test-name>", asserts: "<what the test expects>", code_actually: "<what the code does>", source_file: "<production file it covers>", spec_id: "<US-/FR-/BR- id, or ->", test_state: "<failing|ignored|inconclusive>" } ]
@@ -327,7 +327,7 @@ workflow:
       Generate CHARACTERIZATION / golden-master tests for this adopted slice that
       pin what the legacy code CURRENTLY DOES — the regression fence. READ the
       slice's PRODUCTION code (the files listed in source-map.md, in context) and
-      OBSERVE its actual behaviour; the spec.md + design.md (in context) frame the
+      OBSERVE its actual behaviour; the spec.md + backend-plan.md (in context) frame the
       observable surface. Guidance: {{USER_INPUT}}
       Rules:
       - ASSERT OBSERVED BEHAVIOUR, AS-IS. Capture what the code returns/emits/persists
@@ -349,7 +349,7 @@ workflow:
       - BIND THE STACK + test framework from the constitution + the project's EXISTING
         test project conventions; place files in the test tree per folder-structure and
         match the surrounding test style. Reuse existing fixtures/builders.
-      - Do NOT modify any PRODUCTION code — tests only. Do NOT edit spec.md / design.md.
+      - Do NOT modify any PRODUCTION code — tests only. Do NOT edit spec.md / backend-plan.md.
         If a behaviour is genuinely non-deterministic (time, random, external I/O),
         pin it via the seam the code already exposes (clock/port) or assert the stable
         shape; note it in the test rather than asserting a flaky value.

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

@@ -2,14 +2,14 @@
 # aw-spec-close-delta (orchestrator) — ARCHIVE the change + bump the version
 #
 # The last of the five CR stages, and the counterpart of finalize-delta:
-#   finalize-delta  MERGES the delta into the master docs  (the change stays OPEN)
-#   close-delta     ARCHIVES the change + bumps the version (the change is CLOSED)
+#   finalize-delta  MERGES the delta into spec.md + domain-model.md (the change stays OPEN)
+#   close-delta     ARCHIVES the change + bumps the version    (the change is CLOSED)
 #
-#   specify → design → analyze-delta-design → implement-delta → build
+#   specify → plan → analyze-plan-delta → implement → build → analyze-slice-delta
 #       → finalize-delta → analyze-slice → close-delta        ← you are here
 #
 # WHY THE SPLIT. finalize-delta used to do both. Merging first lets analyze-slice run
-# against a master spec.md/design.md that ALREADY carries the change — so its fix loops
+# against a master spec.md + domain-model.md that ALREADY carry the change — so its fix loops
 # repair code against the true, current requirements with no delta-awareness needed. But
 # if the close travelled with the merge, a red analyze-slice would land on a change that
 # was already archived and version-bumped: the only remedy would be a NEW change to
@@ -19,17 +19,19 @@
 #
 # This stage AUTHORS nothing and generates NO code — no model is invoked. It moves
 # changes/<id>/ into changes/archive/, bumps the minor version, clears active_change,
-# and STAMPS that version into the `**Version**:` header of spec.md + design.md — the
+# and STAMPS that version into the `**Version**:` header of spec.md + backend-plan.md — the
 # single irreversible act of the CR loop, deliberately isolated in a stage of its own.
 #
 # THE VERSION SPINE LIVES HERE, AND ONLY HERE. The number has three carriers — spec.md's
-# header, design.md's header, active_version.json — and all three move in this one step
-# by one deterministic mechanism. Before, design.md's header was bumped by the MODEL at
+# header, backend-plan.md's header, active_version.json — and all three move in this one step
+# by one deterministic mechanism. Before, backend-plan.md's header was bumped by the MODEL at
 # finalize-delta (a stage early, and guessing the target since the number was never
 # passed into the merge prompt) while spec.md's header was bumped by nobody at all,
-# leaving the "living truth" document permanently at v1.0. finalize-delta now writes the
-# Change History rows using version-read's `next_version` — the same bump() authority
-# this stage applies — and touches neither header.
+# leaving the "living truth" document permanently at v1.0. finalize-delta now writes
+# spec.md's Change History row using version-read's `next_version` — the same bump()
+# authority this stage applies — and touches neither header. It no longer merges the lane
+# plans at all (they are derived from spec.md + domain-model.md), so a plan header stamped
+# here is stating the version the slice ships as, not that the plan was re-derived for it.
 #
 # NOTE: nothing MECHANICALLY proves analyze-slice ran green before this point — the
 # stage boundary is operator-driven, as everywhere else in this pipeline. What IS
@@ -43,7 +45,7 @@
 # =============================================================================
 
 name: aw-spec-close-delta
-description: Close the open change — archive changes/<id>/ into changes/archive/, bump the minor version, clear active_change, and stamp that version into the feature's master headers (spec.md, design.md, and design.ui.md where the feature has a UI half), then anchor the close in the OKF freshness log. The final CR stage, run after finalize-delta merged the delta and analyze-slice verified the slice. The sole owner of the version spine; invokes no model and generates no code.
+description: Close the open change — archive changes/<id>/ into changes/archive/, bump the minor version, clear active_change, and stamp that version into the feature's master headers (spec.md, backend-plan.md, and frontend-plan.md where the feature has a UI half), then anchor the close in the OKF freshness log. The final CR stage, run after finalize-delta merged the delta and analyze-slice verified the slice. The sole owner of the version spine; invokes no model and generates no code.
 version: 1.1.0
 agent_agnostic: true
 dialect: aw-spec.orchestrator/v1
@@ -132,8 +134,8 @@ workflow:
       - { name: archived_dir,     from: "$.archived_dir" }
 
   # 4b. STAMP the number just computed into the two master headers, so spec.md,
-  #     design.md and active_version.json all carry it from the same instant by the
-  #     same mechanism. Previously design.md's header was bumped by the MODEL back at
+  #     backend-plan.md and active_version.json all carry it from the same instant by the
+  #     same mechanism. Previously backend-plan.md's header was bumped by the MODEL back at
   #     finalize-delta (guessing the target — the number was never passed to it) and
   #     spec.md's header was bumped by nobody, so it sat at v1.0 for the life of the
   #     feature. Deterministic and idempotent; only the header value moves.
@@ -178,4 +180,4 @@ outputs:
   previous_version: "{{previous_version}}"
   archived_dir: "{{archived_dir}}"
   stamped_docs: "{{stamped_docs}}"
-  next: "Change {{active_change}} CLOSED — archived to {{archived_dir}}, version {{previous_version}} -> {{version}}, stamped into {{stamped_count}} master header(s) ({{stamped_docs}}). spec.md, design.md and active_version.json now all read {{version}} — and design.ui.md too where the feature has a UI half ({{stamped_docs}} names what was actually rewritten); the masters describe the shipped state and the feature is free to take a new change. Next: /appweaver run → deploy, or start the next change with /appweaver specify."
+  next: "Change {{active_change}} CLOSED — archived to {{archived_dir}}, version {{previous_version}} -> {{version}}, stamped into {{stamped_count}} master header(s) ({{stamped_docs}}). spec.md, backend-plan.md and active_version.json now all read {{version}} — and frontend-plan.md too where the feature has a UI half ({{stamped_docs}} names what was actually rewritten); the masters describe the shipped state and the feature is free to take a new change. Next: /appweaver run → deploy, or start the next change with /appweaver specify."

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

@@ -723,5 +723,5 @@ outputs:
   ui_rule_files: "{{ui_rule_files}}"
   ui_validation_ok: "{{ui_ok}}"
   ui_validation_issues: "{{ui_issues}}"
-  note: "Split constitution authored, one half per LANE the project declared in .appweaver/stacks.json. service_lane / ui_lane report which lanes were found there, and the declaration is the ONLY signal read: a half is a lane's standing governance, so a lane declared `(none)` in select-stack gets no half AND no file. constitution.technical.md is the service lane's base (standing input to design + implement); constitution.ui.md is the UI lane's UX-* base (standing input to ui-design + ui-implement); constitution.domain.md is the domain addenda (standing input to specify + a gate checklist), and it is always authored because domain is not a lane — it addends whichever halves exist. All are composed into constitution.md, which now tolerates an absent technical half: a UI-only project's domain half opens the roman-numeral sequence at I instead of continuing one, and numbering_checked reports false because that check has no subject rather than because it silently passed. Mapping ## /aw-spec-ui-constitution supplies the rules the UI half ratifies but no longer creates the lane on its own — a mapped rule set with no declared lane produces a warning naming both fixes. ui_lane false with ui_included true means a lane was retired after its half was authored: the file is left alone and the log says so, because a ratified governance file is never deleted automatically. 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 — /appweaver specify loads constitution.domain.md; design + implement load constitution.technical.md; ui-design + ui-implement load constitution.ui.md. Re-run /appweaver constitution to amend, including to pick up a lane declared or dropped after this run — re-run /appweaver select-stack first to change which lanes exist."
+  note: "Split constitution authored, one half per LANE the project declared in .appweaver/stacks.json. service_lane / ui_lane report which lanes were found there, and the declaration is the ONLY signal read: a half is a lane's standing governance, so a lane declared `(none)` in select-stack gets no half AND no file. constitution.technical.md is the service lane's base (standing input to the SERVICE lane of plan + implement); constitution.ui.md is the UI lane's UX-* base (standing input to their FRONTEND lane); constitution.domain.md is the domain addenda (standing input to specify + a gate checklist), and it is always authored because domain is not a lane — it addends whichever halves exist. All are composed into constitution.md, which now tolerates an absent technical half: a UI-only project's domain half opens the roman-numeral sequence at I instead of continuing one, and numbering_checked reports false because that check has no subject rather than because it silently passed. Mapping ## /aw-spec-ui-constitution supplies the rules the UI half ratifies but no longer creates the lane on its own — a mapped rule set with no declared lane produces a warning naming both fixes. ui_lane false with ui_included true means a lane was retired after its half was authored: the file is left alone and the log says so, because a ratified governance file is never deleted automatically. 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 — /appweaver specify loads constitution.domain.md; the SERVICE lane of plan + implement loads constitution.technical.md; their FRONTEND lane loads constitution.ui.md. Re-run /appweaver constitution to amend, including to pick up a lane declared or dropped after this run — re-run /appweaver select-stack first to change which lanes exist."