@mjasnikovs/pi-task 0.38.29 → 0.38.31

package/dist/config/reasoning.js

@@ -13,16 +13,13 @@ export const REASONING_GROUPS = [
 ];
 export const REASONING_MODES = ['default', 'on', 'off', 'custom'];
 /**
- * The settings offered in /task-config: `inherit` plus pi's OWN cycle
- * (`THINKING_LEVELS` in pi-coding-agent's agent-session).
+ * The settings offered in /task-config: `inherit` plus the standard part of pi's
+ * own thinking cycle.
  *
- * `xhigh` and `max` are DELIBERATELY ABSENT. pi treats an absent
- * `thinkingLevelMap` entry as "supported" for the standard levels but requires a
- * declared entry for the extended two (pi-ai `getSupportedThinkingLevels`), so a
- * model with no map would receive the raw string — and Qwen3.8's chat template
- * answers an unknown effort with HTTP 500, not a clamp. Offering a level that pi's
- * own UI does not is how you ship a `--thinking` that hard-fails on some models.
- * This machine already reaches xhigh through `"high": "xhigh"` in its map.
+ * `xhigh` and `max` are DELIBERATELY ABSENT. pi-ai's `getSupportedThinkingLevels`
+ * accepts the standard levels for any reasoning model, but offers `xhigh` and
+ * `max` only when the model declares them in its `thinkingLevelMap`. Offering
+ * them here would put a level in this UI that pi's own UI may not have.
  */
 export const REASONING_SETTINGS = [
     'inherit',
@@ -32,687 +29,36 @@ export const REASONING_SETTINGS = [
     'medium',
     'high'
 ];
-/**
- * The level mode `on` uses, and the treatment arm of the A/B that fills in
- * {@link DEFAULT_REASONING_TABLE}. ONE constant so the shipped config and the
- * measurement behind it can never drift apart.
- */
+/** The level mode `on` uses. */
 export const REASONING_ON_LEVEL = 'medium';
 /**
  * The per-group table used by mode `default`.
  *
- * A cell is `inherit` until it has been MEASURED, and then it names a level.
- * Every non-`inherit` cell here must be a live A/B result
- * (scripts/live-reasoning-group-ab.ts, n>=20 per arm, arms `off` vs
- * {@link REASONING_ON_LEVEL}) carrying its date, model, counts and RUNG in the
- * comment beside it. A cell filled in from intuition is WORSE than `inherit`:
- * `inherit` is honest about knowing nothing, while a wrong cell is a
- * measurement nobody took, wearing the authority of a default.
- *
- * THE RUNG IS PART OF THE RESULT, so read it before trusting a cell. The
- * harness returns a two-way verdict — `off` or {@link REASONING_ON_LEVEL},
- * never a tie — down a three-rung ladder: rung 1 a significant quality
- * difference, rung 2 quality level and a significant speed difference, rung 3
- * nothing separated the arms and the cheaper level carries it by a stated
- * prior. A rung-3 cell is a DECISION, not a finding: it says "no reason found
- * to pay for thinking", not "thinking was shown not to help". At n=20/arm the
- * run is only powered for large effects, so rung 3 is the common outcome and
- * an absent effect and an undetected one look identical from here.
- *
- * NOTHING IS ALREADY ON THE RECORD, and the belief that something was is worth
- * writing down. This docstring used to say magicknumbers.md had measured the
- * decompose child "with one knob, `enable_thinking` — off answered 1/10, on
- * answered 8/8", and treated that as the split the A/B had to reproduce.
- *
- * VERIFIED 2026-08-27: the string "8/8" does not appear in magicknumbers.md, and
- * never has (`git log -S`; the phrase was introduced by THIS file's own commit,
- * `0b91f71`). What that page records is
- *
- *     "Measured, captured decompose request, REASONING OFF, n=10 per cell:
- *      1/10 → 7/10 (stall detector) → 8/9 (all three)."
- *
- * — a ladder over THREE GUARDS at CONSTANT reasoning off, from `fea7bbb`. Both
- * endpoints are the same arm. `enable_thinking` is not its knob and never was,
- * and the "8/8" is a misread of the ladder's last cell, `8/9`.
- *
- * So no reasoning effect on `planning` had ever been measured, and the 10/10 vs
- * 10/10 read on the current tree was not a contradiction of a prior result — it
- * was the only reading there had ever been. The controls that page DOES record
- * (Qwen3.6-27B 10/10, Gemma4-12B 10/10) are likewise reasoning off, so they say
- * nothing about a cell flipping by model either.
- *
- * The `planning` cell below is the FIRST measured reading of that knob, taken
- * 2026-08-27 on a citation-fidelity axis built for it. It is also the first cell
- * that is not `off`.
+ * `inherit` says nothing was decided for that group and the child keeps the
+ * host's level. Any other value is a decision this project made for that
+ * group's job, and `/task-config` mode `custom` overrides all of it.
  */
 export const DEFAULT_REASONING_TABLE = {
-    // A/B 2026-08-26, Qwen3.8-27B-NVFP4-MTP-VERY-HIGH.gguf (llama.cpp
-    // b10620-0f3b51e03), scripts/live-reasoning-group-ab.ts, n=12/arm over 12
-    // distinct mx5 tasks. off 10/12 vs medium 11/12 (p=1.0000); neither arm
-    // failed to answer. Wall clock, PAIRED by stimulus over the 10 pairs usable
-    // in both arms: p=0.7090, mean off 79.4s vs medium 59.3s.
-    // off real+edited-named 95% CI [0.55, 0.95].
-    // RUNG 3 — a DECISION, not a finding. Nothing separated the arms on either
-    // axis, and off carries it by the stated prior: thinking that buys nothing
-    // measurable is not worth its tokens. At 12 pairs an absent effect and an
-    // undetected one look the same from here. Ledger: ledger-research.jsonl.
-    //
-    // THE AXIS IS THE CONJUNCTION, built for this run: every path the answer
-    // names is real AND every pre-existing file the task edited is named
-    // (`filesAnswered`, scripts/reasoning-ab-files-truth.ts). Recall truth is
-    // the shipped tree, not the recorded answer. Screened offline: restricted
-    // to pre-existing files the recorded answers score 86.6% (71/82 paths, 29
-    // of 38 tasks perfect); counting CREATED files instead drops them to 49.0%
-    // and the CHECK loses, so a file that does not exist yet is not truth.
-    // It is NOT saturated here — 10/12 and 11/12, with genuine judgement errors
-    // in both arms — so the clock was allowed to decide and declined to.
-    //
-    // THE STIMULI ARE HALF THE AXIS. The superseded precision-only run
-    // (ledger-research.PRECISION-ONLY-10rep.jsonl, `--axis precision` to
-    // reproduce) tied 10/10 on TASK_0002..0012, the greenfield head of the mx5
-    // run — SEVEN OF THOSE TEN EDIT NO PRE-EXISTING FILE AT ALL, so it measured
-    // recall where recall does not exist. `filesRecallStimuli` screens for it;
-    // these 12 tasks each edit >=2 pre-existing files. That ledger CANNOT be
-    // rescored onto this axis and the rescorer abstains rather than return a
-    // number.
-    //
-    // INSTRUMENT NOTE, because this cell read `off 8/12` before it. `filesPaths`
-    // split an entry on TWO spaces, which is what the prompt specifies and what
-    // all 470 recorded paths use. Three live `off` trials wrote
-    // `src/client/main.tsx: App root` — one space after a colon — so the
-    // description was taken as part of the path and TASK_0053 scored 0/19 with
-    // all 19 paths real. Fixed by `COLON_ENTRY`; rescored from stored text with
-    // no GPU, 2 of 24 trials changed side, and the known-good answer is
-    // unmoved (53/56 whole-corpus precision, identical path counts). This is
-    // [[ab-scorer-must-see-the-same-input]] a second time in one function.
-    //
-    // THE CONFOUND THE PRECISION RUN EXPOSED IS STILL VISIBLE and still points
-    // the other way: off named 212 real paths to medium's 153, while medium
-    // named 27/27 edited files to off's 26/27. Off says more and is slower for
-    // it. The conjunction was built so that neither half can be gamed alone,
-    // and on these numbers it separates neither arm.
-    //
-    // AXIS RE-AUDITED 2026-08-27, after planning's adjudicator turned out to
-    // have four bugs. One more was found here and it is the SAME-INPUT rule
-    // broken a third time: `filesPaths` read the child's whole raw turn, while
-    // the SCREEN sliced the recorded `## research` down to its FILES block
-    // precisely because APIS is symbols and would score as 100% invented. One
-    // `off` trial emitted its own `APIS` heading despite the prompt's "No other
-    // sections", and three symbols under it — `cn` and two `--*` token lists —
-    // were counted as invented paths, failing a trial whose FILES block was
-    // 20/20 real. The slice now lives in `filesPaths`, where both callers reach
-    // it. The cell is UNCHANGED: that trial still fails, on a genuine recall
-    // miss (`src/client/types.d.ts`), and the counts are identical.
-    // The other two failures were checked by hand and are genuine — both arms
-    // put `AdminPage.spec.tsx` / `.story.tsx` under `src/client/routes/` when
-    // they ship under `src/client/pages/`, a wrong-directory prediction made
-    // from a real sibling.
-    //
-    // MEASURED UNDER THE SERVER'S GLOBAL SAMPLER, which is the THINKING preset,
-    // so the `off` arm decodes on sampling tuned for the `on` arm. That is the
-    // regime this machine really runs pi-task in, so the result is
-    // ecologically valid — it is NOT a clean comparison.
-    //
-    // OVERRIDDEN TO `medium` BY USER DECISION, 2026-08-27. THIS IS NOT A NEW
-    // MEASUREMENT — the trials above are unchanged and still say the arms tied.
-    // What changed is the prior. Rung 3 says "no reason found to pay for
-    // thinking"; it does not say thinking is worthless, and at n=12 an absent
-    // effect and an undetected one look identical.
-    //
-    // WHAT THE SAME LEDGER SAYS ABOUT THE CLOCK, re-read for this decision:
-    // medium is the FASTER arm on the mean, 62.9s vs 105.6s over the 12 paired
-    // stimuli (median 51.7s vs 87.7s), and it is faster on 6 of 12 by 1-265s
-    // while slower on 6 by 0-43s. The mean gap is entirely `off`'s TAIL: off's
-    // two slowest trials are 289s and 367s, medium's slowest is 131s. So the
-    // typical trial is a coin flip worth under a minute and the difference the
-    // arms actually have is in the tail.
-    //
-    // AND THE TAIL IS THE PATHOLOGY THIS CHANGE IS AIMED AT. mx5-n 2026-08-27:
-    // 40.7 of the research phase's 81.4 wall-clock minutes were thrown away on
-    // restarts, all of them in `worker:tooling` and `worker:context` — `files`
-    // and `apis` never restarted once. The worst was 550 tool calls over 20
-    // distinct files in 20 minutes for 25s of useful work.
-    //
-    // THE HONEST LIMIT OF THIS DECISION: no axis in
-    // scripts/live-reasoning-group-ab.ts scores tool-call count or repetition —
-    // the Trial record has no such field and RunWorkerResult exposes no count —
-    // so the ledger CANNOT say whether thinking prevents the wander. It was
-    // never asked. And the ledger's stimuli are the FILES worker, not the two
-    // that looped. Anyone flipping this back should note that the evidence for
-    // `off` is equally silent on the question.
-    //
-    // The structural fix for the wander shipped separately and does not depend
-    // on this cell: StallDetector is now wired into runWorker (it was in phase
-    // children only), so a rotation is killed ~8 calls into its second lap
-    // rather than at the 20-minute ceiling.
     research: 'medium',
-    // ── THE FOUR RESEARCH WORKERS, SPLIT OUT OF `research` 2026-08-28 ──
-    //
-    // WHY THE SPLIT EXISTS, from `research`'s own evidence. The override to
-    // `medium` above was aimed at ONE pathology — the restart tail — and that
-    // tail is not spread evenly. mx5-n 2026-08-27: 40.7 of the research phase's
-    // 81.4 wall-clock minutes were lost to restarts, ALL of them in
-    // `worker:tooling` and `worker:context`; `worker:files` and `worker:apis`
-    // never restarted once. With one cell, paying for thinking in the two that
-    // wander means paying for it in the two that do not.
-    //
-    // ── research:files — MEASURED, `off`. WRITTEN 2026-08-28 ──
-    //
-    // A/B 2026-08-26, Qwen3.8-27B-NVFP4-MTP-VERY-HIGH.gguf (llama.cpp
-    // b10620-0f3b51e03), scripts/live-reasoning-group-ab.ts, n=12/arm over 12
-    // distinct mx5 tasks. off 10/12 vs medium 11/12 (p=1.0000); clock PAIRED
-    // over the 10 usable pairs p=0.7090, mean off 79.4s vs medium 59.3s.
-    // off 95% CI [0.55, 0.95]. RUNG 3 — a DECISION, not a finding.
-    //
-    // THIS IS NOT A NEW RUN. It is ledger-research.jsonl, rescored under the
-    // group's new name:
-    //
-    //   AB_CORPUS=/home/edgars/hub/ab-grouplab/mx5-copy bun run \
-    //     scripts/rescore-reasoning-ledger.ts \
-    //     /home/edgars/hub/ab-grouplab/ledger-research.jsonl research:files --from-text
-    //
-    // That ledger was ALWAYS a FILES worker — `child: 'worker:files'`, prompt
-    // `RESEARCH_FILES_PROMPT`, run in each task's own before-tree — so the split
-    // did not strand it, it named it. The axis is the CONJUNCTION: every path
-    // named is real AND every pre-existing file the task edited is named. The
-    // full derivation, the stimulus screen, the parser fix and the confound sit
-    // on the `research` cell above; they are that ledger's, and this is that
-    // ledger.
-    //
-    // WHY THIS CELL DOES NOT FOLLOW `research`'s OVERRIDE. That override was
-    // aimed at the restart tail, and the tail is not here: `worker:files` never
-    // restarted once. The reason for paying does not apply to this worker, and
-    // its own ledger says the arms tied.
+    // The four research workers, one cell each.
     'research:files': 'off',
-    // NOT MEASURED. DECIDED BY PRIOR: a worker with no trial of its own keeps
-    // whatever `research` was decided to run at. No trial in this repo has ever
-    // run apis, context or tooling as its own arm, so a cell here that differed
-    // from `research` would be intuition wearing the authority of a default.
-    //
-    // AND AN AXIS IS THE HARD PART, not the GPU. Two candidates were screened
-    // offline and DIED there — scripts/research-worker-axes-step0.ts, no model,
-    // no GPU. For APIS: "every dotted symbol named is present in the tree"
-    // scores the recorded answers 28/28 tasks and 81/81 items. SATURATED, and
-    // loose with it — the check greps the symbol's LAST SEGMENT, so
-    // `Hono.c.json` passes on the word `json`. Tightening it has nothing to
-    // bite on, because APIS names are model-composed pseudo-symbols
-    // (`Hono.c.var`, `UUID regex`); that is the same wall
-    // [[apis-contract-stage3-refuted]] hit from the other side.
-    // TO REPLACE THIS WITH A MEASUREMENT, the axis must be an EXECUTION or a
-    // production adjudication, the way gate's and planning's are — not a
-    // property of the text.
-    //
-    // A COST RUN WAS DONE ANYWAY, 2026-08-28, and it found nothing to act on.
-    // n=20/arm on the same corpus and trees, production's tools, extensions,
-    // search hint and the task's own recorded FILES map: off 19/20 answered vs
-    // medium 20/20, and the PAIRED clock over 19 stimuli is off 127.2s vs
-    // medium 144.4s, p=0.5262. So thinking is neither better nor cheaper here
-    // by anything this run can see, and there is no cost argument for moving
-    // the cell either way. Ledger: ledger-research-apis.jsonl.
-    // THAT RUN CANNOT WRITE THIS CELL. Its axis is TERMINATION — "did it answer
-    // at all" — so its `off [rung 3]` line is the standing prior speaking with
-    // no quality reading behind it. See README-research-cost-runs.txt.
-    // ITS BUILD IS b10665-ca3d5a3e1, not the b10620-0f3b51e03 every other cell
-    // was measured on: llama.cpp was rebuilt mid-session. Internally paired, so
-    // off-vs-medium is fair within it; its SECONDS are not comparable to the
-    // files or tooling ledgers.
     'research:apis': 'medium',
-    // NOT MEASURED. DECIDED BY PRIOR — see the block above `research:apis`.
-    // Its candidate axis died offline too: "every backticked project path in a
-    // CONTEXT bullet exists in the tree" scores the recorded answers 6/53 tasks
-    // and 213/391 items. THE CHECK LOSES, on exactly the residue the phase
-    // path-axis audit catalogued — npm specifiers (`@hono/zod-validator`),
-    // import paths (`hono/cookie`, `../server/auth`), bare filenames
-    // (`schema.ts`) and `src/` prefix elision.
-    // TO REPLACE THIS WITH A MEASUREMENT, note that this worker is one of the
-    // two the restart tail lives in, so the honest axis is the wander itself —
-    // and no Trial field records a tool-call count today.
-    //
-    // A COST RUN WAS DONE ANYWAY, 2026-08-28, n=20/arm, production's `read,grep`
-    // and no extensions. It found no clock difference — medians 81.2s vs 80.8s,
-    // paired p=0.8594 over 16 stimuli — but it did see the wander directly:
-    //
-    //     died in a loop        off 3/20  vs  medium 0/20   p=0.2308
-    //     emitted bullets       off 17/20 vs  medium 20/20  p=0.2308
-    //
-    // Neither reaches significance at n=20, and the second is TERMINATION, not
-    // quality. But this is the first time the restart tail has appeared INSIDE
-    // a measured run rather than in a production log, and it appeared only in
-    // the `off` arm. off's higher MEAN (97.8s vs 69.3s) is those three deaths,
-    // not slower work. THIS RUN CANNOT WRITE THIS CELL either: an underpowered
-    // termination signal is not a measurement, and its `off [rung 3]` verdict
-    // line is the prior, not a reading. THE CELL IS UNCHANGED. Ledger: ledger-research-context.jsonl,
-    // README-research-cost-runs.txt, build b10665-ca3d5a3e1.
-    //
-    // INSTRUMENT NOTE, because that run ABSTAINED first with 40 good answers
-    // already stored. It scored CONTEXT with `hasAnswerContent` — the FILES
-    // `name<gap>description` shape — and this worker emits a BULLET list of
-    // prose sentences, which `isEntryLine` rejects for ending in a full stop.
-    // Both arms read 0/20. Fixed by `contextEmittedBullets` and the stored
-    // trials rescored with no GPU. Fourth instance of
-    // [[ab-scorer-must-match-the-real-prompt]] in one harness.
-    // AND THE REPLACEMENT WAS WRONG BY ONE, found in review the same day: it
-    // asked for >=2 bullets where production's `classifyContextSilence` calls
-    // >=1 PRODUCTIVE, so a one-bullet answer production accepts read UNUSABLE
-    // in both arms. `countBullets` — production's own function, called not
-    // restated — moved 37/40 stored trials and the emitted-bullets line above
-    // from off 16/20 to off 17/20. The verdict, the cell and the clock are
-    // unchanged: still an underpowered termination signal, still a prior.
     'research:context': 'medium',
-    // ── research:tooling — MEASURED, `medium`. RUNG 1. WRITTEN 2026-08-28 ──
-    //
-    // A/B 2026-08-28, Qwen3.8-27B-NVFP4-MTP-VERY-HIGH.gguf (llama.cpp
-    // b10620-0f3b51e03), scripts/live-reasoning-group-ab.ts, n=20/arm over 20
-    // distinct mx5 tasks, one rep each so the clock can pair.
-    //
-    //     every command runs   off 13/20  vs  medium 20/20   p=0.0083
-    //     wall clock (paired)  off 49.5s  vs  medium 15.9s   p=0.0400
-    //     off 95% CI [0.43, 0.82].  Ledger: ledger-research-tooling.jsonl.
-    //
-    // RUNG 1 — quality decided it, and this is only the SECOND cell in the table
-    // a quality axis has ever decided. THE FIRST WAS extraction, which went the
-    // other way. Note there is no trade here: medium is both better AND 3.1x
-    // faster, so the sampler caveat below cannot be what produced it.
-    //
-    // THE AXIS: every command the checker can adjudicate must RESOLVE in the
-    // tree the worker inspected (scripts/reasoning-ab-tooling-truth.ts). Not a
-    // property of the text — the same kind of truth as gate's executed VERIFY,
-    // which is why it lives where four `phase` text axes died. `unknown` is a
-    // first-class answer and is scored neither way: three of the four command
-    // shapes can only return `real` or `unknown`, because an undeclared binary
-    // may still be on PATH and `bun test` resolves through the runtime.
-    //
-    // OFF'S FAILURE IS ONE CLASS, AUDITED ROW BY ROW. All seven name a
-    // dev-server command against `src/server/index.ts` — a file that exists in
-    // NEITHER the before-tree nor the after-tree of any of those seven tasks;
-    // it first appears around TASK_0057. The worker's own prompt says "If a
-    // tool isn't present in the repo, omit it — don't invent." Medium omits it.
-    //
-    // THE CHECKER WAS WRONG THREE TIMES FIRST, and all three are pinned in
-    // reasoning-ab-tooling-truth.test.ts:
-    //   1. `bun run <file.ts>` is a file invocation, not a script lookup.
-    //      Caught offline; four of twelve reported failures were this bug.
-    //   2. `bun run <installed-bin>` falls back to `node_modules/.bin`.
-    //      VERIFIED BY EXECUTION: `bun run tsc --version` → `Version 6.0.3`,
-    //      exit 0; `bun run dev` → `error: Script not found "dev"`, exit 1.
-    //      Caught LIVE at trial 19. It cost two MEDIUM trials, and BOTH were
-    //      recovered by rescoring the stored text with no GPU — which is the
-    //      whole reason the ledger stores `output`.
-    //   3. `-f` is a compose file only when a compose token precedes it, and
-    //      `<runner> run <arg>` must be read for EVERY segment of a compound
-    //      line, not the first. Found in review: `curl -f <url>` and
-    //      `git clean -f -d` scored as invented paths (strict), while
-    //      `bun run lint && bun run dev` scored `real` on `lint` alone and let
-    //      `dev` — the exact class this cell turns on — through (LOOSE, and the
-    //      harder half to spot). Caught after the run; rescoring the stored text
-    //      moved 2/40 trials and left every number on this cell IDENTICAL.
-    // No fix moved the offline ceiling (32/45 tasks, 102/118 commands, before
-    // and after all three), so none loosened the check against known-good work.
-    //
-    // WHAT THIS CELL DOES NOT SAY. Medium sits at 20/20, so the axis has no
-    // headroom ABOVE it: a future run could not show medium getting worse. And
-    // the axis does not score the restart tail this worker is known for — no
-    // Trial field records a tool-call count — so "medium is better here" is
-    // about the ANSWER, not about the wander.
-    //
-    // REPRODUCE: `AB_SPECS=research:tooling:20 /abrun/run-group.sh`, then
-    //   AB_CORPUS=.../mx5-copy bun run scripts/rescore-reasoning-ledger.ts \
-    //     /home/edgars/hub/ab-grouplab/ledger-research-tooling.jsonl \
-    //     research:tooling --from-text
     'research:tooling': 'medium',
-    // NOT MEASURED. DECIDED BY PRIOR, 2026-08-27 — the same prior that carries
-    // every rung-3 cell in this table: thinking that buys nothing measurable is
-    // not worth its tokens. `off`.
-    //
-    // WHY A DECISION AND NOT `inherit`. All eight phase children run UNATTENDED
-    // — refine, grill-gen, grill-auto, verify-tooling, compose, critique,
-    // critique-triage, compress-label. Nobody is watching to turn a knob, so
-    // `inherit` does not defer to a judgement, it defers to whatever
-    // ~/.pi/agent/settings.json happens to hold. That is the one case this
-    // table exists to remove. (`plan` is the opposite case and keeps `inherit`
-    // for exactly the opposite reason — see that cell.)
-    //
-    // WHY `off` RATHER THAN `medium`. The one cell decided on QUALITY is
-    // extraction at rung 1, where off beat medium 20/20 vs 15/20 and medium's
-    // failure mode was STITCHING — concatenating non-contiguous passages into
-    // something that reads verbatim. refine, compose and critique all emit prose
-    // that downstream phases consume as fact, which is the same hazard.
-    // `planning` went `medium`, and it is the nearest neighbour by job, but it
-    // is NOT evidence that thinking helps this class: off led that cell on
-    // quality too, 28/30 vs 26/30, and lost only the clock, because it wrote
-    // more. Nothing measured anywhere in this table shows thinking improving a
-    // synthesis child's output.
-    //
-    // WHY IT COULD NOT BE MEASURED. Three candidate axes were each scored
-    // against refine's OWN RECORDED OUTPUT and rejected before any GPU:
-    // `validateRefineShape` scores 55/56 — saturated; "EXTERNAL-DEPENDENCIES
-    // names a real package" finds 4 distinct packages across all 56 tasks — no
-    // signal; "every backticked path exists" scored 56.2%, 6/56 perfect — a bar
-    // the known-good answer could not clear.
-    //
-    // THAT THIRD AXIS WAS RE-AUDITED 2026-08-27, because planning's citation
-    // axis was rejected the same way at 59.2% and reached 97.1% once four
-    // adjudicator bugs were fixed. THE CHECK WAS INDEED LOSING.
-    // scripts/phase-path-axis-audit.ts walks the ladder:
-    //
-    //     NAIVE            60.1% of paths,  5/55 tasks perfect
-    //     CATEGORY-CLEAN   83.8% of paths, 34/52 tasks perfect
-    //     FINAL-TREE       93.4% of paths, 43/52 tasks perfect
-    //
-    // CATEGORY-CLEAN drops the spans that were never repo paths: npm specifiers
-    // (`@hono/zod-validator`, `hono/client`), doc URLs, MIME types, dotted code
-    // expressions (`c.var.user` — nine of them), bare filenames with no
-    // directory, and `./`/`../` import specifiers. FINAL-TREE additionally counts
-    // a path real if it exists anywhere in the tree the RUN shipped, which stops
-    // marking a CORRECT PREDICTION wrong — 16 of the 27 remaining misses are
-    // files a later task really creates.
-    //
-    // AND IT IS STILL NOT A USABLE AXIS. At 93.4% the eleven residual misses are
-    // almost all PATH-PREFIX ELISIONS — `server/index.ts` for
-    // `src/server/index.ts`, `client/main.tsx` for `src/client/main.tsx`.
-    // Loosen enough to accept a suffix match and it saturates; keep them and the
-    // A/B measures whether refine writes the `src/` prefix. Formatting, not
-    // reasoning. DO NOT RE-DERIVE THIS.
-    //
-    // ledger-phase.VOID-wrong-scorer.jsonl stores no output text, so its apparent
-    // off 2/14 vs medium 6/14 is an artefact that cannot be rescored. DO NOT READ
-    // A RESULT INTO IT.
-    //
-    // TO REPLACE THIS WITH A MEASUREMENT: find a bar refine's own recorded output
-    // clears while still leaving headroom, and that is not a property of its
-    // formatting. Four candidates are now dead; a fifth needs a different kind of
-    // truth — an EXECUTION, the way gate and implementation are scored, not a
-    // property of the text.
     phase: 'off',
-    // A/B 2026-08-27, Qwen3.8-27B-NVFP4-MTP-VERY-HIGH.gguf (llama.cpp
-    // b10620-0f3b51e03), scripts/live-reasoning-group-ab.ts, n=30/arm over the
-    // committed mx5 fixture replayed 30 times. Ledger: ledger-planning.jsonl.
-    //
-    // THE FIRST CELL THAT IS NOT `off`, and the only one where the two axes
-    // point in opposite directions. Read both.
-    //
-    // off 28/30 faithful plans vs medium 26/30 (p=0.6707); neither arm ever
-    // failed to terminate. Wall clock, UNPAIRED — one fixture, so there are no
-    // distinct stimuli to pair by and `pairByStimulus` refuses rather than
-    // invent a pairing: mean off 207.3s vs medium 143.6s, p=0.0241.
-    // off faithful-plan 95% CI [0.79, 0.98].
-    // RUNG 2 — quality is level on an axis with headroom, and medium is 1.4x
-    // faster at equal quality. The ladder is symmetric: `off` losing the clock
-    // is not privileged over `medium` losing it.
-    //
-    // THE CLOCK CAVEAT, because the direction is the opposite of every other
-    // cell. off's mean is tail-driven — medians are 157.6s vs 148.2s, ~6% apart
-    // — and off emits a LONGER plan for the same title count (median 6840 vs
-    // 4988 chars, 13 titles both arms). Per character off is the faster arm,
-    // 23.0 vs 29.7 ms/char. So what the clock records here is "off writes more",
-    // not "thinking is free". Production waits for the whole plan, so the cost
-    // is real; it is not evidence that thinking decodes faster.
-    //
-    // THE AXIS IS `planningPlanFaithful`, built for this run:
-    //   a plan is FAITHFUL when it lists >= 2 titles AND EVERY source clause it
-    //   emitted — counted in the RAW TITLE — comes back grounded.
-    // It is production's own adjudicator (`extractTitleSource`) with no model in
-    // the loop, and the source doc is a committed fixture, so every stored trial
-    // stays rescorable with no corpus:
-    //   bun run scripts/rescore-reasoning-ledger.ts \
-    //     ab-grouplab/ledger-planning.jsonl planning --from-text
-    // Counting the clauses in the RAW title is load-bearing: a malformed clause
-    // (a missing closing quote — measured live, 4 trials) stops the peel, and a
-    // scorer that counted only what it peeled reads everything before the break
-    // as a clean sweep.
-    //
-    // THE OLD AXIS WAS A SHAPE CHECK. `parseDecomposeList >= 2` read 10/10 in
-    // both arms at n=10/arm — saturated, the same death as gate's and phase's
-    // first scorers. ledger-planning.SHAPE-AXIS-no-extension-10rep.jsonl is that
-    // run; it is a PRIOR, NOT A REPLICATE, because it also ran a different child
-    // (no single-read extension). Do not pool it.
-    //
-    // THE ADJUDICATOR HAD TO BE FIXED FOUR TIMES BEFORE IT COULD JUDGE, and
-    // every fix was found by auditing failures row by row, not by reading code:
-    //   1. GREEDY REGEX across multi-clause titles (25% of real titles carry
-    //      more than one clause) — two real citations became one superstring.
-    //   2. MARKDOWN EMPHASIS/LIST MARKERS counted as content.
-    //   3. CODE BACKTICKS counted as content — the larger half of (2), and
-    //      found only after this run. A code span renders as bare text, so
-    //      `Invites — create/validate/redeem, /join/:token page.` is a verbatim
-    //      copy of a line the file stores with backticks. Screening EVERY spec
-    //      line of the fixture in its rendered form: 107/216 grounded before,
-    //      216/216 after, floor 0/216.
-    //   4. BACKSLASH-ESCAPED QUOTES. The clause is double-quoted, so a spec line
-    //      containing a double quote comes back as `\"`. The backslash is the
-    //      delimiter's artefact, not content.
-    // The live run scored off 21/30 vs medium 24/30 and printed `medium`; fixes
-    // 3 and 4 moved 9 of 60 trials and the QUALITY ORDER REVERSED, to off 28/30
-    // vs medium 26/30. The verdict survives only because the clock decides at
-    // rung 2. scripts/decompose-fidelity-screen.ts is the standing screen that
-    // would have caught 3 and 4 before the GPU ran.
-    //
-    // THE REMAINING 6 FAILURES ARE GENUINE, checked by hand: 4 malformed clauses
-    // (missing closing quote or bracket), 1 word substituted in a real line
-    // ("invokes" for "invites"), 1 single-quoted where the doc has double.
-    //
-    // THE HARNESS SPAWNS PRODUCTION'S CHILD. `phaseDeps()` passed no
-    // `childExtensions`, so auto-decompose ran WITHOUT the single-read guard
-    // production hands every planning child (auto-orchestrator.ts). Fixed before
-    // this run; `loadableSingleReadExtension()` maps src->dist and ABSTAINS if
-    // neither exists, so `bun run build` is a precondition.
-    //
-    // THE TARGET THIS CELL ONCE CHASED DOES NOT EXIST. "off ~1/10 vs on ~8/8
-    // from magicknumbers.md" was cited here and in this file's header as the
-    // split a positive control had to reproduce. Verified 2026-08-27: that page
-    // has no "8/8" in it and never did, and its `1/10 -> 7/10 -> 8/9` ladder is
-    // labelled REASONING OFF, n=10 per cell — three GUARDS from `fea7bbb`, one
-    // arm throughout. See the header.
-    //
-    // A pre-`fea7bbb` control tree WAS built and verified anyway
-    // (ab-grouplab/make-preguard-tree.sh + preguard-probe.ts, all four guard
-    // behaviours rolled back and asserted both ways). It is the only planning
-    // regime known to have headroom at reasoning off — 1/10 there — but it is a
-    // regime we deleted, so a cell decided in it would not be writable here.
-    // Left unrun on purpose.
-    //
-    // MEASURED UNDER THE SERVER'S GLOBAL SAMPLER, which is the THINKING preset.
-    // Here that cuts AGAINST the written cell rather than for it: the `off` arm
-    // decoded on sampling tuned for `medium` and still led on quality, so a
-    // clean comparison could only widen off's quality margin — which the clock
-    // then has to overcome. Ecologically valid, not clean.
     planning: 'medium',
-    // `inherit` ON PURPOSE, and this is the one cell where that is an ANSWER
-    // rather than an absence of one.
-    //
-    // /task-plan is INTERACTIVE. The user is sitting in the loop, reading each
-    // question and steering the next one, and how much thinking that wants is
-    // theirs to judge per session — a quick sketch and a hard architectural
-    // plan are the same command. Every other group in this table runs
-    // unattended, where nobody is there to turn a knob and the table has to
-    // decide. Here there is, and it should not be overridden.
-    //
-    // `inherit` means the child gets whatever `~/.pi/agent/settings.json` holds
-    // — that is the general objection to it, and here it is exactly the point:
-    // the setting the user chose is the setting the user gets.
-    //
-    // It is also unmeasured: /task-plan has never executed inside the A/B
-    // corpus, so there is no recorded child turn to replay. But that is not why
-    // the cell reads `inherit`. Recording a run and measuring the group would
-    // not change it.
     plan: 'inherit',
-    // A/B 2026-08-26, Qwen3.8-27B-NVFP4-MTP-VERY-HIGH.gguf (llama.cpp
-    // b10620-0f3b51e03), scripts/live-reasoning-group-ab.ts, n=30/arm.
-    //
-    // SCORED AGAINST THE TREE, NOT THE ANSWER'S SHAPE. Ten mx5 tasks were
-    // screened by EXECUTING each one's own VERIFY with no model in the loop:
-    // it fails on the before-tree and passes on the after-tree. So the child
-    // faces 20 (task, tree) pairs whose correct verdict is a fact — FAIL before,
-    // PASS after — balanced, so always-PASS and always-FAIL each score exactly
-    // 50%. The verdict is read by production's own `parseVerifyVerdict`.
-    // UNOBSERVED scores WRONG: the harness just executed the evidence, so
-    // declining to look is a failure to do the job.
-    //
-    // off 28/30 correct verdicts vs medium 28/30 (p=1.0000); neither arm ever
-    // failed to emit a verdict. Wall clock, PAIRED by stimulus over the 27
-    // pairs usable in both arms: off is faster in 23 of them, geometric mean
-    // 0.61x, p=0.0019. off correct-verdict 95% CI [0.79, 0.98].
-    // RUNG 2 — quality is level on an axis with headroom, and off is 1.6x
-    // faster at equal correctness. Not a prior: the axis recorded four genuine
-    // judgement errors across the run, so it could have separated the arms and
-    // did not.
-    //
-    // TWO INSTRUMENT NOTES, because this cell read differently before both.
-    // (1) The clock test was UNPAIRED on a matched design. Every stimulus runs
-    //     once per arm, and the stimulus dominates: the same child is ~25s on a
-    //     before-tree and 100-500s on an after-tree. Pooling buried the arm
-    //     effect. On these numbers the unpaired test reads p=0.3408 and the
-    //     paired one p=0.0019. Fixed in `pairedPermutationP`.
-    // (2) The 20-rep run alone scored 20/20 vs 20/20 — SATURATED, and the
-    //     ladder now refuses rung 2 there. The 10-rep run over the same 20
-    //     stimuli, same fingerprint, same scorer, scored 8/10 vs 8/10. Pooled
-    //     (ledger-gate.POOLED-10rep+20rep.jsonl, pairs keyed by run so the
-    //     pairing stays within-run) the axis has headroom and n=30/arm.
-    // Superseded ledgers kept beside it: VOID-synthetic-prompt (hand-written
-    // prompt, prose-matching scorer) and VOID-saturated-shape-axis.
-    //
-    // AXIS RE-AUDITED 2026-08-27, all four mismatches read by hand. The PARSER
-    // is clean — `verdictWord` extracted the stated word correctly every time.
-    // THE TRUTH IS NOT, on one stimulus. TASK_0009/after is `PASS` because its
-    // own VERIFY script passes there, and BOTH arms answered FAIL with the same
-    // checkable reason: the acceptance list requires phone validation to REJECT
-    // `+1234567`, while the spec's own mandated regex `/^\+[1-9]\d{6,14}$/`
-    // accepts it (`+` `1` then six digits, and the range starts at six), and the
-    // shipped test omits the case. Verified by reading the regex, not by
-    // trusting the model. So "the task's VERIFY passes" is not the same fact as
-    // "the acceptance criteria are met", and on that stimulus the child was
-    // right and the axis was wrong.
-    // THE CELL IS UNCHANGED: both arms fail it identically, so dropping it
-    // leaves off 28/29 vs medium 28/29 — still level, still rung 2. Recorded
-    // because the next axis built on executed VERIFY should expect this gap.
     gate: 'off',
-    // A/B 2026-08-26, Qwen3.8-27B-NVFP4-MTP-VERY-HIGH.gguf (llama.cpp
-    // b10620-0f3b51e03), scripts/live-reasoning-group-ab.ts, n=20/arm over 20
-    // recorded docs queries across 10 packages. off 20/20 usable vs medium
-    // 15/20 (p=0.0471); neither arm failed to answer. off usable 95% CI
-    // [0.84, 1.00]. Wall clock, PAIRED over the 15 stimuli usable in both arms:
-    // off 5.2s vs medium 11.1s, p=0.0010.
-    // RUNG 1 — the ONLY cell in this table decided by a quality difference, and
-    // the clock agrees with it rather than carrying it. Ledger:
-    // ledger-extraction.jsonl.
-    //
-    // THE PROMPT IS PRODUCTION'S. The harness used to hand-write it, because
-    // the two production builders frame content as a named npm package's docs
-    // or an anchored web page and the material it had — a recorded `## research`
-    // section — is neither. The fix was the right MATERIAL, not a better frame:
-    // `.pi-tasks/research-cache.json` records 190 distinct `pi-worker-docs`
-    // (package, query) pairs the run really asked, over 31 packages installed in
-    // the corpus copy, and all 190 replay through `docsRaw` + `buildPrompt` with
-    // no model and no network. See scripts/reasoning-ab-extraction-truth.ts.
-    //
-    // THE AXIS IS THE CONJUNCTION: a non-empty answer AND a citation that is
-    // really in the content the child was shown. Production gates on the first
-    // half only and carries `excerptVerified` as metadata, so this is a HARDER
-    // bar than production's own — legitimate for an A/B, and necessary because
-    // the shape half is the ceiling that returned 10/10 in both arms for gate,
-    // research and planning. SCREENED offline over all 190 recorded answers
-    // before any GPU:
-    //     production's own excerptVerified        189/190  — clears the bar
-    //     every backticked SPAN in the content     51/190  — the CHECK loses
-    //     code-shaped identifiers only            123/190  — the CHECK loses
-    // Both grounding rules die the way phase's three did, for a nameable reason:
-    // real type names the model correctly knows — `ResponseInit`,
-    // `ArrayBufferView`, `DataTransfer` — are simply not in the retrieved
-    // chunks, so a correct answer is marked wrong.
-    //
-    // WHAT MEDIUM ACTUALLY DOES WRONG, audited row by row rather than trusted.
-    // All five failures are genuine and none is a normaliser gap: re-checked
-    // with whitespace and case squashed out, ZERO of them appear in the content.
-    // The failure mode is STITCHING — the arm concatenates non-contiguous
-    // passages into one quote block that reads as verbatim and is not. One
-    // matched 457 of its 522 squashed characters before diverging; another glued
-    // three separate `ts fences and a trailing `export type` line. It is not
-    // inventing the package, it is inventing the CONTIGUITY, which is exactly
-    // what a citation asserts.
-    //
-    // A RESCORE OF THIS GROUP RE-RETRIEVES, and that is a trap the ledger now
-    // guards. Two trials that verified in the container failed when rescored on
-    // the host, both quoting a real bun declaration (`@deprecated Prefer
-    // {@link Bun.sql}`) the host's newer bun does not ship — enough to move the
-    // cell from rung 1 to rung 2 on an artefact of WHERE the rescorer ran.
-    // Retrieval is deterministic within one environment and NOT across two, so
-    // the row now carries `verifyHash` and rescore-reasoning-ledger.ts ABSTAINS
-    // on a mismatch. This ledger predates the field, so the live judgements —
-    // made against exactly the bytes each child was shown — are authoritative.
-    //
-    // MEASURED UNDER THE SERVER'S GLOBAL SAMPLER, which is the THINKING preset,
-    // so the `off` arm decodes on sampling tuned for the `on` arm. That is the
-    // regime this machine really runs pi-task in, so the result is
-    // ecologically valid — it is NOT a clean comparison. Here it makes the
-    // finding CONSERVATIVE: the arm that wins is the one running on the other
-    // arm's sampler.
     extraction: 'off',
-    // A/B 2026-08-25, Qwen3.8-27B-NVFP4-MTP-VERY-HIGH.gguf (llama.cpp
-    // b10618-1efd800e9), scripts/live-implementation-thinking-ab.ts, n=20/arm
-    // over 20 distinct mx5 specs, scored by each task's OWN recorded VERIFY
-    // block against the tree the turn produced. off 12/20 pass vs medium 12/20
-    // (p=1.0000); turn died 6/20 both arms. off pass 95% CI [0.39, 0.78].
-    // RUNG 2, and it was read as rung 3 until 2026-08-26. The quality axes are
-    // identical to the trial, so the clock decides — and the clock test was
-    // UNPAIRED on a design that runs each spec once per arm. Pooled, the mean
-    // wall clock of passing turns is off 237s vs medium 298s, p=0.6150. Paired
-    // by spec over the 12 specs that pass in BOTH arms: off faster in 9,
-    // geometric mean 0.55x, p=0.0166.
-    // Quality is still the widest CI in the table — at 12/20 the true pass rate
-    // is anywhere from 39% to 78%, so an ordinary quality difference would have
-    // been invisible — but 12/20 is not a ceiling, so the clock is allowed to
-    // carry the cell. The value is unchanged; only its standing improved, from
-    // a stated prior to a measured win. Rescored from the original ledger on 2026-08-25 when the harness
-    // moved to a forced two-way verdict; the trials are unchanged.
-    //
-    // OVERRIDE WITHDRAWN 2026-08-28; THE CELL IS `off` AGAIN, ON ITS OWN
-    // MEASUREMENT. Between 2026-08-27 and 2026-08-28 this cell read `medium` by
-    // user decision, overriding the rung-2 result above rather than a prior. The
-    // decision's stated reason was an implementation turn observed wandering in
-    // the mx5-n run, and the cell recorded honestly that the run's .pi-tasks logs
-    // had been destroyed before anyone could count the loop.
-    //
-    // A SECOND mx5-n RUN KEPT ITS LOGS, and they refute the reason. The run
-    // executed 10 tasks in 9h22 with this cell at `medium` — thinking ON for
-    // every implementation turn — and TASK_0004 wandered anyway: 167 assistant
-    // turns, 192 tool calls, 45 files and 2,355 lines committed against a
-    // one-file spec, and its own deliverable (src/server/migrate.ts) never
-    // written; it arrived four tasks later. Two single responses in that turn
-    // were 18,297 and 23,568 output tokens. Thinking did not prevent the
-    // rotation, so the lever the override was reaching for is not this one.
-    // Measured over the run's 15 implementation sessions: 441,399 output tokens,
-    // of which 59.3% by character was thinking (1,314,790 thinking chars vs
-    // 902,034 text chars).
-    //
-    // WHAT IS STRUCTURALLY TRUE, and still true, and checked: the implementation
-    // turn runs in the USER'S OWN SESSION (see task/implementation-thinking.ts
-    // and task/implementation-turn.ts), not as a child. It therefore has NO
-    // LoopDetector and NO StallDetector — only the per-tool-call command
-    // watchdog and superviseImplementation's MAX_COMPACTION_RESUMES, which the
-    // runaway above came nowhere near (it took 2 compactions of an allowed 20).
-    // So `implementation` remains the one group in this table where a rotation
-    // has no guard at all. That is an argument for GIVING it a guard, not for
-    // paying 1.8x in thinking that has now been observed not to guard it.
-    //
-    // THE CELL IS STILL RUNG 2 AND STILL THE WIDEST CI IN THE TABLE ([0.39,
-    // 0.78] at 12/20), so it is carried by the clock, not by quality. Nothing
-    // measured since has withdrawn the paired-clock win. To put it on more
-    // evidence, re-run scripts/live-implementation-thinking-ab.ts at a larger n;
-    // the ledger is /home/edgars/hub/ab-implab/impl-ledger.jsonl, 40 rows,
-    // b10618 — the odd build out, so a re-run on b10620 is not a replicate.
     implementation: 'off'
 };
-/**
- * A hand-edited or stale mode must not reach {@link resolveReasoning}'s switch as
- * an unknown string — the `default:` arm would silently absorb it and the user
- * would see "custom" in the file and the default table in behaviour.
- */
+/** A stored mode, or `default` when the value is not one. */
 export function sanitizeReasoningMode(value) {
     return REASONING_MODES.includes(value) ? value : 'default';
 }
 /**
- * Child NAME → reasoning group, for every child that goes through
- * `runPhaseChild` / `runPlanningChild`.
+ * Child NAME → reasoning group, for every child spawned under a name:
+ * `runPhaseChild`, `runPlanningChild`, and the research workers' `spec.label`.
  *
  * WHY KEYED ON THE NAME
  * ---------------------
@@ -724,15 +70,14 @@ export function sanitizeReasoningMode(value) {
  * express something the call site already says out loud.
  *
  * AN UNMAPPED NAME IS A BUILD FAILURE, not a silent `inherit`.
- * `reasoning-groups.test.ts` scans every literal child name in src/ and fails if
- * it is missing here. A defaulting lookup would let a phase added next year opt
- * itself out of a measured setting without anyone deciding to — which is exactly
- * how `/no_think` ended up applied to eight prompts and read by none of them.
+ * `reasoning-groups.test.ts` scans every literal child name under `src/task`
+ * and fails if it is missing here. A defaulting lookup would let a phase added
+ * later opt itself out of the table without anyone deciding to.
  *
  * The gate and extraction groups are NOT here: those children reach the model
- * through `runWorker` / `focusedChildArgs` at a site with no name in scope, so
- * the group is passed directly. The four RESEARCH workers do have a name — their
- * `spec.label` — and so they are here.
+ * through `groupThinkingArgs('gate' | 'extraction')` at call sites with no name
+ * in scope (gate-deps.ts, fetch-core.ts, docs-core.ts, pi-worker-docs.ts). The
+ * four research workers do have a name — their `spec.label` — so they are here.
  */
 export const REASONING_GROUP_BY_CHILD = {
     // ── phase: task/phases.ts + task/title-label.ts ──────────────────────────
@@ -757,11 +102,6 @@ export const REASONING_GROUP_BY_CHILD = {
     'plan-question': 'plan',
     'plan-answer': 'plan',
     // ── research: task/phases.ts `workerSpecs`, keyed on the spec's LABEL ─────
-    // These were a second table (`RESEARCH_WORKER_GROUPS`) keyed on the section
-    // heading, with a silent `?? 'research'` fallback and a guard that sliced
-    // phases.ts source between two string offsets from the config directory.
-    // The label is the same name the loader, the debug trail and the A/B ledgers
-    // already print, so they belong here with every other named child.
     'worker:files': 'research:files',
     'worker:apis': 'research:apis',
     'worker:context': 'research:context',
@@ -810,22 +150,9 @@ export function sanitizeReasoningLevels(value) {
             out[group] = stored_;
             continue;
         }
-        // A `research:*` key absent from the file falls back to the user's own
-        // `research`, NOT to the default table. This is the migration path: a
-        // config written before the split carries one `research` level and
-        // nothing else, and filling the four sub-cells from the table would
-        // silently overrule a choice the user had already made — the four
-        // workers are exactly the children that `research` used to set.
-        //
-        // IT CANNOT TELL A CHOICE FROM A SEED, and that is accepted. Leaving
-        // `default`/`on`/`off` for ANY reason makes `applyReasoningLevel` seed
-        // every group from `resolveReasoning`, so a user who only ever nudged
-        // `gate` still has a `research` on disk they never picked. Inheriting
-        // it pins the four workers to the old default and the measured
-        // `research:files: 'off'` never reaches them. That is what CUSTOM MODE
-        // MEANS: a frozen table, not a subscription to later measurements — the
-        // same is true of every other group in the file. `default` mode is
-        // where a new reading takes effect, and it takes effect there at once.
+        // A `research:*` key the stored config never had falls back to its
+        // parent `research` value, so a config written before the split keeps
+        // meaning what it meant.
         const parent = RESEARCH_SUBGROUP_PARENT[group];
         out[group] =
             parent && valid(stored[parent]) ? stored[parent] : DEFAULT_REASONING_TABLE[group];
@@ -855,14 +182,10 @@ export function resolveReasoning(group, cfg) {
 /**
  * The WHOLE table, as this config will actually run it.
  *
- * This is the question every caller has — the settings menu when it repaints,
- * the mismatch warning when it scans, the custom-mode seeder when it freezes the
- * table — and each of them used to write the same loop over `resolveReasoning`.
- * A per-key accessor with no whole-table companion is also how a THIRD shape got
- * invented (`Array<{group, setting}>`) and leaked into `reasoningMismatches`.
- *
- * `resolveReasoning` stays: one group is still a fair question, and it is the
- * only place the four modes are interpreted.
+ * The question the mismatch scan and the custom-mode seeder both ask. One
+ * accessor, so they cannot each invent their own shape for it. The settings menu
+ * asks the single-group question instead, through `resolveReasoning` — which is
+ * the only place the four modes are interpreted.
  */
 export function effectiveReasoning(cfg) {
     const out = {};