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

P9.2 Owner Play Report

Status: OWNER_REJECTED_GAMEFUL_OPENING_REQUIRED Candidate: 48228b3843cd35e21adee3ec13d2a4bfcb41eeb8 Gallery item: 46Qn8t4v5HNw

Uncoached Questions

1. From the P9.1 result, was Continue: Breach Watch the obvious next action?
2. Could you explain why the two lines moved and stopped at contact?
3. Could you identify what each profession contributed from movement, HP and the event ribbon without outside explanation?
4. Did Pause, 1x/2x and Inspect behave as expected?
5. At tick 50, could you explain when continuing versus retreating was rational?
6. Did the result make outcome, cause, survivors/HP, reward/cost and next action clear?
7. What was the first confusing, unreadable, slow or weak-feel moment?
8. Would you voluntarily retry or continue after this encounter? Why?

Recorded Observation

On 2026-08-14 the Owner reached the P9.2 battle through the private H5 and reported that "the later part becomes garbled." The supplied 2048x1142 landscape screenshot shows every Chinese character as a missing-glyph box while digits and Latin x remain readable. This blocks all P9.2 comprehension and invalidates the current H5 as an Owner-play candidate even though its bundle is reachable.

Source inspection found that the existing embedded NotoSansSC.ttf and its imported font data are present in the Web PCK. The preserved P9.1 facade binds that font to its own nested theme, but the new P9.2 presenter mounts under the outer runtime root, which has no theme. P92-R1 is the one bounded Step 5 repair batch: inherit the same embedded theme at the outer root, add a Chinese glyph regression, re-export, and re-publish. Automated evidence cannot close the Owner's comprehension, fun, visual/control feel or willingness-to-continue gates after the repair.

Repair Handoff

Source 48228b3 now assigns the facade's existing embedded Noto Sans SC theme to the outer runtime root before P9.2 creates its presentation tree. The focused normal-render test asserts the exact embedded font at the outer root, P9.2 root and battle title, plus the required 裂 glyph. Five source-bound P9.2/P9.1 regressions and the focused normal run are strict-clean.

A browser then completed the real local Web path from Title through Recruit selection, all five preserved battles, route, training and into P9.2. Chinese rendered normally at the exact previously failed screen and browser warnings/ errors remained zero. Gallery item 46Qn8t4v5HNw is byte-identical to that local nine-file export and reaches the real Chinese Title remotely. The prior item GAbcudVktgvh remains historical and must not be used for replay.

Owner action remains unchanged: replay the new item without coaching and report the next first confusing, unreadable or weak-feel boundary. Automated repair evidence does not grant human acceptance.

Second Owner Observation

After the font repair, the Owner reported that the first several pages do not feel like a game and instead feel like an app. This is a product presentation failure, not a font or isolated styling defect.

The earliest failed boundary is immediately after Title: the experience becomes a parchment menu panel, then a briefing panel, four narrow Recruit cards and a formation confirmation panel. Most actions are reading, choosing and confirming inside rectangular UI surfaces while the world and characters are passive. The P9.2 Owner gate is therefore rejected. Successor Goal P9.2R must preserve the accepted selection/battle rules while moving the opening actions into one continuous Guild Yard scene.