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 8f4a7b7
Browse filesBrowse the repository at this point in the historyBrowse files
test(coverage): keep macOS test-suite evidence as owed work and audit accepted reasons
The CI macOS replay lane runs agent-device test with --report-junit and
gates on its exit status, so the test row is closeable with real lane
evidence and stays known-gap on #1916. Each accepted-gap reason now
states the absence it claims against the repository's lanes, and the
gate's docstring encodes that rule.
'No Linux live command creates a downloadable daemon artifact for inventory',
77
-
'The Linux lanes run the local CLI, where every command output is a caller-owned local path; the daemon only inventories artifacts carried over remote artifact transport, so a Linux lane cannot create a downloadable inventory entry without a local-transport product decision.',
77
+
'The Linux lanes run the local CLI, where command outputs are caller-owned local paths; request finalization inventories a response artifact only when the request carries a client artifact path (remote transport) or it is the sparse-snapshot fallback screenshot, which no Linux lane observes, so a Linux lane cannot produce a downloadable inventory entry without a local-transport product decision.',
'No command-specific macOS doctor evidence exists',
145
-
"The doctor checks are daemon-owned host diagnostics (version, state dir, inventory probes, Metro) with no macOS device branch, already pinned by the daemon's own doctor tests; a macOS lane would re-run that identical code, so macOS carries no command-specific doctor evidence.",
145
+
'The doctor checks are daemon-owned host diagnostics — version, state dir, inventory probes, Metro — pinned platform-neutrally by the daemondoctor tests, and no macOS lane invokes the command: neither the System Settings replay nor the desktop and recording provider scenarios carry a doctor step.',
146
146
),
147
147
tvos: tvos.gap('No tvOS-specific doctor command evidence exists yet'),
'The events timeline is daemon-owned session bookkeeping with no platform branch, already pinned for a daemon-backed session by request-router-events.test.ts; a macOS lane would re-run that identical code, so macOS carries no command-specific event timeline evidence.',
313
+
'The events timeline is daemon-owned session bookkeeping, pinned by request-router-events.test.ts for a daemon-backed web session, and no macOS lane invokes the command: neither the System Settings replay nor the desktop and recording provider scenarios carry an events step.',
"The CI macOS replay lane dogfoods the test command to run the replay suite, whose per-command macOS claims are already carried by the replay:system-settings live rows; no lane asserts the test command's own suite result and JUnit output on macOS, and none will.",
"react-native dismiss-overlay only answers meaningfully on a surface that carries a React Native overlay, and the repository's React Native fixtures run on iOS simulators and Android emulators; the macOS lanes drive desktop apps, so no macOS lane will cover this row.",
798
+
"react-native dismiss-overlay only answers meaningfully on a surface that carries a React Native overlay, the repository's React Native overlay evidence runs on iOS simulators and Android emulators, and no macOS lane invokes the command: neither the System Settings replay nor the desktop and recording provider scenarios carry a react-native step.",
"trace never binds a device runtime: its session-scoped start/stop bookkeeping is platform-neutral and already pinned by the daemon's trace-runtime tests, so a macOS lane would re-run identical code and macOS carries no command-specific trace evidence.",
852
+
'trace never binds a device runtime: handleTraceCommand carries no bindDevice or inspectFacts call, its start/stop bookkeeping is pinned by the daemon trace-runtime tests, and no macOS lane invokes the command: neither the System Settings replay nor the desktop and recording provider scenarios carry a trace step.',
"trace never binds a device runtime: its session-scoped start/stop bookkeeping is platform-neutral and already pinned by the daemon's trace-runtime tests, so a Linux lane would re-run identical code and Linux carries no command-specific trace evidence.",
862
+
'trace never binds a device runtime: handleTraceCommand carries no bindDevice or inspectFacts call and its start/stop bookkeeping is pinned by the daemon trace-runtime tests, and no Linux lane invokes the command: neither the replay script nor the command-evidence lane carries a trace step.',
0 commit comments