clearotron 0.3.2-beta.11 → 0.3.2-beta.12

package/driver/portal-service.mjs

@@ -3931,7 +3931,9 @@ const escHtml = (t) => String(t).replace(/[&<>"']/g, (c) => ({ "&": "&amp;", "<"
 // and brand pack §01 fixes dark at #0f0e0c near-black + #f0e8d8 parchment. The pack wins.
 // ── THE PLAIN LINE LEADS; THE ADMINISTRATOR'S TWO LINES STEP BACK INTO A FOLD ────────────────────────
 //
-// A person arriving here needs the field, the button, and one fact: this install signs in one person.
+// A person arriving here needs the field, the button, and one fact: this install has one user, and which
+// address that is. The owner's words, 2026-09-19: "Clearotron portal, as <address>." read as "you are
+// <address>", and a person who found `key issue` first minted a key and could not get in.
 // The reset command and the way to add people are an administrator's business, so they sit in a closed
 // "Administrator help" fold, word for word as they were, with the same link People gives to putting a
 // login system in front. A `<details>` needs no script, which this door must render without.
@@ -3976,9 +3978,7 @@ ${DOOR_THEME_INIT}
   .hint { margin-top:18px; font-size:13px; }
   code { font-family:var(--mono); font-size:12.5px; background:var(--code-bg);
          padding:1px 5px; border-radius:4px; overflow-wrap:anywhere; }
-  .lead { margin:18px 0 0; padding-top:14px; border-top:1px solid var(--line); font-size:13.5px; color:var(--ink); }
-  .lead b { font-weight:600; }
-  .fold { margin-top:10px; }
+  .fold { margin-top:18px; padding-top:14px; border-top:1px solid var(--line); }
   .fold > summary { display:inline-flex; align-items:center; gap:6px; list-style:none; cursor:pointer;
                     font-size:13px; color:var(--link); }
   .fold > summary::-webkit-details-marker { display:none; }
@@ -3993,7 +3993,7 @@ ${signedIn
     ? `<p>You are signed in as <span class="who">${escHtml(email)}</span>.</p>
 <div><a href="/portal">Go to the portal</a></div>
 <form method="post" action="/portal/logout"><button type="submit">Sign out</button></form>`
-    : `<p>${escHtml(BRAND.name)} portal, as <span class="who">${escHtml(email)}</span>.</p>
+    : `<p>This ${escHtml(BRAND.name)} has one user: <b class="who">${escHtml(email)}</b>. Enter its passphrase.</p>
 ${discarded ? `<p class="hint">A session this portal did not start, from another ${escHtml(BRAND.name)} on this address or an expired one, was set aside. Sign in below.</p>` : ""}
 ${error ? `<p class="err">${escHtml(error)}</p>` : ""}
 <form method="post" action="/portal/login">
@@ -4001,10 +4001,10 @@ ${error ? `<p class="err">${escHtml(error)}</p>` : ""}
   <input id="passphrase" name="passphrase" type="password" autocomplete="new-password" autofocus>
   <button type="submit">Sign in</button>
 </form>
-<p class="lead"><b>This ${escHtml(BRAND.name)} signs in one person: you.</b></p>
 <details class="fold"><summary><span>Administrator help</span><svg class="chev" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false"><path d="m9 18 6-6-6-6"/></svg></summary>
-<p class="hint">Lost the passphrase? Run <code>${escHtml(reset)}</code> on the machine
-running this portal. It mints a new one and prints it once.</p>
+<p class="hint">The passphrase was printed once when this ${escHtml(BRAND.name)} first started. Lost it? Run
+<code>${escHtml(reset)}</code> on the machine running this portal. It prints a new one, once, for the same user.</p>
+<p class="hint">A key from <code>${escHtml(bareInvocation("key"))} issue</code> is for an AI assistant, not for this page.</p>
 <p class="hint">To add people, put it behind a login system such as your company single sign-on. <a href="${escHtml(LOGIN_IN_FRONT_DOC)}" target="_blank" rel="noreferrer">How to set that up</a></p>
 </details>`}
 </div></body></html>`;

package/driver/publish/render-knockout.mjs

@@ -62,6 +62,7 @@ import { EXPORT_TOGGLE, exportPopover, EXPORT_MENU_JS } from './report-topbar.mj
 // which is the thing providers/_shared/screen.mjs exists to prevent.
 import { makeClassifyStatus, isAllClass } from '../../providers/_shared/screen.mjs';
 import { saysSomethingNew } from '../../shared/says-something-new.mjs';
+import { isNextStepHeading } from '../knockout-next-step.mjs';
 
 const HERE = dirname(fileURLToPath(import.meta.url));
 
@@ -1513,21 +1514,25 @@ function koScale(framework, band) {
 // It MOVES, it is not copied: `splitOutcome` returns the assessment without it, and the fold renders
 // that remainder, so the words appear once.
 //
+// A RECORD WRITTEN SINCE 2026-09-19 NEVER REACHES THIS WITH ONE: the pipeline removes a next-step section
+// before it writes the record (`knockout-next-step.mjs`), and the heading test below is that module's, so
+// the two cannot come to disagree about what a next step is. What still draws the section is a record
+// written before then, re-rendered.
+//
 // THE HEADING IS THE MODEL'S OWN, so this hoists only the LAST block of the assessment. The assessing
-// skill fixes no heading vocabulary — it asks for sub-headers "where the content divides" and for the
-// read to close on what to do with the name, and the wording is written fresh each run. Matching a list
-// of phrases anywhere in the document would let a mark whose read happens to argue under "Recommendation"
-// in the MIDDLE have that middle lifted to the bottom, handing the client the engine's argument in an
-// order the engine did not write, with nothing going red. A trailing block is the one position where a
-// move cannot reorder what is left. So the phrase list only decides whether the last block is the
-// outcome; anything earlier stays where it was written, and the page renders the assessment whole.
-const OUTCOME_HEADING_RE = /^#{1,6}\s*(?:what to do with it|what happens next|next steps?|recommendations?)\b\s*$/i;
+// skill fixes no heading vocabulary — it asks for sub-headers "where the content divides", and the
+// wording is written fresh each run. Matching a list of phrases anywhere in the document would let a
+// mark whose read happens to argue under "Recommendation" in the MIDDLE have that middle lifted to the
+// bottom, handing the client the engine's argument in an order the engine did not write, with nothing
+// going red. A trailing block is the one position where a move cannot reorder what is left. So the
+// phrase list only decides whether the last block is the outcome; anything earlier stays where it was
+// written, and the page renders the assessment whole.
 export function splitOutcome(assessment) {
   const whole = String(assessment ?? '').trim();
   const lines = whole.split('\n');
   const heads = lines.map((l, i) => [l.trim(), i]).filter(([l]) => /^#{1,6}\s/.test(l));
   const last = heads[heads.length - 1];
-  if (!last || !OUTCOME_HEADING_RE.test(last[0])) return { body: whole, outcome: '' };
+  if (!last || !isNextStepHeading(last[0])) return { body: whole, outcome: '' };
   const outcome = lines.slice(last[1] + 1).join('\n').trim();
   if (!outcome) return { body: whole, outcome: '' };
   return { body: lines.slice(0, last[1]).join('\n').trim(), outcome };

package/driver/register-availability.mjs

@@ -41,7 +41,7 @@
 // CORRECTED 2026-08-11 — THIS PARAGRAPH USED TO SAY "one qid per office … which is the shape
 // joinPlanToBands already has", AND THAT WAS FALSE ABOUT THE COMPILER IT DOCUMENTS. There is no
 // per-office qid. compileRegisterPlan narrows ONE shared `regions` array and hands it to every entry
-// (register-plan.mjs:779 compileRegisterPlan); the unreachable office produces no entry, so no qid, so no band block, so
+// (register-plan.mjs:805 compileRegisterPlan); the unreachable office produces no entry, so no qid, so no band block, so
 // nothing ever reaches joinPlanToBands' deferred bucket — whose only source is a block stamped
 // `error:true && deferred:true` (register-plan.mjs:1317 extendRegisterPlan).
 //

package/driver/register-plan.mjs

@@ -705,12 +705,7 @@ export function excludeHouseElement(manifest, house) {
 
   const lcEl = element.toLowerCase();
   const lcWords = words.map((w) => w.toLowerCase());
-  // A word of the remainder, by word boundary rather than by containment: `includes` would count the
-  // remainder word "on" inside an unrelated mutation and keep a query this exists to drop.
-  const namesRemainder = (v) => {
-    const t = String(v ?? "").toLowerCase();
-    return lcWords.some((w) => new RegExp(`(^|[^\\p{L}\\p{N}])${w.replace(/[.*+?^${}()|[\]\\]/g, "\\$&")}([^\\p{L}\\p{N}]|$)`, "u").test(t));
-  };
+  const namesRemainder = (v) => namesAnyWord(v, lcWords);
 
   // THE DOMINANT WORD OF THE REMAINDER: longest, ties broken by the LAST of them. The lawyer's own
   // phrasing was "the last word alone", and on the matter that produced this the two agree; longest is
@@ -738,11 +733,75 @@ export function excludeHouseElement(manifest, house) {
   // REQUIREMENT 3: the element is still checked ONCE, as a confirmation of the client's own live
   // registrations rather than as a conflict search — so the exclusion is evidenced on the report by a
   // query that ran, not by a sentence saying one would have.
+  // The remainder rides on it so a writer AFTER the compile can apply the same rule (`houseElementOf`).
   const confirmation = { axis: "incumbent-class", predicate: "owner", term: element,
-    expected_kind: "enumerate", provenance: "mark", house_element_confirmation: true };
+    expected_kind: "enumerate", provenance: "mark", house_element_confirmation: true,
+    house_element_remainder: remainder };
   return { manifest: next, confirmation, refused: null };
 }
 
+/**
+ * Does `text` carry any of `words` (lower-case) as a word of its own? By word boundary rather than by
+ * containment: `includes` would count the remainder word "on" inside an unrelated mutation.
+ */
+function namesAnyWord(text, words) {
+  const t = String(text ?? "").toLowerCase();
+  return words.some((w) => new RegExp(`(^|[^\\p{L}\\p{N}])${w.replace(/[.*+?^${}()|[\]\\]/g, "\\$&")}([^\\p{L}\\p{N}]|$)`, "u").test(t));
+}
+
+/**
+ * The house element a plan was compiled without, read off the plan itself, or null.
+ *
+ * WHY THE PLAN CARRIES IT. The compile is not the only writer. After it, the common-law cross-check,
+ * the recall lane, the frame reopen and the jurisdiction candidates fold entries in, and the register
+ * session proposes its own. On the first live run that proposed an exclusion (2026-09-19) the compile
+ * dropped the element and two later writers put it straight back: a contains query from the cross-check
+ * and an exact query the register session proposed, both on the bare element. Those writers hold the
+ * plan and nothing else, so the plan is where the exclusion has to be readable. Its confirmation row
+ * names the element, and the remainder rides beside it because the rule needs both.
+ */
+export function houseElementOf(plan) {
+  const c = (plan?.entries ?? []).find((e) => e?.house_element_confirmation === true);
+  const element = String(c?.term ?? "").trim();
+  if (!element) return null;
+  const remainder = String(c?.house_element_remainder ?? "").trim().toLowerCase();
+  return { element, remainderWords: remainder.split(/\s+/).filter(Boolean) };
+}
+
+/**
+ * Is this term a search on the excluded house element? The compile's own rule (`excludeHouseElement`
+ * keeps a variant only when it names a word of the remainder), applied to a term that arrives after
+ * the compile: a term carrying the element and no word of the remainder is a search on the element,
+ * whether it is the bare element, the element with a suffix, or the element beside other words. A term
+ * carrying a word of the remainder, like the whole mark, is kept, as the compile keeps it.
+ *
+ * A plan frozen before the remainder was recorded knows the element only, and then only the bare
+ * element counts: "carries no word of the remainder" cannot be decided without the remainder.
+ */
+export function isHouseElementTerm(term, house) {
+  if (!house) return false;
+  const t = String(term ?? "").trim().toLowerCase();
+  const el = house.element.toLowerCase();
+  if (t === el || (norm(el) !== "" && norm(t) === norm(el) && formKey(t) === formKey(el))) return true;
+  if (!house.remainderWords.length) return false;
+  const carries = t.includes(el) || (norm(el) !== "" && norm(t).includes(norm(el)));
+  return carries && !namesAnyWord(t, house.remainderWords);
+}
+
+/**
+ * The entry without its house-element terms, or null when none is left. An owner sweep is not mark
+ * text and comes back untouched: the one owner query on the element is the confirmation itself. PURE.
+ */
+export function withoutHouseElementTerms(entry, house) {
+  if (!house || !entry || entry.predicate === "owner") return entry;
+  if (Array.isArray(entry.terms)) {
+    const kept = entry.terms.filter((t) => !isHouseElementTerm(t, house));
+    if (!kept.length) return null;
+    return kept.length === entry.terms.length ? entry : { ...entry, terms: kept };
+  }
+  return isHouseElementTerm(entry.term, house) ? null : entry;
+}
+
 export function compileRegisterPlan({ manifest, job, form = null, skillVersion = "", capabilities = null, unavailableOffices = [], houseElement = null }) {
   // ── AN EXCLUDED ELEMENT'S FORM BAND MUST BE UNREACHABLE, NOT MERELY UNASKED-FOR ─────────────────
   //
@@ -1495,10 +1554,13 @@ export function entryQuestionKey(entry, plan) {
  * an absence, and an absence reported as success is the failure this whole issue is about. Every
  * caller writes them somewhere a reader will meet them.
  *
- * Returns { plan, added: [qid], refused: [{qid, term, issue}] }.
+ * Returns { plan, added: [qid], refused: [{qid, term, issue}], excluded: [qid] } — `excluded` are rows on
+ * the house element the compile set aside, left out quietly (see houseElementOf).
  */
 export function foldSupplementalEntries(plan, entries) {
   const have = new Set(plan.entries.map((e) => e.qid));
+  const house = houseElementOf(plan);
+  const excluded = [];
   // — first qid wins, so the refusal names the row already IN the plan rather than a later
   // arrival. The compiler's own rows are in here too: a supplemental re-proposal of a compiler slice
   // is the case that actually fired on the round in evidence.
@@ -1530,8 +1592,9 @@ export function foldSupplementalEntries(plan, entries) {
   // one identity, which is the fault. Keyed on the qid alone this refused the harmless case too, and
   // the suite's own arm said so.
   const inBatch = new Map();   // qid -> the term that claimed it
-  for (const e of entries ?? []) {
-    if (!e || typeof e.qid !== "string" || !e.qid) continue;
+  for (const offered of entries ?? []) {
+    if (!offered || typeof offered.qid !== "string" || !offered.qid) continue;
+    let e = offered;
     const eTerm = String(e.term ?? e.terms?.[0] ?? "");
     if (inBatch.has(e.qid) && inBatch.get(e.qid) === eTerm) continue;   // the same row twice — one refusal
     if (inBatch.has(e.qid)) {
@@ -1546,6 +1609,12 @@ export function foldSupplementalEntries(plan, entries) {
     inBatch.set(e.qid, eTerm);
     if (have.has(e.qid)) continue;   // already in the PLAN — a re-proposal, expected and quiet
     have.add(e.qid);            // a refused qid is claimed too — the same row twice is one refusal
+    // THE CLIENT'S OWN ELEMENT, SET ASIDE BY THE COMPILE, IS NOT FOLDED BACK IN (see houseElementOf).
+    // QUIET, NOT REFUSED: a refused row renders to the client as an OPEN ask, and this is no unanswered
+    // question. The plan's confirmation row answers it and the report states the exclusion.
+    const kept = withoutHouseElementTerms(e, house);
+    if (!kept) { excluded.push(e.qid); continue; }
+    e = kept;
     const issues = entryTermIssues(e);
     if (issues.length) {
       refused.push({ qid: e.qid, term: String(e.term ?? e.terms?.[0] ?? ""),
@@ -1570,11 +1639,12 @@ export function foldSupplementalEntries(plan, entries) {
     if (key && e.unsupported !== true) asked.set(key, e.qid);   // dedupes the batch too, on the question
     added.push(e);
   }
-  if (!added.length) return { plan, added: [], refused };
+  if (!added.length) return { plan, added: [], refused, excluded };
   return {
     plan: { ...plan, plan_version: (plan.plan_version ?? 1) + 1, entries: [...plan.entries, ...added] },
     added: added.map((e) => e.qid),
     refused,
+    excluded,
   };
 }
 

package/driver/result-noun-fields.mjs

@@ -95,7 +95,9 @@ export const RESULT_NOUN_FIELDS = Object.freeze([
   // writing site like the other two — it is a returned CLASSIFICATION of a checkout, not a field named
   // for a result whose value is what a call returned, so the verdict is unchanged.
   { file: "driver/engine-build.mjs", noun: "outcome", sites: 3, atWriteSite: 0, verdict: "out-of-scope" },
-  { file: "driver/engine/mcp/supplemental.mjs", noun: "executed", sites: 2, atWriteSite: 0, verdict: "out-of-scope" },
+  // Read at the writing site: the third is the reply when every proposal was the house element the
+  // compile set aside — `executed: false` because nothing ran, the same statement as the error reply.
+  { file: "driver/engine/mcp/supplemental.mjs", noun: "executed", sites: 3, atWriteSite: 0, verdict: "out-of-scope" },
   { file: "driver/outbox-backoff.mjs", noun: "outcome", sites: 5, atWriteSite: 0, verdict: "out-of-scope" },
   { file: "driver/portal-service.mjs", noun: "outcome", sites: 2, atWriteSite: 0, verdict: "out-of-scope" },
   { file: "driver/remedy-accounting.mjs", noun: "executed", sites: 1, atWriteSite: 0, verdict: "out-of-scope" },

package/driver/stages-knockout.mjs

@@ -418,7 +418,7 @@ export const KO_STAGES = {
       // The depth rule is not stylistic. `# ` opens a SECTION of the delivered report — parseSections
       // splits on /^# /m and batchSummaryOf terminates on it — so a single hash written here ends the
       // client's summary at that line and drops everything after it, silently, on the entry point.
-      `EVERY mark ALSO carries "assessment": the opening read a reader of THIS MARK'S OWN report meets first, before any table. Write it for a client who ordered this one name and nothing else: what the name is, what the landscape around it looks like, what drives the rating, and what a reader should do with that.`,
+      `EVERY mark ALSO carries "assessment": the opening read a reader of THIS MARK'S OWN report meets first, before any table. Write it for a client who ordered this one name and nothing else: what the name is, what the landscape around it looks like, what drives the rating.`,
       `GIVE IT STRUCTURE A READER CAN SCAN — that is what changed. Sub-headers where the content divides, "- " bullets for the load-bearing points, a blank line between blocks. A sub-header is "## " or "### ". NEVER "# ": one hash opens a section of the report itself, and a summary that opens a section ends there and takes the rest of itself off the client's page. A single sub-header over one unbroken block is not structure — the blocks are what make the length readable, and unstructured length is the complaint this replaces.`,
       `KEEP THE LENGTH. It is still the most useful part of a triage and it is still not rationed. What it now has to be is CONSISTENT: this mark's opening read is the scale of a single-mark report's opening read, and the marks of one batch sit within reach of each other. One assessment several times the size of its siblings is out of family. No word count and none is coming — judge it against the other marks in front of you.`,
       `SYNTHESISE THE SOURCES, DO NOT SHELVE THEM SEPARATELY. Where filings were handed to you for this mark, weigh them in the SAME passage as the marketplace and common-law reading — what the screened field shows, what those filings do to that reading, and what the two together mean for the band. A reader must not be handed one block per source and left to reconcile them.`,

package/driver/suite-census.json

@@ -279,6 +279,12 @@
           "skips": 0,
           "todos": 0
         },
+        "a-demo-stops-when-whatever-started-it-is-gone.test.mjs": {
+          "tests": 3,
+          "asserts": 11,
+          "skips": 0,
+          "todos": 0
+        },
         "a-depth-check-that-read-nothing-is-on-the-investigate-list.test.mjs": {
           "tests": 3,
           "asserts": 8,
@@ -555,6 +561,12 @@
           "skips": 1,
           "todos": 0
         },
+        "a-next-step-the-model-writes-comes-off-at-publish.test.mjs": {
+          "tests": 12,
+          "asserts": 28,
+          "skips": 0,
+          "todos": 0
+        },
         "a-note-the-release-refuses-is-refused-on-its-own-pull-request.test.mjs": {
           "tests": 2,
           "asserts": 3,
@@ -837,6 +849,12 @@
           "skips": 0,
           "todos": 0
         },
+        "a-running-demo-connects-by-its-folder.test.mjs": {
+          "tests": 4,
+          "asserts": 18,
+          "skips": 0,
+          "todos": 0
+        },
         "a-save-that-cannot-commit-says-so.test.mjs": {
           "tests": 4,
           "asserts": 19,
@@ -1827,6 +1845,12 @@
           "skips": 0,
           "todos": 0
         },
+        "dead-names.test.mjs": {
+          "tests": 5,
+          "asserts": 8,
+          "skips": 2,
+          "todos": 0
+        },
         "declared-park-excuses-proof-not-judgment.test.mjs": {
           "tests": 9,
           "asserts": 34,
@@ -2062,8 +2086,8 @@
           "todos": 0
         },
         "doctor-refuses-what-cannot-run.test.mjs": {
-          "tests": 8,
-          "asserts": 20,
+          "tests": 9,
+          "asserts": 22,
           "skips": 0,
           "todos": 0
         },
@@ -2812,8 +2836,8 @@
           "todos": 0
         },
         "knockout-structured-read.test.mjs": {
-          "tests": 14,
-          "asserts": 63,
+          "tests": 12,
+          "asserts": 57,
           "skips": 0,
           "todos": 0
         },
@@ -3004,8 +3028,8 @@
           "todos": 0
         },
         "no-test-writes-inside-the-checkout.test.mjs": {
-          "tests": 17,
-          "asserts": 38,
+          "tests": 20,
+          "asserts": 52,
           "skips": 0,
           "todos": 0
         },
@@ -3305,7 +3329,7 @@
         },
         "portal-local-login.test.mjs": {
           "tests": 28,
-          "asserts": 111,
+          "asserts": 113,
           "skips": 0,
           "todos": 0
         },
@@ -3862,8 +3886,8 @@
           "todos": 0
         },
         "render.test.mjs": {
-          "tests": 161,
-          "asserts": 670,
+          "tests": 162,
+          "asserts": 675,
           "skips": 0,
           "todos": 0
         },
@@ -4486,8 +4510,8 @@
           "todos": 0
         },
         "status-and-stop-see-a-foreground-start.test.mjs": {
-          "tests": 6,
-          "asserts": 25,
+          "tests": 7,
+          "asserts": 30,
           "skips": 0,
           "todos": 0
         },
@@ -4959,6 +4983,12 @@
           "skips": 0,
           "todos": 0
         },
+        "the-house-element-stays-out-of-what-folds-in-later.test.mjs": {
+          "tests": 6,
+          "asserts": 22,
+          "skips": 0,
+          "todos": 0
+        },
         "the-identifier-sweep-fires-on-its-sentinels.test.mjs": {
           "tests": 10,
           "asserts": 36,
@@ -5327,7 +5357,7 @@
         },
         "the-sign-in-door-folds-its-administrator-help.test.mjs": {
           "tests": 5,
-          "asserts": 21,
+          "asserts": 23,
           "skips": 0,
           "todos": 0
         },
@@ -5344,8 +5374,8 @@
           "todos": 0
         },
         "the-summary-carries-structure.test.mjs": {
-          "tests": 13,
-          "asserts": 35,
+          "tests": 14,
+          "asserts": 37,
           "skips": 0,
           "todos": 0
         },
@@ -6034,7 +6064,7 @@
         },
         "root-mcp-json-connects.test.mjs": {
           "tests": 3,
-          "asserts": 13,
+          "asserts": 14,
           "skips": 0,
           "todos": 0
         },
@@ -6446,8 +6476,8 @@
           "todos": 0
         },
         "reportSections.test.ts": {
-          "tests": 9,
-          "asserts": 27,
+          "tests": 13,
+          "asserts": 41,
           "skips": 0,
           "todos": 0
         },

package/driver/verify-knockout.mjs

@@ -29,25 +29,6 @@ const nameKey = (s) => norm(s).toLowerCase().replace(/\s+/g, " ");
 
 // ── Tone guards (the skill's rules, mechanical subset) ───────────────────────────────────────────────
 export const BANNED_TONE_RE = /\b(extremely difficult|most dangerous|massive|enormous)\b/i;
-
-/**
- * A RECOMMENDATION IS A SHAPE, AND THIS SCREEN MAY NOT WRITE ONE (owner, 2026-09-18).
- *
- * The screen states findings and a rating; what to do with the name is the reading lawyer's. Two
- * instructions that asked for a conclusion were cut first, and a re-run then wrote one anyway, under a
- * heading of its own: "Practical next step — <NAME> is not knocked out at this screening depth. Advance
- * it to clearance…". Cutting an instruction stops the engine asking; only a refusal stops the offer.
- *
- * TWO SHAPES, because both reached a reader: a block the writer heads itself, and a closing line that
- * moves the name on. WHAT THIS CANNOT SEE: the same conclusion as ordinary prose — "the remaining work
- * here is a full search" — and no pattern can. It is a floor under the doctrine, never a substitute.
- *
- * The false positives were measured rather than assumed: the degraded note this lane REQUIRES reads
- * "Manual verification recommended" and matches neither, and a register record "proceeding to
- * registration" matches neither — only proceeding *to clearance* does.
- */
-export const RECOMMENDATION_RE = /^[ \t]*(?:[*_]{0,2}|#{1,6}\s*)(?:practical\s+|immediate\s+|suggested\s+)?(?:next steps?|what to do\b|what happens next|recommendations?|our recommendation)/im;
-export const ADVANCE_RE = /\b(?:advance|move|take|send)\s+(?:it|this|the name|[A-Z][A-Z0-9'’-]{2,})\s+(?:on\s+)?(?:to|into|through)\s+(?:a\s+)?(?:full\s+)?clearance\b|\bproceeds?\s+to\s+(?:a\s+)?(?:full\s+)?clearance\b|\bshould\s+(?:proceed|advance|be advanced|move)\b|\bwe\s+recommend\b/i;
 export const QUANT_CLAIM_RE = /(\b\d[\d,.]*\s*(?:M|million|billion|k|thousand)?\s*(?:streams|downloads|copies sold|units sold)\b)|(\$\s?\d[\d,.]*\s*(?:M|million|billion|k)?\s*(?:in\s+)?(?:annual\s+)?(?:revenue|sales))/i;
 
 // ── URL normalization for the receipts gate ──────────────────────────────────────────────────────────
@@ -505,14 +486,6 @@ export const validators = {
       const claim = [prose, c.chunkSummary].filter(Boolean).join("\n").match(REGISTER_CLAIM_RE);
       if (claim)
         return { ok: false, reason: `knockout_register_claim:${m.name}: "${claim[0].trim()}" — this turn cannot see the register lane and must not describe it. The report states register coverage in code, from the run's own count sidecar; a summary that says the registers were not run, above a table of counts that were, is the contradiction this rule closes. Delete the clause` };
-      // THE PER-NAME READ IS SWEPT TOO, and until now it was not: the checks below read the finding
-      // fields, while `assessment` was validated for length and structure alone — which is exactly the
-      // field the conclusion arrived in. Refused HERE so the stage re-asks with the line quoted, rather
-      // than a reader meeting it.
-      const read = [m.assessment, prose].filter(Boolean).join("\n");
-      const recommended = read.match(RECOMMENDATION_RE) ?? read.match(ADVANCE_RE);
-      if (recommended)
-        return { ok: false, reason: `mark "${m.name}": "${recommended[0].trim()}" — this screen states findings and a rating; what to do with the name, and whether it advances, is the reading lawyer's. Delete the sentence: the report's own closing caveat already says what the screen is` };
       const banned = prose.match(BANNED_TONE_RE);
       if (banned) return { ok: false, reason: `mark "${m.name}": banned tone "${banned[0]}" — measured tone only (the band colour carries urgency)` };
       const quant = prose.match(QUANT_CLAIM_RE);

package/mcp-server/CHANGELOG.md

@@ -1,5 +1,9 @@
 # trademark-artifacts-mcp
 
+## 0.3.2-beta.12
+
+No changes in this release.
+
 ## 0.3.2-beta.11
 
 No changes in this release.

package/mcp-server/package.json

@@ -1,6 +1,6 @@
 {
   "name": "trademark-artifacts-mcp",
-  "version": "0.3.2-beta.11",
+  "version": "0.3.2-beta.12",
   "license": "AGPL-3.0-only",
   "private": true,
   "description": "MCP server to interrogate clearotron trademark-clearance runs — list/read artifacts, trace the full decision flow, telemetry/cost, coverage, single-run search, and a gated single-step what-if. Imports the clearotron-driver read-only; touches no driver/template/deploy files.",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "clearotron",
   "type": "module",
-  "version": "0.3.2-beta.11",
+  "version": "0.3.2-beta.12",
   "license": "AGPL-3.0-only",
   "repository": {
     "type": "git",

package/portal-ui/dist/assets/{index-CtvwLCti.css → index-7Lq-dXDV.css}

@@ -254,19 +254,19 @@ html.anon-on [data-anon='mark']:not(.anon-clear) {
   border-bottom: 1px solid var(--border-hairline);
 }
 
-/* THE HEADER'S SECOND ROW: which read you are in, then where you are inside it.
+/* THE HEADER'S LOWER ROWS: which read you are in, then where you are inside it.
    The Reads strip used to sit BELOW this box and the report's own section breadcrumb inside the frame,
    so neither stayed on screen — the frame is sized to its content, which leaves a `position:sticky` bar
    in there pinned to nothing. Both are rows of the pinned header now (owner, 2026-09-18).
-   It scrolls sideways rather than wrapping to a third line: a header that grows taller with the number of
-   sections is a header that eats the document it is heading. */
-.report-nav {
-  display: flex; align-items: center; gap: 10px; margin-top: 9px;
+   THE SECTIONS HAVE A ROW OF THEIR OWN, UNDER THE READS (owner, 2026-09-19). Side by side, sixteen reads
+   wrapped into two ragged columns while the strip floated beside them at mid-height. The reads wrap; the
+   sections scroll sideways rather than wrapping, so the strip stays one line however narrow the screen. */
+.report-nav { display: flex; flex-direction: column; align-items: stretch; gap: 8px; margin-top: 9px; }
+.report-sections {
+  display: flex; align-items: center; gap: 2px;
   overflow-x: auto; scrollbar-width: none;
 }
-.report-nav::-webkit-scrollbar { display: none; }
-.report-nav-sep { flex: none; width: 1px; align-self: stretch; background: var(--border-hairline); }
-.report-sections { display: flex; align-items: center; gap: 2px; }
+.report-sections::-webkit-scrollbar { display: none; }
 .report-section {
   flex: none; display: inline-flex; align-items: center; gap: 7px; white-space: nowrap;
   font: inherit; font-size: 12.5px; font-weight: 600; letter-spacing: .01em;
@@ -277,8 +277,11 @@ html.anon-on [data-anon='mark']:not(.anon-clear) {
 .report-section-dot {
   width: 8px; height: 8px; border-radius: 50%; border: 1.5px solid currentColor; box-sizing: border-box;
 }
+/* PROGRESS: every section reached has a filled dot, the rest stay hollow; the one in view also sits on
+   the sunken pill, so it can be told from the ones behind it. */
+.report-section[data-reached='true'] { color: var(--text-strong); }
+.report-section[data-reached='true'] .report-section-dot { background: var(--accent); border-color: var(--accent); }
 .report-section[aria-current='true'] { color: var(--text-strong); background: var(--surface-sunken); }
-.report-section[aria-current='true'] .report-section-dot { border-color: var(--accent); border-width: 3px; }
 
 /* The breadcrumb above it: one step back as a quiet button, then where the reader is. Compound selectors
    throughout this block, because the button and row rules they adjust are declared later in the file. */