05 — No-Execute Test Report (Workstream D)

Goal: prove the runner/harness does not execute a DOT.

Procedure

Called fn_process_dryrun_prepare_pair('PROC-CAND:dot:kg','DOT_KG_EXPLAIN','DOT_KG_EXPLAIN_VERIFY', 'DRYRUN:dot:kg:explain:fixture-v1','FIXTURE:dot:kg:explain:v1','DRYRUN-NS:dot:kg:explain', 'agent:runner-dryrun-macro','DRYRUN:dot:kg:explain:fixture-v1', '<sha256>'). Rehearsed in BEGIN/ROLLBACK first, then committed.

Results (PASS)

• 1 run + 2 component observations written, all evidence_type=SIMULATED_DRY_RUN, status=completed, source_system=dryrun_prepare_runner, mode=PLAN_VERIFY_ONLY_NO_EXECUTE.
• Idempotency: second identical call returned the same process_run_id (f4ca70b9… in rehearsal) and inserted 0 rows.
• No DOT executed: dot_tools for the pair — usage_count sum = 0, last_executed count = 0 (unchanged; NULL).
• No event_outbox emission (runner never touches it; 7 process.* types remain inactive).
• birth_registry 1,158,319 before == after; trigger_guard_alerts 129 unchanged.
• v3/v4 read-back: dot:kg → candidate_status_v4 = runner_contract_missing, dryrun_readiness_state = blocked_no_runner_contract_fixture_ready, fixture_ready=true, no_execute_tested=true, sim_cnt=2, dry_cnt=0, real_cnt=0.
• Invariant: verified_candidates_v3 = only PROC-CAND:job:cut — the new SIMULATED observation did not push dot:kg toward verified.

Independent MCP read-back (query_pg)

v_process_discovery_dryrun_readiness and process_run_observation both confirm the committed row (run 3903c9c5…, fixture hash matches). PASS.

No-execute path proven. The runner records correlated observations and is structurally incapable of executing a DOT.