# P9.4 Second-Cycle Adaptation Contract > Revision: `p9.4-contract-r1` > Baseline: `73834ab` ## Entry State P9.4 begins only after the accepted P9.3 Open Road return: - Coin `20`; - Company `2/10`: `Hearthguard`, `Farstring`; - remaining standing offers: `Wayrunner` for `10`, `Kindhand` for `11`; - one completed reward receipt for Open Road; - Crosswind is the visible incoming threat: contact plus ranged pressure and a `12 Coin` reward. ## Adaptation Choice | Recruit | Spend | Required role evidence | Required consequence | |---|---:|---|---| | Wayrunner | 10 | visible flank/counter actions | victory tick 99; Hearthguard 22 HP; Coin 22 after reward | | Kindhand | 11 | visible healing actions, including 11 authoritative heals | victory tick 133; Hearthguard 84 HP; Coin 21 after reward | The first actor tap focuses and the second commits exactly once. The other offer remains unhired. No slot selection or confirmation page is added; stable Company order remains system-owned. ## Presentation - On the returned Hall, two small Riftblade silhouettes stand near the departure gate with one short `Crosswind / contact + ranged` caption. - The existing Company remains the first focal read, remaining Recruits second, and the incoming threat third. - Recruit detail may state one strength and limitation, but may not become a panel or forecast exact test numbers in normal play. - Crosswind combat reuses the P9.3 field, actor scale, health bars, damage/heal floats, bounded VFX and pause/speed controls. - The result holds on the battlefield and the returned Hall visibly preserves the selected three-person Company and exact Coin. ## Evidence - dual-path domain test for entry state, exactly-once hire, authoritative role actions, terminal tick/HP, reward and returned Company; - parsed ScreenTouch runtime path through both alternatives with fallback/direct zero; - normal-render frames for returned threat, focused Wayrunner/Kindhand, both role actions, both results and both returned Hall states; - one source-bound H5 update after local runtime gates; - Owner comprehension, game-feel, listening, device and release remain separate.