refactor(ts-migration): Phase 11 batch 9 — the page composition tables
The eight `nodes` files under `src/pages/admin/*/`, which declare what each admin page is made of. Renamed with no annotations needed at all: zero new errors, 8/8 byte-identical, bundle hash unchanged. They came through clean because everything they call was typed first — `makeNode` and the registry in batch 1, the skill sections in batch 2. A descriptor table is only as checkable as the constructor it feeds. `positions/nodes.js` became `.tsx`, joining its seven `nodes.jsx` siblings. That is the exact case `scripts/ssr-resolve.mjs` was written for and says so in its comment: it is the only `.js` under `src/pages`, `skill-check.mjs` loads it by literal path as `.js`, and the resolver tries `.ts` and `.tsx` in turn. The suite loads it and still passes, which is the first time that particular branch has been exercised. Two of these files are also read as source TEXT rather than loaded — `candidates/nodes.jsx` at `skill-check.mjs:6049` and `talent-pool/nodes.jsx` at `:6298`, both through `resolveSourcePath`. That is the second channel, the one that was missed in Phase 0 and found by an ENOContent failure in Phase 4b-ii. Both resolve. Measured against `7a95d95`: typecheck 6 errors, unchanged; no new error anywhere lint exit 0 npm test 1684/1691, the same 7 failures verbatim build exit 0, identical bundle hash 74d17e2d… type erasure 104/104 byte-identical across Phase 11 so far No baseline artifact touched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HBG1wnuRfJKCstGB8Fekr8
This commit is contained in:
Reference in New Issue
Block a user