[hotlong]

Closes #25351

The maintainer's action on #25351, written under the maintainer's delegation in chat: two refused-direction rows in the class-by-class refused table of packages/formula/src/mail-html-hole-placement.test.ts, one per scan correction of 86330c090 (PR #25212), as contract review 6342085020 ③ asked. Test-only: no change to the classifier, the rule, its doors or the renderer.

Per the card's disclosure rule, this body names each row by class only; the samples live in the test source.

The two rows

1. The tag-open state. A hole inside a tag that opens immediately after a character the tag open state reconsumes in the data state answers tag and is refused.
2. A script element's escape states. A hole after an end tag in a script element's double-escaped text answers raw-text-element and is refused.

Both rows were built from the HTML Living Standard's tokenizer section (the tag open state; the script data escaped and double escaped states).

Ablation (local, against the classifier at this PR's base)

Each correction of 86330c090 in packages/formula/src/mail-html-hole-placement.ts was reverted on its own, the file run, and the correction re-applied; the file was byte-identical to the base after each restore.

Correction reverted	Rows red	Reading
Tag open state: reconsume in the data state (back to a plain return to data)	1 of 48: the tag row added here	expected tag, received element-text
Script escape states: the escape flag's arm/disarm and the end-tag guard removed	1 of 48: the raw-text-element row added here	expected raw-text-element, received element-text

With both corrections in place: 48 of 48 pass in this file.

Verification

• packages/formula: vitest run, 53 files and 1424 tests pass; pnpm typecheck (including check:test-typecheck) passes.
• eslint on the changed file: clean.

Declarations

Clause-②: no
Metadata-protocol: none

Test-only, so no changeset: the diff publishes nothing from any released package, and this PR carries skip-changeset, as the card's acceptance states.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 43edf90b56db8b47ad17684c145fb7fa8bf08583 → packageMentionDocs.