feat(thressgame-100): Wave 3 \u2014 player-choice patterns + 8 recipes + e2e

Wave 3 of thressgame-100 epic complete. 85 % MILESTONE HIT.

Coverage: 37/51 \u2192 44-45/51 = 86-88 % (depending on overlap accounting; both
clear the 85 % gate).

W3.0 AUDIT \u2014 request-choice capabilities verified:
- 6 supported kinds (Zod schema): rps | piece | square | column | row | coin-flip
- (NOT yes-no, NOT number \u2014 plan brief was inaccurate; updated learnings.md)
- All 6 wired through schema \u2192 apply() \u2192 RequestChoiceModal.tsx \u2192 unit tests
- No gaps to fix.

8 NEW RECIPES (W3.2\u2013W3.5):

Batch G \u2014 choice-driven spawn (kind: square):
- tpl-bottomless-pit            \u2014 pick a square; permanent pit there
- tpl-call-down-lightning       \u2014 pick a square; death-square spawns there
                                  (SIMPLIFIED: lethality moved to consumer arm
                                  \u2014 destroy-piece needs entity-id not square)
- tpl-portal-storm              \u2014 pick 2 squares; spawn a linked portal pair

Batch H \u2014 choice-driven swap:
- tpl-anti-camping-choice       \u2014 pick victim + swapper; swap them
                                  (SIMPLIFIED: random swap not expressible \u2014
                                  with-probability gates per iteration not
                                  picks one)
- tpl-two-kids-trenchcoat       \u2014 sacrifice 2 pieces; bishop@e4
                                  (SIMPLIFIED: place-piece pieceType/color/square
                                  hardcoded \u2014 strict literal enums)

Batch I \u2014 choice-driven self-modification:
- tpl-blood-sacrifice           \u2014 sacrifice one piece; +5 Hp to another
                                  (uses W1.6's add-to-attribute.target redirect)
- tpl-summoning-ritual-light    \u2014 sacrifice + 50/50 knight-or-bishop@e4
                                  (SIMPLIFIED: hardcoded type/color/square +
                                  no resource cost \u2014 W5 territory)

Batch J \u2014 sophie's-choice:
- tpl-sophies-choice            \u2014 both players pick own piece; both die
                                  (forPlayer:'both' verified working as in
                                  tpl-mr-freeze)

FOUR DOCUMENTED SIMPLIFICATIONS (full rationale in evidence file Section 4):
- tpl-call-down-lightning: lethality dropped (no Position-comparison primitive)
- tpl-anti-camping-choice: random-swap dropped (with-probability per-iteration
  semantics)
- tpl-two-kids-trenchcoat: place-piece hardcoded (strict literal enums)
- tpl-summoning-ritual-light: hardcoded place + RNG branch (no resource yet)

KEY RUNTIME DISCOVERY (documented in learnings.md):
- runPrimitives catches SuspendedExecution INTERNALLY and returns; does NOT
  re-throw. Test pattern is to read PendingChoices off GAME_ENTITY after the
  call rather than asserting throw.
- For multi-step request-choice e2e: poll on data-choice-id flip rather than
  visibility (modal close+reopen is sub-frame). Canonical idiom for future waves.

TEST SURFACE:
- wave3-recipes-real.test.ts:               26 unit tests (60 expect calls)
- recipes.test.ts:                           5 \u00d7 54 = 444 expect calls
- wave3-choices.spec.ts (Playwright):       11 e2e tests (8 load + 3 runtime,
                                            including FIRST multi-step request-choice
                                            runtime test \u2014 portal-storm 2-step
                                            square picker with poll-on-data-choice-id
                                            assertion idiom)

bun run check: 3081 tests pass (was 3055, +26). 0 regressions.
e2e: 11/11 green via .sisyphus/scripts/run-pw.sh against docker compose dev stack.

ANTI-CAMPING OVERLAP NOTE:
Both tpl-anti-camping (W2 dormant variant) and tpl-anti-camping-choice (W3
choice variant) map to the single upstream ThressGame rule `anti_camping`.
This is intentional \u2014 two different mechanical interpretations of the same
rule name. Documented in evidence file with dual coverage accounting:
  - 45/51 = 88 % (recipe-vs-denominator convention, matches plan target)
  - 44/51 = 86 % (strict unique-rule convention)
Both clear the 85 % milestone.

Plan: .sisyphus/plans/thressgame-100.md
Notepads: .sisyphus/notepads/thressgame-100/
Evidence: .sisyphus/evidence/thressgame-100-wave3.txt (gitignored, 832 lines)

.sisyphus/boulder.json

@@ -135,7 +135,10 @@
     "ses_22f5f3792ffeNYKT2W6PDXXbGQ",
     "ses_22f443947ffeqxxdMQ1N9x9H26",
     "ses_22f360d41ffeDcc17l6fPwcWOr",
-    "ses_22f358609ffekrF7uFjsJEyxu6"
+    "ses_22f358609ffekrF7uFjsJEyxu6",
+    "ses_22f2b6cbdffe8YcUpThdI6JHfM",
+    "ses_22f21845affeRgoo73nIvI1GUa",
+    "ses_22f20fba6ffe5fJyOi7HJg8CZQ"
   ],
   "plan_name": "thressgame-coverage",
   "agent": "atlas"