docs: close first-play redesign candidate

This commit is contained in:
2026-08-12 21:29:33 +08:00
parent a534af9f7c
commit db75a17ce8
3 changed files with 39 additions and 1 deletions
+28 -1
View File
@@ -4,7 +4,7 @@ Active Goal: `docs/goals/PHASE9_0R1_GAME_OPENING_REDESIGN_GOAL.md`
Active contract: `docs/runtime/PHASE9_0R1_GAME_OPENING_CONTRACT.md`
Active ledger: `docs/reviews/PHASE9_GODOT_VERTICAL_SLICE_LEDGER.md`
Redesign baseline: `00b019543e571c89c20adaa97b4e805ecbd3e6f4`
Stage: `P9_0R1_GAME_OPENING_ACTIVE`
Stage: `P9_0R1_GAME_OPENING_CANDIDATE_READY`
Current P9.0R1 replaces the Owner-rejected form-like Web opening with one
scene-based flow: Title -> Guild Yard front/rear choice -> deterministic first
@@ -13,6 +13,33 @@ equipment/order configuration, persistence, chapter expansion, authoritative
combat, device packaging, TestFlight, stores and release remain frozen. The
older Phase 8/P9 history below is retained as provenance, not current scope.
Fixed clean/upstream source `a534af9f7cc477dc977f958a9f2a4bf26b40ab71`
passes the P9.0R1 domain, parsed ScreenTouch, layout, three-size normal-render
and dynamic-slice gates. Exact markers include `touch=15 fallback=0 direct=0`,
`fixtures=13`, 18 normal-render frames and a 584-frame/19.47-second battle
recording. Complete design, five-seed anti-dominance, one-slot/individual-level,
96-asset provenance and four identity-anchor regressions pass. Strict runtime
diagnostic markers are zero.
Authoritative ignored evidence is
`runtime/evidence/p9-0r1-a534af9-attempt02/`; its 50-row inventory SHA-256 is
`8dd3b7ece692dfcb7c37b5a51996dcfffc937014c59c97fda4a0f3e6b131d453`
and verifies 50/50. Attempt 01 is append-only
`INVALID_CONTROLLING_SESSION`; the first Web export is
`INVALID_EXPORT_ENVIRONMENT` because isolated HOME hid installed templates.
Neither was reused. The successful local Web bundle is at
`runtime/build/web-preview/a534af9/`, export-manifest SHA-256
`d9f688a4e8a927b15f794026c1c7fb13930f9b98e1e742ba433f6d2c30899636`.
Artifact Gallery runtime ID is `xOSqgKWpzqQt`; no share token is stored.
Remote HTTP/MIME/auth delivery is verified, while automated remote browser
control is `INVALID_PLUGIN_TIMEOUT` and makes no canvas-interaction claim.
Strongest proven level is `runtime_verified` plus `agent_visual_reviewed`.
Owner phone understanding, visual acceptance, fun, listening, physical device,
packaging, store and release remain open. Shortest next action: Owner opens the
new signed Gallery link on a phone in landscape and judges the complete
Title -> Yard -> battle -> first-expedition victory flow.
Historical portfolio baseline: `b3968b0f41f841efb0f699d8fb04a9bcb958182a`
Accepted P8.1 source: `0b4a64fe549af0ff965e654aa4f5fb7f2ff054b4`
P8.2 candidate source: `86a8a1adec39de40b4adfee6b01033407e3e3421`
@@ -1,5 +1,15 @@
# Phase 9.0R1 Game Opening Redesign Goal
Status: `CANDIDATE_READY`
Candidate source: `a534af9f7cc477dc977f958a9f2a4bf26b40ab71`
Authoritative evidence: ignored local
`runtime/evidence/p9-0r1-a534af9-attempt02/`. Attempt 01 is retained only as
`INVALID_CONTROLLING_SESSION` and was not reused. Owner comprehension, visual,
fun, listening, physical-device, packaging, store and release gates remain
open.
## Owner Decision
The Owner rejected remote Web source `f0aa84738041cebf4968d91c6bf170668804e203`.
@@ -13,3 +13,4 @@ separate.
| 2026-08-12 | Web source `f0aa847`; Gallery item `PRji-yhJo0nQ`; `p9-0-web-f0aa847-attempt01` | `P9_0_REMOTE_WEB_READY` | Private signed item redirects to the full-screen runtime entry with an artifact-scoped HttpOnly cookie. Remote HTML/JS/WASM/PCK response types and executable CSP pass; unauthorized entry remains gated. Chrome phone-viewport verification reaches the Chinese Title and Contract by real canvas input, portrait shows the rotate overlay, and browser warnings/errors are zero. Final evidence inventory verifies 34/34 with SHA-256 `cb3111f86012d313c85d1eebed6574b8b5936531bf30821421f89f1442aeb945`; the signed token is not recorded in Git. Owner phone comprehension, fun, listening, physical device, packaging, store and release remain open. |
| 2026-08-12 | Owner remote H5 playtest of `f0aa847` | `P9_0_OWNER_REJECTED_REDESIGN_REQUIRED` | Earliest product failure is the first post-Title action: the runtime reads as a configuration form rather than a game. There is no visible in-game restart/home path; Contract, First Market, provisional two-of-four selection, two later forced hires, equipment/order revision and the stopping point are not understandable without coaching. Engineering labels and receipt language are exposed as if they were chapter content. The current H5 is retained only as a problem reference. P9.0/P9.1 are not Owner-accepted; P9.2, content expansion, packaging and release remain frozen. A successor must compare structural onboarding options and reach a short encounter before advanced preparation systems. |
| 2026-08-12 | Owner authorization for opening redesign | `P9_0R1_GAME_OPENING_ACTIVE` | Owner authorized a full first-play and UI redesign. The active slice is Title -> scene-based two-position Company choice -> deterministic short battle -> explicit first-expedition victory, with always-visible Home/Restart. Contract, difficulty, paid Market hire, equipment/order configuration, persistence, chapters, later combat, packaging and release remain frozen. Existing accepted Japanese hand-painted environment, character, Riftblade and VFX assets are reused before any new generation. |
| 2026-08-12 | fixed source `a534af9`; `p9-0r1-a534af9-attempt02`; Gallery `xOSqgKWpzqQt` | `P9_0R1_GAME_OPENING_CANDIDATE_READY` | Fresh isolated archive passes domain routes=2, parsed ScreenTouch `touch=15 fallback=0 direct=0`, 13 layout fixtures, 18 normal-render frames across 1280x720 zh_CN, 844x390 zh_CN 130% and 390x844 English, and a 584-frame/19.47-second normal-render dynamic battle with advance, front response, rear action, enemy defeat and one victory. Complete design, five-seed anti-dominance, one-slot/individual-level, 96-asset provenance and four identity-anchor regressions pass; strict markers are zero. The 50-row evidence inventory SHA-256 is `8dd3b7ece692dfcb7c37b5a51996dcfffc937014c59c97fda4a0f3e6b131d453` and verifies 50/50. Attempt 01 remains `INVALID_CONTROLLING_SESSION`; Web export attempt 01 remains `INVALID_EXPORT_ENVIRONMENT`; neither was reused. Local Web export manifest SHA-256 is `d9f688a4e8a927b15f794026c1c7fb13930f9b98e1e742ba433f6d2c30899636`; remote HTML/JS/WASM/PCK MIME/auth delivery is verified. Automated remote browser control is `INVALID_PLUGIN_TIMEOUT`, so no remote canvas interaction claim is made. Agent visual review passes; Owner phone understanding, visual acceptance, fun, listening, physical device, packaging, store and release remain open. |