Initial public release

prompts/codex/review/CONTRACT_DRIFT_AUDIT_PROMPT.md

@@ -0,0 +1,26 @@
+# Contract Drift Audit Prompt
+
+```text
+Audit GeoIntel for contract drift.
+
+Compare implementation against:
+- contracts/api/
+- docs/API_SPECIFICATION.md
+- docs/API_CONTRACTS.md
+- docs/DATABASE_SCHEMA.md
+- docs/13-implementation-traps/API_RESPONSE_RULES.md
+
+Find mismatches in:
+- endpoint paths
+- HTTP methods
+- request fields
+- response envelopes
+- error shape
+- status enum
+- date/timestamp fields
+- geometry fields
+- frontend TypeScript types
+- test expectations
+
+Fix safe mismatches by aligning implementation to existing contracts. If the contract itself is clearly incomplete, update docs and explain why in CHANGELOG.md.
+```

prompts/codex/review/END_OF_PASS_REVIEW_PROMPT.md

@@ -0,0 +1,29 @@
+# End-of-Pass Review Prompt
+
+Use this prompt at the end of every Codex implementation pass.
+
+```text
+You are reviewing your own GeoIntel implementation pass.
+
+Do not add new features during this review. Inspect the changed files, run available checks, and produce fixes only for issues introduced by this pass.
+
+Review against:
+- docs/12-build-control/M7_IMPLEMENTATION_CONTROL_LAYER.md
+- docs/11-quality/SELF_REVIEW_CHECKLIST.md
+- docs/11-quality/REGRESSION_TRAPS.md
+- docs/13-implementation-traps/GEOSPATIAL_CALCULATION_RULES.md
+- docs/13-implementation-traps/API_RESPONSE_RULES.md
+- docs/12-build-control/CODEX_DECISION_BOUNDARIES.md
+
+Tasks:
+1. Summarize changed files.
+2. Identify contract drift.
+3. Identify missing tests.
+4. Identify geospatial correctness risks.
+5. Identify UI state gaps.
+6. Fix safe issues immediately.
+7. Update CHANGELOG.md and docs/BUILD_STATUS.md.
+8. List remaining risks and the next recommended pass.
+
+Do not hide failures. If a test cannot run, document why and what command should be run later.
+```

prompts/codex/review/REGRESSION_HUNT_PROMPT.md

@@ -0,0 +1,30 @@
+# Regression Hunt Prompt
+
+```text
+Perform a regression hunt on GeoIntel.
+
+Focus only on regressions, inconsistencies and broken contracts. Do not add new features.
+
+Check:
+- API contracts versus implementation
+- database schema versus docs
+- frontend API client versus backend responses
+- status enums
+- CRS and geometry handling
+- fixture validity
+- QA/QC formula implementation
+- scripts and smoke tests
+- documentation truthfulness
+
+For every issue found:
+- describe the issue
+- identify files affected
+- fix it if safe
+- otherwise add it to docs/BUILD_STATUS.md as an explicit known issue
+
+End with:
+- tests run
+- tests not run
+- confidence level
+- recommended next pass
+```