aw-spec-cli 0.1.16 → 0.1.18

package/assets/.appweaver/scripts/powershell/aw-xref.ps1

@@ -6,10 +6,9 @@
 #
 #   aw-xref.ps1 record         --using X --design <design.md> [--origin ...] [--date YYYY-MM-DD] [--root DIR]
 #   aw-xref.ps1 list           --aggregate Y [--root DIR] [--bundle knowledge]
-#   aw-xref.ps1 concept-upsert   --aggregate X [--source-files a,b,c] [--lane backend|frontend] [--merge] [--description D] [--origin ...] [--root DIR]
+#   aw-xref.ps1 concept-upsert   --aggregate X [--source-files a,b,c] [--description D] [--origin ...] [--root DIR]
 #   aw-xref.ps1 concept-overview --aggregate X (--text PROSE | --text-file F) [--root DIR]
 #   aw-xref.ps1 concept-paths    --aggregate X | --feature-dir <dir> [--root DIR] [--bundle knowledge]
-#   aw-xref.ps1 concept-coverage --aggregate X | --feature-dir <dir> [--ids "FR-001,BR-002"] [--max-list N] [--root DIR] [--bundle knowledge]
 $ErrorActionPreference = "Stop"
 $core = Join-Path $PSScriptRoot "..\python\aw-xref.py"
 & python3 $core @args

package/assets/.appweaver/scripts/python/aw-payload-parity.py

@@ -6,9 +6,9 @@ aw-spec-actions.sh and as a `$PyName = @'…'@` here-string in aw-spec-actions.p
 contract is that each pair is BYTE-IDENTICAL, and nothing checked it — so a fix applied to
 one shell and forgotten in the other is a gate that behaves differently on Windows, in
 silence. Three of the ops with no twin at all are on the forward chain (resolve-hooks, with
-17 call sites across the nine workflows, and checklist-read / checklist-apply, which produce
-analyze-design's and analyze-slice's LIFT-FAILURE findings), and every one of them was read
-in bash when the workflows were reviewed.
+call sites in 21 of the workflows, and checklist-read / checklist-apply, which produce the
+analyze phases' LIFT-FAILURE findings), and every one of them was read in bash when the
+workflows were reviewed.
 
 WHAT IT CHECKS
   1. Every bash payload has a byte-identical PowerShell twin.
@@ -41,7 +41,23 @@ PS_REL = ".appweaver/scripts/powershell/aw-spec-actions.ps1"
 # implemented natively on the PowerShell side and the two must be reviewed in pairs.
 ACCEPTED_BASH_ONLY = {
     "cmd_resolve_hooks",
+    "cmd_list_contexts",
+    "cmd_context_paths",
     "cmd_list_features",
+    # The two change-listing ops. Both walk changes/<cr-id>/ and read a header line out of
+    # each delta document — directory enumeration and a regex, which PowerShell does
+    # natively without paying for a python spawn per invocation. Short enough to review as
+    # a pair, which is the bar for this list.
+    "cmd_cr_list",
+    "cmd_cr_paths",
+    # Aggregate overlap between open model deltas: two markdown regexes over a directory
+    # listing. Native on both sides for the same reason as the pair above.
+    "cmd_cr_overlap",
+    # Header stamping and wave discovery are a few lines of regex over a markdown header.
+    # PowerShell does that natively at a fraction of the cost of spawning python, and both
+    # sides are short enough to review as a pair — which is the bar for this list.
+    "_stamp_header",
+    "_max_open_wave",
     "cmd_checklist_read",
     "cmd_checklist_apply",
     "cmd_compose_constitution",

package/assets/.appweaver/scripts/python/aw-stack.py

@@ -901,9 +901,13 @@ def cmd_resolve(args):
 # when implement writes into it. Every phase that READS the subtree — implement,
 # build, run, onboard — leaves the check on.
 
+# Named in the "no <kind> lane is declared, and %s needs one" message, for a caller that
+# passed --require but no --command of its own. `implement` covers both lanes in one
+# command and requires neither kind, so it passes no --require at all and never reaches
+# these.
 KIND_PHASES = {
-    "backend": "implement / implement-delta / build / run",
-    "frontend": "ui-implement / ui-implement-delta",
+    "backend": "implement's service lane / build / run",
+    "frontend": "implement's frontend lane",
 }