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
{{ message }}
Repository navigation
Commit f5a7e4c
Browse filesBrowse the repository at this point in the historyBrowse files
test(contracts): prove the band forwarding and restore promotion coverage (#3971)
An independent review found that every test of the seam scripted a tree
only, so match.keyboard was always undefined and the forwarding spread
the guard prefers was proven nowhere: delete it and the suite stayed
green. runnerSnapshotEntry now carries extra runner-result fields, and
three scenarios close the gap, each red when its forwarding is deleted:
- keyboardOcclusion (manifest): the producer band over a keyboardLifted
tree, where the tree rule cannot measure and the refusal can only come
from the forwarded fact.
- promotion (plain title, not manifest-derived): the deleted hittable-
ancestor scenario back as transcript evidence for the half of the
nonHittable cell that does run; retargeting findAct.promotion fails it.
- keyboardOcclusion forwarding (plain title): find click hands the same
band to the acting leaf, pinning preresolvedTarget's #2660 claim.
Also: the responseConstruction scenario now pins the payload key set
instead of a vacuous refsGeneration check; the errorTaxonomy scenario
exercises the ambiguous builder its cell names alongside the no-match
arm; the registry says focus <x> <y> is a generic-route command no row
classifies instead of calling it 'the coordinate route'; the coordinate
disclosure unit cases drop as duplicates of the leaf door's, keeping the
lifted-tree hoist with one owner in the shared fixture.
'Mutating `find <locator> focus`, and the focus leg of `find <locator> type`: find captures its own tree, ranks its own candidate set, runs the node stages its `findAct` row declares, then dispatches a point focus itself (`type` then dispatches the text) instead of re-entering the interaction leaf. `find click`/`find fill` are NOT this path — they hand the resolved node to `runtime-ref` as a pre-resolved target (#1654). `focus <x> <y>` is the coordinate route. Every cell below classifies what the `findAct` row plus this seam actually run, not what the acting rows run.',
553
+
'Mutating `find <locator> focus`, and the focus leg of `find <locator> type`: find captures its own tree, ranks its own candidate set, runs the node stages its `findAct` row declares, then dispatches a point focus itself (`type` then dispatches the text) instead of re-entering the interaction leaf. `find click`/`find fill` are NOT this path — they hand the resolved node to `runtime-ref` as a pre-resolved target (#1654). `focus <x> <y>` shares only `executeFocusPoint`; it is a generic-route command that never enters the interaction leaf and no row of this matrix classifies. Every cell below classifies what the `findAct` row plus this seam actually run, not what the acting rows run.',
554
554
commands: ['find'],
555
555
guarantees: {
556
556
// find's own ranking, but under the same ambiguity contract the runtime paths use: one
0 commit comments