@codedrifters/configulator 0.0.260 → 0.0.262

package/lib/index.js

@@ -4543,7 +4543,7 @@ var jestBundle = {
 // src/agent/bundles/maintenance-audit.ts
 var maintenanceAuditSubAgent = {
   name: "maintenance-audit",
-  description: "Audits documentation registries and cross-references for integrity (broken links, registry drift, stale indexes) and applies idempotent fixes. One phase per session, tracked by maint:* GitHub issue labels with filesystem-based durability between phases.",
+  description: "Audits documentation registries and cross-references for integrity (broken links, registry drift, stale indexes), applies idempotent fixes, then re-runs the checks to confirm the fixes cleared the reported findings. One phase per session, tracked by maint:* GitHub issue labels with filesystem-based durability between phases.",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 80,
   platforms: { cursor: { exclude: true } },
@@ -4601,18 +4601,18 @@ var maintenanceAuditSubAgent = {
     "",
     "## State Machine Overview",
     "",
-    "Maintenance audits flow through **2 phases**:",
+    "Maintenance audits flow through **3 phases**:",
     "",
     "```",
-    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
-    "\u2502  1. SCAN     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. FIX      \u2502",
-    "\u2502  Walk doc    \u2502     \u2502  Read audit  \u2502",
-    "\u2502  tree, check \u2502     \u2502  report,     \u2502",
-    "\u2502  xrefs and   \u2502     \u2502  apply safe  \u2502",
-    "\u2502  indexes,    \u2502     \u2502  idempotent  \u2502",
-    "\u2502  write audit \u2502     \u2502  fixes, then \u2502",
-    "\u2502  report      \u2502     \u2502  verify      \u2502",
-    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u2502  1. SCAN     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. FIX      \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  3. VERIFY   \u2502",
+    "\u2502  Walk doc    \u2502     \u2502  Read audit  \u2502     \u2502  Re-run the  \u2502",
+    "\u2502  tree, check \u2502     \u2502  report,     \u2502     \u2502  scan checks \u2502",
+    "\u2502  xrefs and   \u2502     \u2502  apply safe  \u2502     \u2502  scoped to   \u2502",
+    "\u2502  indexes,    \u2502     \u2502  idempotent  \u2502     \u2502  fixed paths,\u2502",
+    "\u2502  write audit \u2502     \u2502  fixes, write\u2502     \u2502  compare pre \u2502",
+    "\u2502  report      \u2502     \u2502  fix report  \u2502     \u2502  and post    \u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
     "```",
     "",
     "**Issue labels encode the phase:**",
@@ -4620,18 +4620,22 @@ var maintenanceAuditSubAgent = {
     "| Label | Phase | Session work |",
     "|-------|-------|-------------|",
     "| `maint:scan` | 1. Scan | Walk the configured doc tree, check cross-references and registry indexes, write a durable audit report. |",
-    "| `maint:fix` | 2. Fix | Read the audit report, apply idempotent fixes, then verify the fixes cleared the reported findings. |",
+    "| `maint:fix` | 2. Fix | Read the audit report, apply idempotent fixes, write a durable fix report. |",
+    "| `maint:verify` | 3. Verify | Re-run the same checks from the parent `maint:scan` issue scoped to the paths and registries the fix phase touched, compare pre and post findings, close the parent scan issue when clean, and file a follow-up `maint:scan` for any residual findings. |",
     "",
     "All issues also carry `type:maintenance` and a `status:*` label.",
     "",
-    "**Issue count per audit cycle:** 1 scan + 1 fix = **2 sessions**.",
+    "**Issue count per audit cycle:** 1 scan + 1 fix + 1 verify = **3 sessions**.",
     "",
     "**Shortened paths:**",
     "- Scan finds no issues \u2192 close scan issue with a justification,",
-    "  do not create a fix issue \u2192 **1 session**.",
+    "  do not create a fix or verify issue \u2192 **1 session**.",
     "- Every reported finding requires a human judgment call \u2192 close",
     "  scan with the report, open a `status:needs-attention` flag,",
-    "  do not auto-create a fix issue \u2192 **1 session**.",
+    "  do not auto-create a fix or verify issue \u2192 **1 session**.",
+    "- Fix phase applied only `flag-for-human` decisions (no auto-",
+    "  fixable findings landed) \u2192 close the fix issue with the",
+    "  skipped list and do not create a verify issue \u2192 **2 sessions**.",
     "",
     "---",
     "",
@@ -4661,7 +4665,9 @@ var maintenanceAuditSubAgent = {
     "Run this loop exactly once per session. Never start a second issue.",
     "",
     "1. Claim one open `type:maintenance` issue using phase priority:",
-    "   `maint:scan` > `maint:fix`.",
+    "   `maint:verify` > `maint:fix` > `maint:scan`. Verify ahead of fix",
+    "   and scan so the oldest in-flight audit cycle finishes closing",
+    "   the loop before a new cycle starts.",
     "2. Transition `status:ready` \u2192 `status:in-progress` and create the",
     "   branch per your project's branch-naming convention.",
     "3. Execute the phase handler that matches the issue's `maint:*`",
@@ -4773,24 +4779,30 @@ var maintenanceAuditSubAgent = {
     "   - **All findings need human judgment** \u2192 commit the report,",
     "     comment on the scan issue summarizing the findings, apply",
     "     `status:needs-attention`, and close the issue. Do not create",
-    "     a `maint:fix` issue.",
+    "     a `maint:fix` or `maint:verify` issue.",
     "   - **At least one auto-fixable finding** \u2192 create a `maint:fix`",
     "     issue (blocked on this scan issue via `Depends on: #N`). The",
-    "     fix issue body must reference the audit report path and",
-    "     enumerate the auto-fix categories to apply.",
+    "     fix issue body must reference the audit report path, enumerate",
+    "     the auto-fix categories to apply, and record the parent scan",
+    "     issue number so Phase 3 (Verify) can close the loop.",
     "",
-    "6. **Commit and push.**",
+    "6. **Commit and push.** Leave the scan issue open so the downstream",
+    "   `maint:verify` phase can close it (or file a follow-up scan)",
+    "   after Phase 2 runs.",
     "",
     "---",
     "",
     "## Phase 2: Fix (`maint:fix`)",
     "",
-    "**Goal:** Read the audit report, apply idempotent fixes, verify",
-    "they cleared the reported findings, and commit the doc-tree changes.",
+    "**Goal:** Read the audit report, apply idempotent fixes, write a",
+    "fix report, and enqueue the verify phase so the audit cycle",
+    "actually closes its loop.",
     "",
-    "**Budget:** Bounded edits to files under `<DOCS_ROOT>` plus a final",
-    "verification re-run of the checks from Phase 1. No new audit",
-    "categories. No fixes that require authoring new content.",
+    "**Budget:** Bounded edits to files under `<DOCS_ROOT>` and one fix",
+    "report file. No new audit categories. No fixes that require",
+    "authoring new content. The formal re-scan lives in Phase 3 \u2014",
+    "Phase 2 confirms only that it did not regress the files it touched",
+    "(a smoke check, not the full pre/post comparison).",
     "",
     "### Fix Categories",
     "",
@@ -4824,11 +4836,13 @@ var maintenanceAuditSubAgent = {
     "   mark it `flag-for-human` and skip. Authoring new docs belongs",
     "   to the writer agent for that doc type, not this agent.",
     "",
-    "5. **Verify.** Re-run the same checks the scan phase ran, scoped",
-    "   to the files the fix phase touched (plus any index files those",
-    "   edits affect). Every finding the fix phase claimed to resolve",
-    "   must now be gone. Any finding that remains is a regression \u2014",
-    "   revert the corresponding edit and mark it `flag-for-human`.",
+    "5. **Smoke check the touched files.** Before writing the fix",
+    "   report, spot-check that the specific findings the fix phase",
+    "   claimed to resolve are at least no longer present in the edited",
+    "   file(s). This is a narrow local check \u2014 not the full re-scan,",
+    "   which is Phase 3's job. If a finding the fix phase targeted",
+    "   still reproduces in the edited file, revert that edit and mark",
+    "   the finding `flag-for-human` in the fix report instead.",
     "",
     "6. **Write the fix report** to:",
     "   ```",
@@ -4859,18 +4873,141 @@ var maintenanceAuditSubAgent = {
     "",
     "   ## Skipped",
     "   <findings that were stale, flagged for human, or reverted",
-    "   during verification \u2014 one entry each, with the reason>",
+    "   during the smoke check \u2014 one entry each, with the reason>",
     "",
-    "   ## Verification",
-    "   - **Re-scan result:** clean / <N> residual findings",
-    "   - **Residual findings:** <list, with reasons \u2014 each becomes a",
-    "     follow-up `flag-for-human` note>",
+    "   ## Paths Touched",
+    "   <ordered list of files edited, plus any index files those edits",
+    "   affect. This is the Phase 3 re-scan scope \u2014 the verify phase",
+    "   reads this section to decide which paths to re-check.>",
     "   ```",
     "",
     "7. **Comment on the scan issue** with a summary of what was fixed,",
-    "   what was skipped, and any residual findings.",
+    "   what was skipped, and that Phase 3 (Verify) will close the loop.",
+    "",
+    "8. **Create the `maint:verify` issue.** Block it on this fix issue",
+    "   via `Depends on: #N` so it only runs after the fix PR lands.",
+    "   The verify issue body must reference:",
+    "   - The parent `maint:scan` issue number",
+    "   - The Phase 1 audit report path",
+    "   - The Phase 2 fix report path",
+    "   - The `Paths Touched` list (so Phase 3 scopes the re-scan",
+    "     correctly)",
+    "   - The same check catalog the scan phase used",
+    "",
+    "   If the fix phase applied **zero** auto-fixes (every finding was",
+    "   `stale-finding` or `flag-for-human`), skip the verify issue \u2014",
+    "   there is nothing to verify. Close the fix issue with a summary,",
+    "   comment on the scan issue, and let a human decide whether to",
+    "   re-scan.",
+    "",
+    "9. **Commit and push.**",
     "",
-    "8. **Commit and push.**",
+    "---",
+    "",
+    "## Phase 3: Verify (`maint:verify`)",
+    "",
+    "**Goal:** Close the loop on the audit cycle. Re-run the same checks",
+    "the scan phase ran, scoped to the paths and registries the fix",
+    "phase actually touched, compare pre and post findings, and record",
+    "the result in a durable verify report.",
+    "",
+    "**Budget:** Filesystem reads + registry parsing, just like Phase 1,",
+    "but bounded to the paths enumerated in the fix report's",
+    "`Paths Touched` section (plus any index files those paths transit).",
+    "No edits to source docs in this phase \u2014 if the re-scan surfaces a",
+    "regression, record it and file a follow-up `maint:scan` issue,",
+    "but do not attempt to re-fix in-session.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the verify scope** from the issue body. Confirm the parent",
+    "   scan issue number, the audit report path, the fix report path,",
+    "   and the `Paths Touched` list. If any of these are missing or",
+    "   the files they reference do not exist, close the verify issue",
+    "   with `status:needs-attention` and stop.",
+    "",
+    "2. **Re-run the same checks the scan phase ran**, scoped to the",
+    "   paths the fix phase touched plus any index or registry files",
+    "   those paths transit. Use the identical check catalog that the",
+    "   parent scan issue declared \u2014 do not add or remove checks",
+    "   between scan and verify.",
+    "",
+    "3. **Compare pre and post findings.** For each finding in the Phase 1",
+    "   audit report that fell within the re-scan scope, classify it as:",
+    "   - **resolved** \u2014 absent from the re-scan; the fix worked.",
+    "   - **still-failing** \u2014 still present in the re-scan; the fix did",
+    "     not clear it.",
+    "   - **regressed** \u2014 was not in the Phase 1 audit report but appears",
+    "     now; the fix introduced it.",
+    "   - **out-of-scope** \u2014 was in the Phase 1 audit report but its",
+    "     path was not in the fix phase's `Paths Touched` list, so this",
+    "     verify pass cannot speak to it.",
+    "",
+    "4. **Write the verify report** to:",
+    "   ```",
+    "   <AUDIT_ROOT>/maint-verify-<AUDIT_SLUG>-<YYYY-MM-DD>.md",
+    "   ```",
+    "",
+    "   Format:",
+    "   ```markdown",
+    "   ---",
+    '   title: "Maintenance Verify: <AUDIT_SLUG>"',
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   scan_issue: <N>",
+    "   fix_issue: <N>",
+    "   audit_report: <path to Phase 1 scan report>",
+    "   fix_report: <path to Phase 2 fix report>",
+    "   status: complete",
+    "   ---",
+    "",
+    "   # Maintenance Verify: <AUDIT_SLUG>",
+    "",
+    "   ## Source Reports",
+    "   - Scan report: <link>",
+    "   - Fix report: <link>",
+    "",
+    "   ## Re-scan Scope",
+    "   - **Paths re-checked:** <list \u2014 from the fix report's",
+    "     `Paths Touched` section>",
+    "   - **Checks re-run:** <same catalog the scan phase used>",
+    "",
+    "   ## Pre/Post Comparison",
+    "   | Status | Count | Findings |",
+    "   |--------|-------|----------|",
+    "   | resolved | N | <one line per finding: category + file:line> |",
+    "   | still-failing | N | <one line per finding> |",
+    "   | regressed | N | <one line per finding> |",
+    "   | out-of-scope | N | <one line per finding> |",
+    "",
+    "   ## Verdict",
+    "   - **clean** \u2014 every in-scope finding resolved and no regressions;",
+    "     the parent scan issue will be closed.",
+    "   - **residual** \u2014 one or more still-failing or regressed findings;",
+    "     a follow-up `maint:scan` issue is filed and the parent scan",
+    "     issue is closed with a reference to the follow-up.",
+    "   ```",
+    "",
+    "5. **Decide the next step:**",
+    "   - **Clean verdict** (every in-scope finding resolved, no",
+    "     regressions, no still-failing entries) \u2192 comment on the parent",
+    "     `maint:scan` issue summarizing the result and **close it**.",
+    "     Do not file a follow-up scan.",
+    "   - **Residual verdict** (one or more `still-failing` or",
+    "     `regressed` entries) \u2192 file a new `maint:scan` issue for the",
+    "     residual scope, blocked on nothing (it is ready to run on its",
+    "     own schedule), and link the verify report from its body. Then",
+    "     comment on the parent scan issue with the residual summary and",
+    "     **close it**.",
+    "   - **Out-of-scope-only verdict** (every finding fell outside the",
+    "     fix phase's `Paths Touched`) \u2192 comment on the parent scan",
+    "     issue explaining that the fix phase did not cover those paths",
+    "     and leave it open with `status:needs-attention` so a human can",
+    "     re-scope the cycle. Do not auto-close the parent scan issue",
+    "     in this case.",
+    "",
+    "6. **Commit and push.** Close the verify issue with a one-line",
+    "   summary of the verdict.",
     "",
     "---",
     "",
@@ -4880,11 +5017,13 @@ var maintenanceAuditSubAgent = {
     "|-----------|-------|------|",
     "| Downstream (last resort) | Writer agent for the audited doc type | When the audit surfaces findings that require authoring new content (missing target, partial coverage that can only be resolved by writing a new doc), the fix phase flags them for human \u2014 the human may then dispatch the appropriate writer agent. This agent never opens writer-agent issues itself. |",
     "",
-    "**File boundaries:** Writes audit and fix reports to",
+    "**File boundaries:** Writes audit, fix, and verify reports to",
     "`<AUDIT_ROOT>/`. Applies bounded, idempotent edits under",
-    "`<DOCS_ROOT>/` per the fix-policy declared in the fix issue body.",
-    "Never writes to source code, never writes to doc trees outside",
-    "`<DOCS_ROOT>`, never authors new document files to close a gap.",
+    "`<DOCS_ROOT>/` only in Phase 2 (Fix), per the fix-policy declared",
+    "in the fix issue body. Phase 3 (Verify) never edits doc files \u2014",
+    "it only reads and re-scans. Never writes to source code, never",
+    "writes to doc trees outside `<DOCS_ROOT>`, never authors new",
+    "document files to close a gap.",
     "",
     "---",
     "",
@@ -4896,6 +5035,10 @@ var maintenanceAuditSubAgent = {
     "- All findings are `flag-for-human` and the fix issue has nothing",
     "  to auto-apply \u2014 resolve by closing the fix issue with a summary",
     "  instead",
+    "- A `maint:verify` issue references a fix report whose",
+    "  `Paths Touched` list is empty \u2014 there is nothing to re-scan, so",
+    "  close the verify issue with a summary and let a human decide",
+    "  whether to re-run the scan",
     "",
     "---",
     "",
@@ -4910,13 +5053,24 @@ var maintenanceAuditSubAgent = {
     "  Record out-of-scope observations in the report for human review.",
     "- **No authoring.** Do not invent new document content to close a",
     "  finding. That work belongs to the writer agent for the doc type.",
-    "- **Verify before closing.** Always re-run the checks after",
-    "  applying fixes and record the result in the fix report."
+    "- **Verify closes the loop.** Every fix-phase run that lands at",
+    "  least one auto-fix must enqueue a `maint:verify` issue. Phase 3",
+    "  is the only phase that closes the parent `maint:scan` issue.",
+    "  Phase 2 never closes the scan issue itself.",
+    "- **Pre/post comparison is required.** The verify report must",
+    "  classify every in-scope finding from the scan report as",
+    "  `resolved`, `still-failing`, `regressed`, or `out-of-scope`.",
+    "  An unclassified finding means the re-scan was incomplete \u2014 re-",
+    "  run the missing checks before writing the verdict.",
+    "- **Residual findings get their own cycle.** When the verify phase",
+    "  finds `still-failing` or `regressed` entries, file a follow-up",
+    "  `maint:scan` issue rather than attempting to re-fix in-session.",
+    "  The new scan starts its own audit cycle with a fresh report."
   ].join("\n")
 };
 var maintenanceAuditSkill = {
   name: "audit-docs",
-  description: "Kick off a documentation-maintenance audit cycle (scan \u2192 fix). Creates a maint:scan issue for the supplied scope and dispatches Phase 1.",
+  description: "Kick off a documentation-maintenance audit cycle (scan \u2192 fix \u2192 verify). Creates a maint:scan issue for the supplied scope and dispatches Phase 1.",
   disableModelInvocation: true,
   userInvocable: true,
   context: "fork",
@@ -4928,7 +5082,8 @@ var maintenanceAuditSkill = {
     "Kick off a maintenance-audit cycle against a configurable doc",
     "tree. Creates a `maint:scan` issue targeted at the requested",
     "scope and dispatches Phase 1 (Scan) in the maintenance-audit",
-    "agent.",
+    "agent. Subsequent phases (`maint:fix`, `maint:verify`) are",
+    "created automatically as the cycle progresses.",
     "",
     "## Usage",
     "",
@@ -4955,30 +5110,102 @@ var maintenanceAuditSkill = {
     "2. Execute Phase 1 (Scan) of the maintenance-audit agent.",
     "3. If auto-fixable findings exist, a `maint:fix` issue is created",
     "   automatically.",
+    "4. When the fix phase lands, a `maint:verify` issue is created",
+    "   automatically so Phase 3 can re-run the checks and close the",
+    "   parent scan issue.",
     "",
     "## Output",
     "",
     "- A `maint-audit-<slug>-<YYYY-MM-DD>.md` report under",
     "  `<AUDIT_ROOT>`.",
-    "- A `maint:fix` issue if auto-fixable findings were found."
+    "- A `maint:fix` issue if auto-fixable findings were found.",
+    "- A `maint:verify` issue after the fix phase lands (Phase 3",
+    "  produces a `maint-verify-<slug>-<YYYY-MM-DD>.md` report)."
+  ].join("\n")
+};
+var maintenanceVerifySkill = {
+  name: "verify-audit",
+  description: "Kick off the verify phase of a documentation-maintenance audit cycle. Creates a maint:verify issue that re-runs the scan checks scoped to the paths a fix phase touched, compares pre/post findings, and closes the parent maint:scan issue when clean or files a follow-up maint:scan for residual findings.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "maintenance-audit",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Verify Audit",
+    "",
+    "Close the loop on a maintenance-audit cycle. Creates a",
+    "`maint:verify` issue and dispatches Phase 3 (Verify) in the",
+    "maintenance-audit agent.",
+    "",
+    "Phase 3 re-runs the same checks the scan phase ran, scoped to the",
+    "paths the fix phase actually touched, compares pre and post",
+    "findings, and writes a verify report. Based on the verdict the",
+    "phase either closes the parent `maint:scan` issue or files a",
+    "follow-up `maint:scan` for residual findings.",
+    "",
+    "## Usage",
+    "",
+    "/verify-audit <scan-issue-number>",
+    "",
+    "Where `<scan-issue-number>` is the `maint:scan` issue that kicked",
+    "off the audit cycle. The skill resolves the scan report, the",
+    "Phase 2 fix report, and the `Paths Touched` list from that scan",
+    "issue's downstream `maint:fix` issue.",
+    "",
+    "Most cycles do not need this skill \u2014 Phase 2 (Fix) creates the",
+    "verify issue automatically. Use this skill when:",
+    "- Phase 2 ran on an older audit cycle that predates the verify",
+    "  phase and never enqueued a verify issue, or",
+    "- A human wants to re-run the verify phase after a manual fix",
+    "  applied on top of the Phase 2 PR.",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `maint:verify` issue with `type:maintenance`,",
+    "   `priority:medium`, and `status:ready`. Body must list:",
+    "   - The parent `maint:scan` issue number",
+    "   - The Phase 1 audit report path",
+    "   - The Phase 2 fix report path (if one exists)",
+    "   - The `Paths Touched` list (copied from the fix report)",
+    "   - The audit check catalog (copied from the scan issue)",
+    "2. Execute Phase 3 (Verify) of the maintenance-audit agent.",
+    "",
+    "## Output",
+    "",
+    "- A `maint-verify-<slug>-<YYYY-MM-DD>.md` report under",
+    "  `<AUDIT_ROOT>` containing the pre/post comparison.",
+    "- The parent `maint:scan` issue is closed (clean verdict) or a",
+    "  follow-up `maint:scan` issue is filed (residual verdict)."
   ].join("\n")
 };
 var maintenanceAuditBundle = {
   name: "maintenance-audit",
-  description: "Documentation-maintenance agent bundle. 2-phase pipeline (scan, fix) with maint:* phase labels for auditing registries and cross-references and applying idempotent fixes. Enabled by default.",
+  description: "Documentation-maintenance agent bundle. 3-phase pipeline (scan, fix, verify) with maint:* phase labels for auditing registries and cross-references, applying idempotent fixes, and confirming the fixes cleared the originally-flagged findings. Enabled by default.",
   appliesWhen: () => true,
   rules: [
     {
       name: "maintenance-audit-workflow",
-      description: "Describes the 2-phase documentation-maintenance pipeline, the maint:* label taxonomy, and the audit-before-fix boundary.",
+      description: "Describes the 3-phase documentation-maintenance pipeline, the maint:* label taxonomy, the audit-before-fix boundary, and the verify-closes-the-loop rule.",
       scope: AGENT_RULE_SCOPE.ALWAYS,
       content: [
         "# Maintenance Audit Workflow",
         "",
         "Use `/audit-docs <scope>` to kick off a documentation-maintenance",
-        "audit cycle. The pipeline runs in 2 phases \u2014 scan and fix \u2014 each",
-        "tracked by its own GitHub issue labeled `maint:scan` or",
-        "`maint:fix`. All issues carry `type:maintenance`.",
+        "audit cycle. The pipeline runs in 3 phases \u2014 scan, fix, and",
+        "verify \u2014 each tracked by its own GitHub issue labeled",
+        "`maint:scan`, `maint:fix`, or `maint:verify`. All issues carry",
+        "`type:maintenance`.",
+        "",
+        "One additional user-invocable skill drives the verify phase",
+        "on demand:",
+        "",
+        "- `/verify-audit <scan-issue-number>` \u2014 re-run the scan checks",
+        "  scoped to the paths the fix phase touched, compare pre/post",
+        "  findings, and close the parent `maint:scan` issue (or file a",
+        "  follow-up for residual findings). Phase 2 (Fix) normally",
+        "  enqueues the verify issue automatically \u2014 this skill is the",
+        "  explicit entry point for re-running the phase on demand.",
         "",
         "The maintenance-audit agent *audits doc registries and applies",
         "idempotent fixes*; it does **not** author new document content.",
@@ -4994,7 +5221,7 @@ var maintenanceAuditBundle = {
       tags: ["workflow"]
     }
   ],
-  skills: [maintenanceAuditSkill],
+  skills: [maintenanceAuditSkill, maintenanceVerifySkill],
   subAgents: [maintenanceAuditSubAgent],
   labels: [
     {
@@ -5011,6 +5238,11 @@ var maintenanceAuditBundle = {
       name: "maint:fix",
       color: "BFDADC",
       description: "Phase 2: apply idempotent fixes from a maintenance audit report"
+    },
+    {
+      name: "maint:verify",
+      color: "D4C5F9",
+      description: "Phase 3: re-run the scan checks scoped to the paths the fix phase touched, compare pre/post findings, and close or re-queue the parent scan"
     }
   ]
 };
@@ -14224,7 +14456,7 @@ var slackBundle = {
 // src/agent/bundles/software-profile.ts
 var softwareProfileAnalystSubAgent = {
   name: "software-profile-analyst",
-  description: "Researches a software product (competitor, adjacent, incumbent, enabler, infrastructure, or ecosystem-tool) from public sources, produces a structured markdown profile, and contributes rows to a shared feature matrix ranked against configurable segment-importance weights, then enqueues downstream `company:research` and `people:research` issues for the vendor company and primary-attribution founders/leaders surfaced during profiling. One product per session, tracked by software:* GitHub issue labels.",
+  description: "Researches a software product (competitor, adjacent, incumbent, enabler, infrastructure, or ecosystem-tool) from public sources, produces a structured markdown profile, contributes rows to a shared feature matrix ranked against configurable segment-importance weights, maps features back to the BCM capability model and flags unmapped features, then enqueues downstream `bcm:outline`, `company:research`, and `people:research` issues for new sub-capabilities, the vendor company, and primary-attribution founders/leaders surfaced during profiling. One product per session, tracked by software:* GitHub issue labels.",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 80,
   platforms: { cursor: { exclude: true } },
@@ -14234,8 +14466,9 @@ var softwareProfileAnalystSubAgent = {
     "You research a single software product from public sources and write",
     "a structured markdown profile. Each profile cycle runs across a small",
     "sequence of GitHub issues \u2014 one per phase \u2014 and produces a single",
-    "profile file on disk, a set of feature-matrix rows, and optional",
-    "follow-up research issues for adjacent products.",
+    "profile file on disk, a set of feature-matrix rows, a back-mapping",
+    "onto the BCM capability model, and optional follow-up research",
+    "issues for adjacent products.",
     "",
     "This agent is **domain-neutral**. It makes no assumptions about what",
     "the consuming project sells, which industry it serves, or which",
@@ -14280,6 +14513,14 @@ var softwareProfileAnalystSubAgent = {
     "   weights belong in `docs/src/content/docs/project-context.md` (or an override",
     "   passed in the issue body). This agent reads them; it never",
     "   invents them.",
+    "8. **Map back to the capability model.** The BCM capability model is",
+    "   the single source of truth for what the business does. Every",
+    "   feature on every profile is mapped to the owning capability in the",
+    "   BCM tree during the map phase. Features that match nothing in the",
+    "   tree are candidates for new BCM sub-capabilities \u2014 they are",
+    "   flagged and handed off to the `bcm-writer` bundle via",
+    "   `bcm:outline` issues. This agent never authors BCM documents",
+    "   itself.",
     "",
     "---",
     "",
@@ -14345,14 +14586,15 @@ var softwareProfileAnalystSubAgent = {
     "## State Machine Overview",
     "",
     "```",
-    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510   \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510   \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510   \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
-    "\u2502 1. RESEARCH  \u2502\u2500\u2500\u25B6\u2502 2. PROFILE   \u2502\u2500\u2500\u25B6\u2502 3. MATRIX    \u2502\u2500\u2500\u25B6\u2502 4. FOLLOWUP  \u2502",
-    "\u2502 Collect      \u2502   \u2502 Write the    \u2502   \u2502 Extract      \u2502   \u2502 Enqueue      \u2502",
-    "\u2502 public       \u2502   \u2502 structured   \u2502   \u2502 feature rows \u2502   \u2502 research for \u2502",
-    "\u2502 sources into \u2502   \u2502 markdown     \u2502   \u2502 and score    \u2502   \u2502 adjacent     \u2502",
-    "\u2502 bounded      \u2502   \u2502 profile to   \u2502   \u2502 against the  \u2502   \u2502 products     \u2502",
-    "\u2502 notes file   \u2502   \u2502 <PROFILES>/  \u2502   \u2502 weights      \u2502   \u2502 surfaced     \u2502",
-    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518   \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518   \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518   \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510  \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u25021.RESEARCH\u2502\u2500\u25B6\u25022.PROFILE \u2502\u2500\u25B6\u25023.MATRIX  \u2502\u2500\u25B6\u25024.MAP     \u2502\u2500\u25B6\u25025.FOLLOWUP\u2502",
+    "\u2502Collect   \u2502  \u2502Write the \u2502  \u2502Extract   \u2502  \u2502Map each  \u2502  \u2502Enqueue   \u2502",
+    "\u2502public    \u2502  \u2502structured\u2502  \u2502feature   \u2502  \u2502feature to\u2502  \u2502research  \u2502",
+    "\u2502sources   \u2502  \u2502markdown  \u2502  \u2502rows and  \u2502  \u2502BCM       \u2502  \u2502for       \u2502",
+    "\u2502into      \u2502  \u2502profile to\u2502  \u2502score     \u2502  \u2502capability\u2502  \u2502adjacent  \u2502",
+    "\u2502bounded   \u2502  \u2502<PROFILES>\u2502  \u2502against   \u2502  \u2502and flag  \u2502  \u2502products  \u2502",
+    "\u2502notes file\u2502  \u2502          \u2502  \u2502weights   \u2502  \u2502gaps      \u2502  \u2502surfaced  \u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518  \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
     "```",
     "",
     "**Issue labels encode the phase:**",
@@ -14361,20 +14603,22 @@ var softwareProfileAnalystSubAgent = {
     "|-------|-------|-------------|",
     "| `software:research` | 1. Research | Gather public sources. Write a bounded research-notes file. Create the profile issue. |",
     "| `software:profile` | 2. Profile | Read the research notes. Write the structured profile to `<PROFILES_DIR>`. Create the matrix issue. |",
-    "| `software:matrix` | 3. Matrix | Read the profile. Extract feature rows into `<MATRIX_FILE>`. Score against segment weights. Create the follow-up issue if warranted. |",
-    "| `software:followup` | 4. Followup | Read the profile. Enqueue software-research issues for adjacent products surfaced in the profile. |",
+    "| `software:matrix` | 3. Matrix | Read the profile. Extract feature rows into `<MATRIX_FILE>`. Score against segment weights. Create the map issue. |",
+    "| `software:map` | 4. Map | Read the profile and matrix rows. Map each feature to the owning BCM capability. Write the mapping back onto the profile. Enqueue `bcm:outline` follow-ups for unmapped features above the configured threshold. Create the followup issue. |",
+    "| `software:followup` | 5. Followup | Read the profile. Enqueue software-research issues for adjacent products surfaced in the profile. |",
     "",
     "All issues also carry `type:software-profile` and a `status:*` label.",
     "",
     "**Issue count per product cycle:** 1 research + 1 profile + 1 matrix +",
-    "0\u20131 followup = **3\u20134 sessions**. The followup phase is skipped when",
-    "the profile did not surface any adjacent product worth researching.",
+    "1 map + 0\u20131 followup = **4\u20135 sessions**. The followup phase is",
+    "skipped when the profile did not surface any adjacent product worth",
+    "researching.",
     "",
     "**Shortened paths:**",
     "- Research phase determines the product is out of scope (not",
     "  relevant, insufficient public material) \u2192 research issue closes",
     "  with a justification and no downstream issues are created \u2192 **1 session**.",
-    "- Narrow product with no adjacent candidates \u2192 **3 sessions**.",
+    "- Narrow product with no adjacent candidates \u2192 **4 sessions**.",
     "",
     "---",
     "",
@@ -14393,11 +14637,25 @@ var softwareProfileAnalystSubAgent = {
     "| `<PRODUCT_SLUG>` | Short kebab-case slug identifying the product | derived from the product name |",
     "| `<COMPANY_PROFILES_DIR>` | Where existing company profiles live (for duplicate detection during followup) | `docs/companies/profiles/` |",
     "| `<PEOPLE_PROFILES_DIR>` | Where existing people profiles live (for duplicate detection during followup) | `docs/people/profiles/` |",
+    `| \`<BCM_DOC_ROOT>\` | Root folder for BCM capability-model documents (used by Phase 4 to locate capabilities) | \`${DEFAULT_AGENT_PATHS.bcmRoot}/\` |`,
+    "| `<BCM_CAPABILITY_MAP>` | Capability-map file that lists the L1/L2/L3 hierarchy | `<BCM_DOC_ROOT>/capability-map.md` |",
+    "| `<UNMAPPED_THRESHOLD>` | Minimum number of unmapped features on a single profile that triggers a `bcm:outline` follow-up for that feature cluster | `1` (every unmapped feature triggers a `bcm:outline`) |",
     "",
     "If `docs/src/content/docs/project-context.md` specifies a different software-research",
     "tree (for example by reusing the research-pipeline deliverables",
     "folder), prefer that. Otherwise fall back to the defaults above.",
     "",
+    "The `<BCM_DOC_ROOT>` default above is sourced from configulator's",
+    "`DEFAULT_AGENT_PATHS.bcmRoot`. If the consuming project's capability",
+    "model lives somewhere else, pass an override in the invoking issue",
+    "body or extend this rule in `agentConfig.rules` \u2014 reading",
+    "`agentConfig.paths.bcmRoot` directly is not currently wired through",
+    "to rule content at synth time. Override `<UNMAPPED_THRESHOLD>` the",
+    "same way when the default (one `bcm:outline` per unmapped feature)",
+    "is too noisy \u2014 for example, raise it to `3` to require at least",
+    "three unmapped features on a single profile before any follow-ups",
+    "are filed.",
+    "",
     "---",
     "",
     "## Agent Loop",
@@ -14406,7 +14664,7 @@ var softwareProfileAnalystSubAgent = {
     "",
     "1. Claim one open `type:software-profile` issue using phase priority:",
     "   `software:research` > `software:profile` > `software:matrix` >",
-    "   `software:followup`.",
+    "   `software:map` > `software:followup`.",
     "2. Transition `status:ready` \u2192 `status:in-progress` and create the",
     "   branch per your project's branch-naming convention.",
     "3. Execute the phase handler that matches the issue's `software:*`",
@@ -14541,7 +14799,12 @@ var softwareProfileAnalystSubAgent = {
     "",
     "   ## Features",
     "   <grouped bullet list of notable features, each cited. These become",
-    "   the rows in the feature matrix during Phase 3.>",
+    "   the rows in the feature matrix during Phase 3 and the rows of the",
+    "   capability mapping during Phase 4.>",
+    "",
+    "   ## Capability Mapping",
+    "   _To be filled in during Phase 4 (Map). Leave as",
+    "   `_Pending capability mapping \u2014 filled in Phase 4._` until then._",
     "",
     "   ## Technology Signals",
     "   <stack hints from docs, integrations, and public engineering",
@@ -14647,18 +14910,141 @@ var softwareProfileAnalystSubAgent = {
     "",
     "5. **Update the matrix front-matter** (`updated: YYYY-MM-DD`).",
     "",
-    "6. **Decide whether a follow-up issue is warranted.** Create a",
-    "   `software:followup` issue (depending on this matrix issue) only",
-    "   if the profile lists at least one adjacent product candidate.",
-    "   Otherwise, note in the matrix issue's closing comment that no",
-    "   follow-up is needed.",
+    "6. **Create the `software:map` issue** with",
+    "   `Depends on: #<matrix-issue>`. Its body references the profile",
+    "   path, the matrix file path, the BCM document root",
+    "   (`<BCM_DOC_ROOT>`), the capability map file",
+    "   (`<BCM_CAPABILITY_MAP>` if it exists), and the unmapped-feature",
+    "   threshold (`<UNMAPPED_THRESHOLD>`). The map phase always runs \u2014",
+    "   every profile is mapped back to the capability model regardless",
+    "   of whether any adjacent products were surfaced.",
     "",
     "7. **Commit and push** the matrix file (and any profile updates).",
     "   Close the matrix issue.",
     "",
     "---",
     "",
-    "## Phase 4: Followup (`software:followup`)",
+    "## Phase 4: Map (`software:map`)",
+    "",
+    "**Goal:** Map each feature on the profile back to the owning",
+    "capability in the BCM capability model, write the mapping onto the",
+    "profile, and enqueue `bcm:outline` follow-ups for features that do",
+    "not match any existing capability.",
+    "",
+    "**Budget:** No new web searches. Read the profile, matrix, and BCM",
+    "tree; write the mapping section onto the profile; open",
+    "`bcm:outline` issues for the gaps.",
+    "",
+    "### Capability Mapping Format",
+    "",
+    "The mapping lives in the `## Capability Mapping` section of the",
+    "profile file. It is a table with one row per feature and explicit",
+    "evidence for each mapping decision:",
+    "",
+    "```markdown",
+    "## Capability Mapping",
+    "",
+    "_Mapped against `<BCM_CAPABILITY_MAP>` on YYYY-MM-DD._",
+    "",
+    "| feature | capability (id \xB7 name) | tier | confidence | notes |",
+    "|---------|-----------------------|------|------------|-------|",
+    "| <feature> | <bcm-id> \xB7 <capability name> | L1/L2/L3 | high/medium/low | <evidence or rationale> |",
+    "| <feature> | _unmapped_ | \u2014 | \u2014 | Candidate for new BCM sub-capability. Tracked in #<bcm-outline-issue> |",
+    "```",
+    "",
+    "Confidence levels:",
+    "",
+    "- **high** \u2014 the feature's jobs-to-be-done clearly match the",
+    "  capability's definition and business object.",
+    "- **medium** \u2014 the feature plausibly maps to the capability, but the",
+    "  match is partial (e.g. the feature covers only one facet of the",
+    "  capability, or the capability's definition is broader than the",
+    "  feature).",
+    "- **low** \u2014 the feature overlaps the capability only tangentially.",
+    "  Prefer `_unmapped_` over a low-confidence match when the feature",
+    "  is a genuine capability gap rather than a near-miss.",
+    "",
+    "### Steps",
+    "",
+    "1. **Load the BCM tree.** Read `<BCM_CAPABILITY_MAP>` if it exists,",
+    "   otherwise walk `<BCM_DOC_ROOT>/` for capability-model documents.",
+    "   Build an in-session index of `{ id, name, tier, business_object }`",
+    "   entries. If the tree is empty (no BCM documents yet), note the",
+    "   gap in the profile's `## Risks / Open Questions`, skip the",
+    "   per-feature mapping, and mark **every** feature as a candidate",
+    "   for a new sub-capability \u2014 subject to `<UNMAPPED_THRESHOLD>`.",
+    "",
+    "2. **Read the profile file** and extract the `## Features` bullets.",
+    "   Each bullet is one row in the mapping table.",
+    "",
+    "3. **Map each feature to the best-fit capability.** Preferred",
+    "   algorithm:",
+    "   - Match against the capability's **business object** first (the",
+    "     thing the capability acts on).",
+    "   - Then match against the capability's **definition** and",
+    "     jobs-to-be-done.",
+    "   - Tie-break in favor of the most specific (deepest tier)",
+    "     capability \u2014 an L3 match beats an L2 match that covers it.",
+    "",
+    "4. **Record low-confidence mappings explicitly** \u2014 never hide a weak",
+    "   match behind a high-confidence label. If the best available",
+    "   match is low-confidence, mark the feature `_unmapped_` instead",
+    "   and describe the near-miss in the `notes` column.",
+    "",
+    "5. **Count unmapped features.** If the count meets or exceeds",
+    "   `<UNMAPPED_THRESHOLD>` (default `1`), open one `bcm:outline`",
+    "   issue per unmapped feature. The issue must carry:",
+    "",
+    "   - `type:bcm-document`",
+    "   - `bcm:outline`",
+    "   - `priority:medium`",
+    "   - `status:ready`",
+    "",
+    "   The issue body must include:",
+    "   - A **discovery source** line naming this software profile",
+    "     (`Discovered while mapping: <product name>`)",
+    "   - A link to the software profile path",
+    "     (`Software profile: <PROFILES_DIR>/<PRODUCT_SLUG>.md`)",
+    "   - The feature name, its one-line description from the profile,",
+    "     and a candidate capability name framed as a noun (BIZBOK-aligned)",
+    "   - Enough identifying metadata that the `bcm-writer` agent can",
+    "     begin the outline phase without revisiting this software",
+    "     profile",
+    "",
+    "6. **Avoid duplicate `bcm:outline` issues.** Before opening one,",
+    "   scan `<BCM_DOC_ROOT>/` for an existing capability that covers",
+    "   the feature (in case the tree grew between the matrix and map",
+    "   phases) and scan open issues carrying `bcm:outline` so this",
+    "   phase never re-queues a capability that is already being",
+    "   outlined. If a match is found, reuse it as a cross-reference in",
+    "   the mapping table instead of opening a new issue.",
+    "",
+    "7. **Write the `## Capability Mapping` section** back onto the",
+    "   profile file, replacing the `_Pending capability mapping \u2014 filled",
+    "   in Phase 4._` placeholder. Preserve every other section of the",
+    "   profile verbatim \u2014 this phase only rewrites the mapping section.",
+    "",
+    "8. **Create the `software:followup` issue** with",
+    "   `Depends on: #<map-issue>`. Its body references the profile path",
+    "   and lists any adjacent products the profile's Follow-up",
+    "   Candidates section identified. Skip creating the followup issue",
+    "   only when the profile lists zero adjacent products, zero",
+    "   primary-attribution people, and the vendor already has a",
+    "   company profile \u2014 note the skip in the map issue's closing",
+    "   comment.",
+    "",
+    "9. **Assume the peer is present.** This phase assumes the",
+    "   `bcm-writer` bundle is enabled in the consuming project. If the",
+    "   bundle has been disabled, flag the map issue with",
+    "   `status:needs-attention` and list the unmapped features that",
+    "   could not be routed \u2014 never invent an alternative label",
+    "   taxonomy.",
+    "",
+    "10. **Commit and push** the updated profile. Close the map issue.",
+    "",
+    "---",
+    "",
+    "## Phase 5: Followup (`software:followup`)",
     "",
     "**Goal:** Create downstream research issues for the adjacent products,",
     "vendor company, and primary-attribution people surfaced in the",
@@ -14778,10 +15164,15 @@ var softwareProfileAnalystSubAgent = {
     "",
     "- `<NOTES_DIR>/` \u2014 research-notes files (Phase 1)",
     "- `<PROFILES_DIR>/` \u2014 software profiles (Phase 2, updated in later",
-    "  phases)",
+    "  phases including the `## Capability Mapping` section in Phase 4)",
     "- `<MATRIX_FILE>` \u2014 shared feature matrix (Phase 3)",
     "",
-    "In Phase 4, this agent also **creates `company:research` and",
+    "In Phase 4, this agent **creates `bcm:outline` issues** for every",
+    "unmapped feature that meets the `<UNMAPPED_THRESHOLD>` so the",
+    "`bcm-writer` bundle can author the new sub-capability. It never",
+    "authors BCM capability-model documents itself.",
+    "",
+    "In Phase 5, this agent also **creates `company:research` and",
     "`people:research` issues** for the vendor company and primary-",
     "attribution people surfaced in the profile that are not already",
     "tracked under `<COMPANY_PROFILES_DIR>/` or `<PEOPLE_PROFILES_DIR>/`.",
@@ -14790,15 +15181,18 @@ var softwareProfileAnalystSubAgent = {
     "`people-profile-analyst` agents, which pick up the issues this",
     "pipeline creates.",
     "",
-    "The pipeline produces **software profiles, notes, and matrix rows",
-    "only**. Deeper research on adjacent products is delegated to new",
-    "cycles of this same pipeline via `software:research` issues. Deeper",
-    "research on the vendor company and primary-attribution people is",
-    "delegated to the `company-profile` and `people-profile` bundles via",
+    "The pipeline produces **software profiles, notes, matrix rows, and capability mappings**.",
+    "Deeper research on adjacent products is delegated to new cycles of",
+    "this same pipeline via `software:research` issues. New BCM",
+    "sub-capabilities for unmapped features are delegated to the",
+    "`bcm-writer` bundle via `bcm:outline` issues. Deeper research on",
+    "the vendor company and primary-attribution people is delegated to",
+    "the `company-profile` and `people-profile` bundles via",
     "`company:research` and `people:research` issues. This agent never",
-    "writes company profiles, person profiles, formal requirement",
-    "documents, or comparative long-form analyses itself. Keep this",
-    "boundary clean so the software-profile pipeline stays generic.",
+    "writes BCM documents, company profiles, person profiles, formal",
+    "requirement documents, or comparative long-form analyses itself.",
+    "Keep this boundary clean so the software-profile pipeline stays",
+    "generic.",
     "",
     "---",
     "",
@@ -14813,31 +15207,41 @@ var softwareProfileAnalystSubAgent = {
     "  `docs/src/content/docs/project-context.md` or an explicit issue-body override. If",
     "  neither is available, fall back to the single-segment default and",
     "  flag the gap \u2014 never guess.",
-    "- **Delegate, don't duplicate.** The vendor company and primary-",
-    "  attribution people surfaced during profiling are handed off to the",
-    "  `company-profile` and `people-profile` bundles via",
-    "  `company:research` and `people:research` issues in Phase 4 \u2014 never",
-    "  inlined as company or person profiles in this pipeline.",
-    "- **Check before enqueueing.** Before opening a `company:research`",
-    "  or `people:research` issue, verify no existing profile or open",
-    "  research issue already covers the candidate. Reuse existing",
-    "  profiles as cross-references rather than re-queuing research.",
+    "- **Delegate, don't duplicate.** Unmapped capabilities are handed off",
+    "  to the `bcm-writer` bundle via `bcm:outline` issues in Phase 4.",
+    "  The vendor company and primary-attribution people surfaced during",
+    "  profiling are handed off to the `company-profile` and",
+    "  `people-profile` bundles via `company:research` and",
+    "  `people:research` issues in Phase 5 \u2014 never inlined as BCM",
+    "  documents, company profiles, or person profiles in this pipeline.",
+    "- **Check before enqueueing.** Before opening a `bcm:outline`,",
+    "  `company:research`, or `people:research` issue, verify no existing",
+    "  document or open issue already covers the candidate. Reuse",
+    "  existing BCM documents and profiles as cross-references rather",
+    "  than re-queuing work.",
+    "- **Respect the threshold.** Phase 4 opens `bcm:outline` issues only",
+    "  when the count of unmapped features on a single profile meets or",
+    "  exceeds `<UNMAPPED_THRESHOLD>`. The default is `1` \u2014 one unmapped",
+    "  feature triggers one outline issue. Raise the threshold in the",
+    "  invoking issue body or in the consuming project's",
+    "  `agentConfig.rules` when the default is too noisy.",
     "- **Restrain the queue \u2014 people only.** The vendor company always",
     "  qualifies (duplicate check aside). For people, only enqueue",
     "  research for those with **primary attribution** \u2014 founders, the",
     "  current CEO, principal creators, lead maintainers, or the head of",
     "  product. Do not open issues for every name on the vendor's about",
     "  page, every investor, or every advisor.",
-    "- **Produce profiles and matrix rows, not requirement or evaluation",
-    "  documents.** Do not open `type:requirement` or formal evaluation",
-    "  issues from this pipeline. Follow-up research is scoped through",
-    "  `software:research`, `company:research`, and `people:research`",
-    "  only."
+    "- **Produce profiles, matrix rows, and capability mappings \u2014 not",
+    "  BCM documents, requirement documents, or evaluation documents.**",
+    "  Do not open `type:requirement` or formal evaluation issues from",
+    "  this pipeline, and never author BCM capability-model documents",
+    "  inline. Follow-up work is scoped through `software:research`,",
+    "  `bcm:outline`, `company:research`, and `people:research` only."
   ].join("\n")
 };
 var profileSoftwareSkill = {
   name: "profile-software",
-  description: "Kick off a software-profile pipeline. Creates a software:research issue for the given product and dispatches Phase 1 (Research) in the software-profile-analyst agent. Phase 4 (Followup) enqueues downstream `company:research` and `people:research` issues for the vendor company and primary-attribution founders/leaders surfaced in the profile.",
+  description: "Kick off a software-profile pipeline. Creates a software:research issue for the given product and dispatches Phase 1 (Research) in the software-profile-analyst agent. Phase 4 (Map) writes a BCM capability mapping onto the profile and enqueues `bcm:outline` issues for unmapped features. Phase 5 (Followup) enqueues downstream `company:research` and `people:research` issues for the vendor company and primary-attribution founders/leaders surfaced in the profile.",
   disableModelInvocation: true,
   userInvocable: true,
   context: "fork",
@@ -14864,6 +15268,9 @@ var profileSoftwareSkill = {
     "- `weights: <table>` \u2014 override the segment-importance weights for",
     "  this profile cycle (otherwise loaded from",
     "  `docs/src/content/docs/project-context.md`)",
+    "- `unmapped_threshold: <n>` \u2014 override the Phase 4 threshold for",
+    "  opening `bcm:outline` issues (default `1` \u2014 one unmapped feature",
+    "  triggers one outline issue)",
     "- `sources: <list>` \u2014 additional authorized sources beyond public web",
     "",
     "## Default Paths",
@@ -14883,16 +15290,20 @@ var profileSoftwareSkill = {
     "2. Execute Phase 1 (Research) of the software-profile-analyst",
     "   agent.",
     "3. Phase 1 creates the `software:profile` issue. Phase 2 creates",
-    "   the `software:matrix` issue. Phase 3 may create a",
-    "   `software:followup` issue. Each downstream issue declares its",
-    "   `Depends on:` predecessor.",
+    "   the `software:matrix` issue. Phase 3 creates the `software:map`",
+    "   issue. Phase 4 creates the `software:followup` issue (unless the",
+    "   profile surfaced zero follow-ups). Each downstream issue",
+    "   declares its `Depends on:` predecessor.",
     "",
     "## Output",
     "",
     "- A research-notes file under the project's notes directory",
-    "- A single software profile under the profiles directory",
+    "- A single software profile under the profiles directory, including",
+    "  a `## Capability Mapping` section written in Phase 4",
     "- One or more rows appended to the shared feature-matrix file,",
     "  scored against the configured segment weights",
+    "- `bcm:outline` issues for each unmapped feature above the",
+    "  configured threshold (handed off to the `bcm-writer` bundle)",
     "- Optional follow-up `software:research` issues for adjacent",
     "  products surfaced in the profile",
     "- `company:research` issue for the vendor company (handed off to",
@@ -14900,46 +15311,132 @@ var profileSoftwareSkill = {
     "- `people:research` issues for primary-attribution founders, CEOs,",
     "  or principal creators (handed off to the `people-profile`",
     "  bundle)",
-    "- This pipeline produces **software profiles, notes, and matrix",
-    "  rows only** \u2014 it does not write company profiles, person",
-    "  profiles, or formal requirement documents itself."
+    "- This pipeline produces **software profiles, notes, matrix rows,",
+    "  and capability mappings** \u2014 it does not write BCM documents,",
+    "  company profiles, person profiles, or formal requirement",
+    "  documents itself."
+  ].join("\n")
+};
+var mapSoftwareSkill = {
+  name: "map-software",
+  description: "Kick off a standalone software-capability mapping session. Creates a software:map issue for an already-profiled product and dispatches Phase 4 (Map) in the software-profile-analyst agent. Produces the `## Capability Mapping` section on the profile and enqueues `bcm:outline` issues for unmapped features above the configured threshold.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "software-profile-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Map Software",
+    "",
+    "Kick off a standalone `software:map` session for a product that",
+    "already has a profile file and matrix rows on disk. Creates a",
+    "`software:map` issue carrying the profile path and dispatches Phase",
+    "4 (Map) in the software-profile-analyst agent.",
+    "",
+    "Use this skill when:",
+    "",
+    "- A profile was written before the map phase existed and is still",
+    "  carrying the `_Pending capability mapping \u2014 filled in Phase 4._`",
+    "  placeholder.",
+    "- The BCM tree has grown enough that a previously-mapped profile",
+    "  should be re-mapped against the updated capability model.",
+    "- A profile's features were edited after the map phase ran and the",
+    "  mapping table is now out of date.",
+    "",
+    "## Usage",
+    "",
+    "/map-software <product-slug-or-profile-path>",
+    "",
+    "Optional extensions in the issue body:",
+    "- `unmapped_threshold: <n>` \u2014 override the threshold for opening",
+    "  `bcm:outline` issues (default `1`)",
+    "- `bcm_doc_root: <path>` \u2014 override the BCM document root",
+    "  (otherwise the configulator default at",
+    "  `DEFAULT_AGENT_PATHS.bcmRoot`)",
+    "- `capability_map: <path>` \u2014 override the capability-map file",
+    "  (otherwise `<BCM_DOC_ROOT>/capability-map.md`)",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/src/content/docs/project-context.md` or",
+    "`agentConfig.rules`, the mapping reads from:",
+    "",
+    `- \`${DEFAULT_AGENT_PATHS.bcmRoot}/\` \u2014 BCM capability-model documents`,
+    `- \`${DEFAULT_AGENT_PATHS.bcmRoot}/capability-map.md\` \u2014 capability map`,
+    "",
+    "and writes back to `docs/software/profiles/<slug>.md` under the",
+    "`## Capability Mapping` section only. No other section of the",
+    "profile is rewritten.",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `software:map` issue with `type:software-profile`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   profile path and any overrides.",
+    "2. Execute Phase 4 (Map) of the software-profile-analyst agent.",
+    "3. Phase 4 writes the `## Capability Mapping` section, enqueues",
+    "   `bcm:outline` issues for unmapped features above the threshold,",
+    "   and \u2014 when the profile lists adjacent products or",
+    "   primary-attribution people \u2014 creates the `software:followup`",
+    "   issue.",
+    "",
+    "## Output",
+    "",
+    "- An updated `## Capability Mapping` section on the target profile",
+    "- `bcm:outline` issues for each unmapped feature above the",
+    "  configured threshold (handed off to the `bcm-writer` bundle)",
+    "- An optional `software:followup` issue when the profile surfaced",
+    "  adjacent products, a vendor company without an existing profile,",
+    "  or primary-attribution people",
+    "- This skill does not run Phase 1\u20133 \u2014 it assumes the profile and",
+    "  matrix rows already exist on disk."
   ].join("\n")
 };
 var softwareProfileBundle = {
   name: "software-profile",
-  description: "Software research, profiling, and feature-matrix pipeline: research, profile, matrix, followup. Enabled by default; domain-neutral; filesystem-durable between phases; ranks features against configurable segment-importance weights. Phase 4 (Followup) hands the vendor company and primary-attribution founders/leaders off to the `company-profile` and `people-profile` bundles via `company:research` and `people:research` issues.",
+  description: "Software research, profiling, feature-matrix, and capability-mapping pipeline: research, profile, matrix, map, followup. Enabled by default; domain-neutral; filesystem-durable between phases; ranks features against configurable segment-importance weights and maps features back to the BCM capability model. Phase 4 (Map) hands unmapped features off to the `bcm-writer` bundle via `bcm:outline` issues. Phase 5 (Followup) hands the vendor company and primary-attribution founders/leaders off to the `company-profile` and `people-profile` bundles via `company:research` and `people:research` issues.",
   appliesWhen: () => true,
   rules: [
     {
       name: "software-profile-workflow",
-      description: "Describes the 4-phase software-profile pipeline, the software:* label taxonomy, the generic software-type taxonomy, and the segment-weights convention that drives feature-matrix scoring.",
+      description: "Describes the 5-phase software-profile pipeline, the software:* label taxonomy, the generic software-type taxonomy, the segment-weights convention that drives feature-matrix scoring, and the capability-mapping hand-off to the bcm-writer bundle.",
       scope: AGENT_RULE_SCOPE.ALWAYS,
       content: [
         "# Software Profile Workflow",
         "",
         "Use `/profile-software <product-name>` to kick off a software",
-        "research, profiling, and feature-matrix pipeline. The pipeline",
-        "runs in up to 4 phases \u2014 research, profile, matrix, followup \u2014",
-        "each tracked by its own GitHub issue labeled",
-        "`software:research`, `software:profile`, `software:matrix`, or",
-        "`software:followup`. All issues carry `type:software-profile`.",
-        "",
-        "The pipeline produces **software profiles, research notes, and",
-        "rows in a shared feature matrix**. Features are ranked against",
-        "segment-importance weights declared in",
-        "`docs/src/content/docs/project-context.md` under a `## Segment Weights` section.",
-        "Deeper research on adjacent products surfaced in a profile is",
-        "delegated to new cycles of this same pipeline via",
-        "`software:followup` issues. Deeper research on the vendor",
-        "company and primary-attribution founders/product leaders is",
-        "delegated to the `company-profile` and `people-profile`",
-        "bundles via `company:research` and `people:research` issues",
-        "opened during Phase 4 (Followup).",
+        "research, profiling, feature-matrix, and capability-mapping",
+        "pipeline. The pipeline runs in up to 5 phases \u2014 research,",
+        "profile, matrix, map, followup \u2014 each tracked by its own GitHub",
+        "issue labeled `software:research`, `software:profile`,",
+        "`software:matrix`, `software:map`, or `software:followup`. All",
+        "issues carry `type:software-profile`.",
+        "",
+        "The pipeline produces **software profiles, research notes, rows",
+        "in a shared feature matrix, and capability mappings onto the",
+        "BCM tree**. Features are ranked against segment-importance",
+        "weights declared in `docs/src/content/docs/project-context.md`",
+        "under a `## Segment Weights` section. Features that do not map",
+        "to any existing capability in the BCM tree are flagged during",
+        "the map phase as candidates for new BCM sub-capabilities and",
+        "handed off to the `bcm-writer` bundle via `bcm:outline` issues",
+        "(subject to a configurable threshold). Deeper research on",
+        "adjacent products surfaced in a profile is delegated to new",
+        "cycles of this same pipeline via `software:followup` issues.",
+        "Deeper research on the vendor company and primary-attribution",
+        "founders/product leaders is delegated to the `company-profile`",
+        "and `people-profile` bundles via `company:research` and",
+        "`people:research` issues opened during Phase 5 (Followup).",
+        "",
+        "Use `/map-software <product-slug>` to kick off a standalone",
+        "`software:map` session for a profile that already exists on",
+        "disk \u2014 for example, when the BCM tree has grown enough that a",
+        "previously-mapped profile should be re-mapped.",
         "",
         "See the `software-profile-analyst` agent definition for full",
         "workflow details, default paths, the software-type taxonomy,",
-        "the segment-weights convention, and phase-by-phase",
-        "instructions."
+        "the segment-weights convention, the capability-mapping format,",
+        "and phase-by-phase instructions."
       ].join("\n"),
       platforms: {
         cursor: { exclude: true }
@@ -14947,13 +15444,13 @@ var softwareProfileBundle = {
       tags: ["workflow"]
     }
   ],
-  skills: [profileSoftwareSkill],
+  skills: [profileSoftwareSkill, mapSoftwareSkill],
   subAgents: [softwareProfileAnalystSubAgent],
   labels: [
     {
       name: "type:software-profile",
       color: "0E8A16",
-      description: "Work that produces or maintains a software profile, research notes, or feature-matrix rows"
+      description: "Work that produces or maintains a software profile, research notes, feature-matrix rows, or capability mappings"
     },
     {
       name: "software:research",
@@ -14970,10 +15467,15 @@ var softwareProfileBundle = {
       color: "D4C5F9",
       description: "Phase 3: extract feature rows into the shared feature matrix and score them against segment weights"
     },
+    {
+      name: "software:map",
+      color: "A2EEEF",
+      description: "Phase 4: map each feature back to the BCM capability model, write the mapping onto the profile, and enqueue `bcm:outline` issues for unmapped features above the configured threshold"
+    },
     {
       name: "software:followup",
       color: "FBCA04",
-      description: "Phase 4: enqueue follow-up research issues for adjacent products, the vendor company, and primary-attribution people surfaced in the profile"
+      description: "Phase 5: enqueue follow-up research issues for adjacent products, the vendor company, and primary-attribution people surfaced in the profile"
     }
   ]
 };