Jens
faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
49 lines
840 B
Markdown
49 lines
840 B
Markdown
# Pass Completion Report Prompt
|
|
|
|
Use this at the end of every Codex implementation pass.
|
|
|
|
Produce a concise but complete report with:
|
|
|
|
## Completed
|
|
|
|
List what was actually implemented.
|
|
|
|
## Changed files
|
|
|
|
List each changed file and why it changed.
|
|
|
|
## Commands run
|
|
|
|
List commands and exact result status.
|
|
|
|
## Test results
|
|
|
|
Mention pass/fail/skipped and why.
|
|
|
|
## Self-review scorecard
|
|
|
|
Score 0-10:
|
|
|
|
- Scope control:
|
|
- Architecture consistency:
|
|
- Backend correctness:
|
|
- Frontend correctness:
|
|
- GIS correctness:
|
|
- AI/ML correctness:
|
|
- QA/QC correctness:
|
|
- Tests:
|
|
- Documentation:
|
|
- Release readiness:
|
|
|
|
## Known limitations
|
|
|
|
List real limitations. Do not hide TODOs.
|
|
|
|
## Contract deviations
|
|
|
|
State explicitly whether any API, DB, storage, CRS, state machine or governance contract changed.
|
|
|
|
## Next recommended pass
|
|
|
|
Name the next pass and why.
|