# WEAPON WAVE: per-weapon fixes after the user's ratings (coordinator, 27 Oct ~22:20)

The user reviews one weapon page at a time. SMG is done (its wave is in `_tools/SMG_REPLACE_WAVE.md`). Each next weapon gets a builder who works through that weapon's ratings, as they arrive, in `_tools/coord/RATINGS.md` (that weapon's section).

## Read first
1. `_tools/SMG_REPLACE_WAVE.md`: all the rules, the SHOW EARLY steps and the uniqueness/ledger process. These apply to every weapon.
2. `_tools/CINE_ROLLOUT.md`: CONTEXT AWARENESS (the top rule) and STYLE PICKS: LIVE RULES.
3. `_tools/coord/STYLE_PICKS.md` (all follow-ups):
   - no faces, ever;
   - the game's gore via K58.STYLE;
   - nothing painted on bodies;
   - no bones, organs or fat bodies;
   - head explosions and old-style explosions scaled to the gore level (full at EXTREME).
4. The user's notes for your weapon: `_tools/coord/RATINGS.md`. New notes are forwarded to you as they come.

## Per kill
- **GOOD:** keep as is. A shared STYLE change may still touch it; check it still reads right.
- **OK BUT:** fix exactly what the note says, in the kill's own file. Send 2 full-size frames.
  - Common notes are fixed centrally by A in 58k_style.js / 58k_cine.js:
    - head explosion;
    - explode (old style);
    - faces;
    - bones;
    - body marks;
    - hit circles;
    - the zoomed end.
  - Verify the central fix covers your kill. Only hand-fix it if the kill draws its own version outside the helpers.
- **REPLACE** (the user's REPLACE rating, or the ⟲ REPLACE NEEDED mark from `58k_replace58.js`, i.e. it plays on too few maps): build a NEW cinematic kill IN THAT KEY. The SMG wave process applies:
  1. beat summary → my OK;
  2. blocking live + 4 full-size frames + a 0.1 s sheet;
  3. polish;
  4. FINAL pack.
  - Map-independent: generic elements most maps have are OK.
  - Move at THE X level.
  - CONTEXT AWARENESS applies throughout.
- **Bugs** the user reports (e.g. "infinite walking at the end"): reproduce headless, fix, and verify.

## Order
1. Bugs.
2. OK BUT fixes, one by one with frames.
3. REPLACE slots: summaries first.

Ping me per item. I relay each one to the user straight away.

SAFETY: the coordinator's rules:
- never print or commit keys;
- kill only your own PIDs;
- no destructive git; `git add <paths>` only;
- headless Chrome only;
- no store builds;
- python deletes with absolute paths;
- re-read shared files (`58k_<w>.html`, `58k_files.js`) right before minimal edits.