incomplete
timeout obligations
target_completion_unestablished
Inspect the evidence without QNX
These are the actual Phase 10 sensor and job cases. The corrected replay keeps the same contract and ignore-unblock setting; only its fixture source/build changes.
This is the actual initial collection snapshot from the staged SSH-loss exercise, not a current live job. The original native run continued independently. Later collection used the same run ID/supervisor and preserved the service FAIL; this earlier infrastructure ERROR remains recorded.
{'kind': 'execution-summary', 'cases': [{'run_id': 'w580171c801dd40b0bb-timeout', 'case_id': 'timeout', 'reasons': ['target_completion_unestablished'], 'verdict': 'ERROR', 'bundle_id': None, 'completion': 'incomplete'}], 'run_id': 'w580171c801dd40b0bb', 'completion': 'incomplete', 'host_error': 'TransportError', 'execution_exit': 2, 'request_sha256': '321dd80243f7c2b014b7ea19a93657d8b0682a61263fb79a6bfb7b8d2b882632', 'schema_version': 1}incomplete
target_completion_unestablished
This initial state had no finalized native bundle. No bundle is invented for this screen.
Source qualification record (available after checkpoint publication) →PASS: all required obligations established. FAIL: service contract violation. ERROR: harness/infrastructure/evidence failure. UNSUPPORTED: required capability unavailable. NOT_RUN: work withheld. Separate assertions may legitimately have different outcomes.