aw-spec-cli 0.1.26 → 0.1.27

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

@@ -16,7 +16,7 @@ into a single cross-platform python core, with two brownfield additions:
     are SIGNALS, not decisions: the workflow's agent draws the real aggregate
     boundaries. This is the "inventory following aggregate root" the pipeline
     needs — one aggregate ≈ one candidate specs/<Feature>/ vertical slice.
-  * frontend_signals — candidate FRONTEND LANE roots derived from component /
+  * frontend_signals — candidate FRONTEND lane root folders derived from component /
     view / stylesheet clustering around frontend build configs. Like the
     aggregate signals these are SIGNALS, not decisions, and they are what lets
     /appweaver onboard answer "does this repo have a UI, and where" from the
@@ -24,7 +24,7 @@ into a single cross-platform python core, with two brownfield additions:
   * ui_attribution — which frontend files serve which aggregate, so a slice's OKF
     concept carries its UI surface and not just its backend files. Needed because
     the lane scoping below builds aggregate_signals from backend files ALONE.
-    Searches the FRONTEND SOURCE PATH only (declared root, else the roots the scan
+    Searches the FRONTEND LANE ROOT FOLDER only (declared root, else the roots the scan
     found) and does not run at all where the repo has no frontend — a backend repo's
     email templates and docs stylesheets are not its UI. Signals again: files
     matching no aggregate are reported unattributed rather than forced into one.
@@ -153,7 +153,7 @@ UI_COMPONENT_RE = re.compile(
 UI_MARKUP_RE = re.compile(r"\.(html?|xhtml)$", re.IGNORECASE)
 UI_STYLE_RE = re.compile(r"\.(css|scss|sass|less|styl|pcss)$", re.IGNORECASE)
 # A build/tooling config only a frontend carries. The strongest separable-lane
-# signal there is: the directory holding one IS the lane root.
+# signal there is: the directory holding one IS the lane root folder.
 UI_BUILD_CFG_RE = re.compile(
     r"(^|/)(angular\.json|vite\.config\.[cm]?[jt]s|next\.config\.[cm]?[jt]s|"
     r"nuxt\.config\.[cm]?[jt]s|svelte\.config\.[cm]?[jt]s|vue\.config\.[cm]?[jt]s|"
@@ -223,7 +223,7 @@ UI_STRONG_MIN = 5
 
 
 def frontend_signals(files, churn_map):
-    """Derive CANDIDATE frontend lane roots — the deterministic answer to "does
+    """Derive CANDIDATE frontend lane root folders — the deterministic answer to "does
     this repo have a UI, and where". Each root reports its evidence, what KIND of
     UI it is, and whether it is SEPARABLE (owns a subtree) or server-rendered
     inside the service tree.
@@ -471,9 +471,16 @@ def is_excluded(path, config_excludes):
 
 # The agent integrations the kit installs beside a project, and the agent-instruction
 # files at the repository root. Configuration for an assistant, never evidence of how
-# the project's code is built.
-KIT_AGENT_DIRS = (".claude", ".agents", ".kilocode")
-KIT_AGENT_FILES = ("CLAUDE.md", "AGENTS.md")
+# the project's code is built. Each agent folder is excluded whole, the project's own
+# assistant setup in it included. `.kilocode` is where older kit installs put Kilo.
+# `.github/` also holds the project's CI, so only the kit's launcher there is excluded,
+# by its exact path.
+KIT_AGENT_DIRS = (
+    ".claude", ".agents", ".kilo", ".kilocode", ".cursor", ".copilot", ".devin",
+    ".cline", ".clinerules", ".roo", ".opencode", ".factory", ".augment",
+    ".continue", ".kiro", ".codex", ".gemini", ".amp",
+)
+KIT_AGENT_FILES = ("CLAUDE.md", "AGENTS.md", ".github/prompts/appweaver.prompt.md")
 
 
 def kit_excludes(root):
@@ -485,11 +492,11 @@ def kit_excludes(root):
     `guardrails/` and `foundations/` are ordinary names a project may use for its own
     code, so each is excluded only when it has the kit's shape: `guardrails/` holding
     one of the kit's rule tiers, `foundations/` holding a scaffold pack (a directory with
-    a `*.pack.txt`). The agent directories and root instruction files are excluded
+    a `*.pack.txt`). The agent directories and agent instruction files are excluded
     whenever present."""
     names = [d for d in KIT_AGENT_DIRS if os.path.isdir(os.path.join(root, d))]
     g = os.path.join(root, "guardrails")
-    if any(os.path.isdir(os.path.join(g, t)) for t in ("projects", "technology", "domain")):
+    if any(os.path.isdir(os.path.join(g, t)) for t in ("project-specific", "technology", "domain")):
         names.append("guardrails")
     f = os.path.join(root, "foundations")
     if os.path.isdir(f):
@@ -518,7 +525,7 @@ def _ignore_rules(dirpath, base):
     """The patterns one .gitignore contributes, as (dir_rel, pattern, dir_only, anchored).
 
     Best-effort by design — negation, character classes and escaped spaces are not
-    honoured. It exists for the one case git cannot answer: a lane root the HOST
+    honoured. It exists for the one case git cannot answer: a lane root folder the HOST
     repository ignores wholesale, whose own nested .gitignore files still describe
     what inside it is build output."""
     rules = []
@@ -589,11 +596,11 @@ def list_files(root, config_excludes, lane_roots=()):
     same ignore rules git itself would, including nested .gitignore files, so build
     output (obj/, bin/, node_modules/) stays out exactly as before.
 
-    A DECLARED LANE ROOT IS READ EVEN WHEN THE HOST REPO IGNORES IT. A codebase under
+    A DECLARED LANE ROOT FOLDER IS READ EVEN WHEN THE HOST REPO IGNORES IT. A codebase under
     assessment is often nested inside a repository that deliberately keeps it out of
     version control — a test bed, a vendored drop, a legacy tree copied in for analysis.
     git then answers "nothing here" for the one subtree select-stack said IS the code.
-    The declaration outranks the host's ignore rule: an ignored lane root is walked from
+    The declaration outranks the host's ignore rule: an ignored lane root folder is walked from
     disk, with build output pruned and the lane's OWN nested .gitignore files applied.
     """
     if git(root, "rev-parse", "--git-dir"):
@@ -2941,7 +2948,7 @@ def attribute_ui_files(signals, fe_files, churn_map, ui_roots, feature_aggs=None
     the architecture note instead of being forced into a slice.
 
     SCOPED TO THE FRONTEND TREE, AND SKIPPED ENTIRELY WITHOUT ONE. `ui_roots` is the
-    lane's source path — the declared one, or the roots the scan actually found. Two
+    lane root folder — the declared one, or the roots the scan actually found. Two
     guards, because neither is sufficient alone: with no UI root declared scope_to_lanes
     hands back the WHOLE REPO as the frontend list, and the file-shape regexes match
     plenty of things a backend repo legitimately owns — a server-side email template, a
@@ -3091,7 +3098,7 @@ def bundle_state(bundle_dir):
 
 
 def _lane_prefix(p):
-    """A declared source path as a '/'-terminated repo-relative prefix, or ''."""
+    """A declared lane root folder as a '/'-terminated repo-relative prefix, or ''."""
     s = (p or "").strip().replace("\\", "/").lstrip("./").lstrip("/")
     if s and not s.endswith("/"):
         s += "/"
@@ -3177,7 +3184,7 @@ def cmd_scan(args):
 
     # A DECLARED UI lane is a lane. The strength test below UI_STRONG_MIN exists to
     # stop a scan INVENTING one from a wwwroot/ of loose scripts; it has no business
-    # overruling a person who declared the lane and named its source path. What the
+    # overruling a person who declared the lane and named its lane root folder. What the
     # evidence still decides is what goes IN the governance — and a declared root
     # holding no recognisable UI files is reported as exactly that, so onboard can
     # say so rather than quietly authoring a UI half out of nothing.
@@ -3193,7 +3200,7 @@ def cmd_scan(args):
                               "build_configs": [], "route_files": [], "store_files": []}]
 
     # Give every aggregate candidate the UI that serves it — searching the FRONTEND
-    # SOURCE PATH and nothing else. The declared root is the authority; absent a
+    # LANE ROOT FOLDER and nothing else. The declared root is the authority; absent a
     # declaration the roots the scan actually found stand in, which keeps a repo whose
     # UI is server-rendered inside the service tree covered. With neither, this repo
     # has no frontend and the pass does not run at all.
@@ -3295,7 +3302,7 @@ def cmd_scan(args):
         "frontend_present": "true" if fsig["present"] else "false",
         "frontend_separable": "true" if fsig["separable"] else "false",
         "frontend_root_count": len(fsig["roots"]),
-        # The PRIMARY lane root — the strongest candidate, and the single value a
+        # The PRIMARY lane root folder — the strongest candidate, and the single value a
         # lane declaration needs. Empty when no root reached lane strength.
         "frontend_root": next((r["root"] for r in fsig["roots"]
                                if r["confidence"] == "strong"), ""),
@@ -4526,10 +4533,10 @@ def main():
     ps.add_argument("--bundle", help="OKF bundle dir to check for existing curation (default: <root>/knowledge).")
     ps.add_argument("--config", help="okf-config.yml whose exclude: list is honored.")
     ps.add_argument("--service-root", dest="service_root", default="",
-                    help="The service lane's declared source path. Backend signals are "
+                    help="The declared lane root folder of the service lane. Backend signals are "
                          "derived from this subtree only.")
     ps.add_argument("--ui-root", dest="ui_root", default="",
-                    help="The UI lane's declared source path. Frontend signals are derived "
+                    help="The declared lane root folder of the UI lane. Frontend signals are derived "
                          "from this subtree only, and it is excluded from the backend's — "
                          "so neither lane's substrate carries the other's files.")
     ps.add_argument("--map", help="Machine map whose features attribute UI feature folders "
@@ -4541,9 +4548,9 @@ def main():
     pp.add_argument("--root", help="Codebase to scan (default: CWD).")
     pp.add_argument("--config", help="okf-config.yml whose exclude: list is honored.")
     pp.add_argument("--service-root", dest="service_root", default="",
-                    help="The service lane's declared source path.")
+                    help="The declared lane root folder of the service lane.")
     pp.add_argument("--ui-root", dest="ui_root", default="",
-                    help="The UI lane's declared source path.")
+                    help="The declared lane root folder of the UI lane.")
     pp.add_argument("--strategy", default="",
                     help="Pass A strategy: structure | reference | persistence. "
                          "Default: the highest-coverage AVAILABLE strategy, ties "

package/assets/.appweaver/scripts/python/aw-plan-coverage.py

@@ -15,7 +15,7 @@ lane's code names it and whether the generating model reported it done.
 TWO KINDS OF ELEMENT.
   checked      an identifier the code must contain — an entity, value object, domain
                event or use-case (backend); a component (frontend); an identifier in a
-               delta plan's ADDED table. Searched for in the lane's source path, test
+               delta plan's ADDED table. Searched for in the lane root folder, test
                files excluded. Entities and value objects must appear as a whole word.
                Every other checked name may carry a suffix, because stacks add one by
                convention: `MedicationOrderPlaced` is realised as
@@ -246,7 +246,7 @@ def is_test_file(rel):
 
 
 def scan(repo, source_path, test_path, names):
-    """{name: [relative files naming it]} over the lane's source path, tests excluded.
+    """{name: [relative files naming it]} over the lane root folder, tests excluded.
 
     `names` holds (name, whole) keys: whole is True when the name must appear as a whole
     word, False when an identifier that STARTS with it counts.

package/assets/.appweaver/scripts/python/aw-rev-constitution.py

@@ -15,7 +15,7 @@ amends it additively from its own code. The standalone
 steps without calling this core.
 
 This core is the MODEL-FREE half: it gathers the project framing the OKF bundle holds
-and scaffolds the `guardrails/projects/brf-<domain>/` project directory; the calling
+and scaffolds the `guardrails/brf-<domain>/` project directory; the calling
 workflow's authoring agents fill its rule files + the split constitution. Governance
 stance is AS-BUILT (the constitution reflects what the code does, not an aspiration).
 
@@ -36,7 +36,7 @@ STDERR so they never corrupt the JSON contract:
           works; it answers with this framing and no longer lists features.
 
   project-setup --name <domain> [--fallback <name>] [--root <dir>]
-      -> slugify + `brf-` prefix the domain, create guardrails/projects/<slug>/ with its
+      -> slugify + `brf-` prefix the domain, create guardrails/<slug>/ with its
          service/ frontend/ domain/ subfolders when the project does not exist yet.
          Without --name, an ACTIVE `brf-` project (.appweaver/domain.json) that already
          holds rule files wins over the fallback name, so every later context amends the
@@ -196,7 +196,7 @@ def _active_brf_project(root):
         return ""
     if not name.startswith("brf-"):
         return ""
-    d = os.path.join(root, "guardrails", "projects", name)
+    d = os.path.join(root, "guardrails", name)
     return name if _md_files(d, root) else ""
 
 
@@ -214,7 +214,7 @@ def cmd_pack_setup(args):
     slug = re.sub(r"^brf-+", "", slug)
     domain_slug = "brf-" + slug
 
-    pack_dir = os.path.join(root, "guardrails", "projects", domain_slug)
+    pack_dir = os.path.join(root, "guardrails", domain_slug)
     # A project that already holds .md files was authored by an earlier context: the
     # calling workflow AMENDS it rather than authoring it again. The walk covers the
     # whole subtree, because a project's rule files live in its service/ frontend/
@@ -248,7 +248,7 @@ def cmd_pack_setup(args):
         "root": root,
     }
     print(
-        f"[govern-backward] project: guardrails/projects/{domain_slug}/ "
+        f"[govern-backward] project: guardrails/{domain_slug}/ "
         f"({'EXISTS — ' + ', '.join(f'{k} {len(v)}' for k, v in tiers.items()) if present else 'created'})",
         file=sys.stderr,
     )
@@ -273,7 +273,7 @@ def main(argv):
     # the folder it creates is a PROJECT, so the primary name says so, and a caller
     # written against either spelling reaches the same code.
     for name in ("project-setup", "pack-setup"):
-        ps = sub.add_parser(name, help="create the guardrails/projects/brf-<domain>/ project dir")
+        ps = sub.add_parser(name, help="create the guardrails/brf-<domain>/ project dir")
         ps.add_argument("--name", default="")
         ps.add_argument("--fallback", default="")
         ps.add_argument("--root", default="")