GPT Review — P10B-2C D28 Execute Prompt v0.1

Date: 2026-04-29

Verdict

Approve with small patches. Do not dispatch v0.1 as-is.

The prompt is well structured and follows the proven D32 execute pattern, but because this is a mutation step it needs precision patches before Agent dispatch.

Required patches

P1 — Create /tmp/p10b-2c before baseline tee

T1g writes:

tee /tmp/p10b-2c/d28-baseline-counts.txt

but /tmp/p10b-2c is only created in T2. Add:

mkdir -p /tmp/p10b-2c

at the start of T1.

P2 — Backup evidence wording

T1g says BOTH backup + baseline required, but command allows backup dir missing. Clarify:

• baseline snapshot is mandatory;
• recent backup evidence is logged if available;
• if baseline snapshot cannot be captured: STOP;
• missing backup alone is warning, not STOP.

P3 — Run-file COMMIT verification must not be confused by ON COMMIT DROP

Keep current ^COMMIT; and ^ROLLBACK; checks. When documenting COMMIT/ROLLBACK, explicitly state ON COMMIT DROP is temp-table clause, not transaction commit.

P4 — Render must use source span/order from package output, not heuristic HR insertion only

T6 says preserve --- HR between top-level sections. That is okay, but the renderer must report whether HR positions match the original. If HR reconstruction differs, diff will catch it, but report must classify it.

Add:

• save raw render TSV before conversion;
• generated markdown must preserve unit body verbatim;
• HR insertion is allowed only between top-level rendered sections matching original source pattern;
• if uncertain, do not silently invent HR; report difference.

P5 — Diff failure should still upload artifacts

If normalized diff fails, the task should not terminate before uploading evidence. Add:

• capture diff result;
• if content drift detected: mark FAIL, upload original/reconstructed/diff/tree/counts/report, then STOP.

P6 — Rollback instructions must include actual IDs or exact doc_code/version scope

T9 should include actual pub_id and exact rollback SQL scope. If rollback.sql is self-scoped by doc_code/version, say so. If it needs pub_id, fill it.

Direction

Patch v0.1 to v0.2 with P1–P6. After patch, P10B-2C execute may be dispatched. No additional GPT review is required if only these exact patches are applied.

Scope remains:

• execute approved SQL once;
• no schema/role/seed changes;
• no auto rollback after commit mismatch;
• upload deliverables; STOP.