@mjasnikovs/pi-task 0.38.29 → 0.38.31

package/dist/task/question-source.js

@@ -1,36 +1,12 @@
 /**
- * Where the NEXT question comes from — the other half of `question-dialog.ts`.
+ * Where the NEXT question comes from — the other half of `question-dialog.ts`,
+ * which owns the ANSWER side.
  *
- * `question-dialog.ts` unified the ANSWER side of the adaptive dialogs (the picker
- * cards, the reply mapping) and its own docstring makes the argument for doing so:
- * *"It was written three times… the two mirrors were never converted, and they had
- * already drifted apart in three ways… The next edit to any of them is where the
- * bug lands."* The QUESTION side — generate → parse → pick the real question →
- * dedupe → spend one corrective re-prompt → yield or exhaust — was left behind,
- * and it had drifted between the two loops that use the SAME parser on the SAME
- * prompt format (`plan-prompts.ts` says `parseClarifyList` parses it "UNCHANGED";
- * `auto-prompts.ts` specifies the identical shape).
- *
- * The five drifts, all in clarify's favour of being wrong:
- *
- *  1. **Which entry is the question.** `parseClarifyList` pushes an entry for
- *     EVERY numbered line, and the local model writes numbered analysis notes
- *     before the question it was asked for (measured live). `pickQuestion` prefers
- *     the first entry carrying a `SUGGESTED:` line; clarify took `parsed[0]`
- *     blindly, showing the note as the question and losing the recommendation
- *     attached further down.
- *  2. **NONE vs unparseable.** The parser returns `[]` for both. Clarify's
- *     `if (parsed.length === 0) break` ended the whole clarify — and decomposed the
- *     feature with ZERO clarifications — on a formatting slip.
- *  3. **A re-typed sentinel.** `isNoneReply`'s regex was a byte-identical second
- *     copy of the parser's own.
- *  4. **Missing SUGGESTED** bought one corrective re-prompt in plan and none in
- *     clarify, so clarify showed a card-less question.
- *  5. **The deferral guard.** It exists because an accepted "clarify with the user
- *     before proceeding" rode into `/task`'s handoff AS AN AUTHORITATIVE DECISION
- *     and produced a task whose VERIFY asserted no source file had changed.
- *     Clarify's answers ride into the decompose prompt and the AUTO file with
- *     exactly the same authority, and had no guard.
+ * One state machine: generate → parse → pick the real question → dedupe → spend
+ * one corrective re-prompt → yield or exhaust. Two loops drive it, `/task-auto`'s
+ * clarify and `/task-plan`, and they use the SAME parser on the SAME prompt format
+ * — plan-prompts.ts says `parseClarifyList` parses its output UNCHANGED, and
+ * auto-prompts.ts specifies the identical shape.
  *
  * NOT unified here: grill's generation loop. It uses a different parser
  * (`parseGrillQuestions`, which yields bare strings) and has no `SUGGESTED` at
@@ -43,11 +19,9 @@ import { parseClarifyList } from './parsers.js';
 import { DUP_REPROMPT_HINT, isDuplicateQuestion, MAX_DUP_STRIKES } from './question-dedup.js';
 import { stripInlineMarkdown } from './inline-markdown.js';
 /**
- * The cap on distinct questions ONE adaptive dialog may ask.
- *
- * Clarify and plan each declared their own `8`, linked only by a comment saying
- * "matches /task-auto's MAX_CLARIFY_QUESTIONS, for the same reason". They bound
- * the same thing for the same reason; this is that reason, once.
+ * Default cap on distinct questions ONE adaptive dialog may ask. Both live
+ * callers pass their own constant of the same value instead
+ * (MAX_CLARIFY_QUESTIONS, MAX_PLAN_QUESTIONS); this is what an unset `cap` gets.
  */
 export const MAX_DIALOG_QUESTIONS = 8;
 /** True when the reply is the deliberate "nothing left to ask" sentinel, as
@@ -58,13 +32,12 @@ export function isNoneReply(raw) {
 /**
  * Which of the parsed entries is the actual question.
  *
- * `parseClarifyList` turns EVERY numbered line into an entry, and the local model
- * sometimes writes a numbered analysis note or two before the question it was
- * asked for (measured live: the first numbered line was a note like
- * "1. gateDebugWriter in orchestrator.ts — wraps a raw append function"). Taking
- * entry 0 blindly then shows the note as the question and loses the SUGGESTED line
- * attached further down. The prompt requires exactly one SUGGESTED, and the parser
- * attaches it to the entry it follows.
+ * `parseClarifyList` turns EVERY numbered line into an entry, and a model that
+ * writes a numbered analysis note before the question it was asked for produces
+ * more than one. Taking entry 0 blindly then shows the note as the question and
+ * loses the SUGGESTED line attached further down. The prompt requires exactly one
+ * SUGGESTED, and the parser attaches it to the entry it follows, so preferring the
+ * entry that HAS one lands on the real question.
  */
 export function pickQuestion(parsed) {
     return parsed.find(q => q.suggested !== undefined && q.suggested.length > 0) ?? parsed[0];
@@ -98,17 +71,16 @@ export function makeQuestionSource(deps) {
             const parsed = parseClarifyList(raw);
             if (parsed.length === 0) {
                 // `[]` means BOTH "deliberate NONE" and "could not parse". Ending
-                // the dialog on the second is how a formatting slip becomes a
-                // feature decomposed with zero clarifications.
+                // the dialog on the second would decompose the feature with zero
+                // clarifications because of one formatting slip.
                 if (!isNoneReply(raw) && hint === null) {
                     deps.log?.('unparseable question reply — one format re-prompt');
                     hint = deps.formatHint;
                     continue;
                 }
-                // A SECOND unreadable reply is not a NONE. Recording it as one is
-                // the very conflation this module exists to end — it would put
-                // "model has no further questions" on the trail for a run where
-                // the model produced two malformed replies.
+                // A SECOND unreadable reply is not a NONE: the caller is told
+                // 'unparseable', so nothing writes "model has no further
+                // questions" on a run that produced two malformed replies.
                 if (!isNoneReply(raw)) {
                     deps.log?.('second unparseable reply — giving up on this draw');
                     hint = null;
@@ -163,8 +135,7 @@ export function makeQuestionSource(deps) {
      *
      * `/task-plan` lets the user ask the model a question or state a decision
      * mid-session; that is new context, so a generator that had struck out may now
-     * have something novel. The plan loop reset its own `dupStrikes` at two sites
-     * for exactly this; the budget lives here now, so the reset has to.
+     * have something novel.
      */
     function reopen() {
         dupStrikes = 0;

package/dist/task/refuted-constraint.d.ts

@@ -1,43 +1,22 @@
 /**
  * A refutation is a DELETION, not an addition.
  *
- * THE LEAD (mx5 run 19, `~/hub/mx5 @ dfbdd6f`, TASK_0001). Refine invented a
- * dependency the design explicitly rules out; the run's own research said so, in
- * writing, in the same file; the composed spec then turned the invention into a
- * capitalised prohibition against the design's own API:
+ * The failure this closes: refine writes a dependency into CONSTRAINTS that the
+ * design rules out, the run's own research says so in its CONTEXT section, and
+ * compose reads both and hardens the invention into a prohibition against the API
+ * the repo actually uses. An appended correction loses to the text it contradicts,
+ * because CONSTRAINTS is what the implementer is told is authoritative.
  *
- *   :21   refine CONSTRAINTS   "Add only new entries the task requires (e.g.,
- *                              `hono`, `bun-sql`-equivalent, …, `argon2`, …)"
- *   :92   research CONTEXT     "Password hashing uses `Bun.password` (built-in
- *                              argon2id) — no external `argon2` or
- *                              `@node-rs/argon2` dependency needed despite the
- *                              task's mention of it."
- *   :132  spec CONSTRAINTS     "Do NOT use built-in `Bun.password` for hashing —
- *                              the refined task explicitly requires `argon2`."
- *
- * `argon2@^0.41.0` shipped as a runtime dependency of a repo that never imports
- * it, locked in by a VERIFY assertion, next to a spec telling the next
- * implementer not to use `Bun.sql` — the API the whole data layer is built on.
- *
- * This is `memory/phantom-correction-additive-not-subtractive.md` at spec scale:
- * the correction was APPENDED to research CONTEXT while the wrong text stayed in
- * refine's CONSTRAINTS, and CONSTRAINTS is what the implementer is told is
- * authoritative.
- *
- * THE LEVER. Deterministic detection, then a scoped removal, BEFORE compose sees
- * the refined task. Never a model rewrite: every model-rewrite lever at this seam
- * has resolved contradictions by deleting the AUTHORITATIVE side
- * (`memory/owned-freeze-critique-lever-refuted.md`, 11/20). This pass can only
- * delete a refine-invented token, and can never touch an owned line.
+ * So the correction is SUBTRACTIVE, and it runs before compose sees the refined
+ * task (phases.ts `composeCarry`). Never a model rewrite: this pass can only
+ * delete a refine-invented token, and it skips any line carrying the
+ * owned-requirement stamp.
  *
  * The match is lexical, never semantic: a research CONTEXT bullet refutes a
  * refine constraint when it carries one of a closed set of negation-of-need
  * shapes AROUND a backticked token, and that same token appears backticked in a
  * refine CONSTRAINTS line. Both sides are already separate strings in the task
  * file.
- *
- * STEP 0 (`scripts/refuted-constraint-baserate.ts`) measured the closed set over
- * every recorded task file in the corpus before any of it was wired.
  */
 export type Refutation = {
     /** The token as it appears inside the backticks, e.g. `argon2`. */
@@ -77,6 +56,7 @@ export type RefutationResult = {
 };
 /**
  * Apply every detected refutation to the refined prompt. Purely subtractive: the
- * result is always a character subsequence of the input (`inv-no-line-invention`).
+ * result is always a character subsequence of the input, which
+ * refuted-constraint.test.ts asserts under `inv-no-line-invention`.
  */
 export declare function applyRefutations(refined: string, research: string): RefutationResult;

package/dist/task/refuted-constraint.js

@@ -1,43 +1,22 @@
 /**
  * A refutation is a DELETION, not an addition.
  *
- * THE LEAD (mx5 run 19, `~/hub/mx5 @ dfbdd6f`, TASK_0001). Refine invented a
- * dependency the design explicitly rules out; the run's own research said so, in
- * writing, in the same file; the composed spec then turned the invention into a
- * capitalised prohibition against the design's own API:
+ * The failure this closes: refine writes a dependency into CONSTRAINTS that the
+ * design rules out, the run's own research says so in its CONTEXT section, and
+ * compose reads both and hardens the invention into a prohibition against the API
+ * the repo actually uses. An appended correction loses to the text it contradicts,
+ * because CONSTRAINTS is what the implementer is told is authoritative.
  *
- *   :21   refine CONSTRAINTS   "Add only new entries the task requires (e.g.,
- *                              `hono`, `bun-sql`-equivalent, …, `argon2`, …)"
- *   :92   research CONTEXT     "Password hashing uses `Bun.password` (built-in
- *                              argon2id) — no external `argon2` or
- *                              `@node-rs/argon2` dependency needed despite the
- *                              task's mention of it."
- *   :132  spec CONSTRAINTS     "Do NOT use built-in `Bun.password` for hashing —
- *                              the refined task explicitly requires `argon2`."
- *
- * `argon2@^0.41.0` shipped as a runtime dependency of a repo that never imports
- * it, locked in by a VERIFY assertion, next to a spec telling the next
- * implementer not to use `Bun.sql` — the API the whole data layer is built on.
- *
- * This is `memory/phantom-correction-additive-not-subtractive.md` at spec scale:
- * the correction was APPENDED to research CONTEXT while the wrong text stayed in
- * refine's CONSTRAINTS, and CONSTRAINTS is what the implementer is told is
- * authoritative.
- *
- * THE LEVER. Deterministic detection, then a scoped removal, BEFORE compose sees
- * the refined task. Never a model rewrite: every model-rewrite lever at this seam
- * has resolved contradictions by deleting the AUTHORITATIVE side
- * (`memory/owned-freeze-critique-lever-refuted.md`, 11/20). This pass can only
- * delete a refine-invented token, and can never touch an owned line.
+ * So the correction is SUBTRACTIVE, and it runs before compose sees the refined
+ * task (phases.ts `composeCarry`). Never a model rewrite: this pass can only
+ * delete a refine-invented token, and it skips any line carrying the
+ * owned-requirement stamp.
  *
  * The match is lexical, never semantic: a research CONTEXT bullet refutes a
  * refine constraint when it carries one of a closed set of negation-of-need
  * shapes AROUND a backticked token, and that same token appears backticked in a
  * refine CONSTRAINTS line. Both sides are already separate strings in the task
  * file.
- *
- * STEP 0 (`scripts/refuted-constraint-baserate.ts`) measured the closed set over
- * every recorded task file in the corpus before any of it was wired.
  */
 /** Bare ALL-CAPS section header, the boundary convention used across the
  *  refined prompt and every research section. */
@@ -53,9 +32,10 @@ const TOKEN_LIST = `${TOKEN}(?:(?:\\s*,\\s*|\\s+or\\s+|\\s+and\\s+)${TOKEN})*`;
  * ("no `@node-rs/argon2` dependency — we use `argon2`") can only ever refute the
  * one inside the phrase.
  *
- * Kept deliberately small. `inv-precision` is a FAIL of the whole task on one
- * false drop, so a shape earns its place here only by surviving a hand-read of
- * every corpus hit it produces.
+ * Kept deliberately small. One false drop silently removes a real constraint, so
+ * a shape belongs here only when it cannot be read as anything but a claim that
+ * the dependency is unnecessary. refuted-constraint.test.ts pins the rejected
+ * shapes under `inv-precision`.
  */
 const NEGATIONS = [
     {
@@ -71,29 +51,25 @@ const NEGATIONS = [
     {
         // "no `argon2` dependency is needed".
         //
-        // The trailing need-negation is NOT optional, and STEP 0 is why. The
-        // first cut of this pattern was the bare "no `X` dependency", and it
-        // fired 300 times in 306 corpus hits — every one of them on a
-        // MANIFEST-STATE bullet that says the exact opposite of a refutation:
+        // The trailing need-negation is NOT optional. Without it the pattern is
+        // the bare "no `X` dependency", which matches MANIFEST-STATE bullets that
+        // say the exact opposite of a refutation:
         //
         //   "`package.json` currently lists no `hono` or `@hono/zod-validator`
-        //    dependencies; they MUST BE ADDED at versions 4.12.27 and 0.8.0"
+        //    dependencies; they MUST BE ADDED"
         //   "`package.json` has … and no `sharp` dependency — MUST ADD `sharp`
         //    as devDependency"
         //
-        // Dropping on that signal mutilated real constraints ("use  with the
-        // shared `loginSchema`"). "The repo does not have X yet" is a fact about
-        // the tree; "X is not needed" is a claim about the task. Only the second
-        // one refutes anything.
+        // "The repo does not have X yet" is a fact about the tree; "X is not
+        // needed" is a claim about the task. Only the second refutes anything.
         name: 'no-dep-needed',
         re: new RegExp(`\\bno\\s+(${TOKEN_LIST})\\s+dependenc(?:y|ies)\\s+(?:is\\s+|are\\s+)?(?:needed|required|necessary)\\b`, 'i')
     },
     // The two shapes below name no dependency noun of their own, so they carry a
-    // DEP_WORD guard. STEP 0's near-miss census is the reason: "does not require"
-    // appears in 412 corpus CONTEXT bullets, and the shape is overwhelmingly
-    // prose about behaviour, not dependencies — "the `GET /api/listings`
-    // endpoint does NOT require authentication for the `mine` filter". Token
-    // adjacency alone would eventually reach a backticked API expression there.
+    // DEP_WORD guard. "does not require" is mostly prose about behaviour, not
+    // dependencies — "the `GET /api/listings` endpoint does NOT require
+    // authentication for the `mine` filter" — and token adjacency alone would
+    // eventually reach a backticked API expression inside such a bullet.
     {
         // "`argon2` is not needed" / "`argon2` and `sharp` are not required"
         name: 'not-needed',
@@ -109,9 +85,8 @@ const NEGATIONS = [
 ];
 /** The claim has to be ABOUT a dependency for a dependency to be dropped. */
 const DEP_WORD = /\bdependenc(?:y|ies)\b|\bnpm\b|\bpackages?\b|\bdevDependenc(?:y|ies)\b/i;
-/** The owned-requirement stamp (requirements.ts:813). A line carrying it is a
- *  design-sourced obligation and is NEVER refutable by research — this is the
- *  guard that keeps this pass out of nexttask 2's failure mode. */
+/** The owned-requirement stamp requirements.ts writes onto every design-sourced
+ *  obligation. A line carrying it is NEVER refutable by research. */
 const OWNED_MARKER = 'owned requirement from the source design';
 /** Section body between a bare ALL-CAPS header and the next one (or EOF). */
 export function extractCapsSection(text, heading) {
@@ -253,7 +228,8 @@ export function dropToken(line, token) {
 }
 /**
  * Apply every detected refutation to the refined prompt. Purely subtractive: the
- * result is always a character subsequence of the input (`inv-no-line-invention`).
+ * result is always a character subsequence of the input, which
+ * refuted-constraint.test.ts asserts under `inv-no-line-invention`.
  */
 export function applyRefutations(refined, research) {
     const refutations = detectRefutations(refined, research);

package/dist/task/regenerable-artifacts.d.ts

@@ -1,14 +1,10 @@
 /**
  * The one place that knows which repo paths are regenerable machine OUTPUT.
  *
- * This module exists because the knowledge was in exactly one module and two
- * others needed it (mx5 run 20). `git-state-guard.ts` knew `test-results/` was
- * regenerable and used it for VERDICT decisions only; `write-guard.ts`'s deletion
- * guard did not, so it rejected two whole fix attempts over three Playwright
- * failure screenshots — taking each attempt's real `src/client/api.test.tsx`
- * repair with them — and `auto-commit.ts` did not, so its blind `git add -A` is
- * how the screenshots became tracked in the first place. Three modules, one fact,
- * shared with neither of the two that needed it. Import from here; do not copy.
+ * Three call sites need the fact and all three import it from here rather than
+ * keeping a copy: `git-state-guard.ts` (verdicts), `write-guard.ts` (whether a
+ * deletion rejects the whole fix attempt) and `auto-commit.ts` (what the commit
+ * may newly track). Import from here; do not copy.
  *
  * TWO LISTS, and the split between them is the whole point.
  *
@@ -21,28 +17,12 @@
  * deliverable, so it is narrower, and `dist/`, `build/`, `.next/`, `.turbo/` and
  * `.svelte-kit/` are deliberately NOT in it.
  *
- * MEASURED over 269 git work trees under ~/hub, ~/tmp, ~/.cache
- * (`scripts/tracked-artifact-baserate.ts`, 2026-08-07):
- *
- *     trees tracking any artifact path      33   (33 of 33 have .pi-tasks)
- *     test-results/                         33 trees / 33 files
- *     .last-run.json                        33 trees / 33 files  ← the SAME 33 files
- *     dist/, build/, .next/, .turbo/, .svelte-kit/, playwright-report/,
- *     coverage/, .nyc_output/, *.tsbuildinfo      0 trees
- *
- * So `test-results/` and `.last-run.json` are exempt on MEASUREMENT — they are the
- * only artifact paths this corpus tracks at all, and the one real episode is
- * exactly a tracked `test-results/` deletion. `playwright-report/`, `coverage/`,
- * `.nyc_output/` and `*.tsbuildinfo` are exempt BY CONSTRUCTION with zero corpus
- * evidence either way: none of the four has a hand-authored form, so there is no
- * version of them that is a deliverable. `dist/` and its family have exactly the
- * hand-authored form the other six lack — a published package's `dist/` IS the
- * shipped artifact — and with 0 tracked instances here the exemption would never
- * fire anyway, so it would buy nothing while carrying that risk.
- *
- * 32 of the 33 trees are one A/B harness's delivery trees built from a single mx5
- * DESIGN/PROJECT.md: 32 independent RUNS of one project shape, which is evidence
- * of reproducibility and not of breadth. The 33rd is mx5 itself.
+ * The line between the two lists is whether the path has a HAND-AUTHORED form.
+ * `test-results/`, `playwright-report/`, `coverage/`, `.nyc_output/`,
+ * `.last-run.json` and `*.tsbuildinfo` have none — no version of them is
+ * somebody's deliverable — so deleting one can never destroy work. `dist/` and
+ * its family do: a published package's `dist/` IS the shipped artifact, so a
+ * delete there can.
  */
 /** Directory prefixes and file names that are regenerable test/build output. */
 export declare const REGENERABLE_ARTIFACT_PATTERNS: readonly RegExp[];
@@ -54,7 +34,8 @@ export declare const REGENERABLE_ARTIFACT_PATTERNS: readonly RegExp[];
  * `.svelte-kit/` — see the header.
  */
 export declare const DELETION_EXEMPT_ARTIFACT_PATTERNS: readonly RegExp[];
-/** Human-readable form of the exempt list, for trail lines and pathspecs. */
+/** Human-readable form of the exempt list. Nothing in this repo reads it today;
+ *  the guards go through {@link isDeletionExemptArtifact}. */
 export declare const DELETION_EXEMPT_ARTIFACT_GLOBS: readonly string[];
 /** Is this path regenerable machine output, for VERDICT purposes? */
 export declare function isRegenerableArtifact(relPath: string): boolean;

package/dist/task/regenerable-artifacts.js

@@ -1,14 +1,10 @@
 /**
  * The one place that knows which repo paths are regenerable machine OUTPUT.
  *
- * This module exists because the knowledge was in exactly one module and two
- * others needed it (mx5 run 20). `git-state-guard.ts` knew `test-results/` was
- * regenerable and used it for VERDICT decisions only; `write-guard.ts`'s deletion
- * guard did not, so it rejected two whole fix attempts over three Playwright
- * failure screenshots — taking each attempt's real `src/client/api.test.tsx`
- * repair with them — and `auto-commit.ts` did not, so its blind `git add -A` is
- * how the screenshots became tracked in the first place. Three modules, one fact,
- * shared with neither of the two that needed it. Import from here; do not copy.
+ * Three call sites need the fact and all three import it from here rather than
+ * keeping a copy: `git-state-guard.ts` (verdicts), `write-guard.ts` (whether a
+ * deletion rejects the whole fix attempt) and `auto-commit.ts` (what the commit
+ * may newly track). Import from here; do not copy.
  *
  * TWO LISTS, and the split between them is the whole point.
  *
@@ -21,28 +17,12 @@
  * deliverable, so it is narrower, and `dist/`, `build/`, `.next/`, `.turbo/` and
  * `.svelte-kit/` are deliberately NOT in it.
  *
- * MEASURED over 269 git work trees under ~/hub, ~/tmp, ~/.cache
- * (`scripts/tracked-artifact-baserate.ts`, 2026-08-07):
- *
- *     trees tracking any artifact path      33   (33 of 33 have .pi-tasks)
- *     test-results/                         33 trees / 33 files
- *     .last-run.json                        33 trees / 33 files  ← the SAME 33 files
- *     dist/, build/, .next/, .turbo/, .svelte-kit/, playwright-report/,
- *     coverage/, .nyc_output/, *.tsbuildinfo      0 trees
- *
- * So `test-results/` and `.last-run.json` are exempt on MEASUREMENT — they are the
- * only artifact paths this corpus tracks at all, and the one real episode is
- * exactly a tracked `test-results/` deletion. `playwright-report/`, `coverage/`,
- * `.nyc_output/` and `*.tsbuildinfo` are exempt BY CONSTRUCTION with zero corpus
- * evidence either way: none of the four has a hand-authored form, so there is no
- * version of them that is a deliverable. `dist/` and its family have exactly the
- * hand-authored form the other six lack — a published package's `dist/` IS the
- * shipped artifact — and with 0 tracked instances here the exemption would never
- * fire anyway, so it would buy nothing while carrying that risk.
- *
- * 32 of the 33 trees are one A/B harness's delivery trees built from a single mx5
- * DESIGN/PROJECT.md: 32 independent RUNS of one project shape, which is evidence
- * of reproducibility and not of breadth. The 33rd is mx5 itself.
+ * The line between the two lists is whether the path has a HAND-AUTHORED form.
+ * `test-results/`, `playwright-report/`, `coverage/`, `.nyc_output/`,
+ * `.last-run.json` and `*.tsbuildinfo` have none — no version of them is
+ * somebody's deliverable — so deleting one can never destroy work. `dist/` and
+ * its family do: a published package's `dist/` IS the shipped artifact, so a
+ * delete there can.
  */
 /** Directory prefixes and file names that are regenerable test/build output. */
 export const REGENERABLE_ARTIFACT_PATTERNS = [
@@ -62,7 +42,8 @@ export const DELETION_EXEMPT_ARTIFACT_PATTERNS = [
     /(?:^|\/)\.last-run\.json$/,
     /\.tsbuildinfo$/
 ];
-/** Human-readable form of the exempt list, for trail lines and pathspecs. */
+/** Human-readable form of the exempt list. Nothing in this repo reads it today;
+ *  the guards go through {@link isDeletionExemptArtifact}. */
 export const DELETION_EXEMPT_ARTIFACT_GLOBS = [
     'test-results/',
     'playwright-report/',

package/dist/task/render-check.d.ts

@@ -10,12 +10,10 @@ export type RenderOutcome = {
 };
 /**
  * The newest Playwright-cache Chromium, if any — the HEADLESS SHELL preferred over
- * the full build. Found, never installed: the cache exists on any box that ever ran
- * Playwright browsers (the mx5-class projects install it as their own test
- * dependency). The headless shell is purpose-built for `--dump-dom` and returns
- * promptly on a network URL where the full system chromium can stall under a
- * virtual-time budget (validated live on this box: shell exits 0 in ~1s, full
- * chromium times out at 30s on the same http:// URL).
+ * the full build. Found, never installed: the cache exists on any box that ever
+ * ran Playwright browsers, which many projects install as a test dependency. The
+ * headless shell is preferred because it is purpose-built for exactly this — one
+ * `--dump-dom` and exit — with no browser UI to bring up.
  */
 export declare function playwrightCachedChromium(): string | null;
 /**
@@ -37,27 +35,18 @@ export declare function judgeRenderedDom(html: string): {
 /**
  * The page's console output, as captured while the DOM was being rendered.
  *
- * MEASURED on this box (2026-08-14) against the shipped mx5 run-21 bundle, both
- * binaries the probe can discover:
- *
- *     /usr/bin/chromium              --dump-dom alone → 0 bytes of stderr
- *                                    + --enable-logging=stderr --v=0 → 2 CONSOLE
- *                                      lines, one of them the cause
- *     playwright chrome-headless-shell
- *                                    → the 2 CONSOLE lines either way
- *
- * and in ALL FOUR arms stdout was byte-identical at 318 bytes, so the DOM the
- * judge reads is untouched by the flags.
+ * `--enable-logging=stderr --v=0` is what routes the page's console to stderr.
+ * The DOM the judge reads is untouched by those flags: with and without them,
+ * `--dump-dom` writes byte-identical stdout on both binaries this probe can
+ * discover.
  */
 export declare function parseConsoleLines(stderr: string): string[];
 /**
  * Append the console output to a FAIL detail — and to nothing else.
  *
- * WHY (nexttask 19B; the class 18A opened for repo-health). Run 21's fix child was
- * told "the body is EMPTY" and nothing more. It spent 45 minutes on tests, bundler
- * config and static serving, read the offending line twice, and moved on. The
- * probe was holding the answer the whole time: `Uncaught ReferenceError: process
- * is not defined`, at main.js:322.
+ * Without it the fix child is told "the body is EMPTY" and nothing more, while the
+ * probe was holding the cause the whole time: the page's own
+ * `Uncaught ReferenceError`, with the source file and line Chrome already printed.
  *
  * Strictly additive by construction: it takes an existing FAIL detail and returns
  * it with text appended. It cannot turn a PASS into a FAIL, cannot reach