`FIX2_PROMPT.txt`

35 lines
You are doing a ROUND-2 FIX pass. Read these two files in this directory:

- `CHANGES.md` — list of patches that were applied earlier
- `CODEX_REREVIEW.md` — re-review findings about those patches (what still broke, what's newly broken, what was missed)

Your job: apply ONLY the fixes the re-review marked as P0 or "BROKEN" or "concern", IF they are SAFE.

WHAT TO FIX (SAFE):
- "Missed call-sites" listed in the re-review (apply the same fix to the additional locations).
- "New issues introduced" of severity P0 or P1 that are clearly mechanical (e.g., move validation out of module scope into a route handler, fix a missing import, narrow an over-broad `try/except`, add a dict-type guard before `.get()`).
- Patches the re-review marked "BROKEN" or "concern" with a clear small fix.

WHAT YOU MUST NOT TOUCH:
- Database schema or migrations (any `.sql`, any `migrations/` dir).
- Anything under `dw_unified`, `Designer-Wallcoverings`, or `shopify/` paths.
- DNS, Cloudflare, nginx, certbot configs.
- pm2 ecosystem files, systemd units, launchd plists.
- Cron specs.
- Anything under `node_modules/`, `venv/`, `.venv/`, `dist/`, `build/`, `.next/`.
- Package version bumps.
- Public-facing copy/HTML/CSS that customers see.
- Real-secret rotation (no access).

WRITE `CHANGES2.md` to this directory with:
- `## Round 2 Applied` — bullet list of each: `file:line — what changed — why (cite the rereview finding)`.
- `## Still Deferred` — bullet list of issues left for Steve.

CONSTRAINTS:
- Read-only outside the project directory.
- Cap edits at ~10 files.
- Surgical patches only — no rewrites.
- No git, no installs, no tests.
- Cap CHANGES2.md at ~400 words.
- If `CODEX_REREVIEW.md` Verdict is "SHIP IT" with no concerns, write a one-line CHANGES2.md saying "no round-2 changes needed" and exit.