Phillip Tarrant
c5f127e0f1
Adversarial re-review of 6589d7c found three assertions in the same species as
the seven it fixed: green against the bug they name.
- test_the_displayed_scores_are_the_draft_s_scores spent zero points, so
final() == rolled() and a Box/Value bound to `rolled[stat]` instead of
`final[stat]` would pass unnoticed. Now presses the Plus node to force a
divergence, and checks the Box/Rolled sub-label too (previously unchecked).
- No test ever emitted a node's `pressed` signal — every interaction went
through the _on_*_pressed handler directly, so _wire() itself, and every
card-to-index binding, had zero coverage. Minus had no coverage of any
kind. Helper and interaction tests now press the authored nodes; added
dedicated press tests for race/calling/pool/bonus/minus, plus the
Plus/Minus disabled-boundary bindings.
- The Luck sweep only ever checked the default binding (human + sellsword),
covering 1 of the 28 race x calling combinations whose authored prose
(fragment/blurb) actually renders on screen. Now sweeps all 28.
Plus three cheap adds: a degenerate-origin (§13) guard, orphan-authored-card
counts for the race/calling/bonus rows, and a non-empty assertion on the
origin-card RichTextLabel.
Each fix verified by deliberately reintroducing its named bug, confirming the
guard test goes red, then reverting — see
.superpowers/sdd/task-6-report-fix2.md. 291 -> 298 tests, all green.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
/client — Godot 4.7 game client
GDScript. Holds ALL game state and ALL game rules (charter §2, §4). The AI never mutates state; the client validates and applies everything.
Open: Godot 4.7, import this folder as the project (project.godot).
Responsibilities
- All state: stats, HP/MP, inventory, quest flags, Luck, disposition/approval (§8, §9)
- All rules: deterministic combat, Luck branch-selection, move validation (§6, §7, §10)
- The canon log — compact structured fact list, code-maintained, injected into every call (§11)
- Talks to
/apiover HTTP. No API key, ever. Knows one base URL + role endpoints (§4) - Degrades to authored fallback text (from
/content/fallback) when the API is down (§13)
Key rule — never do this (charter §2)
If an AI response directly sets a variable that persists, stop. Parse → validate → apply or discard.
See docs/ for scene structure, input model, and combat wiring.