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
29 lines
836 B
Markdown
29 lines
836 B
Markdown
# Day 1 Operator Checklist
|
|
|
|
Use this checklist while running Codex.
|
|
|
|
## Before starting
|
|
|
|
- [ ] Extract latest full ZIP.
|
|
- [ ] Open repo in development environment.
|
|
- [ ] Ensure Docker/Postgres/PostGIS are available if implementation reaches DB stage.
|
|
- [ ] Provide Codex with `prompts/codex/day-1/00_START_HERE.md`.
|
|
|
|
## During each pass
|
|
|
|
- [ ] Codex read required docs.
|
|
- [ ] Codex changed only pass-relevant files.
|
|
- [ ] Codex ran validation or explained why not.
|
|
- [ ] Codex updated execution log.
|
|
- [ ] Codex reported changed files.
|
|
- [ ] Codex did not silently change architecture.
|
|
|
|
## After Day 1
|
|
|
|
- [ ] Backend starts or documented blocker exists.
|
|
- [ ] Frontend starts/builds or documented blocker exists.
|
|
- [ ] API contracts match actual behavior.
|
|
- [ ] TODO reflects reality.
|
|
- [ ] CHANGELOG updated.
|
|
- [ ] Next pass is clear.
|