[AlexSamBY]

What

The process half of the 2026-10-08 audit: lint for the code nobody linted, a gate against focused tests, coverage thresholds at what the suite covers, and the plan's stale lines.

Lint covers the tooling

npm run lint:js now runs over scripts/, e2e/ and the config files at the root, as well as src. That is 63 more files, under eslint-config-react-app's rules without the React, JSX and hooks ones (TOOLING_RULES in eslint.config.js). Each file gets the node, browser or jest globals of the place it runs. The first run found 16 problems:

• Fixed, 11.
  • Seven unused names in the browser specs: five imports (DISMISSAL, TOUCH, tooltipA11yWiring, topmostAt, BUBBLE), and two bubble helpers nothing called. Their BUBBLE imports went with them.
  • scripts/jest-console-guard.js reassigned its buffer under a function created in a loop (no-loop-func). The buffer is now a constant array cleared in place, with the same behaviour.
  • The two webpack configs export a named value (import/no-anonymous-default-export).
  • A /* global globalThis */ redeclared a built-in, and is gone.
• Configuration, 4.
  • document was undefined in scripts/fixtures/packed-browser-entry.js, which runs in a page; that file has browser globals now.
  • The hooks rules read a Playwright fixture's use as React's use; they are not applied to the tooling.
• Suppressed, 1. A string of prose in scripts/wrapper-prop-curation.js names the ${id}-help template. The suppression states that reason.

A focused test fails lint

The ban covers it.only, describe.only, test.only, test.describe.only, test.concurrent.only, .only.each, fit and fdescribe. It applies in src/**/__tests__, scripts/__tests__, e2e/**/*.pw.js and e2e/**/*.packed.js.

A focused test runs alone: the rest of its file is skipped, and the run still passes. Jest has no --forbid-only, and Playwright's forbidOnly is set for CI only. eslint-plugin-jest is not installed, so the gate uses two core rules: no-restricted-properties on .only and no-restricted-globals on fit/fdescribe.

Coverage thresholds at what the suite measures

Each threshold is the measured value, rounded down to a whole percent (statements/branches/functions/lines):

• global: 89/79/85/90 → 98/95/97/99;
• rules.tsx: 89/76/98/91 → 96/87/100/98;
• ten more entries rise by 1 to 3 points;
• function.ts goes 96 → 100 on branches and 75 → 80 on functions, and its comment says why;
• six files get entries of their own: documentHost.ts, formData.ts, errorMapping.ts, dataMapping.ts, popupScope.ts and lodash-lite.ts.

jest.config.js states the rule above the block: a change that covers less either covers what it adds or lowers the number in the same commit, saying why.

The plan's stale lines

13 lines in docs/UPGRADE-PLAN.md changed, each one in place, with a date and the evidence:

• Sequencing (§6, §9.3, §9.9). "Never mix an upgrade with a refactor in one release" is recorded as not held. Nothing has been released since Phase 2 (the last tag is v0.34.3, 2026-08-12), and §9.2's hooks migration and §9.3's decomposition landed after it. §9.3's "do not start" and §9.9's sequencing get the dates the work was done.
• §9.3 step 2. "STARTED" and "Still to extract" now name what §9.3 closed without extracting: transformConfig/toOpenLConfig and initSelectStatesFromData, still in rules.tsx.
• R8. javascriptEnabled went on 2026-10-08, and size()/px() are called at 133 sites, not 186.
• R10. The audit and the prop list are done. The owners' MINOR call overruled "anything dropped ⇒ major", and the migration notes are in the changelog.
• Appendix B. The npm audit baseline was 0 on 2026-09-30 and 35 on 2026-10-06, and has not been re-measured since. The line also says why the "prop-types": pattern has a colon.
• Appendix C.
  • The upstream form-stack line is qualified by F4's finding.
  • There are two cloneElement sites, not one.
  • prop-types is retired.
  • The React 19 box no longer contradicts itself.

Measured

• Lint. 445 files, 0 problems: 382 in src and 63 in the tooling. Master's versions of five of the fixed files each fail the new configuration, with the rule named.

• Focused tests. A probe with nine focused forms was linted as a file in each of the three test locations. All nine are reported in each; describe.skip is not, and neither is .only outside a test file.

• The open PRs.

  • Under this configuration, EPBDS-16211: the published package is driven in a browser on React 16.14, 17 and 19 too #200's and EPBDS-16211: validateMeta finds the props a 0.34 host lost, and the meta contract agrees with the renderer on more shapes #201's changed tooling and test files lint clean.
  • EPBDS-16211: unset refuses prototype paths, and a select with no label has an accessible name #202's one finding is the unused BUBBLE this PR removes, in a different hunk of the same file.

• Coverage.

  • Two runs, one in the local time zone and one in UTC as on CI, were identical on every file and metric (214 suites, 2776 tests).
  • The thresholds are the lower of the two, rounded down.

• Local gates, all exit 0. That covers all 21 gates plus the manifest contract, on Node 24.14.0:

  • lint and types: lint:js, lint:css, typecheck, typecheck:contract;
  • generated files: docs:props:check, docs:views:check, css:fixture:check, build-css:check;
  • builds and jest: test:env-flags, test:coverage, build, test:react16, test:react17, test:react19;
  • packaging: test:pack, test:css:built, test:pack:peers, test:types, test:pack:browser;
  • browser: test:e2e, test:e2e:react19.

  They ran on this commit's tree before two wording fixes, one in a comment in eslint.config.js and one in the changelog entry. After those, lint:js was rerun, along with the two suites that read those files (wrapper-prop-reference.contract.test.js, NavTabs.history.test.js), all exit 0.

• Against the open PRs. git merge-tree merges this commit cleanly with EPBDS-16211: the published package is driven in a browser on React 16.14, 17 and 19 too #200, EPBDS-16211: validateMeta finds the props a 0.34 host lost, and the meta contract agrees with the renderer on more shapes #201 and EPBDS-16211: unset refuses prototype paths, and a select with no label has an accessible name #202. The file this PR and EPBDS-16211: unset refuses prototype paths, and a select with no label has an accessible name #202 both change, e2e/keyboard-a11y.pw.js, lints clean once merged.

Left for the owners

GitHub holds eight branches; merged PR branches are deleted on merge. Besides master, gh-pages and the three open PRs' branches, three remain:

• main: a 2021 initial commit holding only LICENSE, outside master's history.
• h1-dead-weight: PR EPBDS-16211 H1: delete the dead weight, 26 files #52 was closed unmerged, and its content merged as EPBDS-16211 H1: delete the dead weight, 26 files #53 from h1-dead-weight-rebased.
• release/v0.34: the 0.34 patch line §10 names. It carries two commits outside master's history (Epbds 16435 #27 and v0.34.3, 2026-08-12) and has no workflows.

Whether to delete the first two, and whether the third gets CI or a statement that 0.34 takes no more fixes, is not decided here.

🤖 Generated with Claude Code