dot-iu-cutter v0.4 — PG-backed Dry-run RERUN#3 Harness Negatives UUID JSON GPT Review

Date: 2026-05-17 Reviewer: GPT Reviewed report: knowledge/dev/laws/dieu44-trien-khai/v0.4-db-adapter-dry-run/dot-iu-cutter-v0.4-pg-backed-dry-run-RERUN3-EXECUTION-FAIL-harness-negatives-uuid-json-2026-05-17.md

Verdict

pg_backed_dry_run_rerun3_result: FAIL_ACCEPTED_GATE_INCOMPLETE
agent_behavior: PASS_CORRECT
happy_path_validation: PASS
r3_15_row_baseline: PASS
dot_pair_signature_cross_ref_fix: VALIDATED
dot_lane_overlap_prevention: VALIDATED_ON_HAPPY_PATH
blocker_type: harness_result_serialization_defect
system_under_test_defect: not_proven_by_this_failure
production_touched: false
pg_backed_dry_run_blocked: true
next_phase: dry_run_harness_uuid_safe_result_serialization_fix

RERUN#3 produced important validation: the canonical MARK → SWEEP → REVIEW → CUT → VERIFY happy path reached the exact r3 15-row baseline against real PostgreSQL. DOT-991/DOT-992 lane separation and deployed dot_pair_signature_check XOR held on the happy path.

The run cannot be marked PASS because the negative/idempotency battery did not complete. The blocker is isolated to the throwaway dry-run harness serializing its own result dict with json.dump(... ) without UUID-safe handling.

Accepted Findings

validated:
  - orchestrator_ACCEPTED_pin_updated_to_e93424b
  - current_run_dump_shredded_on_fail_path
  - C10a_happy_path_executed
  - C11a_r3_15_row_matrix_exact
  - dot_pair_signature_count_2
  - DOT_991_references_change_set_only_on_happy_path
  - DOT_992_references_verify_result_only_on_happy_path
  - deployed_XOR_constraint_satisfied_on_happy_path
  - production_sysid_unchanged
  - protected_envs_untouched
  - no_hardcode_or_label_issue
fail_reason:
  scenario: C10b_negatives
  root: harness_json_dump_without_default_str
  object: psycopg3_uuid_UUID_entry_id_from_idempotency_replay
  result: harness_crash_before_shell_side_delta0_post_count

Required Next Phase

Open a bounded harness-hardening phase:

phase: v0_4_PG_backed_dry_run_harness_UUID_safe_result_serialization
nature: execution_artifact_fix_only

Allowed scope:

modify_allowed:
  - gitignored dr_harness_v0_4.py
  - gitignored run_dryrun_v0_4.sh only if needed to reference updated harness sha or preserve teardown hygiene
modify_forbidden:
  - iu-cutter source code
  - iu-cutter tests
  - database schema
  - production configuration

Fix Requirements

requirements:
  - normalize_harness_result_values_before_json_dump_or_use_default_str
  - preserve_uuid_semantics_for_system_under_test
  - do_not_mask_system_under_test_errors
  - ensure_negative_idempotency_delta0_shell_post_count_runs
  - keep_happy_path_r3_15_gate_unchanged
  - keep_teardown_prod_dump_shred_on_all_exit_paths
  - keep_ACCEPTED_pin_e93424b5ff7fa5e4b8406131977ce4339cd0856a
  - hash_corrected_harness_and_orchestrator
  - no_iu_cutter_code_change
  - no_git_commit

GPT preference:

preferred_fix:
  - add_small_recursive_json_safe_encoder_in_harness_for_report_values
  - or_use_json.dump_default_str_for_harness_report_only
  - do_not_change_cutter_agent_code
  - do_not_change_scenario_semantics

Rerun Authorization After Harness Fix

After fixing the gitignored harness artefact and hashing it, Agent may rerun PG-backed dry-run RERUN#4 under the already approved isolated-env protocol, using:

code_commit: e93424b5ff7fa5e4b8406131977ce4339cd0856a
verification_plan: r3
expected_final_rows: 15

Required Report Additions

Final report must include:

report_required:
  - harness_serialization_fix_summary
  - corrected_harness_sha256
  - corrected_orchestrator_sha256_if_changed
  - no_iu_cutter_code_change_no_commit_proof
  - git_status_short_iu_cutter
  - happy_path_15_row_result
  - negative_idempotency_delta0_result
  - current_run_prod_dump_teardown_proof
  - hardcode_control_statement
  - metadata_label_hardcoding_absent_statement

Still Forbidden

forbidden:
  - iu_cutter_code_change
  - git_commit
  - production_secret_read
  - production_write
  - production_CUT_VERIFY
  - deploy_or_restart
  - schema_migration
  - index_DDL
  - JSONB_normalization
  - vector_integration
  - label_registry_schema_change

Status

ready_for_harness_hardening_and_rerun_prompt: true
agent_self_advance_before_harness_fix: prohibited