@renzrollon/interlock 1.5.0 → 1.6.0

package/lib/limits.mjs

@@ -141,6 +141,18 @@ export const LIMITS = {
    */
   maxReviewPolicyBytes: 65_536,
 
+  /**
+   * Character budget for the living-requirement text one review prompt carries
+   * in its `domain` dimension. Whole requirement blocks are added in capability
+   * then spec order until the next would exceed this; every block left out is
+   * counted in the text and named in the result, never cut mid-requirement. It
+   * bounds a prompt, not a merge decision, so it lives here and not in
+   * `MERGE_BANDS`. Read by `assembleDomainContext` in
+   * `lib/prompts/domain-context.mjs`.
+   * See judge-against-base-and-living-specs design.md D4.
+   */
+  maxDomainSpecChars: 12_000,
+
   /**
    * Milliseconds a close's push to the ntfy relay may take before it is
    * abandoned as a failed push. A hanging network call must not stall the
@@ -512,6 +524,54 @@ export const SOLO = {
   maxTasks: 20
 }
 
+/**
+ * The thresholds the merge verdict applies (`interlock merge-confidence`,
+ * `lib/merge-confidence.mjs`), published here so no skill, prompt or document
+ * restates one as the rule — the reason this module exists.
+ *
+ * A separate export from LIMITS, like LANE_CAPS and EVAL_CAPS, for two reasons.
+ * `ceiling` is a table, not a positive-integer loop count, and the LIMITS
+ * invariant holds every entry to that shape. And these are not loop caps: the
+ * verdict is the worst band over every signal, and these numbers only decide
+ * which band one signal reads, or where inside its band's range a score lands.
+ *
+ * `ceiling` is the score each band may reach; a band's floor is one above the
+ * next-worse band's ceiling, and red's floor is 0. `unobserved` has no row: it
+ * takes amber's range, as it takes amber's rank for the verdict, so a fourth
+ * number would be one nobody reads. The domain-spec text cap the epic lists is
+ * deliberately absent: its reader lands with the `domain` review dimension, and a
+ * printed cap with no reader fails the cap-authority sweep.
+ *
+ * Read by `lib/merge-confidence.mjs`, which cites each key by name in the reason
+ * it applies it in; printed by `interlock limits` and emitted as `mergeBands` by
+ * `--json`. The cap-authority sweep covers the group, `ceiling` counting as one
+ * cap on the terms `LANE_CAPS.byTier` does.
+ */
+export const MERGE_BANDS = Object.freeze({
+  ceiling: Object.freeze({ green: 100, amber: 79, red: 39 }),
+
+  /** Surviving review warnings at or under this read green; one more is amber. */
+  maxWarningsForMerge: 2,
+
+  /** Skeptic verdicts a surviving blocker or warning needs before it counts as adjudicated. */
+  minVerdictsPerFinding: 2,
+
+  /** Points the project coverage total may fall below the base total and still read green. */
+  maxCoverageDeclinePts: 1,
+
+  /** Changed-line coverage, in percent, a change with no baseline must reach to read green. */
+  patchCoverageFloorPct: 80,
+
+  /** Changed lines below which coverage is not judged at all; a change of exactly this many is. */
+  minChangedLinesForCoverage: 20,
+
+  /** Changed lines, added plus deleted, above which the diff shape is amber. */
+  maxChangedLinesForMerge: 400,
+
+  /** Changed files above which the diff shape is amber. */
+  maxChangedFilesForMerge: 20
+})
+
 /**
  * Caps for the corpus reader (`interlock report`).
  *
@@ -573,6 +633,7 @@ export function formatLimits({ runtimeObserved } = {}) {
     ['verify preview budget (chars)', LIMITS.verifyPreviewChars],
     ['wave handoff budget (chars, per task)', LIMITS.maxHandoffChars],
     ['review policy scan cap (bytes)', LIMITS.maxReviewPolicyBytes],
+    ['domain spec text budget (chars)', LIMITS.maxDomainSpecChars],
     ['push timeout (ms)', LIMITS.notifyTimeoutMs],
     ['resume card list rows (per list)', LIMITS.resumeCardListRows],
     ['launch ledger max age (ms)', LIMITS.launchLedgerMaxAgeMs],
@@ -623,6 +684,20 @@ export function formatLimits({ runtimeObserved } = {}) {
       .map(tier => [`cache write multiplier: ${tier} (x input)`, MODEL_PRICES.cacheMultipliers.write[tier]])
   ]
   const reportRows = [['report trajectory scan cap', REPORT_CAPS.maxRunsScanned]]
+  // One row per ceiling, then one per threshold. `unobserved` prints beside
+  // amber because it takes amber's range; it has no number of its own.
+  const mergeRows = [
+    ['merge band ceiling: green', MERGE_BANDS.ceiling.green],
+    ['merge band ceiling: amber (also unobserved)', MERGE_BANDS.ceiling.amber],
+    ['merge band ceiling: red', MERGE_BANDS.ceiling.red],
+    ['merge: max surviving warnings', MERGE_BANDS.maxWarningsForMerge],
+    ['merge: min skeptic verdicts per finding', MERGE_BANDS.minVerdictsPerFinding],
+    ['merge: max coverage decline (points)', MERGE_BANDS.maxCoverageDeclinePts],
+    ['merge: patch coverage floor (%, no baseline)', MERGE_BANDS.patchCoverageFloorPct],
+    ['merge: min changed lines to judge coverage', MERGE_BANDS.minChangedLinesForCoverage],
+    ['merge: max changed lines', MERGE_BANDS.maxChangedLinesForMerge],
+    ['merge: max changed files', MERGE_BANDS.maxChangedFilesForMerge]
+  ]
   // One row per tier, rather than a rendered object: an operator reading this
   // wants to know what bounds the lane in front of them, and a tier is how they
   // find it. The cohesion ceiling and the solo envelope print beside them because
@@ -650,7 +725,7 @@ export function formatLimits({ runtimeObserved } = {}) {
     ['effort: review skeptic step', EFFORT.skeptic]
   ]
   const width = Math.max(
-    ...[...rows, ...laneRows, ...evalRows, ...priceRows, ...reportRows, ...effortRows].map(
+    ...[...rows, ...laneRows, ...mergeRows, ...evalRows, ...priceRows, ...reportRows, ...effortRows].map(
       ([label]) => label.length
     )
   )
@@ -660,6 +735,8 @@ export function formatLimits({ runtimeObserved } = {}) {
     '\n\n' +
     laneRows.map(fmt).join('\n') +
     '\n\n' +
+    mergeRows.map(fmt).join('\n') +
+    '\n\n' +
     evalRows.map(fmt).join('\n') +
     '\n\n' +
     priceRows.map(fmt).join('\n') +