aetherbound-guild/docs/runtime/p9_2/STEP_2_RUNTIME_EVIDENCE.md

P9.2 Step 2 Horizontal Runtime Evidence

Source: 2e2ed932f0b9a01b32208fcc548b5452a6eec6ea Step: P9.2-STEP-2 HORIZONTAL_BATTLE_RUNTIME Evidence level: runtime_verified plus supporting agent visual review

Focused Runtime Marker

ABG_P9_2_HORIZONTAL_BATTLE_RUNTIME_OK viewport=844x390 source=p9_1_result members=3 hp_import=true movement=true contact=true member_events=true enemy_events=true outcome=victory domain_bound=true

The focused run used a fresh isolated HOME/cache/TMP root, Godot 4.6.1 and Dummy audio. It exited zero with zero SCRIPT ERROR, parse/compile/resource, ObjectDB or cleanup markers.

The same source also passed:

ABG_P9_2_AUTHORITATIVE_BATTLE_DOMAIN_OK cases=93 actions=37
ABG_P9_1_FOUNDATION_ATOMICITY_OK success=76 rejected=28 exact_guild_ids=2 legacy_leaks=0
ABG_P9_1_FULL_FIRST_SESSION_OK paths=180 pairs=6 adaptations=2 guild=2 routes=3 growth=all exact_hp=true exact_coin=true formation=true level=true

Normal-Render Frames

One exclusive normal-render run at 844x390 produced five PNGs. They are temporary reviewer evidence, not Git source; the hashes are retained here.

State	SHA-256
01-entry.png	0182906f1df2944dc3678d51ba1e94d6634508a640bdbc305ebd7d7544830c63
02-advance.png	c42cd8ee9c285ea45d729efca0b27498f3344c7f854af4de7eb8202a6ebfa593
03-contact.png	11738b2555c47c2561e6872aff813c08aa082d33e83fa215537033de120badeb
04-actions.png	5fa4ce3ba2bf19c85c9d52fe0634869a9918d14d45836d8a808b0d79927b2cc6
05-victory.png	4e051eedb5d3f88150694709c3ab65e5b92a9d256a2ffa29cd8e68fa441dfb78

All five images are native 844x390 RGBA PNGs. They show the actual field background, three imported P9.1 members with end-session HP, two enemies, logical movement, contact, event action and victory. Actor nodes retain domain member/enemy IDs, logical positions and HP in runtime metadata; the event ribbon retains event index, kind and source/target IDs.

Boundary Notes

• P9.2 now has a real horizontal runtime path, but Pause, 1x/2x, Inspect, Retreat and terminal result controls are intentionally Step 3.
• The event ribbon is a deliberately wide central diagnostic strip in this step; HUD hierarchy and controls are the next bounded repair, not an excuse to add more encounters here.
• Human comprehension, fun, visual acceptance, listening, device, packaging, stores and release remain open.