P9.5 Equipment And Individual Growth Implementation Plan

Status: ACTIVE Active step: P9.5-STEP-1 DOMAIN_TRANSACTIONS Baseline: e006160 Goal: docs/goals/PHASE9_5_EQUIPMENT_GROWTH_GOAL.md Contract: docs/runtime/PHASE9_5_EQUIPMENT_GROWTH_CONTRACT.md

Player Outcome

After the second reward, the player equips one visible Recruit for a known Bell push, sees safety versus exposed tempo change the third fight, and returns with the item plus each Recruit's earned individual Lv/XP preserved.

Steps

Step	Status	Outcome	Gate
P9.5-STEP-0 Contract	`COMPLETE`	Two existing items, compatible wearers, four exact Bell outcomes and individual XP are bounded.	Goal, contract, plan, checkpoint and ledger agree before product edits.
P9.5-STEP-1 Domain transactions	`IN_PROGRESS`	One-slot equip, Bell push/item effects, reward and individual XP commit atomically across four paths.	Focused domain test proves exact ticks/order/HP/Coin/Lv/XP and inert invalid/duplicate actions; P9.3/P9.4 regressions pass.
P9.5-STEP-2 World equipment choice	`PENDING`	Two item pedestals and the Bell threat are readable in the returned Hall; actor-body equip replaces forms.	Normal 844x390 unselected/focused/committed states, 44px targets and no card surfaces.
P9.5-STEP-3 Third-cycle runtime	`PENDING`	Parsed touch completes all four equip/battle/growth routes with event-bound feedback.	Four runtime paths, representative frames, fallback/direct zero and strict diagnostics.
P9.5-STEP-4 Pacing and H5	`PENDING`	Five profiles preserve choice consequences and the Owner can play the source-bound Web build.	Five-profile timestamps, regressions, clean H5 export and private Gallery delivery.

Active Step Contract

ID: P9.5-STEP-1 DOMAIN_TRANSACTIONS
PLAYER OUTCOME: Equipment ownership, Bell consequence and personal growth are
  real state transitions before presentation is built around them.
IN SCOPE: runtime/p9_3/core_loop_state.gd,
  runtime/p9_3/core_loop_service.gd, one new runtime/tests/p9_5/ domain test and
  their task-owned UIDs, plus P9.5 durable status documents.
OUT OF SCOPE: controller/UI, assets, unrelated battle rules, save/offline,
  audio, content expansion, packaging, release and other games.
OWNED FILES: the exact in-scope paths above.
ACCEPTANCE CHECKS: both P9.4 third hires by both items; exact four terminal
  projections; one-slot/compatibility/duplicate rejection; `12/14/16` XP;
  exact post-Bell levels/XP/Coin; unchanged P9.3 and P9.4 focused markers.
EVIDENCE LEVEL EXPECTED: automated_verified.
COMMIT BOUNDARY: focused pushed domain source before Step 2 becomes active.
LEGAL TERMINAL: P9.5 Step 1 complete, or redesign required at the earliest
  contradictory transaction/mechanical boundary.
NEXT STEP: P9.5-STEP-2 WORLD_EQUIPMENT_CHOICE.

Frozen

Only the active step's exact files may change. Existing P9.3/P9.4 values, controller composition, accepted assets, P9.2 default battle behavior, save, content, packaging and release remain frozen.

Issue Register

ID	Status	Finding
P95-I01	`RESOLVED_IN_CONTRACT`	The existing battle has no generic push/equipment API. P9.5 owns a Bell-only boundary inside the P9.3 service; default P9.2 behavior remains unchanged.
P95-I02	`OPEN_HUMAN_GATE`	Automated outcomes cannot prove the player understands why preserving the line or exposing Farstring was rational.

3.4 KiB Raw Blame History