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
refactor: make resolution-disclosure choices self-evident
Replace the direct-iOS/maestro message-sniffing (and its justification
paragraph) with an explicit maestroFallback flag passed from the dispatch
site that already owns the path decision, and shrink every why-this-is-OK
paragraph to one-line constraint statements per the maintainer directive.
via: 'runner ELEMENT_NOT_FOUND/AMBIGUOUS_MATCH fall back to tree-based resolution (isDirectIosSelectorFallbackError delegateSemanticFailures; non-maestro dispatches only), which attaches the shared no-match diagnostics, ambiguous shape, and hints',
272
267
},
273
-
// ADR 0012 decision 2: the XCTest fast path has no daemon tree and
274
-
// cannot truthfully report a match count or candidates, so it discloses
275
-
// only the explicit not-observed provenance marker — never a fabricated
276
-
// unique-match or identity claim. No selection-parity table is claimed:
277
-
// that would falsely imply XCTest selection has runtime parity. Via the
278
-
// shared response builder (same symbol as `responseConstruction`),
279
-
// where the marker is attached for the runner-payload source.
268
+
// No daemon tree, so only the not-observed marker — no counts or
269
+
// candidates, and no parity table (that would imply runtime parity).
0 commit comments