ci(test-shards): the self-test verdict names the closure allowance when the bins exceed the bare cap

The success line said "within the <cap> density cap" from the bare cap alone;
once a dataset slices only through the allowance (bins 1553 s against a
1455.81 s cap on the 2026-11-02 refresh) that sentence would be false. It
now names the allowance exactly when the bare cap did not decide, so today's
line is byte-identical.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017ihL2gLghEqeDKTbDTC7Zd

Author: claude

scripts/partition-test-shards.mjs

@@ -3878,8 +3878,12 @@ function selfTest() {
     `partition-test-shards: self-test OK (${datasetPackages.length} measured packages ` +
       `-> ${datasetItems.length} shard items, ${SHARD_COUNT} shards, ` +
       `max/mean ${balance.ratio.toFixed(2)}x <= ${MAX_SHARD_OVER_MEAN}x, floor ${balance.floor.toFixed(0)}s, ` +
-      `bins ${balance.totals.map((t) => t.toFixed(2)).join('/')}s within the ${datasetCap.toFixed(2)}s density cap, ` +
-      `whole legs ${wholeLeg.sums.map((t) => t.toFixed(0)).join('/')}s within ${WHOLE_LEG_CAP_SECONDS}s, ` +
+      `bins ${balance.totals.map((t) => t.toFixed(2)).join('/')}s within the ${datasetCap.toFixed(2)}s density cap` +
+      // Named only when the bare cap did not decide, so the line never claims a cap the bins exceed.
+      (balance.max > datasetCap
+        ? ` plus its ${closureAllowance(datasetItems, SHARD_COUNT).toFixed(2)}s declaration-closure allowance`
+        : '') +
+      `, whole legs ${wholeLeg.sums.map((t) => t.toFixed(0)).join('/')}s within ${WHOLE_LEG_CAP_SECONDS}s, ` +
       `file-level slices: ` +
       `${datasetPlan.decisions.filter((d) => d.count > 1).map((d) => `${d.name} x${d.count}`).join(', ') || 'none'})`
   );