Tomi's Quest

## Summary

### Player Controls

- [x] B: Swing sword
- [ ] Upgrade: Hold for spin attack
- [x] A: Short - Jump
- [x] A: Long - switch to instrument mode
- [x] Right Swipe Down: Shoot arrow
- [ ] Upgrade: three simultaneous arrows (fan shape)
- [x] Right Swipe Up: Drop Bomb
- [ ] Upgrade: three simultaneous bombs
- [x] Right Touch Tap: Boomerang (simon says microgame)
- [ ] Upgrade: Boomerang fills in hole floor tiles
- [x] Left Touch Tap: Four shield zones
- [ ] Upgrade: perfect shields reflect projectiles
- [ ] Turntable station: Spin Rhythm XD minigame

### Game Sequence

- [x] Get Ewi
- [x] Slash bush
- [x] Get MPoints
- [x] Buy Bombs
- [x] Bomb wall
- [x] Get Jump
- [x] Jump over pit
- [x] Get Shield
- [ ] Fight shield-necessary enemy
- [x] Get Bow
- [x] Shoot bow-specific target
- [x] Get Boomerang
- [x] Something that requires a boomerang
- [x] Get Turntables
- [ ] Play turntable minigame
- [x] Get Dorias Lullaby
- [x] Play lullaby to open gate

### Misc

- [x] Script action trigger when block is on a switch

## Technical Spec

## UI

## Mockups

## How to Test

No files or tests are named. Start by locating the Tomi's Quest gameplay code and where player input plus sequence/state progression are handled, then map each unchecked checklist item to those components. After mapping, follow the project’s normal firmware build/flash path to run the game and validate the quest flow and controls. Done means all unchecked tasks (upgrades, enemy/fight step, and pending mini-games) behave as described in the sequence.

Vom Indexierungsmodell aus dem Issue-Text verfasst.