Copy/Paste Agent Prompt — P3D Vector Search Reliability Hardening

Date: 2026-05-11 Recommended effort: high Mode: Production hardening with strict safety gates

Prompt

Implement the approved P3D Vector Search Reliability Hardening pack.

Recommended effort: high.

Reason: this is production hardening for Agent Data search. It includes compose/build durability, canary script, possible code patch, audit logic, service recreate, and rollback discipline.

Read first:

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-final-approval-vector-search-reliability-hardening-prompt-rev2-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-vector-search-reliability-hardening-implementation-prompt.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-vector-search-reliability-hardening-design.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-vector-search-hybrid-path-title-boost-implementation-report.md
knowledge/dev/laws/dieu44-trien-khai/reports/opus-verification-vector-search-boost-pass-2026-05-11.md

Then execute exactly the implementation prompt:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-vector-search-reliability-hardening-implementation-prompt.md

Goal:

Harden the already-passing search boost into production-grade infrastructure:

1. deployment durability so search boost survives agent-data recreate/rebuild;
2. repeatable search canary T1–T8;
3. conservative recency tie-break only if timestamp metadata is available;
4. audit warning cleanup by code classification only;
5. unified search contract compatibility for future IU vector.

Hard boundaries:

• No Qdrant point delete/upsert.
• No Qdrant collection replacement.
• No new Qdrant collection.
• No bulk reindex.
• No auto-heal.
• No /kb/reindex.
• No /kb/reindex-missing.
• No /kb/cleanup-orphans write mode.
• No PG schema mutation.
• No DB INSERT/UPDATE/DELETE.
• Do not update kb_documents rows, including test_empty.md.tmpl.
• No trigger/function/index/permission changes.
• No TAC/IU migration.
• No IU vector implementation.
• No Pack 1 DDL.
• Do not recreate the whole stack; only agent-data may be rebuilt/recreated.
• Do not touch Qdrant container except read-only point-count checks.

Required execution behavior:

1. Run preflight exactly.
2. Back up code, compose, and existing canary if any.
3. Add safe build: directive for agent-data only if compose/Dockerfile validation passes.
4. Create/adapt /opt/incomex/dot/bin/dot-search-canary using actual API response shape.
5. Implement recency tie-break only if timestamp metadata is already available; otherwise skip and report.
6. Implement audit warning cleanup only by code classification; no DB write, no auto-heal, no reindex.
7. Add unified search contract shape only if low-risk; no IU vector collection or payload implementation.
8. Run py_compile and docker compose config before rebuild.
9. Build/recreate only agent-data.
10. Run canary after force-recreate.
11. Verify Qdrant point count unchanged.
12. Roll back immediately if build/health/canary/Qdrant checks fail.

Expected report path:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-vector-search-reliability-hardening-implementation-report.md

Final response format:

vector_search_hardening_status=PASS|FAIL|ROLLED_BACK|BLOCKED
report_path=knowledge/dev/laws/dieu44-trien-khai/reports/p3d-vector-search-reliability-hardening-implementation-report.md
production_durability=PASS|FAIL|BLOCKED
canary_status=PASS|FAIL|BLOCKED
recency_tiebreak=IMPLEMENTED|SKIPPED_METADATA_UNAVAILABLE|DEFERRED
audit_warning_cleanup=IMPLEMENTED|DEFERRED_CODE_PATH_UNCLEAR|FAILED
qdrant_points_before=<n>
qdrant_points_after=<n>
db_write_performed=false
qdrant_mutation_performed=false
rollback_performed=true|false
health_after=<status>

Return only the final response format plus critical blocker notes. Do not write a long essay.