@biffo/cli 0.313.1 → 0.313.2

package/dist/index.js

@@ -4461,7 +4461,35 @@ function buildPrBody(from, to, plan, migrations, base = GLOBAL_DISPATCH_REF, loc
   lines.push(
     "Automated core upgrade generated by `biffo core upgrade` (ADR-0006).",
     "",
-    `Bumps the Biffo template core from **${from}** to **${to}** and updates \`biffo.core.json\`. Only template-owned paths (see \`core-manifest.json\`) were touched \u2014 product, plugin, and infra files were left untouched.`,
+    // SCOPED TO THE COMMIT THIS TOOL WRITES, NOT TO THE BRANCH (#1999).
+    //
+    // The old wording was "Only template-owned paths were touched — product,
+    // plugin, and infra files were left untouched", stated flatly about the PR.
+    // It is true when this runs and routinely FALSE by the time the PR merges,
+    // because an instance carrying a divergence declaration cannot go green
+    // without a second, user-owned commit on this same branch:
+    // `test_known_divergence_derivation_matches_the_current_core_pin` asserts
+    // the derivation constant equals `biffo.core.json`'s pin in BOTH
+    // directions, so bumping the pin without re-deriving is red on a required
+    // check, and re-deriving without the bump turns `dev` red instead. Neither
+    // half can land alone.
+    //
+    // Live cost of the old wording, tabsii-com/tabsii-platform#1420: a
+    // prosecutor compared the branch head to this claim, correctly found the
+    // claim false, and rejected the PR. The remediation split the re-derivation
+    // into a stacked PR and deadlocked — the upgrade could not go green without
+    // it, and it could not merge before the upgrade. Three builder dispatches, a
+    // model escalation and a blocker filed at the owner, with nothing wrong in
+    // the code at any point. The tool asserted something it cannot keep true and
+    // a guard believed it.
+    //
+    // This says only what the tool actually knows: what ITS OWN commit did.
+    // #1994 made that distinction real on the guard side too, scoping the
+    // ownership exemption to the mechanical commit — so the body and the guard
+    // now mean the same thing by "the upgrade".
+    `Bumps the Biffo template core from **${from}** to **${to}** and updates \`biffo.core.json\`.`,
+    "",
+    `The commit generated by \`biffo core upgrade\` touches only template-owned paths (see \`core-manifest.json\`) \u2014 no product, plugin or infra files. **Any later commit on this branch is an ordinary reviewable change and is not covered by that statement.** A divergence-pin re-derivation belongs here, for example: the pin-equality test requires it to land together with the core bump, and it edits a user-owned path by design.`,
     ...carriedPrsSection(carriedPrs),
     "",
     `## Changes (${plan.changes.length})`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@biffo/cli",
-  "version": "0.313.1",
+  "version": "0.313.2",
   "description": "Biffo project scaffolding CLI",
   "license": "MIT",
   "type": "module",