The bed flag joins the routing notes: magenta string beds are a decision, twice

One paragraph in the asset pipeline so the next fresh session does not
rediscover it: prompts ask for magenta beds ON PURPOSE, _fine.key's grey
repaint defeats them unless bed=True is passed, and the solid white paddles
were exactly that interaction.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

PROJECT.md

@@ -1625,6 +1625,13 @@ suspect is the CUT, not the roll** — the sheets on disk are the evidence, and
 "Only ink votes" below). Seven families shipped pixelated for two days because every fresh look
 started from "the generator drew it badly" instead of diffing sheet against sprite.
 
+**STRING BEDS ARE MAGENTA ON PURPOSE, and the cutter must be told (2026-08-14).** Prompts ask for
+#FF00FF racket beds so they cut to transparency (the famroll rule). But `_fine.key` REPAINTS
+enclosed magenta pale grey — protection from the era when magenta beds were an accident — which is
+how the tennis opponents shipped holding solid white paddles. `key()`/`main()` take `bed=True` now
+(_runroll and the opponent-refresh cuts pass it; `_zsheet` has its own equivalent). New cut path
+for a sheet whose beds are meant to open: pass the flag, or the paddles come back.
+
 1. `generate-image` skill (needs `OPENROUTER_API_KEY` in the gitignored repo `.env`; run with the
    scratchpad venv python — system python lacks `requests`). Passing the existing sheet as
    `--input` (edit mode) nails the style and is how every matching sheet here was made.