claiming coverage in prose
Round 5 returned BLOCKED. Its blocker was a durable coverage claim the tree
contradicted, and its other findings were the same class one layer down.
F1, the blocker. The record said `Complete<T>` "is applied … at each construction
site, which is what keeps the phantom direction alive." This PR annotated
`replacePathReplacements` and `replaceRemoteLibraryPreferences` at the wrapper
but left their construction sites as bare generic `.map` callbacks — the exact
shape spa-conventions §4b rule 2 says is unchecked. Injecting `phantomFieldZZZ`
into both literals typechecked CLEAN. Both sites are annotated now and both
reject the phantom with TS2353.
F2. Five mutations of the composition resolver left the whole file GREEN:
dropping `anyOf` entirely, making the alternatives loop non-recursive, taking
only the first arm's properties, ignoring top-level `required` when alternatives
are present, and dropping `items` descent. Three of those are silent-miss
direction — a droppable member the guard reports nothing about. The six existing
cases pinned the `allOf` path and the `oneOf` intersection and nothing else, so
the previous commit's "witnessed" claim covered one branch of five. All five now
redden; fourteen parametrised cases instead of six.
F3. "A new optional member anywhere in the request graph fails this test" was
false in three constructed shapes. Two are now handled — an inline body that is
an ARRAY of objects, and properties under `if`/`then` — and the third was a real
collision: `_inline_body_members` keyed on verb+path with no media type, so a
second `[Consumes]` on one action made the later body silently overwrite the
earlier. Keyed by media type now. The universal is replaced in both copies by the
actual boundary.
`if` is treated as a condition, not a constraint: its properties are collected (a
client may send them) and its `required` is discarded, because that `required`
selects a branch rather than obliging anyone to send anything.
F4/F5. The record characterised the annotated wrappers as "the ones reachable
from a droppable schema, plus the six builders" — five fall outside both. And
`oneOf` and `anyOf` were concatenated into one alternatives list, which
intersects `required` ACROSS the two keywords; they are conjunctive with each
other, so each intersects within itself and the results union. Safe-direction but
wrong, and untested.
The prose change is the one that matters. Five rounds, five blockers, every one a
hand-written claim about a population. So the record no longer asserts present
coverage at all: it states the RULE, says plainly that nothing enforces the
second half (#820), and tells the reader to read the code rather than a summary.
A set phrased in words rots exactly like a count — deleting the counts in an
earlier commit while leaving the worded set was treating the symptom.
895 passed 2 skipped (up from 887), ruff format 0, ruff check 0, typecheck 0,
eslint 0, 1200/1200 web, build 0, catalog clean.