chore(todo): add acceptance criteria and test hints to open issues

Flesh out the 14 still-open issues (GAL-34/35/36/37, 40/41, 43, 46/47/48/49,
52/53/55) with explicit acceptance criteria and concrete integration test
hints that reference existing types and headless tooling, so future work
on these tickets has a clear definition of done.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Harald Hoyer 2026-05-07 09:53:09 +02:00
parent 53938f22b5
commit 365e3a7cc4
14 changed files with 188 additions and 0 deletions

View file

@ -9,3 +9,15 @@ labels: [gameplay, advanced-mechanics]
# GAL-35: Allow the player to shoot a Boss that is holding a captured ship
Allow the player to shoot a Boss that is holding a captured ship.
## Acceptance criteria
- [ ] Player bullets register a hit on a Boss whose `EnemyState::ReturningWithCaptive` is active (today they may pass through or be ignored — verify and fix).
- [ ] Bullet despawns on hit like any other collision.
- [ ] Hit awards a distinct rescue-bonus point value (Galaga: 1500/3000 depending on timing) — not the regular Boss 300.
- [ ] No double-counting if multiple bullets connect on the same frame.
## Integration test hints
- Spawn a Boss with `EnemyState::ReturningWithCaptive` and a `Captured` player attached; insert a bullet at boss position; tick world one frame; assert: `Score` increased by rescue bonus, bullet entity gone, boss entity gone.
- Negative test: same setup but with boss in `EnemyState::InFormation` — confirm only normal hit/score path runs (no rescue bonus).