orbit/.pi/goals/archived/goal_2026091923060370_mu986...

11 KiB
Raw Blame History

{ "version": 3, "id": "mu986lbo-140zqa", "objective": "=== Goal ===\nObjective: Give the 7 new enemy ships (spritesheet frames 1–7) distinct stats and attack patterns using a mix of weapon types (heat-seeking missiles, spray, plus new ideas), ramping modestly in difficulty frame 1 → 7, and rewire the ?combat demo to send a sequence of rolling waves — one wave per ship type in difficulty order, 6 ships of that type per wave, 3 on screen at a time.\n\nSuccess criteria:\n- data/combat.json → enemyTypes has 7 new types (frames 1–7), each with distinct stats + a distinct weapon pattern; difficulty (hull/shields/damage) climbs monotonically frame 1 → 7 with only modest bumps (not a wall).\n- Weapon types actually implemented and used: heat-seeking missile (dodgeable — capped turn-rate), spray fan, rapid burst, rapid-fire, ring burst, and a heavy/elite combo. The missile is the only genuinely new projectile; the rest are loops/config over the existing bolt.\n- All 7 fire their pattern correctly in BOTH the main-game ?combat boot and the standalone range (shared firing path).\n- The ?combat boot now dispatches a sequence of rolling waves: 7 waves in difficulty order, each wave = 6 ships of that single type, maxConcurrent=3, each kill sending in a replacement (replacePerKill=1).\n- dev/combat.test.mjs still passes (pure Node modules: EnemyTypes/Waves stay Phaser-free).\n\nBoundaries:\n- In scope: data/combat.json (enemyTypes + a new wave script + ?combat wiring), js/combat (new weapon behaviors: EnemyShip firing, a missile projectile, fireEnemy dispatch in both CombatScene and CombatSystem), dev/combat.test.mjs.\n- Out of scope: new art/sprites, player-ship changes, the XP curve, and the existing pirate_ambush quest wave (stays as-is). The pre-existing frame-0 raider stays untouched.\n- New weapons must not break the standalone range (combat.html / dev server /combat) — it shares the firing path.\n\nConstraints (hard rules):\n- Heat-seeking missiles MUST be dodgeable: capped turn-rate + moderate speed, so the player can out-turn them.\n- Each subsequent ship only a LITTLE harder than the previous (modest +hull/+shields/+damage), not a big jump.\n- Keep EnemyTypes.js and Waves.js pure (no Phaser/scene imports) so dev/combat.test.mjs runs in bare Node.\n- ?combat demo: exactly 7 waves, one type each, in difficulty order; rolling; 6 per wave; 3 concurrent; 1 replacement per kill.\n- Don't mutate shared config sections in place (deepMerge already guards this; follow the pattern).\n\nVerification contract:\n- Run dev/combat.test.mjs → 0 failures.\n- grep confirms the new wave script is wired to the ?combat boot (spawnPack replaced) and all 7 frames are referenced in enemyTypes.\n- Manual browser check of ?combat: 7 waves fire in order, 3 on screen at a time, one type per wave; missiles visibly home and can be dodged; spray/burst/ring render correctly.\n- Re-read the 7-ship roster table and confirm each type's pattern + difficulty bump is present.\n\nIf blocked: stop and ask the user.", "status": "complete", "autoContinue": true, "usage": { "tokensUsed": 10055317, "activeSeconds": 7168 }, "sisyphus": false, "revision": 142, "createdAt": "2026-09-20T02:57:00.276Z", "updatedAt": "2026-09-20T05:06:03.752Z", "scheduler": { "version": 1, "owner": "01a0bcb6-3151-728d-8a3d-e5448d16a70b", "generation": "e1b3640c-c13f-41e4-9c2d-4b3af8df49d9", "used": 1, "phase": "running", "repairUsed": false, "decision": { "kind": "ready", "nextAction": "Continue pursuing the goal, then verify and complete it when satisfied.", "purpose": "ready" }, "dispatch": { "id": "18fbeaa1-987d-4e0e-a7e6-57129de676e8", "kind": "ready", "claimedAt": 1789873020301 } }, "taskList": { "tasks": [ { "id": "task-1", "title": "Design 7 enemyTypes (frames 1–7) in data/combat.json", "status": "complete", "verificationContract": "combat.json has 7 enemyTypes entries (frames 1–7), each with distinct stats + weapon config; hull/shields/damage climb monotonically with modest bumps; EnemyTypes.enemyTypeIds()/enemySheetList() resolve all 7.", "completedAt": "2026-09-20T03:05:24.312Z", "evidence": "Node check: 7 types (frames 1–7) resolve; hull 80→150, xp 18→42 monotonic; 7 distinct patterns; combat_demo normalizes to 7 rolling waves (6/3/1 each)" }, { "id": "task-2", "title": "Implement new weapon behaviors (missile + spray/burst/ring/rapid/heavy)", "status": "complete", "verificationContract": "Missile projectile class with capped turn-rate homing exists; spray/burst/ring/rapid dispatch from fireEnemy in BOTH CombatScene and CombatSystem; EnemyTypes.js + Waves.js remain pure Node (no Phaser import).", "completedAt": "2026-09-20T04:21:17.494Z", "evidence": "Missile.js (capped turn homing, Node-tested) + Weapons.js firePattern dispatch all 7 patterns; both contexts wired (CombatScene/CombatSystem.fireEnemy → firePattern); Node suite green importing EnemyT" }, { "id": "task-3", "title": "Rewire ?combat boot to the 7-wave rolling sequence", "status": "complete", "verificationContract": "GameScene ?combat boot calls startWaves(new script) instead of spawnPack; script = 7 rolling waves, 6 per wave, one type each, difficulty order, maxConcurrent=3, replacePerKill=1.", "completedAt": "2026-09-20T04:21:17.495Z", "evidence": "GameScene:1050 startWaves('combat_demo') (spawnPack no longer the boot path); combat_demo = 7 rolling waves bomber→warden, 6/3/1 each; Node e2e run passes; browser sfxcheck found live wave ship after " }, { "id": "task-4", "title": "Extend tests + manual playtest verification", "status": "complete", "verificationContract": "dev/combat.test.mjs passes (0 failures) incl. new script normalize/runner cases; manual ?combat run shows 7 waves in order, 3 at a time, missiles dodgeable, spray/burst/ring render.", "completedAt": "2026-09-20T05:03:03.768Z", "evidence": "node dev/combat.test.mjs: all checks passed (0 failures). CDP demo check PASS: range renders all 7 patterns w/ shape; main 7 waves in order, 3 on screen, replacement/kill, 42 kills done. sfxcheck PASS" } ], "blockCompletion": true, "proposedAt": "2026-09-20T02:56:38.761Z" }, "stopReason": "agent", "archivedPath": ".pi/goals/archived/goal_2026091923060370_mu986lbo-140zqa.md" }

Goal Prompt

=== Goal === Objective: Give the 7 new enemy ships (spritesheet frames 1–7) distinct stats and attack patterns using a mix of weapon types (heat-seeking missiles, spray, plus new ideas), ramping modestly in difficulty frame 1 → 7, and rewire the ?combat demo to send a sequence of rolling waves — one wave per ship type in difficulty order, 6 ships of that type per wave, 3 on screen at a time.

Success criteria:

  • data/combat.json → enemyTypes has 7 new types (frames 1–7), each with distinct stats + a distinct weapon pattern; difficulty (hull/shields/damage) climbs monotonically frame 1 → 7 with only modest bumps (not a wall).
  • Weapon types actually implemented and used: heat-seeking missile (dodgeable — capped turn-rate), spray fan, rapid burst, rapid-fire, ring burst, and a heavy/elite combo. The missile is the only genuinely new projectile; the rest are loops/config over the existing bolt.
  • All 7 fire their pattern correctly in BOTH the main-game ?combat boot and the standalone range (shared firing path).
  • The ?combat boot now dispatches a sequence of rolling waves: 7 waves in difficulty order, each wave = 6 ships of that single type, maxConcurrent=3, each kill sending in a replacement (replacePerKill=1).
  • dev/combat.test.mjs still passes (pure Node modules: EnemyTypes/Waves stay Phaser-free).

Boundaries:

  • In scope: data/combat.json (enemyTypes + a new wave script + ?combat wiring), js/combat (new weapon behaviors: EnemyShip firing, a missile projectile, fireEnemy dispatch in both CombatScene and CombatSystem), dev/combat.test.mjs.
  • Out of scope: new art/sprites, player-ship changes, the XP curve, and the existing pirate_ambush quest wave (stays as-is). The pre-existing frame-0 raider stays untouched.
  • New weapons must not break the standalone range (combat.html / dev server /combat) — it shares the firing path.

Constraints (hard rules):

  • Heat-seeking missiles MUST be dodgeable: capped turn-rate + moderate speed, so the player can out-turn them.
  • Each subsequent ship only a LITTLE harder than the previous (modest +hull/+shields/+damage), not a big jump.
  • Keep EnemyTypes.js and Waves.js pure (no Phaser/scene imports) so dev/combat.test.mjs runs in bare Node.
  • ?combat demo: exactly 7 waves, one type each, in difficulty order; rolling; 6 per wave; 3 concurrent; 1 replacement per kill.
  • Don't mutate shared config sections in place (deepMerge already guards this; follow the pattern).

Verification contract:

  • Run dev/combat.test.mjs → 0 failures.
  • grep confirms the new wave script is wired to the ?combat boot (spawnPack replaced) and all 7 frames are referenced in enemyTypes.
  • Manual browser check of ?combat: 7 waves fire in order, 3 on screen at a time, one type per wave; missiles visibly home and can be dodged; spray/burst/ring render correctly.
  • Re-read the 7-ship roster table and confirm each type's pattern + difficulty bump is present.

If blocked: stop and ask the user.

Progress

  • Status: complete
  • Auto-continue: on
  • Sisyphus mode: no
  • Time spent: 1h59m28s
  • Tokens used: 10M (10,055,317) tokens

Tasks

  • task-1: Design 7 enemyTypes (frames 1–7) in data/combat.json — evidence: Node check: 7 types (frames 1–7) resolve; hull 80→150, xp 18→42 monotonic; 7 distinct patterns; combat_demo normalizes to 7 rolling waves (6/3/1 each)
  • task-2: Implement new weapon behaviors (missile + spray/burst/ring/rapid/heavy) — evidence: Missile.js (capped turn homing, Node-tested) + Weapons.js firePattern dispatch all 7 patterns; both contexts wired (CombatScene/CombatSystem.fireEnemy → firePattern); Node suite green importing EnemyT
  • task-3: Rewire ?combat boot to the 7-wave rolling sequence — evidence: GameScene:1050 startWaves('combat_demo') (spawnPack no longer the boot path); combat_demo = 7 rolling waves bomber→warden, 6/3/1 each; Node e2e run passes; browser sfxcheck found live wave ship after
  • task-4: Extend tests + manual playtest verification — evidence: node dev/combat.test.mjs: all checks passed (0 failures). CDP demo check PASS: range renders all 7 patterns w/ shape; main 7 waves in order, 3 on screen, replacement/kill, 42 kills done. sfxcheck PASS