clearotron 0.2.0 → 0.2.2

package/driver/contract-dictation-registry.mjs

@@ -90,7 +90,7 @@ export function knownToolNames() {
  * The intersection is fail-closed on the PROVIDER axis — signa exposes two register tools where
  * corsearch exposes eight — and it duly produced 19 hits saying the register doctrine orders
  * `register_enumerate`, which signa does not carry. Every one of those is true and none of them is
- *: they are findings about a vendor's capability envelope, which 's deferral contract already
+ *: they are findings about a vendor's capability envelope, which the deferral contract already
  * owns and states on the coverage form. Folding them in here would bury the grant/doctrine mismatch
  * this contract exists for under a vendor-capability report nobody asked E12 for.
  */
@@ -101,9 +101,9 @@ export function grantedToolsFor(stage) {
   return out;
 }
 
-// ── 's members: two were known, TEN are real ────────────────────────────────────────────────────
+// ── the members: two were known, TEN are real ────────────────────────────────────────────────────
 //
-// E3's precedent, and 's rule under it: "a lint that greenlights every existing hole certifies the
+// E3's precedent, and the rule under it: "a lint that greenlights every existing hole certifies the
 // problem" — so the lint holds the line and the BACKLOG names what is already there, each entry saying
 // which move removes it. rejects "a whitelist of the two known members as the route to green", and
 // this is not that: it is the measured population, which is FIVE TIMES the two members was filed
@@ -209,7 +209,7 @@ export function contracts() {
     //
     // SCOPED TO THE BACKTICKED FIELD NAME, and the loose form was measured before choosing: `/\banchor\b/`
     // fires 52 times across the served corpus against 10 for this pattern, because `anchor` is also a link
-    // anchor ('s subject) and a variant anchor. A pattern whose extra 42 hits would have to be
+    // anchor (the subject) and a variant anchor. A pattern whose extra 42 hits would have to be
     // excused is a pattern kept green by exemptions rather than by fixes — the whitelist route
     // forbids, arriving as a regex instead of a path filter. `anchor-owed` is in because the corrective
     // ladder ORDERS it in exactly that spelling.

package/driver/contract-dictation.mjs

@@ -6,7 +6,7 @@
 // and computes. Nothing here runs on a clearance. The impure edge — building the corpus out of the
 // tracked tree — is scripts/contract-dictation-scan.mjs, and the split is not tidiness:
 //
-//   's hardest acceptance is "plant a divergence in a NEW authoring layer — the check must find it
+//   That hardest acceptance is "plant a divergence in a NEW authoring layer — the check must find it
 //   STRUCTURALLY, not because the layer was enumerated". A checker that reads the tree itself can only
 //   be tested by writing a file into the working tree, which is dirty, fights the repo-hygiene guards,
 //   and — because `git ls-files` is the corpus — may not even be visible to the check being tested.
@@ -52,7 +52,7 @@
 //
 // Whether `/` opens a regex or divides is decided by the previous significant character, which is the
 // standard heuristic and is exact for everything in this tree (a `/` after a value divides; after
-// `( , = : [ ! & | ? { } ; return` it opens a pattern).
+// `(= : [ ! & | ? { } ; return` it opens a pattern).
 const REGEX_PRECEDERS = new Set(["(", ",", "=", ":", "[", "!", "&", "|", "?", "{", "}", ";", "\n", "+", "-", "*", "%", "<", ">", "~", "^"]);
 
 /**

package/driver/contract-e3-backlog.mjs

@@ -5,7 +5,7 @@
 // E3 is "structure is returned, never emitted as text": CI fails a stage message containing a literal
 // JSON skeleton, an "EXACTLY these keys" clause, or a dictated line shape a parser re-parses. 74 such
 // sites exist today across the 19 stages and the skill files they read, so E3 cannot simply go red —
-// and it must not simply go green either. 's judging note applies verbatim:
+// and it must not simply go green either. That judging note applies verbatim:
 //
 //     "a lint that greenlights every existing hole certifies the problem."
 //
@@ -390,7 +390,7 @@ export const E3_BACKLOG = [
     kind: "dictated-line-shape",
     // ── (a) THE ORIGINAL SUBJECT WAS DELETED BY DESIGN — DISCHARGED, NOT FAILED. This row quoted
     // "ARM 2 — a run with NO coverage form … Write one row per coverage unit | Coverage unit | Status |
-    // Reason |". M6 (, 2026-08-14) deleted the code arm and (cdf38676) deleted this
+    // Reason |". M6 (2026-08-14) deleted the code arm and (cdf38676) deleted this
     // skill-file half two days later — exactly the both-sites deletion this row's removedByMove
     // demanded. `git grep "ARM 2"` on the skill file returns nothing. Its evidence sat in
     // E3_EVIDENCE_UNRESOLVED from the day the checker landed; per the ruling the row is
@@ -435,7 +435,7 @@ export const E3_BACKLOG = [
     reparsedBy: "driver/verify.mjs validators.frameDiff + driver/pipeline.mjs runSupplementalSweeps (the parser REFUSES a firing variant directive that dictates nothing dispatchable)",
     removedByMove: "NOTHING ON THE #850 PLAN REMOVES THIS",
   },
-  // DISCHARGED by 's third conversion. The row described SKILL.md's "Then ALSO save the STRUCTURED
+  // DISCHARGED by the third conversion. The row described SKILL.md's "Then ALSO save the STRUCTURED
   // diff … a JSON OBJECT with EXACTLY these keys" skeleton, and that order is gone: the seat calls
   // `record_frame_diff` and the driver serializes the object. What replaced it in the doc is a field list
   // for a typed call, which is not a dictated skeleton — the schema owns those names, and a seat cannot
@@ -791,7 +791,7 @@ export const E3_BACKLOG = [
   // The third is the one worth pausing on: its `removedByMove` said "M2 — the quote half only; the closed
   // three-file enum survives". The enum did not survive the transport, because the transport removed the
   // FIELD it lived in rather than validating it — a schema that cannot express a bad value beats a
-  // validator that rejects one, which is 's ruling applied one lane over.
+  // validator that rejects one, which is the ruling applied one lane over.
 ];
 
 /** Entries with no move on the plan that removes them. */
@@ -804,7 +804,7 @@ export const E3_UNPLANNED = E3_BACKLOG.filter((e) => e.removedByMove === "NOTHIN
  * The registry's failure mode was that a MOVE could delete a dictation and leave the row: the count
  * then overstates the work, and the next agent spends a conversion slot on a hole already filled. Two
  * instances existed when this was written — M6's register-digest arm (deleted 2026-08-14, row survived)
- * and synthesis's disposition list (, deleted the same morning by the agent adding this check).
+ * and synthesis's disposition list (deleted the same morning by the agent adding this check).
  * Both are gone; this list is what remains.
  *
  * A BLANKET ASSERTION WAS THE OBVIOUS BUILD AND IT WOULD HAVE BEEN NOISE. Measured before choosing:
@@ -865,7 +865,7 @@ export const E3_EVIDENCE_UNRESOLVED = [
 /**
  * THE PER-SURFACE CENSUS, PINNED EXACTLY IN BOTH DIRECTIONS.
  *
- * 's urgency claim is that `tool-response` GROWS — one surface at a time, each move taking a row out
+ * That urgency claim is that `tool-response` GROWS — one surface at a time, each move taking a row out
  * of sight while the count stays plausible. A ceiling on that number would fail upward exactly as the E3
  * ceiling did: a surface that shrank would pass silently and leave room for a move nobody
  * recorded. So this is exact. A migration that moves a row from `stage-message` to `tool-response` turns

package/driver/contract-vocabulary.mjs

@@ -155,7 +155,7 @@ export const VOCABULARY = [
   // red on any that no row covers. That is the census working the way the previous conversion's gap
   // taught it to — skeptic's nine tokens were raised for two conversions before anything could see them.
   { token: "reportoverview_", stages: ["report-overview"], site: "driver/report-overview-record.mjs acceptReportOverview", family: "driver/report-overview-record.mjs", dynamic: "D3" },
-  // Conversion 5's transport family. Declared in the SAME commit as the module — 's extractor reads
+  // Conversion 5's transport family. Declared in the SAME commit as the module — the extractor reads
   // the acceptance boundary, so `report-card-record.mjs` is read for the `reason:` shape and the E2
   // soundness tripwire sees every `reportcard_*` token the moment it exists.
   { token: "reportcard_", stages: ["report-card"], site: "driver/report-card-record.mjs acceptReportCard", family: "driver/report-card-record.mjs", dynamic: "D3" },
@@ -396,7 +396,7 @@ export const TRIPWIRE_OUT_OF_SCOPE = [
  * nothing.
  *
  * WHY NOT A VOCABULARY ROW. A row asserts "this stage emits this token", and for all nineteen of these
- * that assertion is false. 's own judging condition forbids writing it: *no row claims a stage emits
+ * that assertion is false. its own judging condition forbids writing it: *no row claims a stage emits
  * a token that stage cannot emit*.
  *
  * WHY NOT A BARE EXEMPTION. An out-of-scope rule excuses a token and asserts nothing, so it cannot fail.
@@ -541,7 +541,7 @@ export const COVERED_SOURCES = [
  */
 
 /**
- * The tables whose rows carry a citation — the population 's symbol arms walk.
+ * The tables whose rows carry a citation — the population the symbol arms walk.
  *
  * Named once, here, rather than retyped in the test: a fifth table added later and missed by a hand-typed
  * list would be unchecked while every arm stayed green. The test asserts this map's own membership too,

package/driver/corrections-feedforward.mjs

@@ -3,7 +3,7 @@
 // corrections-feedforward.mjs — the reviewer's flags reach the corrective pass as DATA, and the recheck
 // is handed what the driver OBSERVED rather than being asked to re-read two documents.
 //
-// 's first acceptance criterion is that a BLOCKING-verdict full re-run becomes structurally
+// That first acceptance criterion is that a BLOCKING-verdict full re-run becomes structurally
 // impossible. `docs/design/clearance-critical-path.md` §4 bounds how that can be built: refutation cannot
 // run before synthesis (`stageInputs["narrative-refutation"]` includes the narrative, and dependencyOrder
 // derives the edge mechanically), so the lever available is the CHANNEL the reviewer already writes into

package/driver/coverage-form-io.mjs

@@ -14,10 +14,10 @@
 // written by runDigest on every pass that will actually run, is already the arming key for the off-enum
 // gate, and is already declared in stage-context.VALIDATOR_SIDECARS. adds `form_required: true` and
 // `form_path` to it rather than minting a second stamp, so there is one answer to "was a form required
-// on this run" and archived runs — which carry either no sentinel at all or a pre- one with no
+// on this run" and archived runs — which carry either no sentinel at all or a pre-change one with no
 // `form_required` — leave the whole coverage-form arm OFF and never flip a replay verdict.
 //
-// THE WRITE ORDER IS LOAD-BEARING AND IT IS STAMP FIRST. 's form write is best-effort and only
+// THE WRITE ORDER IS LOAD-BEARING AND IT IS STAMP FIRST. That form write is best-effort and only
 // note()s on failure, and its own comment names the outcome it fears: "an absence reading as a pass,
 // which is the one outcome this file exists to refuse". It is reachable — a full disk fails as "artifact
 // absent", not as a disk error. Writing the FORM first and the stamp second reproduces that hole: a

package/driver/coverage-form.mjs

@@ -22,7 +22,7 @@
 // PURE — no node imports, so it tests offline, exactly like coverage-ledger.mjs and connotation-search.mjs
 // (whose headers state the same rule for the same reason). `shortId` is IMPORTED from connotation-search
 // rather than re-implemented: it is a generic fnv1a64 id stamp, and a second copy of an id function is
-// two calculations kept in step, which is 's defect.
+// two calculations kept in step, which is the defect.
 //
 // ONE CALCULATION, NOT TWO. `openBlocksByAxis` (register-plan.mjs) computes the open crowd blocks — the
 // same C2..C7 conditions the deleted gate computed, unchanged — and it is called EXACTLY ONCE per pass,
@@ -108,7 +108,7 @@ export const SEAT_ROW_FIELDS = Object.freeze(["kind", "axis", "unit", "status",
 /**
  * WHAT A SEAT ROW OWES, written INTO the accumulator (and told to the seat in the dispatch brief and
  * the tool's own refusals — the seat no longer opens this file). The allowed axis set is not prose
- * about the file, it is a field OF the file: 's finding was "a fact obeyed as a failure and
+ * about the file, it is a field OF the file: the finding was "a fact obeyed as a failure and
  * ignored as an input", and a closed vocabulary the seat must hit and is never shown is exactly that.
  * PURE data.
  *
@@ -474,7 +474,7 @@ export function coverageFormRows({ skeleton = [], activeAxes = null, plan = null
       // the receipt should be able to tell which of the two a run carried.
       deferred_offices: (Array.isArray(plan?.deferred_coverage) ? plan.deferred_coverage : []).length,
       // AN ABSENCE IS A FINDING, RECORDED IN THE ARTIFACT. An axis whose band would not parse
-      // contributes NO open-block rows, exactly as the pre- gate's per-axis catch did — a band
+      // contributes NO open-block rows, exactly as the pre-change gate's per-axis catch did — a band
       // parse defect is refused one stage earlier by validators.registerUnit. Naming the axes here
       // means the gap is visible on the form a reader opens instead of being a silent zero.
       bands_unreadable: [...(bandsUnreadable ?? [])],
@@ -568,7 +568,7 @@ export function coverageAbsenceGaps(parsed) {
 }
 
 /**
- * The sentence a lawyer reads where the ledger would be. NEVER an empty section: 's lesson one lane
+ * The sentence a lawyer reads where the ledger would be. NEVER an empty section: the lesson one lane
  * over — a heading with nothing under it asserts an absence it cannot explain, and a reader cannot tell
  * it from a run that swept nothing. This says which material was missing and, therefore, exactly what
  * the rest of the report does and does not rest on.

package/driver/coverage-ledger.mjs

@@ -108,7 +108,7 @@ export const CROWD_RULING_UNIT_GRAMMAR = `<axis> / ${CROWD_RULING_TOKEN} (<N> me
 // was accepted, carried through the union, passed the coverage gate, and blocked the run three gates
 // later over a ruling the seat had made. Both readers now call this, so call time and delivery time
 // cannot disagree about what a count is. That is the point of the function, not a tidiness: two copies
-// of this regex would let the refusal and the block drift apart, which is 's defect.
+// of this regex would let the refusal and the block drift apart, which is the defect.
 //
 // THREE ANSWERS, and the middle one is the whole reason the return is not a boolean:
 //   null  — the cell rules no crowd. Every other coverage row, and the overwhelming majority.
@@ -500,11 +500,11 @@ export function parseCoverageLedgerJson(raw, { allowedAxes = REGISTER_AXES, acti
   return rows;
 }
 
-// ── tracker issue 476 — `renderCoverageLedgerJson` IS DELETED, AND THE DIRECTION WITH IT ─────────────────────────
+// ── `renderCoverageLedgerJson` IS DELETED, AND THE DIRECTION WITH IT ─────────────────────────
 //
 // Map #3 code-derived this JSON FROM the model's `## Coverage ledger` prose, which was an improvement
 // (the model stopped authoring the JSON) that left the real source of truth where it was: a markdown
-// table the model wrote. Under tracker issue 476 the DRIVER-WRITTEN coverage form is the source and both the table
+// table the model wrote. The DRIVER-WRITTEN coverage form is the source and both the table
 // and this JSON are renders of it — coverage-form.renderCoverageLedgerJsonFromForm. There is no
 // prose→JSON direction left to keep, and keeping one would be the legacy path this build has none of.
 //

package/driver/coverage-union.mjs

@@ -21,7 +21,7 @@
 // is. This file mints no row, no id, no unit label and no definition of "settled": `coverageFormRows`
 // and `rowIsSettled` both come from coverage-form.mjs — the same code the GATE judges with. A union that
 // preserved a status the gate would refuse, or dropped one it would accept, would make the outstanding
-// count mean two different things in two places, which is 's defect exactly.
+// count mean two different things in two places, which is the defect exactly.
 
 import { coverageFormRows, rowIsSettled, seatFields, formRowKey, seatRows, SEAT_ROW_CONTRACT } from "./coverage-form.mjs";
 

package/driver/declination-call.mjs

@@ -2,7 +2,7 @@
 // Copyright 2026 Cordillera Sàrl. Additional terms under section 7 of the AGPL-3.0 apply — see ADDITIONAL-TERMS.md
 // declination-call.mjs — a record that reached the findings surface leaves it BY A STATED DECISION.
 //
-// ── THE DEFECT THIS CLOSES (, and 's half of the same seam) ────────────────────────────────
+// ── THE DEFECT THIS CLOSES (and the half of the same seam) ────────────────────────────────
 //
 // `record-carry.json` on R2 round `e48f7056` read `unreasoned: 0` and was telling the truth in the weak
 // sense only: every drop had a LABEL, and on 102 of them the label was inferred from where the record
@@ -70,7 +70,7 @@
 // that a note describing the material instead of stating a ground is the defect one artifact over.
 // Measured against seven realistic declinations before anything was built on it, that classifier refused
 // ALL SEVEN as `unclear` — including "already delivered as finding 4 under the EUIPO record for the same
-// proprietor". It is not a bug in the classifier. It answers a different question: 's notes must say
+// proprietor". It is not a bug in the classifier. It answers a different question: the notes must say
 // what could NOT BE ESTABLISHED about a charged rating, and a declination says why a record does not earn
 // a line. Two different speech acts, and a grammar built for one rejects the other on sight.
 //
@@ -210,6 +210,38 @@ export function contradictionFor(reason, row, scope) {
       + `own-right or duplicate-of-delivered.`;
   }
 
+  // ── ECONOMY IS NOT A REASON ABOUT A LIVE IN-CLASS MARK (owner ruling 2026-09-07) ─────────────────
+  //
+  // `not-worth-the-line` means "it fits none of the four manageable categories and is not relevant
+  // enough to drive the read". That is a statement about the REPORT'S BUDGET, not about the record. On a
+  // live registration inside one of the matter's own instructed classes it is the one thing the seat may
+  // not say: the reader is paying for a judgment about that mark, and "there was no room" is not one.
+  //
+  // Measured on the run that prompted the ruling: 26 of 49 declinations at this seam were this token,
+  // and two of the lawyer's own reference marks were among them — one carried on every earlier run.
+  //
+  // ✕ WHY THIS IS NOT THE REFUSAL THAT WAS REMOVED BELOW, and the difference is the whole reason it can
+  // stand. That one refused `unrelated-goods` and `off-field-not-major` on class overlap, fired on 170
+  // of 170 records, and made the ENGINE decide relatedness — the lawyer's call. This one refuses ONE
+  // token and leaves every substantive reason available. The seat may still decline this record: it may
+  // say the goods are unrelated, that it is off-field and not a major brand, that it is the applicant's
+  // own right, or that it is already delivered. What it may no longer do is decline it for taking up
+  // space. The refusal is about the SHAPE of the reason, not about whether the record is relevant, so
+  // the relatedness judgment stays exactly where it was.
+  //
+  // It does effectively retire this token for live in-class records, because the sweep is already scoped
+  // to the instructed classes. That was put to the owner as the consequence and ruled anyway.
+  if (reason === "not-worth-the-line" && isLive(row?.status) && shared.length) {
+    return `this record is ${String(row?.status ?? "").trim() || "live"} and sits in class `
+      + `${shared.join(", ")} — one of the matter's own instructed classes. "not worth the line" is a `
+      + `statement about the report's budget, not about this mark, and a live registration in an `
+      + `instructed class is never omitted for want of room. Either carry it, or decline it on something `
+      + `true of THIS MARK: unrelated-goods if its goods do not meet the matter's, off-field-not-major `
+      + `if it is off-field and not a major brand, an active dispute or a well-known enforcer, `
+      + `own-right if it belongs to the applicant, duplicate-of-delivered if the same right is already `
+      + `reported. Say what makes this mark distant, or give it its line.`;
+  }
+
   // THERE IS NO CLASS-OVERLAP REFUSAL, AND THE FIRST DRAFT HAD ONE. It refused `unrelated-goods` and
   // `off-field-not-major` over any record sharing one of the matter's filed classes, on the reasoning
   // that the driver holds both class lists and they disagree with the stated reason.
@@ -231,7 +263,7 @@ export function contradictionFor(reason, row, scope) {
 }
 
 /**
- * THE SEAM'S DECISION, AS A PURE FUNCTION — 's guarantee, in the one place it can be asserted.
+ * THE SEAM'S DECISION, AS A PURE FUNCTION — the guarantee, in the one place it can be asserted.
  *
  * `recordSynthesisSeam` is module-private in pipeline.mjs and always will be; it does file I/O and takes
  * a run context. The JUDGMENT it makes about each discarded record is this, and it is extracted so a test

package/driver/declination-duty.mjs

@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: AGPL-3.0-only
 // Copyright 2026 Cordillera Sàrl. Additional terms under section 7 of the AGPL-3.0 apply — see ADDITIONAL-TERMS.md
 // declination-duty.mjs — every record handed to synthesis left by a NAMED EXIT, or the run says which
-// ones did not. ('s missing half; the R2 round on is the incident.)
+// ones did not. (the missing half; the R2 round on is the incident.)
 //
 // THE RULE IS ALREADY DICTATED, AND IT WAS NEVER CHECKED. synthesis's own contract states it in one
 // line — "a record that reached your findings surface leaves this stage as a finding in findings.json

package/driver/deliver-trigger.sh

@@ -4,7 +4,7 @@
 # v2 (pure-MCP courier, docs/DELIVERY.md): the outbox carries EVERY requester-facing event — delivered
 # markers (body = the forwarding agent id) AND self-contained JSON packets (run-failed / intake-rejected /
 # duplicate-skipped / late-bind-ack, each with an "agent" field). For each DISTINCT agent named across
-# pending events, wake it ONCE to run the prelim-deliver skill, which routes everything over the ops MCP
+# pending events, wake it ONCE to run the clearotron-deliver skill, which routes everything over the ops MCP
 # (list_outbox_events → get_delivery_packet → send → mark_sent/ack_event).
 #
 # THE TRIGGER NEVER DELETES EVENTS: consumption belongs to mark_sent (delivered) and ack_event (the rest),
@@ -35,7 +35,7 @@ DRAIN_WAIT="${CLEAROTRON_OUTBOX_DRAIN_WAIT:-180}"
 # (openclaw models); set CLEAROTRON_OUTBOX_WAKE_MODEL="" to fall back to the agent default. `-` (not `:-`) so
 # an explicit empty value disables the override, while unset keeps the Haiku default.
 WAKE_MODEL="${CLEAROTRON_OUTBOX_WAKE_MODEL-anthropic/claude-haiku-4-5}"
-MSG="The trademark engine's outbox has pending events. Run the prelim-deliver skill now: list_outbox_events, route each event (delivered → get_delivery_packet + send VERBATIM + mark_sent; every other kind → relay its text + ack_event)."
+MSG="The trademark engine's outbox has pending events. Run the clearotron-deliver skill now: list_outbox_events, route each event (delivered → get_delivery_packet + send VERBATIM + mark_sent; every other kind → relay its text + ack_event)."
 
 # THE WALL, RESOLVED ONCE AND NAMED WHEN IT IS ABSENT (tracker issue 820).
 #
@@ -112,7 +112,7 @@ for agent in "${!by_agent[@]}"; do
     continue
   fi
 
-  echo "prelim-outbox: waking $agent to run prelim-deliver"
+  echo "prelim-outbox: waking $agent to run clearotron-deliver"
   # timeout(1) is the enforced wall: the 2026-07-04 incident proved the CLI's own --timeout does not
   # guarantee process EXIT (the agent turn finished; the process idled 19h and wedged the lane).
   # SIGTERM at 840s (inside the unit's TimeoutStartSec budget so the failure is OURS and logged),

package/driver/deploy-live-run-guard.mjs

@@ -37,7 +37,7 @@ function listDir(dir) {
  * Everything holding this deployment open, named.
  *
  * @param {object} a
- * @param {string} a.queueDirs  EVERY queue tree, not the one this box thinks it uses. 's lesson:
+ * @param {string} a.queueDirs  EVERY queue tree, not the one this box thinks it uses. That lesson:
  *                                a headless CLEAROTRON_QUEUE_DIR and the agent workspace queues are both
  *                                real, and a guard that reads one of them passes over work sitting in
  *                                the other.
@@ -66,7 +66,11 @@ export function liveRunHolds({ queueDirs = [], lockDir = null, isAlive = claimer
     const { names, error } = listDir(lockDir);
     if (error) unreadable.push({ path: lockDir, error });
     for (const n of names) {
-      if (!n.startsWith("slot-") || !n.endsWith(".lock")) continue;
+      // `draw-` alongside `slot-`: a direct --experiment invocation is work on this box and the guard's
+      // question is whether the box is busy, so a draw has to answer yes. It holds its own prefix rather
+      // than a run slot, because a run slot is admission-controlled and taking one would make a draw wait
+      // behind clearances — changing what a draw IS in order to fix what this can see.
+      if (!/^(slot|draw)-/.test(n) || !n.endsWith(".lock")) continue;
       let raw = null;
       try { raw = readFileSync(join(lockDir, n), "utf8"); } catch { continue; }   // released mid-scan
       const pid = Number(String(raw).split(":")[0]);

package/driver/dev-portal.mjs

@@ -373,7 +373,7 @@ export function startPortal({ poolRoot = null, port = 18899, host = "127.0.0.1",
       if (url.pathname === "/dev/enqueue" && req.method === "POST") {
         let body;
         try { body = await readJsonBody(req); } catch (e) { return sendJson(res, 400, { ok: false, error: e.message }); }
-        // `searchLevel` IS REFUSED, NOT DROPPED. This form offered a "Search level" menu (prelim · Depth 4
+        // `searchLevel` IS REFUSED, NOT DROPPED. This form offered a "Search level" menu (clearotron · Depth 4
         // / knockout · Depth 1) and posted the field to an assembler that stopped reading it, so picking
         // "knockout" enqueued a job naming no product at all and ran whatever the account default or the
         // request's own territories named — a silent product substitution at a live door, from a control

package/driver/disposition-call.mjs

@@ -145,7 +145,7 @@ export const CALL_REFUSALS = Object.freeze([
   "obstacle_absent",      // an obstacle was claimed with nothing said about what blocks the proof
 ]);
 
-// The proof-of-reading arms, and ONLY those. 's obstacle waives this duty and no other, so this set
+// The proof-of-reading arms, and ONLY those. That obstacle waives this duty and no other, so this set
 // is the exact boundary between "you have not proved you read it" and "you have not judged it" — derived
 // by prefix from the vocabulary above rather than retyped, so a new evidence arm joins it automatically
 // and a new judgment arm cannot wander in.
@@ -183,7 +183,7 @@ export const RETIRED_CALL_REFUSALS = Object.freeze([
 // and it must never appear in the same bucket, because the two demand opposite responses — one says
 // "change your answer", the other says "stop asking, it is ours".
 //
-// 's leading unproven hypothesis lives here. The accumulator's rows and candidates are REGENERATED
+// That leading unproven hypothesis lives here. The accumulator's rows and candidates are REGENERATED
 // on every pass, and `seatFields` re-resolves an already-resolved row against whatever the current pass
 // holds (`disposition-union.mjs:98`, which discards `resolveCandidate`'s `state`). If that second
 // resolution misses, a row the tool accepted lands with an empty receipt and reads as unruled. This
@@ -442,7 +442,7 @@ export function detectRulingDrift(ledger) {
  *
  * ── WHY THE TOTAL IS RETURNED TOO ───────────────────────────────────────────────────────────────────
  *
- * 's warning sits in this exact number: filtering it after a split reported
+ * That warning sits in this exact number: filtering it after a split reported
  * `obligationsNeverAddressed: 0` on the run that died owing 75. So the total comes back as its own field
  * and the two parts must sum to it. Nothing can go to zero without a companion number rising to meet it.
  *
@@ -822,7 +822,7 @@ export function validateDispositionCall(rows, recorded, { told = null } = {}) {
 /**
  * CAN THIS ROW'S EVIDENCE DEMAND EVER BE SATISFIED?
  *
- * — the agreement guard for the `evidence_owed` seam, and it is 's shape one module over. The
+ * — the agreement guard for the `evidence_owed` seam, and it is the shape one module over. The
  * demand (`quote_required`) is SET at form-build against candidates that carried text; the satisfaction is
  * enforced by `segmentBinding` against the candidate's snippet AS IT IS NOW. Between the two, candidates
  * regenerate. When they come back without quotable passages the flag survives and its justification does

package/driver/disposition-tool.mjs

@@ -19,7 +19,7 @@
 //   decided, which is the thing already in the record, rather than what we were given.
 //
 //   THE INDEX IS WRITTEN BY THE RECEIVER, NEVER BY THE CONSUMER. This handler writes both the payload and
-//   the line naming it, in that order, before it validates anything. 's three snapshot sites all
+//   the line naming it, in that order, before it validates anything. That three snapshot sites all
 //   discard their return, so no attempt row names its snapshot and correlation is by mtime — which is
 //   precisely how the union discard had to be diagnosed. A consumer-written index can only ever name the
 //   payloads the consumer got to; a call that dies mid-flight writes no index line, and its absence is
@@ -46,7 +46,7 @@ const CALLS_DIR = "disposition-calls";
 /**
  * The obligations sidecar — what the seat was TOLD it owed, written when the block was rendered.
  *
- * 's rule, applied to this filename: the path is derived ONCE and imported, never re-derived at the
+ * That rule, applied to this filename: the path is derived ONCE and imported, never re-derived at the
  * other end. perplexity-server.mjs writes this file and this module reads it; two spellings of one name
  * is the drift cost weeks, and the reader would fail OPEN — it would simply find no file, fall back
  * to the live derivation, and renumber the seat's page without anyone being told.
@@ -338,7 +338,7 @@ export function outstandingWithAnchors(canonicalRows, formRows) {
  * Record one typed call. The tool handler's core.
  *
  * `spec` is the DRIVER-WRITTEN grid spec — the same file the grid tool was given. The seat names no path
- * of its own: 's rule is that the path is the driver's, taken from the spec it wrote, because two
+ * of its own: the rule is that the path is the driver's, taken from the spec it wrote, because two
  * derivations of one filename is the drift that cost weeks.
  */
 export function recordDispositions(spec, received, { now = () => new Date().toISOString() } = {}) {
@@ -415,7 +415,7 @@ export function recordDispositions(spec, received, { now = () => new Date().toIS
   // accumulator" are two different facts and nothing compared them.
   //
   // This compares them, per call, and records any disagreement as OURS. It is deliberately not a throw:
-  // 's silent-drop hypothesis is unproven, and an instrument that crashes the run it is measuring
+  // That silent-drop hypothesis is unproven, and an instrument that crashes the run it is measuring
   // cannot measure it. If the count is always zero the hypothesis is dead and we will be able to say so
   // from the artifact — which is the point of building it before the cure.
   const landed = new Map((Array.isArray(u.form?.rows) ? u.form.rows : [])

package/driver/disposition-union.mjs

@@ -21,7 +21,7 @@
 // definition of "ruled" and — since the review of this build — no row LOOKUP either. `obligationRows`,
 // `formRowFinder` and `isRuled` all come from connotation-search.mjs, the same code the GATE
 // judges with. A union that preserved a ruling the gate would refuse, or dropped one it would accept,
-// would make the outstanding count mean two different things in two places, which is 's defect
+// would make the outstanding count mean two different things in two places, which is the defect
 // exactly: one calculation running twice, silently disagreeing, both copies looking correct. The lookup
 // had been written out twice — here and in the gate — and both copies carried the same punctuation defect.
 
@@ -160,7 +160,7 @@ export function unionDispositionForm(prior, submitted, ob, { half = null, genera
   const findSubmitted = formRowFinder(submitted, form.rows);
   // — a park is STICKY, for the same reason a ruling is. This module exists because the outstanding
   // count churned instead of shrinking (see the header): a park that could lift would let the count rise
-  // again, which is 's defect in new clothes. So the prior form's park is authority, and `parkedIds`
+  // again, which is the defect in new clothes. So the prior form's park is authority, and `parkedIds`
   // only ever ADDS.
   const newlyParked = new Set((parkedIds ?? []).map((x) => String(x ?? "").trim()).filter(Boolean));
   let ruled = 0, carried = 0, parked = 0;

package/driver/doc-constants.mjs

@@ -350,7 +350,7 @@ export const DOC_CONSTANTS = [
     doc: "providers/uspto-local/README.md",
     pattern: /last successful sync goes past (\d+) hours/,
   },
-  // The same figure, twice in the same file — 's shape, and the reason each occurrence is a row.
+  // The same figure, twice in the same file — the shape, and the reason each occurrence is a row.
   {
     constant: "FRESHNESS_HOURS.sync",
     source: { file: "providers/uspto-local/src/index-store.js", symbol: "FRESHNESS_HOURS.sync" },

package/driver/door-gates.mjs

@@ -97,7 +97,7 @@ export function gateResolvedRequest({ job = null, profile = null, resolved = nul
   // A resolution that could not be taken is not a refusal — see the fail-open note in the header.
   if (!resolved) return out;
   // A CLARIFY IS RELAYED VERBATIM. It is already an actionable sentence naming the selector that could
-  // not be honoured ("product \"prelim\" names no search we offer — one of: … (or omit it for the
+  // not be honoured ("product \"clearotron\" names no search we offer — one of: … (or omit it for the
   // account's default)"), and flattening it into a cause would lose the remedy clause.
   if (resolved.clarify) { out.errors.push(resolved.clarify); return out; }
   // deliveryRoute "portal" — DECLARED but not BUILT. It validates shape-wise, has no consumer (the
@@ -133,7 +133,7 @@ export function doorGates(job, opts = {}) {
   return { ...r, ...gateResolvedRequest({ job, ...r }, opts) };
 }
 
-// ── WHY tracker issue 216'S REFUSAL IS NOT ALSO A DOOR GATE ─────────────────────────────────────────
+// ── WHY THE CONFIGURED-TO-SEARCH REFUSAL IS NOT ALSO A DOOR GATE ─────────────────────────────────────────
 //
 // It was, briefly, and it was removed with a measurement rather than an opinion. Adding "is this box
 // configured to search at all" here reddened `driver/test/doors-agree.test.mjs` — nineteen arms green

package/driver/doubt-selection.mjs

@@ -2,7 +2,7 @@
 // Copyright 2026 Cordillera Sàrl. Additional terms under section 7 of the AGPL-3.0 apply — see ADDITIONAL-TERMS.md
 // doubt-selection.mjs — which OPEN doubts the closure seat is asked about, chosen by the DRIVER.
 //
-// 's architecture, one lane over from profile-selection.mjs: "prefer driver selection wherever the
+// That architecture, one lane over from profile-selection.mjs: "prefer driver selection wherever the
 // key precedes the dispatch." The key is on the doubt before doubt-closure is dispatched, so there is
 // nothing here for a directive to ask a seat to judge — the driver lists the ids, and a doubt it does
 // not list is never mentioned.
@@ -68,7 +68,7 @@ export function keptTiersFor(doubtClosure) {
  * WHICH OF THE THREE SILENCES THIS IS. `keptTiersFor` returns null for `every-doubt` AND for a word it
  * does not know, deliberately — a typo must not silently drop every keyed doubt. But that makes the two
  * indistinguishable in the run's event: a misspelt cut records exactly what the shipped cut records, and
- * the product row looks graded while the dispatch is not. 's arm catches a bad word on the ROW; this
+ * the product row looks graded while the dispatch is not. That arm catches a bad word on the ROW; this
  * is the runtime face of the same question, on the run that actually happened.
  *
  * `hasOwnProperty` rather than a truthiness test on the lookup, because `TIER_CUTS[w]` reaches the

package/driver/drainer-identity.mjs

@@ -34,7 +34,7 @@
 import { readFileSync, writeFileSync, mkdirSync, renameSync } from "node:fs";
 import { execFileSync } from "node:child_process";
 import { join, dirname } from "node:path";
-import { drainPosture, absentDrainerIsNormal } from "./drain-posture.mjs";   // tracker issue 206 — one rule about the box
+import { drainPosture, absentDrainerIsNormal } from "./drain-posture.mjs";   // one rule about the box
 
 export const STAMP_BASENAME = "_drainer-identity.json";