@codedrifters/configulator 0.0.393 → 0.0.395

package/lib/index.d.mts

@@ -5168,6 +5168,23 @@ declare const DEFAULT_SOURCES_THRESHOLDS: ScopeGateThresholds;
  *   leadership, history, sources, …) is the content spec for that
  *   single document, not a decomposable plan. Cap: `mediumMax: 12`
  *   on the AC axis; sources unchanged.
+ * - `business-models:canvas` / `business-models:complete` — the
+ *   business-models pipeline authors one cohesive Business Model
+ *   Canvas document per segment across two content-spec phases that
+ *   edit the SAME `business-model.md` file. The canvas phase writes
+ *   the nine Osterwalder blocks + segment index + downstream handoff;
+ *   the complete phase appends BIZBOK value streams, size / geographic
+ *   / regulatory variations, and the value-stream-to-capability
+ *   linking table. Both AC lists are the per-section content checklist
+ *   for that single indivisible document, not a phase-completion
+ *   checklist that can be decomposed — a single canvas cannot be split
+ *   into sequential sub-issues without every phase editing the same
+ *   file. A representative canvas issue observed at ac=7
+ *   (`codedrifters/openhi-planning`#13613). Cap: `mediumMax: 12` on the
+ *   AC axis for both (matching the `bcm:*` / `company:research`
+ *   document-authoring norm; the complete phase is a multi-section
+ *   append, so it takes the same cap as its canvas sibling rather than
+ *   a tighter single-section cap); sources unchanged.
  * - `req:draft-trace` — the `requirements-analyst` draft-trace
  *   phase emits a single proposal-with-traceability document whose
  *   ACs enumerate per-section content invariants. Sibling of

package/lib/index.d.ts

@@ -5217,6 +5217,23 @@ declare const DEFAULT_SOURCES_THRESHOLDS: ScopeGateThresholds;
  *   leadership, history, sources, …) is the content spec for that
  *   single document, not a decomposable plan. Cap: `mediumMax: 12`
  *   on the AC axis; sources unchanged.
+ * - `business-models:canvas` / `business-models:complete` — the
+ *   business-models pipeline authors one cohesive Business Model
+ *   Canvas document per segment across two content-spec phases that
+ *   edit the SAME `business-model.md` file. The canvas phase writes
+ *   the nine Osterwalder blocks + segment index + downstream handoff;
+ *   the complete phase appends BIZBOK value streams, size / geographic
+ *   / regulatory variations, and the value-stream-to-capability
+ *   linking table. Both AC lists are the per-section content checklist
+ *   for that single indivisible document, not a phase-completion
+ *   checklist that can be decomposed — a single canvas cannot be split
+ *   into sequential sub-issues without every phase editing the same
+ *   file. A representative canvas issue observed at ac=7
+ *   (`codedrifters/openhi-planning`#13613). Cap: `mediumMax: 12` on the
+ *   AC axis for both (matching the `bcm:*` / `company:research`
+ *   document-authoring norm; the complete phase is a multi-section
+ *   append, so it takes the same cap as its canvas sibling rather than
+ *   a tighter single-section cap); sources unchanged.
  * - `req:draft-trace` — the `requirements-analyst` draft-trace
  *   phase emits a single proposal-with-traceability document whose
  *   ACs enumerate per-section content invariants. Sibling of

package/lib/index.js

@@ -4633,7 +4633,17 @@ function buildBaseBundle(paths = DEFAULT_AGENT_PATHS) {
           "  `status:ready`.",
           "- **Automated flag** \u2192 add `status:needs-attention` (do not remove existing",
           "  status). Never auto-reset a `status:needs-attention` issue back to ready;",
-          "  a human must decide.",
+          "  a human must decide. The flag is **additive**: apply it with `--add-label`",
+          "  alone \u2014 never pair it with a `--remove-label` that strips the base",
+          "  `status:*` label. A flag that swaps out the base status (e.g. scope-gate",
+          "  or worker-failure paths removing `status:ready` / `status:in-progress`)",
+          "  leaves the issue with no base status \u2014 invisible to every status-driven",
+          "  query and to the queue, and unrecoverable once the flag is cleared.",
+          "- **Automated-flag clear** \u2192 when `status:needs-attention` is cleared, if the",
+          "  issue carries no base `status:*` label (a legacy issue flagged before the",
+          "  additive-flag rule, whose base status was stripped at flag time), restore",
+          "  `status:ready` \u2014 or `status:blocked` if the body still declares an open",
+          "  `Depends on:` dependency \u2014 in the same edit so it re-enters the workflow.",
           "- **PR CI failure** \u2192 add `status:needs-attention` to the associated PR (and",
           "  its linked issue) when CI fails in a **permanent** state \u2014 i.e. the failure",
           "  persists after a rerun, or the failure is clearly not a flake (compile",
@@ -14255,6 +14265,12 @@ var DEFAULT_BUNDLE_OVERRIDES = {
   "company:draft": {
     acceptanceCriteria: { smallMax: 3, mediumMax: 12 }
   },
+  "business-models:canvas": {
+    acceptanceCriteria: { smallMax: 3, mediumMax: 12 }
+  },
+  "business-models:complete": {
+    acceptanceCriteria: { smallMax: 3, mediumMax: 12 }
+  },
   "req:draft-trace": {
     acceptanceCriteria: { smallMax: 3, mediumMax: 20 }
   },
@@ -14421,8 +14437,19 @@ function renderScopeGateSection(gate, excludeBundles = []) {
     "",
     "When the classifier returns `large`:",
     "",
-    "1. Apply the `status:needs-attention` label and remove",
-    "   `status:ready` from the issue.",
+    "1. **Add** the `status:needs-attention` label to the issue with",
+    "   `--add-label` alone. Leave the existing base `status:*` label",
+    "   (`status:ready`) in place \u2014 `status:needs-attention` is",
+    "   **additive**, so a flagged issue reads `status:ready` +",
+    "   `status:needs-attention`. Do **not** remove the base status:",
+    "   stripping it leaves the issue with no base `status:*` label,",
+    "   invisible to every status-driven query and to the queue itself,",
+    "   and a later flag-clear can never restore dispatchability. The",
+    "   `status:needs-attention` label already keeps the issue out of",
+    "   the dispatch queue, so the base label safely stays:",
+    "   ```bash",
+    '   gh issue edit <number> --add-label "status:needs-attention"',
+    "   ```",
     "2. Post the decomposition-proposal comment (see template below),",
     "   with `<AC_COUNT>` / `<SOURCES_COUNT>` substituted from the",
     "   classification and `<AC_LIMIT>` / `<SOURCES_LIMIT>` set to",
@@ -14443,7 +14470,12 @@ function renderScopeGateSection(gate, excludeBundles = []) {
       "4. **Auto-file is OFF.** Stop after posting the comment. A human",
       "   reviews the proposal, files the phased sub-issues manually,",
       "   and clears `status:needs-attention` when the decomposition",
-      "   is in place."
+      "   is in place. When clearing the flag, if the issue carries **no**",
+      "   base `status:*` label \u2014 a legacy issue flagged before the",
+      "   additive-flag fix, whose base status was stripped at flag time \u2014",
+      "   also add `status:ready` (or `status:blocked` when the body still",
+      "   declares an open `Depends on:` dependency) in the same edit so",
+      "   the issue re-enters the queue instead of going invisible."
     );
   }
   const overrideEntries = Object.entries(gate.bundleOverrides).filter(
@@ -16998,9 +17030,16 @@ var orchestratorSubAgent = {
     "",
     "If the scope is `large`, **do not dispatch**. Instead:",
     "",
-    "1. Apply `status:needs-attention` and remove `status:ready`:",
+    "1. **Add** `status:needs-attention` with `--add-label` alone \u2014",
+    "   leave the base `status:*` label (`status:ready`) in place.",
+    "   `status:needs-attention` is **additive**; pairing it with a",
+    '   `--remove-label "status:ready"` strips the base status and',
+    "   leaves the issue with no `status:*` label at all, invisible to",
+    "   the queue and unrecoverable when the flag is later cleared. The",
+    "   `status:needs-attention` label already keeps the issue out of",
+    "   dispatch, so the base label stays:",
     "   ```bash",
-    '   gh issue edit <number> --remove-label "status:ready" --add-label "status:needs-attention"',
+    '   gh issue edit <number> --add-label "status:needs-attention"',
     "   ```",
     "2. Post the decomposition-proposal comment (see the **Scope gate**",
     "   section in `CLAUDE.md` for the template). Substitute the",
@@ -17098,7 +17137,9 @@ var orchestratorSubAgent = {
     "5. **Priority order:** critical > high > medium > low > trivial, then **funnel tier asc** (lower tier wins ties), then FIFO by issue number.",
     "6. **Never dispatch a `large` issue.** Always run the scope check",
     "   on the top `PICK` line before reporting `NEXT_WORK_ITEM`. A",
-    "   `large` issue must be flagged with `status:needs-attention` and",
+    "   `large` issue must be flagged by **adding** `status:needs-attention`",
+    "   (additive \u2014 leave the base `status:*` label in place; never pair",
+    "   the flag with a `--remove-label` that strips the base status) and",
     "   handed a decomposition proposal \u2014 never claimed, never branched,",
     "   never delegated to the `issue-worker`.",
     "7. **Sweep dependents whenever you apply `status:done`.** Every",
@@ -17766,9 +17807,17 @@ var issueWorkerSubAgent = {
     "   downstream agents (notably the `pr-reviewer`) can identify",
     "   bot-authored PRs. Pass `--label 'origin:issue-worker'` on every",
     "   `gh pr create` call.",
-    "7. **On failure:** If you cannot complete the issue, update labels and leave a comment:",
+    "7. **On failure:** If you cannot complete the issue (including a",
+    "   wrong-agent / routing mismatch), flag it for human triage and",
+    "   leave a comment. **Add** `status:needs-attention` with",
+    "   `--add-label` alone \u2014 do **not** remove the base",
+    "   `status:in-progress` label. `status:needs-attention` is",
+    "   additive, so the flagged issue reads `status:in-progress` +",
+    "   `status:needs-attention` and keeps a base status a human can act",
+    "   on; stripping it leaves the issue with no base `status:*` label,",
+    "   invisible to every status-driven query:",
     "   ```bash",
-    '   gh issue edit <number> --remove-label "status:in-progress" --add-label "status:needs-attention"',
+    '   gh issue edit <number> --add-label "status:needs-attention"',
     '   gh issue comment <number> --body "Worker could not complete: <reason>"',
     "   ```",
     "8. **Never force-push in feedback mode.** If a `git pull --rebase`",