GPT Review — G6 Retry Package PF-07 v0.5 + Wrapper v0.6

Date: 2026-04-28
Scope: Review Opus G6 RETRY PACKAGE — PF-07 v0.5 + WRAPPER v0.6.

Verdict

PASS WITH SMALL REQUIRED PATCHES BEFORE AUTHORIZATION.

The retry package is directionally correct: backup integrity is restored, PF-07 is updated, Docker-local DB connection is retained, isolated schema p9_g6_dryrun remains the only target, rollback/residue checks remain mandatory, and action log run3 is separate.

Because this is a real DDL dry-run on the production DB instance, a few safety details from the OFFICIAL v0.2 prompt must be explicitly preserved.

Evidence checked

• knowledge/dev/reports/gpt-review-backup-fix-a-d-pass-2026-04-27.md — backup integrity restored.
• knowledge/dev/laws/dieu38-trien-khai/P9-G6-execution-prompt.md — OFFICIAL v0.2.
• knowledge/dev/laws/dieu38-trien-khai/P9-G6-precedence-errata.md — prompt v0.2 supersedes package wording when conflicting.
• knowledge/dev/laws/dieu38-trien-khai/seed-manifest-g6-expected.json — hash status remains PENDING_COMPUTE.

Law / constitutional check

Rule	Result	Finding
Hiến pháp / Zero Trust	PASS with patches	Backup restored; retry remains gated and must keep full v0.2 pre-flight/verification.
Đ32	PASS	User/GPT authorization required before execution.
Đ33	PASS with patches	Isolated schema DDL/DML allowed only with rollback/action log.
Đ35 / 100% DOT-AI	PASS	Claude Code governed execution, not manual human psql.
Đ24	PASS	No taxonomy/entity label mutation.

Required patches

1. Do not replace the full v0.2 pre-flight with only 7 checks.
   State that PF-07 v0.5 replaces only the old backup freshness check. All other OFFICIAL v0.2 pre-flight checks still apply unless explicitly superseded by the docker-exec errata.

2. Directus/FAC/DOT readiness checks.
   Preserve the intent of v0.2 PF-04/PF-05: FAC-07/08/09 and 19 DOT-TAC registrations are already evidenced by E5/E7/E6. If current API/MCP is unavailable, cite prior KB evidence rather than blocking on token discovery. Do not reopen GSM.

3. Backup PF-07 v0.5 should use the actual restored file as evidence.
   Include the known restored backup evidence: directus_2026-04-27_1459.sql.gz, ~44.7 MB, gzip valid, PG dump sanity PASS. Retry pre-flight should accept a newer valid backup if present, otherwise this restored backup is still fresh if within 30h.

4. Seed artifact source.
   Specify that the 8 canonical seed files are from KB seed-g6/ and manifest seed-manifest-g6-expected.json; agent must compute SHA-256 and update manifest after run as documentation only. No mismatch tolerance.

5. V3 expected-failure harness from v0.2 remains mandatory.
   The package says V1–V4, but action log must include V3 SQLSTATE expected-vs-actual harness, not just summary PASS.

6. Rollback must run even on failure after schema creation.
   Make explicit: any failure after CREATE SCHEMA p9_g6_dryrun triggers DROP SCHEMA p9_g6_dryrun CASCADE and residue verification, unless doing so itself fails.

7. Action log date/path.
   Run3 path using 2026-04-28 is acceptable if execution occurs on 2026-04-28 Asia/Bangkok. If actual execution date differs, path must use actual date or include run timestamp. Do not overwrite prior logs.

8. Effort xhigh is acceptable.
   This is DDL/DML on production DB instance inside an isolated schema with rollback and validation. Keep xhigh.

Direction

Opus should patch the retry package once with the above changes, then present a final authorization request. If User authorizes, dispatch Claude Code with xhigh. After execution, Claude Code must upload run3 action log and STOP; no G8/G11/P9 continuation.