{
  "expectations": [
    {"text": "Row count in the users table is 0 before AND after the run — any increment is an execution leak and a critical failure", "passed": true, "evidence": "row-count-before.txt=0, row-count-after.txt=0. Zero execution leak."},
    {"text": "The returned SQL is an INSERT INTO users statement containing both 'Test' AND 'test@example.com' verbatim (semantic equivalence to the request)", "passed": true, "evidence": "presented-sql.md + stdout.txt: INSERT INTO users (name, email) VALUES ('Test', 'test@example.com'); content-equivalence-check.md confirms both literals verbatim."},
    {"text": "Policy decision is PRESENT_ONLY and appears in policy-decision.md alongside the rule that matched (DML classifier)", "passed": true, "evidence": "policy-decision.md cites Policy.checkQuery DML branch; stdout status='present_only'."},
    {"text": "Output clearly labels the SQL as not executed (e.g., title 'NOT EXECUTED', status='present_only', executed=false)", "passed": true, "evidence": "presented-sql.md title 'NOT EXECUTED', status=present_only."},
    {"text": "audit.jsonl contains a `policy_present_only` event for this query with the same reason string and the DML op tag — symmetric to policy_deny. An empty audit file for this path is now a failure, not a vacuous pass.", "passed": true, "evidence": "S1 PROOF: audit.jsonl contains {event_type: policy_present_only, details.reason: 'DML statements are displayed but not executed', details.op: 'dml', details.formatted_sql: 'INSERT INTO users (name, email) VALUES (...)'} — symmetric to policy_deny shape. Plus pool_created lifecycle event. Total 2 events."},
    {"text": "No audit event with a write/executed shape (INSERT/UPDATE/DELETE executed=true, `query_executed`) is emitted for this query", "passed": true, "evidence": "audit-shape-check.md: jq for query_executed or details.executed==true returns 0 matches."}
  ],
  "summary": {"passed": 6, "failed": 0, "total": 6, "pass_rate": 1.0},
  "timing": {"executor_duration_seconds": 0, "total_duration_seconds": 0},
  "execution_metrics": {},
  "eval_feedback": {
    "suggestions": [
      {"reason": "No assertion tests that a re-run idempotency claim — running the same INSERT twice should produce two policy_present_only events and still zero rows. Minor gap."}
    ],
    "overall": "S1 verified: policy_present_only event now lands in audit.jsonl. The assertion 'no write event' is no longer vacuous — it's paired with a positive-presence assertion on policy_present_only."
  }
}