# M9 Implementation Review Script

Use this manual review script after Codex produces a build.

## 1. Repository Hygiene

- [ ] No random root-level files.
- [ ] No duplicate docs with conflicting instructions.
- [ ] No generated caches committed.
- [ ] No secrets committed.
- [ ] `.env.example` updated if env vars changed.

## 2. Backend

- [ ] App starts.
- [ ] Health endpoint returns envelope or documented health format.
- [ ] API routes grouped logically.
- [ ] Validation errors are structured.
- [ ] Database models match schema docs.
- [ ] Geometry fields are not plain unvalidated strings.
- [ ] Tests exist for implemented endpoints.

## 3. Frontend

- [ ] App starts.
- [ ] No blank route screens.
- [ ] API client centralizes envelope parsing.
- [ ] Loading, empty, error states present.
- [ ] Demo workflow visible.
- [ ] Map shell does not depend on unavailable live data.

## 4. Geospatial Logic

- [ ] CRS metadata preserved.
- [ ] Area calculations are server-side.
- [ ] Invalid geometries rejected.
- [ ] Demo fixtures load correctly.
- [ ] No fake geospatial metrics presented as real.

## 5. Documentation

- [ ] Changelog updated.
- [ ] Build status updated.
- [ ] Execution log updated.
- [ ] Known limitations updated if needed.

## 6. Commands

Run what is available:

```bash
python -m pytest
npm test
npm run build
npm run lint
docker compose config
```

If commands are not available yet, Codex must document why.