You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Blind-spot fix#2 (generator — case + special tags): the net can now DISCOVER a case-asymmetry bug
The mixed-case raw-text bug was invisible to the generative net for TWO reasons, both now fixed in the
input generator (test-only; no grammar change):
- The materializer only ever emitted the grammar's literals VERBATIM (lowercase) and generic placeholder
tag names (`a`) — it never varied case and never used the SPECIFIC special-tag literals. So it could not
produce `<SCRIPT>` (a raw-text tag, uppercased), the exact shape the bug needs.
- Fix: (a) `markupRawText()` — a directed emission that builds raw-text/void elements from the SPECIFIC
`markup.rawText.tags` / `voidTags` (`<script><b</script>`, `<br>`), so the case-insensitive raw-text /
void behaviours are exercised instead of a generic `<a>`; (b) `caseVaryTags()` in `push` — for every
markup input, a CASE-VARIED copy that UPPERCASEs the tag names (derived from `markup.tagOpen`/
`closeMarker`; tag-name matching is case-insensitive, length-preserving so offsets stay valid).
Proven by revert-test: with the #2 grammar fix disabled, the improved generator now makes the scope≡role
net report a gated inconsistency on `<SCRIPT>…` — the class the old generator missed entirely. With the
fix in place it is green. 26/26 gates; grammars untouched (the change is in the test generator only).
0 commit comments