40 KiB
Current Checkpoint
Active Goal: docs/goals/PHASE9_1_ARBITRARY_PARTY_FIRST_SESSION_GOAL.md
Active contract: .agent-taskgraph/spec.md revision p9.1-spec-r1 until expert integration freezes docs/runtime/PHASE9_1_ARBITRARY_PARTY_FIRST_SESSION_CONTRACT.md
Active ledger: docs/reviews/PHASE9_GODOT_VERTICAL_SLICE_LEDGER.md
P9.1 TaskGraph batch: abg-p9-1-continuous-development-01
P9.0R5 baseline: 6ae33971451912b3cc87c8ffe3b8831fa67c967c
P9.0R5 product preview source: 073ff690ea5a27cb47ee1b563c3eebd6cde9e788
P9.0R4 baseline: 232e3a0a45ec2437ddd528502d487d5264f1c6ae
P9.0R4 product preview source: e895c42e83950acf141470629f4a8c4a3fde67e2
P9.0R4 test-metadata closure: 365af5429ba6b4c3e2179c7a8ae6c70de7aeb774
Animation repair baseline: db75a17ce8b0a3bc702ad535fa16491debf582e4
Fixed product source: 425fae82d3d88a002bdaadeabb498d8bf0d069cd
Battle-feedback behavior commit: 3b26b3d671ae7d043ab4bfcbd8b31e77df6d6d0d
Battle-feedback baseline: be17debf4ed3ebe5c3e6de2701d5e3c374de1dcb
P9.0R6 baseline: c064fb2344fdbf9e95e18b8e1073844ce4d1f212
P9.0R6 product preview source: 3620e5a7cf6b762fefc3eb92d72b465c8bb209eb
P9.0R6 Gallery item: iS4R4BKNLQr1
P9.0R7 baseline: 89ed89b2a5b45ee5ab10c989736f2d8c65ea88dd
P9.0R7 product preview source: b7d50af403d3fe5d3fcc92943bc21d1d1748ae3d
P9.0R7 Gallery item: REs3L6178z7p
P9.0R8 baseline: d008c792ee8bc819fd642533a386cc54f85ce36d
P9.0R8 product preview source: 3bed822dc1e69ed9a5f05c87d1931eaadaf9bd7d
P9.0R8 Gallery item: Fb1N2BuvoC7f
P9.0R9 baseline: d4b56e69c1f311441d7d02e4ecdf5307a2e6f093
P9.0R9 product preview source: 079338612c0146ca19dc7bd2f18942807ec1cacf
P9.0R9 Gallery item: KpgLxlVQlBp6
P9.0R9A baseline: 1ce563b401dc9d6091ea54044cac6a838c27c283
P9.0R9A product preview source: 32b4fdb
P9.0R9A Gallery item: VL8pU8RUhXNn
P9.0R10 baseline: d8b359a12f5641257c549894a8114245fa987962
P9.0R10 product preview source: 41204acafa911a505f5b24a493aa032983e706d1
P9.0R10 Gallery item: gHS8jEZdGa2x
Stage: P9_1_EXPERT_SPEC_WAVE_PENDING_DISPATCH
P9.1 owns the next bounded runtime milestone. It must preserve P9.0R10 and carry all six legal starting pairs through the existing five-battle first-session shape with truthful Guild response, route, growth and final-result behavior. The first wave is specification-only: game design, UX/visual design and runtime architecture work in disjoint files, then PMO freezes one implementation contract. No runtime implementation may begin before that integration gate. Chapters, bulk content, authoritative full combat/economy/save, paid media, packaging, devices, stores and release remain frozen.
P9.0R10 owns the next compatibility boundary after automatic formation. All six
legal two-Recruit pairs must receive a truthful first-Victory diagnosis, choose
the preserved safety or tempo loan without a default, show the actual second-
member behavior in battle two, and reach a causal second result. The exceptional
Hearthguard/Wayrunner path must retain the Runner flank counter instead of
falling through to healing. R10 stops at the second-result page; later R5-R7
systems, save/content/release scope and authoritative combat remain frozen.
Clean/upstream source 41204ac now carries all six pairs through truthful
first-Victory diagnosis, the unselected safety-versus-tempo loan and the second
result. The 12-path matrix passes exact HP 90/100 versus 70/82, times
7.05/6.00, Coin 20, ranged/healing/flank-counter identity and exceptional-
pair Home cleanup. Parsed touch reports touch=5 fallback=0 direct=0; the
serial R1-R10 run passes 22 tests with strict markers zero. Eight 844x390
normal-render states pass 44px bounds after repairing an English-130% overflow.
The fixed-source runtime-only Web build is
runtime/build/web-preview/41204ac-r10-fast/; export.sha256 digest is
7aef140b95d4c5d5bcc5c5815f4ae02894ee49367a6fbeb87dc07915d258f859.
PCK inventory is 227 files with forbidden paths zero; Gallery item
gHS8jEZdGa2x serves a byte-identical PCK and reaches the corrected Chinese
Title with browser diagnostics zero. Remote cold start remains about four
minutes. Shortest next action: Owner plays the new H5 and judges whether every
pair's result and safety-versus-tempo choice are understandable and worth
continuing.
Owner review rejected the R9 interaction boundary: players should select two people, not manually perform separate front and rear slot selection. R9A owns one unified four-Recruit page, selection/cancellation up to two people, system- assigned field order and one review/commit. All six unordered two-person pairs must enter the first battle. The preserved R9 H5 remains historical review evidence.
Clean/upstream source 32b4fdb now implements one unified four-Recruit page.
The player may select or remove any person until exactly two are chosen; a
third unselected card becomes disabled at capacity. Selection order never
determines position. The system consistently orders Hearthguard, Wayrunner,
Farstring and Kindhand by field priority, then shows the assigned lead and
second member on review with one unified Revise command.
The focused matrix passes all six unordered pairs in both click orders, both
exceptional structures (Hearthguard/Wayrunner and Farstring/Kindhand), Victory,
exactly-once commit and Home/Restart cleanup. Parsed ScreenTouch reports
touch=11 fallback=0 direct=0. The complete three-battle touch path and R1-R8
standard-pair gameplay, animation and audio regressions pass; an intermediate
R3 qualifier wording failure was corrected by restoring the accepted standard-
pair string and the fresh rerun passes. Ten normal-render 844x390 states cover
zero/one/two selections, capacity, both exceptional reviews/battles, English
130% and Restart with 44px controls and clean final diagnostics.
The fixed-source runtime-only Web build is
runtime/build/web-preview/32b4fdb-r9a-fast/; nine payloads verify against an
export.sha256 whose SHA-256 is
20785617bccb3ee646f41cbd3c576757e626ccce9cd8c2c63cd2845be4fb99c2.
Gallery item VL8pU8RUhXNn serves correct remote MIME/length and a byte-identical
PCK. Shortest next action: Owner checks whether choosing any two people and
seeing the automatic order now feels natural; later-system support for unusual
pairs remains a separate module.
P9.0R9 replaces only the first New Game onboarding boundary. New Game opens a mission briefing, then separate front and rear Recruit selection pages, then a formation review. The player learns the role of Hearthguard, Wayrunner, Farstring and Kindhand in plain language, may revise either slot, and commits exactly once into the preserved first battle. No Recruit is preselected. Combat values, post-battle flow, formal Market, persistence, chapters, packaging and release remain frozen.
Clean/upstream source 0793386 now implements the complete first Company
module. The first mission names the Riftblade threat and what to observe; the
front and rear pages show only the two relevant roles with no preselection;
formation review composes both selected members and allows either slot to be
revised before one commit into the preserved first battle.
The fast gate passes four legal front/rear combinations, two invalid-slot
boundaries, reversible front/rear choices, preserved Back, exactly-once commit
and Home/Restart cleanup. Parsed ScreenTouch covers the full revision path with
touch=15 fallback=0 direct=0; the complete three-battle touch regression now
enters through the R9 flow. R1-R8 gameplay, character-animation and audio-
lifecycle regressions pass. Eight normal-render 844x390 states cover Chinese,
English/130%, disabled actions and Restart with 44px controls and zero strict
runtime diagnostics. The fixed-source runtime-only Web build excludes tests,
evidence and build source; its nine files verify against export.sha256 whose
SHA-256 is 41145503d8e7b75cf0bc4e598fa7e446ca1deba4bcc97d2d66b39f66ba642308.
Private Gallery item KpgLxlVQlBp6 serves correct MIME/length and a remote PCK
byte-identical to the local export. This remains a fast preview, not a formal
candidate. Shortest next action: Owner plays New Game -> first mission -> both
role choices -> review -> battle and judges whether the formation decision is
understandable before the next module opens.
P9.0R5 preserves the complete real Title-to-second-result P9.0R4 path and owns
one Guild return decision plus a third battle. From 20 Coin, the player either
retains the learned item for 12 and keeps Company 2, or recruits the missing
rear for 14, returns the loan and reaches Company 3. The third encounter
must visibly use the retained item or added rear and end with exact causal
Coin/Company/HP/time facts. Formal Market, inventory, save, chapters,
authoritative combat, packaging and release remain frozen.
Clean/upstream source 073ff69 now implements the complete real
Title -> Yard -> battle 1 -> diagnosis -> loan -> battle 2 -> Guild return -> retain item or recruit missing rear -> battle 3 -> session result path. The
Guild decision is unselected and reversible until commit; retain spends 12 and
ends at Coin 8 / Company 2, while recruit spends 14, returns the loan and ends
at Coin 6 / Company 3. All six initial rear/item/response combinations win with
the declared 7.60/6.60/7.00 timings and exact front HP outcomes.
The bounded fast gate passes focused transaction/routes, one complete real
parsed-ScreenTouch path from Title (touch=11 fallback=0 direct=0), P9.0R4 and
P9.0R3 regressions, and six normal-render 844x390 Chinese states with 44px
control bounds. Strict runtime diagnostics are zero. The runtime-only Web
projection excludes tests/evidence/build and is published as Gallery item
XnBQy0rhoJHh; signed delivery, MIME/bytes and normal-GPU remote Title launch
pass. This remains fast preview evidence, not a formal candidate. Cold start is
still roughly one minute because the 53 MB Web bundle is delivered without
compression.
On 2026-08-13 the Owner accepted the full first-session preview and authorized
continued development. Clean/upstream source 3620e5a now completes the
smallest strategically different next cycle: three neutral connected-map
routes whose coverage changes with retained EQ-002, retained EQ-061, or
the three-person line; one explicit review and route commit; one fourth
automatic battle; and one causal second-cycle result.
The fast gate passes 18 route/profile/original-rear outcomes, parsed
ScreenTouch touch=8 fallback=0 direct=0, all declared P9.0R3-R5 regressions,
and nine 844x390 Simplified-Chinese normal-render states with 44px bounds and
zero strict runtime diagnostics. Runtime-only PCK scope excludes tests,
evidence and build content. Local and remote normal-GPU Chrome both reach the
real Chinese Title with zero browser warning/error logs. The ignored delivery
is runtime/build/web-preview/3620e5a-r6-fast/; its export.sha256 digest is
9fb846f795bca1cd729e884d8e5d8fee6be001299425384cf3590571fb6fc5bf.
The new private Artifact Gallery item is iS4R4BKNLQr1 and does not overwrite
P9.0R5. Cold start remains slow because the 53 MB Web bundle is uncompressed.
This remains fast preview evidence, not a formal candidate. Shortest next
action: Owner plays one covered and one gap route and judges whether inherited
build -> route pressure -> consequence is understandable and worth another
cycle.
The Owner reviewed the P9.0R6 delivery and requested a larger continuation.
P9.0R7 now owns the next incremental layer only: the verified R6 result grants
one individual training decision; the player raises exactly one actual Company
member from Lv.1 to Lv.2; a fifth encounter applies both front and original-
rear pressure; and the third-cycle result exposes the selected role's survival,
tempo or recovery consequence plus one-time +8 Coin. Authoritative XP,
promotion, Market, Party order, casualty/recovery, persistence, chapters and
release remain frozen. Bounded R7 implementation and its fast H5 gate are now
complete at the fixed product source below.
Clean/upstream source b7d50af now implements that complete R7 path. Training
opens without a preselection, shows only actual Company slots, supports revise
and review cancel, and raises exactly one selected member to Lv.2. The fifth
battle visibly distinguishes front mitigation (90/75 HP versus 70/55), a
Farstring's single earlier shot (6.40s versus 7.40s), and Kindhand recovery
(85 rear HP versus 72/60), then commits +8 Coin once.
The fast gate passes the R7 domain matrix, parsed ScreenTouch
touch=8 fallback=0 direct=0, all declared R3-R6 regressions, and eleven
844x390 Simplified-Chinese normal-render states with 44px controls and zero
strict runtime diagnostics. The fixed-source runtime-only PCK excludes tests,
evidence and build content. Local and remote Chrome reach the real Chinese
Title with browser warning/error logs empty. The ignored delivery is
runtime/build/web-preview/b7d50af-r7-fast/; its export.sha256 SHA-256 is
6a2b04e823da55af21b658d1d96bf3faf969849496cdabe077770ca0fa55066e.
The new Gallery item is REs3L6178z7p. Cold start remains slow because the
roughly 53 MB bundle is uncompressed. This remains a fast preview, not a formal
candidate. Shortest next action: Owner plays to the training scene and judges
whether survival, tempo and recovery are understandable, meaningfully
different and worth another cycle.
Owner-directed modular development opened P9.0R8 from clean/upstream
d008c79. Clean/upstream source 3bed822 now separates resource verification,
visual Title and Main Menu; the menu contains only Start New Game, Game
Introduction and Settings. Introduction explains formation, automatic battle,
post-battle adaptation and route/member growth. Settings names language, text
size, motion and sound with live values. No fake Continue or Load appears while
save is absent. Home and confirmed Restart clear transient state and return to
Main Menu; New Game is the only route into the preserved Guild Yard.
The fast gate passes R8 domain/navigation, parsed ScreenTouch
touch=10 fallback=0 direct=0, P9.0R1-R7 regressions, and six 844x390
normal-render states including English 130% Settings. The fixed-source PCK
excludes tests/evidence/build. Local and remote Chrome reach the new Chinese
Title with browser diagnostics empty. The ignored delivery is
runtime/build/web-preview/3bed822-r8-fast/; its export.sha256 SHA-256 is
5012b7e90726b332f0597f65a576816dad2b25e05a52b0f106db54de2c2f84ba.
Gallery item Fb1N2BuvoC7f is new. Remote cold start took roughly three minutes
because the roughly 53 MB bundle remains uncompressed. Shortest next action:
Owner reviews Title -> Main Menu -> Introduction -> Settings -> New Game and
judges whether the product front door is understandable before another module
opens.
P9.0R4 Fast-Preview Baseline
P9.0R4 owns only the first-result diagnosis, the existing B0/R1/Q0 Steady
+20 Coin payout, one unselected choice between run-local loaned EQ-002 and
EQ-061, and one second tutorial battle whose survival/time consequence is
visible. The accepted first battle remains unchanged. Market, permanent
inventory, Party order, casualty/recovery, persistence, chapters, authoritative
combat, packaging and release stay frozen.
The fast gate on clean product source e895c42 passes second-cycle behavior,
real parsed ScreenTouch (touch=4 fallback=0 direct=0), preserved P9.0R1
domain, preserved P9.0R3 feedback and five normal-render 844x390 Simplified-
Chinese states. It proves Coin=20 once, no preselection, reversible choice,
commit lock, safe HP 90/100, fast HP 70/82, declared time 7.05/6.00, and
cleanup. Strict product/runtime diagnostics are zero.
The nine-file 53 MB Web preview is published as Artifact Gallery item
qpgmCKQMz1TS. Remote signed delivery, MIME types, Godot cold load, Title
rendering and zero browser warning/error logs pass. This remains a direction
preview, not immutable candidate evidence. Cold load took roughly one minute
because the delivery serves a 37.7 MB WASM and 17.1 MB PCK without gzip or
brotli and with only Cache-Control: private, max-age=300; delivery optimization
is open but does not invalidate gameplay.
Only after Owner direction acceptance run the complete candidate regressions, matrices, both route recordings, immutable inventory, PCK/browser and final Gallery gates. Shortest next action: Owner plays both P9.0R4 loan routes and judges whether the cause -> adaptation -> changed second battle is clear.
P9.0R3 Owner-Accepted Baseline
Fixed clean/upstream source 425fae8 tightens the six-phase automatic battle
from the prior 13.50 seconds to 7.25 declared / 7.33 rendered seconds.
Every committed HP delta emits exactly one signed animated payload for block,
evasion mitigation, ranged damage, healing, combo and finisher feedback. The
existing HP results, victory, roles, authored animation assets, Title/Yard flow
and Home/Restart behavior remain unchanged.
Authoritative ignored evidence is
runtime/evidence/p9-0r3-425fae8-attempt04/. Its 65-row content inventory
SHA-256 is d1040cec77d3cc63e8322c63d2df5dcc6ee88c35ab04329d52f6687c5529720a
and verifies 65/65. Three viewport profiles cover all six feedback states;
two 1280x720, 30 fps H.264 recordings each run 15.233333 seconds and
retain the visible victory screen rather than teardown frames. PCK scope
excludes tests/evidence and includes the real VFX and five representative
action resources. Local Chrome reaches Title -> Yard -> battle -> victory with
zero browser diagnostics; portrait shows the rotate prompt. The clean
nine-file Web bundle is runtime/build/web-preview/425fae8-r3/, manifest
SHA-256 d48922ed4892e15057284275e237d6ef35dd77201a2c67efd170e870c98225bb.
Final Artifact Gallery runtime ID is _N8bdzMkdn1c; no share token is stored.
Attempts 01-03 remain append-only invalid history for recording teardown,
forced audio exit and isolated export-template visibility respectively; none
was reused. Strongest proven level is runtime_verified plus
agent_visual_reviewed. On 2026-08-13 the Owner played the signed Gallery
build and explicitly accepted this version's battle cadence, character motion
and event-bound feedback. That bounded direction is now human_reviewed and
frozen. Listening, broader fun/continuation, physical device, packaging, store
and release remain open. Shortest next action: define a bounded successor that
turns the accepted first victory into one readable adaptation and a visibly
different second battle.
P9.0R2 Accepted Automated Baseline
Owner review rejected the P9.0R1 battle motion because whole static images
were translated and bobbed instead of characters changing body and limb poses.
Fixed clean/upstream source 6c72e24 preserves the accepted Title, Yard,
front/rear choice, battle layout, victory, Home and confirmed Restart while
replacing static-actor motion with 92 authored frames across 20 states. Five
actors visibly change body and limb poses; damage and healing commit exactly
once at impact frames, and Riftblade death holds its final frame.
Authoritative ignored runtime evidence is
runtime/evidence/p9-0r2-6c72e24-attempt02/. Its pre-Web 44-row inventory
SHA-256 is e92e2f7e1897cb8723f886cb463f878455ddc24a294000328170e17c8edd1e1a
and verifies 44/44. Two 1280x720 H.264 recordings each run 19.466667 seconds
and cover Hearthguard/Farstring and Wayrunner/Kindhand routes. Attempt 01 is
append-only INVALID_MOVIE_OUTPUT_PATH and was not reused.
The clean replacement Web bundle is
runtime/build/web-preview/6c72e24-r2/; its nine-file manifest SHA-256 is
04f655e9ba23e11c21fb1f4d1c7873459d003f0db07964106bc2e93bb3c46483.
PCK scope proves that tests and evidence are absent while all five actors'
representative action frames are present. Artifact Gallery runtime item
pPeYCfGUlBjV reaches the remote Title without browser diagnostics. The share
token is intentionally not stored in Git.
The prior P9.0R1 source and evidence below remain append-only history. Its
agent_visual_reviewed animation conclusion is superseded by Owner feedback.
Economy, equipment, chapters, persistence, authoritative combat, packaging
and release remain frozen. Human visual/fun/understanding remains open.
Historical P9.0R1 Candidate
Current P9.0R1 replaces the Owner-rejected form-like Web opening with one scene-based flow: Title -> Guild Yard front/rear choice -> deterministic first battle -> explicit first-expedition victory. Contract/difficulty, paid Market, 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
Accepted P8.2 closure: d308f8bc14b043ed133ce2d99cbce461aecec81f
Rejected P8.3 source: 5f0cb2695ba149b1efcab27a882ade00a275c6ac
P8.3 documentation closure: fab5eebf4260ab3da42dee8abe63dd7b7588789b
P8.3R1 candidate source: 169e3877fa262da3db7495d61bc77ce061704ae7
P8.3R1 documentation closure: 5f4e4cdadee6e0f6a457ab57a55964f7fd4c38a5
P8.3R2 candidate source: 02eb1e64ad54978b0c04dd9da59c7ed7eb941a87
P8.3R2 candidate closure: 0818c60dcdde3f84ddbd57b0bc81a787e9915e08
Stage: P8_3R2_OWNER_ACCEPTED_P8_4_ACTIVE
The Phase 6 battle, VFX and equipment direction is Owner-accepted. Phase 7 turns the existing 50-screen design inventory into an individually viewable, Chinese-first, production-oriented landscape HTML atlas. Runtime, engine, audio, bulk asset production, device, package and release work remain frozen.
Strongest evidence: fixed-source static design validation, exact
asset-provenance checks, browser interaction and responsive-layout
verification, offline self-contained bundle verification, and agent visual
review. The Phase 7.1 candidate evidence is ignored local evidence at
prototype/gallery/evidence/r7-1-candidate-e23b00b-attempt01/. Its browser log
SHA-256 is
b735e2218321b4452e3ea2a49b0e03d6c2f568cd218fb15f340d9fe635453441;
the 23-row inventory SHA-256 is
a169dbdc4d03eb00a6ffffc447d035cf5cb0a423422af9060d4eaff81d0b2706
and verifies 23/23 from its evidence root. The self-contained HTML bundle
SHA-256 is
64dbe54f94e66d0bff6bcdf17f5852c5c77c8b56b25eef8f30068ab9198f8176.
Phase 7.1 remains the accepted automated design baseline: every Recruit has one active equipment slot and individual run-scoped level/XP capped at level 10. The Owner has authorized Phase 8 as five separately playable experience packages. On 2026-08-12 the Owner reviewed the published P8.1 Contract and receipt flow and explicitly accepted it. P8.2 Market Preparation is now the only active package; P8.3-P8.5 and Godot/runtime development remain frozen.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-1-candidate-0b4a64f-attempt01/. Its nine-file
inventory verifies 9/9 with SHA-256
b076e5990aadb5e2b72ed979e27403a294c17b342c9bbadbad63b460c7fd60f3.
The P8.1 browser log SHA-256 is
c7e9a7278cb99881b51715bc25e3bd3112293ad282b63bc8449c1150653f6729;
the Phase 7 regression log SHA-256 is
af5eb0616e7dc1061f702d392952419701a93b6452475d626fac490d5c8f3aae;
the self-contained bundle SHA-256 is
e5895441d2835a22e9f94d6615c95be7180b7df6983c4611b499efc730feb915.
P8.2 uses the authority price formula rather than the obsolete Phase 7 sample:
each level-1 base Recruit costs 14 Coin, so two separate hire receipts move the
opening balance 52 -> 38 -> 24 and Company 2 -> 3 -> 4 while Line capacity
remains four. It then owns one equipment transaction and one tap-select/tap-
destination order change, stopping before Risk. Fixed clean/upstream source
86a8a1adec39de40b4adfee6b01033407e3e3421 passes the complete P8.2 browser
chain, P8.1 regression, complete Phase 7 browser regression, design validation,
anti-dominance, single-equipment/individual-level and asset-provenance gates.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-2-candidate-86a8a1a-attempt01/. Its 42-row
inventory verifies 42/42 with SHA-256
d41bed33f982b6504f91aaa6830d2ce09422d9b5dbbd70cfdf7c46d08f5b053e.
The P8.2 browser log SHA-256 is
5eab37da40298740b76f598701b983a53584abef4f61e1f0c43bf3210a69d0a6;
the P8.1 regression log SHA-256 is
564964d31a0bb1cf4c2f8ccb3611c8c94863d4f331d67e238851112773016f20;
the Phase 7 regression log SHA-256 is
55616bf1325da8bce24fbe6d52adf002382ee37cd4ce0e7e780b0f0696b53d2f;
and the self-contained bundle SHA-256 is
96751234e01a2c3c66fc4065be2db20517efd50abf0ced18075676ec42080251.
On 2026-08-12 the Owner reviewed the published P8.2 experience and replied
OK. P8.2 comprehension and visual direction are accepted for progression.
P8.3 is the only active package: compare three risks, commit one, observe a
bounded automatic battle, pause/change speed and inspect one causal event.
P8.4-P8.5, authoritative battle simulation, Godot/runtime, audio, device,
packaging and release remain frozen.
Fixed clean/upstream P8.3 source
5f0cb2695ba149b1efcab27a882ade00a275c6ac passes the three-risk selection,
single commit, frozen opening, six-event automatic presentation, pause/speed,
read-only causal inspection and result-withheld terminal gates. It also passes
P8.1/P8.2 and complete Phase 7 browser regressions plus unchanged design,
anti-dominance, single-equipment/individual-level and asset-provenance gates.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-3-candidate-5f0cb26-attempt01/. Its 53-row
inventory verifies 53/53 with SHA-256
3ad48cfa135a29f01f75ed69dc07f6a2037fbf984c3d94b7cae21da2199af1c8.
The P8.3 browser log SHA-256 is
f34ec892e12dfd5022182de2b5f3f68687a77e1066a78aa2fe8e81bdd3ea7e21;
the P8.2 regression log SHA-256 is
3139beb66a7f265a40c29e02518ad63ffa802bb10f9ab819cb62cf7e39060747;
the P8.1 regression log SHA-256 is
c38118d8b66bb1270e625586f5d9ae77af85ae60ae0c1ab88631a2f764fc6a8b;
the Phase 7 regression log SHA-256 is
b2b8329301b944af8a9301da4a4c493007730f66a310e6942de67ba00a3343c8;
and the self-contained bundle SHA-256 is
5989cb87c5e422d26bd1cdc5d2e74db4177090b32540d1cb53b77560bec943e9.
Owner review rejected the prior P8.3 battle presentation because static unit cards and the central event explainer made it read as a timeline board rather than an animated horizontal automatic battle. P8.3R1 is bounded to rebuilding that battle presentation around one continuous ground line with visible advance, attack, projectile, intercept/Guard, hit and sustain motion. The accepted P8.1/P8.2 behavior and the P8.3 risk/commit/event/result boundaries remain unchanged; P8.4 remains locked.
Fixed clean/upstream P8.3R1 source
169e3877fa262da3db7495d61bc77ce061704ae7 replaces the rejected static-card
battle with one continuous horizontal arena. It uses 62 byte-identical accepted
motion-proof frames for the Hearthguard and Riftblade identities, preserves the
other three Recruit identities with explicitly prototype-only motion transforms,
and visibly presents advance, equipment retarget, attack, projectile, Guard/
intercept, hit and sustain states. Pause freezes event and sprite-frame motion;
1x/2x/4x changes presentation speed only.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-3r1-candidate-169e387-attempt01/. Its 64-row
inventory verifies 64/64 with SHA-256
336a6e1757470648d269c2206834fc95df2bc67013315d50c1a185cf1fac5b06.
The P8.3R1 browser log SHA-256 is
d86fb7527efc89a9c764ce94a818e71696406c9f9c9c70e54dc0d8ac18d0ea63;
the self-contained bundle SHA-256 is
c8d57710162a928dea583b54786afc58e61ec2d80aa8a546d01259a06d4cd717.
Supporting motion evidence is the 8.76-second 1280x720 WebM at
prototype/gallery/evidence/p8-3r1-motion-review-169e387-attempt02/ with
SHA-256 55f7389afb08efa3a7e7b61b38618a1ffa6f4f850a533d8107bfba27944cdb3a.
Owner review rejected P8.3R1 because the units animated in fixed positions but did not visibly advance to collision, stop at contact, preserve a rear healer and ranged attacker, or replace a fallen frontline footprint. P8.3R2 is the only active repair. It must bind visible geometry and HP changes to one state chain: two-sided entry, collision stop, post-contact melee, Kindhand healing an injured ally, Farstring attacking from the rear, a separately labeled PF-B06 spell-language demonstration that does not add a fifth Company member, and one no-respawn frontline replacement. Victory/defeat, formal casualty, reward, recovery and P8.4 remain frozen.
Fixed clean/upstream source 02eb1e64ad54978b0c04dd9da59c7ed7eb941a87
passes the P8.3R2 browser chain from an isolated Git archive. Both formations
enter from opposite sides; one explicit contact line stops melee translation;
Wayrunner/Hearthguard act after contact; Kindhand raises Mael from 72 -> 88
HP from the rear; Farstring lowers a legal rear target from 100 -> 72 HP; an
enemy-side PF-B06 demonstration uses distinct charge/bolt/impact language;
and a zero-HP front stays down while the next living enemy advances to the same
contact footprint without respawn or Reserve entry. Pause freezes position,
event, frame and projectile time; 1x/2x/4x changes presentation speed only.
Attempt 01 is retained append-only as INVALID_AUDIT_COMMAND because its
inventory verifier ran from the wrong directory after all product commands.
Fresh attempt 02 is authoritative at
prototype/gallery/evidence/p8-3r2-candidate-02eb1e6-attempt02/. Its 68-row
inventory SHA-256 is
179b4ed720ac9d6e1da8e9955096572572c44528909fa4a38c280dc901b62d79;
the P8.3R2 browser log SHA-256 is
730a07358c1353ab80ab0509fee1e2694efae68d14f5cfe31b629e5ec2950ff4;
and the self-contained bundle SHA-256 is
bd73e97c48fb967ce638d252ae2eecf6f3d5342afaef7e5c2640074fb1882e81.
The continuous 10.96-second 1280x720 motion review is at
prototype/gallery/evidence/p8-3r2-motion-review-02eb1e6-attempt01/, WebM
SHA-256 69fb297fc3f0b3d6d0cc77439382c1f785eb17897122daf57ac280f4aa39b5d6.
P8.1/P8.2, the complete 50-screen atlas, design counts, anti-dominance,
single-equipment/individual-level and 96-asset provenance regressions pass.
On 2026-08-12 the Owner reviewed the published P8.3R2 experience and replied
好可以了. This accepts the visible frontline behavior and comprehension
boundary for progression to P8.4. It does not grant final animation, audio,
authoritative combat, Godot/runtime, device, packaging or release acceptance.
P8.4 Result and Recovery is now unlocked but has not started. It owns only the visible victory/defeat diagnosis, permanent casualty, reward, replacement and next-Market handoff defined by Phase 8. P8.5 and all production/runtime/release work remain frozen.
P8.4 fixed source f1488655ac677fc8260779a27f0628347e4d6920
is pushed clean/upstream and passes fresh fixed-source attempt 02. The
interactive package now proves diagnosis-first result reading, one permanent
Ilya casualty, exact 14 Credit and returned EQ-014, a stable independent
reward choice, three independent recovery responses and a choice-derived next-
Market ledger. P8.1-P8.3R2, the 50-screen atlas and all current design/economy/
loadout/provenance regressions pass.
The authoritative ignored evidence is at
prototype/gallery/evidence/p8-4-candidate-f148865-attempt02/. Its 75-row
inventory SHA-256 is
cd11540e6ea76cb5882d8318e8a4f79dbd899b8c25fcd1ee512742efbc95ff34
and verifies 75/75. The P8.4 browser log SHA-256 is
af5ef09e3e97d57f386eb8608dbe0f91d685589710613d2c821a00d6054f4d62;
the self-contained bundle SHA-256 is
19a1431b46152d90f08361bcc56b9c14099a3bcbfe429ea716780ba1a2c15eb2.
Fixed-source attempt 01 remains INVALID_AUDIT_COMMAND and is not reused.
On 2026-08-12 the Owner reviewed the published P8.4 experience and replied
OK了. P8.4 comprehension, visual direction and choice flow are accepted for
progression. This does not grant human fun, authoritative combat/save, final
media/audio, Godot/runtime, device, packaging, store or release acceptance.
Stage: P8_4_OWNER_ACCEPTED_P8_5_ACTIVE
P8.5 fixed source f1e93aa453406c6826b4758dc72d9c5520324ae9 is
pushed clean/upstream and passes fresh isolated-archive attempt 02. The
?package=p8-5 prototype joins the accepted opening, Market, risk, dynamic
battle, result and recovery across two consequential cycles. Ilya's casualty,
returned EQ-014, AR-043 and Credit-funded Vela are inherited; the Owner then
decides whether Vela equips EQ-014 before choosing between Open Span and
Needle Rain and observing a distinct second dynamic battle.
The authoritative ignored evidence is at
prototype/gallery/evidence/p8-5-candidate-f1e93aa-attempt02/. Its 21-row
inventory verifies 21/21 with SHA-256
d7786c48b1b83b56cbc13f2d51970122307e19aeaf0a9a7b137bb4aa4de7a6a2;
the P8.5 browser log SHA-256 is
97e1b6b33677684754c599cb94bc8871f14bd7102c2e107be9cb1e6025420b67;
the self-contained bundle SHA-256 is
20d66e39270b51d82716629b8affc48c0edb6064ee1c8c6c8d87c54b0fe81aaa.
Attempt 01 is INVALID_HARNESS_TERMINAL and is not reused.
Stage: P9_0_BOOT_TITLE_CANDIDATE_READY
On 2026-08-12 the Owner reviewed the published integrated loop and replied
这个OK了. Phase 8 comprehension, visual direction, choice flow and the
second-cycle continuation handoff are Owner-accepted. Prototype Web Audio cues
remain temporary and human listening is not claimed. Authoritative combat/save,
final media/audio, Godot/runtime, device, packaging, store and release remain
frozen and require their own evidence.
Owner authorization on 2026-08-12 opens Phase 9 as four separately accepted
runtime increments. P9.1 alone is active: implement the accepted opening
Company and first-Market preparation in a landscape Godot 4.6 project under
runtime/. P9.2 battle, P9.3 result/recovery/persistence, P9.4 device delivery,
final media, packaging, stores and release remain frozen.
P9.1 fixed product source
e7eb408e0e07200dd8e65f7226478c0383036371 is pushed clean/upstream. It
implements Contract/difficulty, four stable Recruit offers, an exactly-two
opening Company, separate Mael/Ilya hires, EQ-012 purchase/equip, one visible
Party-order swap and a final readiness receipt. It stops before battle.
Fresh isolated Git-archive evidence passes:
ABG_P9_1_DOMAIN_OK cases=40 final_coin=12 company=4 commits=6;ABG_P9_1_TOUCH_OK touch=25 fallback=0 direct=0 locale=en text_130=true reduced_motion=true mute=true final_coin=12 company=4;ABG_P9_1_LAYOUT_OK fixtures=18 viewports=3 states=6 locales=2 text_130=true;ABG_P9_1_RUNTIME_CAPTURE_OK frames=6 touch=19 fallback=0 direct=0.
The fixed-source bundle is retained at
runtime/evidence/p9-1-e7eb408-attempt01/. It contains six normal-render
states at each exact native size 1280x720, 844x390 and 390x844; the latter
two are explicitly domain-fixture render evidence and make no touch claim.
The 28-row evidence inventory SHA-256 is
7ff16f1a231e6c76dba0ec0545ea112f0afcc87f611b2ceb7ea953bbe7d22384.
Strict script/parse/resource/import/ObjectDB/RID diagnostic scan is clean.
Existing design validation, five-seed anti-dominance, 320-equipment one-slot
contract and 96-asset provenance regressions also pass. Agent visual review
found the six required states readable at all three sizes after repairing the
initial hidden heading, orphan HUD node and Party-card layout defects.
Human comprehension, choice quality, visual acceptance, fun and listening are still Owner gates. Physical-device, P9.2 battle, P9.3 persistence/recovery, packaging and release remain open/frozen.
Owner sequencing decision: the prior P9.1 candidate is preserved but not
Owner-accepted. Real implementation must now proceed one screen boundary at a
time, starting before run setup. Current P9.0 owns only SYS-001 cold boot and
the no-run SYS-003 Title. Start New Game may enter the preserved Contract
page but cannot alter its authority. P9.1 Owner review and P9.2 remain frozen.
P9.0 fixed product source
f881920b1be29933169950429d4e55d8cac825d8 is pushed clean/upstream. Fresh
isolated Git-archive attempt runtime/evidence/p9-0-f881920-attempt01/ passes
the ordered nine-resource Boot, visible 9/9 verified terminal, no-run Title,
five parsed ScreenTouch path with fallback/direct zero, keyboard/controller
initial focus, six layout fixtures and six normal-render frames at exact
1280x720, 844x390 and 390x844. P9.1 domain/touch/layout regressions and
the current design, anti-dominance, single-equipment/individual-level and
96-asset provenance authorities also pass with zero strict diagnostic markers.
The evidence content inventory verifies 27/27 with SHA-256
3c34f1742357d0cc57e8c4c59124133b8fb92de0a2dec01a90b2bbcf4ffb8318;
the structured audit SHA-256 is
5f2951c9f488760913a6fe7c67f96909fbce45bbaf3f6277f2346847428854f7.
Automated, runtime and agent visual gates pass. Owner understanding, visual
acceptance, fun, listening and willingness to continue remain open. Physical
device, packaging, store, release and every later page remain open/frozen.
Stage: P9_0_OWNER_REJECTED_REDESIGN_REQUIRED
Web successor f0aa84738041cebf4968d91c6bf170668804e203 is pushed
clean/upstream and is privately deployed as Artifact Gallery item
PRji-yhJo0nQ. Fresh remote checks prove the signed item redirects to its
full-screen entry, the artifact-scoped cookie does not expose other items,
HTML/JS/WASM/PCK response types are correct, the runtime HTML is not placed in
the ordinary document sandbox, and anonymous raw entry access remains gated.
Chrome phone-viewport verification renders the Simplified Chinese Title,
reaches Contract through real canvas input, shows the portrait rotate overlay,
and records zero browser warnings/errors.
The source-bound Web evidence remains at
runtime/evidence/p9-0-web-f0aa847-attempt01/. Its remote result records only
the public Artifact ID and verification facts; the signed share token is not
stored in Git. The final evidence inventory verifies 34/34 with SHA-256
cb3111f86012d313c85d1eebed6574b8b5936531bf30821421f89f1442aeb945.
Remote browser delivery is verified. Owner comprehension,
visual acceptance, fun, listening and willingness to continue remain open;
physical device, packaging, store, release and later pages remain frozen.
Owner remote play on 2026-08-12 failed the first-play comprehension and game-
presentation gate. The first post-Title screen begins a form-like Contract,
difficulty, provisional two-of-four selection, two additional forced hires,
equipment and order chain before any playable encounter. The Owner could not
understand Contract/First Market terminology, why the two recruitment stages
both existed, how to revise later choices, what had been completed, or how to
restart from inside the game. Visible P9.1, IDs, receipts and the milestone
ending incorrectly expose engineering structure as player-facing content.
The code contains no save/load persistence, so a full document reload should construct a fresh in-memory run, but relying on browser refresh is itself a UX failure. There is no visible Home or Restart control once the run flow begins. The current H5 is retained only as an append-only problem reference and must not be described as an accepted playable candidate.
Shortest next action: prepare two mutually exclusive, game-like first-five-minute onboarding structures for Owner choice; both must include visible Home/Restart, one unified recruitment interaction and a short encounter before equipment, formation optimization, difficulty or chapter systems. Do not modify runtime code until that structure is accepted.