GPT Review — Track A Residual Stabilization Prompt

Date: 2026-05-03

Verdict

Prompt is directionally correct and ready after minor tightening. The four tasks are the right residual scope after OGV-P0: persist trigger/function, fix dot-vector-audit in report-only mode, verify/add Qdrant backup cron, and run post-fix verification.

Required tightening before dispatch

1. Persist trigger/function: do not rely on docker-entrypoint init-only location unless Agent verifies it is actually part of the deploy mechanism. Prefer repo-managed migration/deploy asset or operations runbook asset that is version-controlled. The report must state whether this protects rebuilds, redeploys, and new DB init separately.
2. dot-vector-audit: report-only mode must be default. Agent must not run any heal/cleanup/reindex path. Manual run must be with report-only flags only.
3. Backup cron: avoid duplicating cron entries. Agent must check existing crontab before adding and make the operation idempotent.
4. Health/audit verification: use the same OGV pagination-safe manual method for orphan/ghost counts; do not trust a single endpoint unless code was verified read-only.
5. Agent should not perform broad cleanup or re-embed. Track A residual is stabilization only.

Directive to Opus

Polish the prompt once with these five tightening points, then dispatch to Agent with /effort medium. Do not ask Agent to design IU/outbox or P44-6. After Agent returns the Track A residual report, review for: trigger persistence evidence, audit report-only PASS, backup cron PASS, orphan bug = 0, ghost bug = 0, correct-behavior ghosts separated, legacy search smoke PASS.