mandrel 2.23.0 → 2.24.0

package/.agents/scripts/lib/orchestration/single-story-close/runner.js

@@ -353,8 +353,8 @@ function closeResult({
     note: waitedForMerge
       ? 'Close-and-land: PR merge confirmed. Story flipped agent::closing → agent::done, the issue closed (confirmStoryMerged), and the post-land tail ran.'
       : autoMergeEnabled
-        ? 'PR open against baseBranch with auto-merge enabled. Story rests at agent::closing (issue stays OPEN). GitHub will squash-merge when required checks pass; run single-story-confirm-merge.js after the merge confirms to flip agent::done and close the issue (the Closes #<id> footer also auto-closes it).'
-        : 'PR open against baseBranch. Story rests at agent::closing (issue stays OPEN). Operator merges via GitHub UI; run single-story-confirm-merge.js after the merge confirms to flip agent::done (the Closes #<id> footer also auto-closes the issue).',
+        ? 'PR open against baseBranch with auto-merge enabled. Story rests at agent::closing (issue stays OPEN and assigned to the operator). GitHub will squash-merge when required checks pass; run single-story-confirm-merge.js after the merge confirms to flip agent::done, release the lease, and close the issue (the Closes #<id> footer also auto-closes it).'
+        : 'PR open against baseBranch. Story rests at agent::closing (issue stays OPEN and assigned to the operator). Operator merges via GitHub UI; run single-story-confirm-merge.js after the merge confirms to flip agent::done and release the lease (the Closes #<id> footer also auto-closes the issue).',
   };
 }
 
@@ -552,7 +552,18 @@ async function runClosePipeline({
     config,
     progress,
   });
-  const leaseReleased = await releaseLease(leaseArgs);
+  // Story #4860 — the clean-path lease release USED to sit here, immediately
+  // after the arm and the `agent::closing` flip. That dropped the operator's
+  // claim the moment the PR opened, so a ticket read unassigned for the whole
+  // time its PR was in flight — and forever on the operator-merge path, where
+  // nothing downstream ever re-claimed it. The release now belongs to the
+  // post-land tail, which runs only on a CONFIRMED merge and which both
+  // landing surfaces reach. Every non-merged ending below — the
+  // `merge.unlanded` block, an exhausted wait budget, `--no-wait-merge`,
+  // `--no-auto-merge` — deliberately RETAINS the claim: the PR is open and the
+  // work still has an owner. The only releases that survive here are
+  // `releaseLeaseOnBlock`'s two throwing exits above, which fire before the PR
+  // is ever armed (Story #4257's hand-off property).
 
   // Close-and-land (Story #4428; default since `delivery.routing.closeAndLand`
   // — Story #4539): poll the just-armed PR to merge confirmation, or block
@@ -625,7 +636,11 @@ async function runClosePipeline({
       autoMergeEnabled,
       autoMergeReason,
       worktreeReaped,
-      leaseReleased,
+      // Story #4860 — the release is a post-land tail step now, so the tail's
+      // own per-step boolean IS the answer. A wait that ended anything other
+      // than landed never ran the tail, and correctly reports `false`: the
+      // claim is still held, by design.
+      leaseReleased: waitOutcome.tail?.leaseRelease === true,
       localCleanupDeferred,
       directMerged,
       waitedForMerge: true,
@@ -663,7 +678,10 @@ async function runClosePipeline({
     autoMergeEnabled,
     autoMergeReason,
     worktreeReaped,
-    leaseReleased,
+    // Story #4860 — this is the no-wait ending: the PR is open and a human
+    // owns the merge, so the Story stays assigned until the confirm-merge
+    // surface lands it and runs the tail.
+    leaseReleased: false,
     localCleanupDeferred,
     directMerged,
   });

package/.agents/scripts/lib/workers/maintainability-worker.js

@@ -7,16 +7,20 @@
  * Message contract — see lib/cpu-pool.js:
  *   IN  : { item: string }      — absolute file path to score
  *         { exit: true }        — drain & terminate
- *   OUT : { ok: true, result: { filePath, score: number | null } }
+ *   OUT : { ok: true, result: { filePath, score, unscorable?, reason? } }
  *
  * `score` is `null` only when the file genuinely cannot be read (ENOENT
- * or other I/O error). Parse failures inside escomplex still resolve to
- * `0` to preserve byte-for-byte parity with the pre-pool serial path
- * (calculateForSource swallows parse errors and returns 0).
+ * or other I/O error).
+ *
+ * A file the kernel cannot analyse comes back as `unscorable: true` with the
+ * kernel's own `reason`, rather than as a bare `0`. The `0` is still carried in
+ * `score` for wire compatibility, but it is no longer the only signal — the
+ * point of the flag is that the caller can *report* the file instead of
+ * silently dropping it (see `maintainability-engine.js`'s `UNSCORABLE`).
  */
 
 import { parentPort } from 'node:worker_threads';
-import { calculateForFile } from '../maintainability-engine.js';
+import { scoreFile } from '../maintainability-engine.js';
 
 /**
  * Pure handler for a single inbound worker message. Exported so unit
@@ -24,7 +28,7 @@ import { calculateForFile } from '../maintainability-engine.js';
  * without spawning a real `Worker` thread.
  *
  * @param {unknown} msg
- * @param {{ score?: (filePath: string) => number | null }} [deps]
+ * @param {{ score?: (filePath: string) => { score: number, unscorable: boolean, reason: string|null } }} [deps]
  * @returns {{kind: 'exit'} | {kind: 'reply', message: object}}
  */
 export function handleMaintainabilityWorkerMessage(msg, deps = {}) {
@@ -40,12 +44,13 @@ export function handleMaintainabilityWorkerMessage(msg, deps = {}) {
     };
   }
   const filePath = msg.item;
-  const scoreFn = deps.score ?? calculateForFile;
+  const scoreFn = deps.score ?? scoreFile;
   try {
-    const score = scoreFn(filePath);
+    // `scoreFn` returns `{ score, unscorable, reason }` — spread so the flag
+    // and its reason reach the pool caller intact.
     return {
       kind: 'reply',
-      message: { ok: true, result: { filePath, score } },
+      message: { ok: true, result: { filePath, ...scoreFn(filePath) } },
     };
   } catch (err) {
     // I/O or other unexpected error — surface as a per-item null score

package/.agents/workflows/helpers/deliver-light.md

@@ -48,6 +48,11 @@ Because the predicted footprint is a *declaration* — a guess, and a gameable o
 multi-capability enumeration). Size is enforced where ground truth is available:
 the diff backstop in step 4. Do not talk yourself past that one.
 
+**The backstop counts by the same principle.** It reads magnitude — changed
+lines over implementation files — not artifacts, and exempts the test and doc
+companions the framework itself mandates. A ceiling that punishes a repo for
+obeying its own test-first rule is a ceiling that over-fires.
+
 Sensitivity is the exception and stays absolute: a footprint touching an auth,
 crypto, billing, or migration class routes `full` however small or mechanical —
 and unlike a ceiling, it is **not overridable** (§ Recording a proceed-light
@@ -136,10 +141,22 @@ answer).
    node .agents/scripts/deliver-light.js --backstop --story <storyId>
    ```
 
-   Exit `3` (`blocked: true`) means the landed diff exceeds the light ceilings
-   (file count or a sensitive-path class). STOP, flip `agent::blocked`, and
-   escalate to `/plan` — do not land. This is the pass that actually bounds
-   size, which is why the prediction gate above can afford to be coarse.
+   This is the pass that actually bounds size, which is why the prediction gate
+   above can afford to be coarse. It measures **magnitude on the change's
+   implementation half** — changed lines (additions + deletions) plus a file
+   sprawl tripwire — never raw artifact count. Tests, `docs/**`, `**/*.md`,
+   `baselines/**`, and lockfiles are exempt from the counts, because the
+   framework mandates those companions and obeying it must not inflate the
+   number that then rejects the change. They are **not** exempt from
+   sensitive-path matching, which runs over the full change set.
+
+   Exit `3` (`blocked: true`) means the diff exceeds a light ceiling or touches a
+   sensitive-path class. STOP, flip `agent::blocked`, and **recycle the receipt**
+   through the envelope's `nextCommand` (`/plan <storyId>`) — tickets mode
+   rewrites it into properly-planned Stories and closes it as superseded. Do not
+   land, and do not leave the receipt open with no successor: it already carries
+   the branch, the worktree, and the implementation, all of which are evidence
+   the plan should read.
 
 5. **Close and land (same engine).** Exactly [`/deliver`](../deliver.md)'s close:
 

package/docs/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.24.0](https://github.com/dsj1984/mandrel/compare/mandrel-v2.23.0...mandrel-v2.24.0) (2026-07-31)
+
+
+### Fixed
+
+* **deliver:** hold the Story assignee-lease until the PR is confirmed merged (refs [#4860](https://github.com/dsj1984/mandrel/issues/4860)) ([#4861](https://github.com/dsj1984/mandrel/issues/4861)) ([d722a65](https://github.com/dsj1984/mandrel/commit/d722a6558f2fa1af6aa428d2f8549101c4bedc23))
+* **maintainability:** score the Babel AST the escomplex kernel actually parses ([#4859](https://github.com/dsj1984/mandrel/issues/4859)) ([279b86f](https://github.com/dsj1984/mandrel/commit/279b86fa49c48454b5e8421ca1e0bb01f54a3bba))
+* scope the light diff backstop by change magnitude, and recycle the receipt instead of orphaning it ([#4856](https://github.com/dsj1984/mandrel/issues/4856)) ([#4857](https://github.com/dsj1984/mandrel/issues/4857)) ([114b479](https://github.com/dsj1984/mandrel/commit/114b4797f248bf00064206f32f490413e28276fb))
+
 ## [2.23.0](https://github.com/dsj1984/mandrel/compare/mandrel-v2.22.0...mandrel-v2.23.0) (2026-07-30)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mandrel",
-  "version": "2.23.0",
+  "version": "2.24.0",
   "description": "Claude Code-first opinionated workflow framework: instructions, skills, rules, and SDLC workflows that govern AI coding assistants.",
   "files": [
     ".agents/",