Roadmap & Milestones

Phase 00 — Repository, engine and dedicated-server baseline

ROAD-P00 Partial

Entry / dependencies: None; reconcile the existing baseline before dependent runtime work.

Current evidence: Source/LambeerServer.Target.cs, Core classes, GAS module dependencies and Git LFS rules exist. UI records include owner dedicated-server testing. A packaged Linux server build and clean-clone recovery were not verified in this audit.

Work packages

1. ROAD-P00-01 Evidence: Retain the UE 5.8 project, source-control/LFS rules, Core framework and server target; record the exact revision used for the next build.
2. ROAD-P00-02 Remaining: Verify a clean checkout can resolve required LFS assets and build the Windows client and Linux dedicated target.
3. ROAD-P00-03 Remaining: Package and launch the development server with configuration and logs retained; have the owner verify two clients connect, move and disconnect.
4. ROAD-P00-04 Remaining: Record authoritative ownership, build configuration and deployment instructions; establish the profiling capture baseline.

Exit / acceptance: Reproducible client/server artifacts, two-client owner result and build logs are linked. Existing owner PIE evidence does not substitute for the Linux package check.

Canonical specifications and detailed tasks: ROAD-P00-02 clean checkout/LFS/build runbook; ROAD-P00-03 package/launch/two-client runbook; Tech Stack & Engine TECH-STACK-ENGINE; Network Architecture TECH-NETWORK-ARCH; Performance Profiling & Debugging TECH-PERFORMANCE-PROFILING

Phase 01 — Player movement, camera and animation closure

ROAD-P01 Partial

Entry / dependencies: P00 for packaged network acceptance; retain existing movement work.

Current evidence: LambeerLocomotionComponent, LambeerAimComponent, LambeerCameraComponent and LambeerAnimInstance exist. MCP lists ABP_Player. The animation guide records owner prone results on 2026-09-05, but retains provisional collision/speed values and incomplete visual/network coverage for other selectors.

Work packages

1. ROAD-P01-01 Evidence: Retain standing/crouch/prone runtime and existing animation graphs; preserve the owner-recorded prone checks.
2. ROAD-P01-02 Remaining: Close the guide’s outstanding movement, transition, pivot/turn/spin and collision verification cases; resolve only their canonical tuning decisions.
3. ROAD-P01-03 Remaining: Check camera/aim transitions against movement, posture, obstruction and replicated remote presentation.
4. ROAD-P01-04 User-only: Owner performs missing retargeting and PIE checks; record clip/body mappings and separate standalone, listen-server and dedicated-client evidence.

Exit / acceptance: The animation guide has no unaccounted blocking cases for the selected slice body/locomotion set; remaining content variants have explicit follow-up scope.

Canonical specifications and detailed tasks: Player Locomotion Animation Guide TECH-PLAYER-LOCOMOTION; Player Character FEAT-PLAYER-CHARACTER

Phase 02 — Inventory, item identity and survival backend baseline

ROAD-P02 Partial

Entry / dependencies: Existing P00/P01 framework; prerequisite for subsequent inventory and gameplay extensions.

Current evidence: InventoryComponent, EquipmentComponent, HeldItemComponent, GAS attributes and SurvivalComponent are implemented. Owner UI records cover inventory commands, nested death drops, bed sleep and L1810 magazine flows. This does not close the full survival or combat feature.

Work packages

1. ROAD-P02-01 Evidence: Retain item-instance identity, nested containers, hand/worn/back equipment, quick-slot validation and server command checks from G3.2/G4.
2. ROAD-P02-02 Evidence: Retain L1810 world/held/back visuals and magazine load/install/cancel/unload/remove owner results; keep grip polish separate.
3. ROAD-P02-03 Remaining: Reconcile use, transfer, split and drop edge cases with the canonical inventory contract, including stale requests and full containers. Tools-folder Data Assets and world/held meshes are authored (ROAD-TOOLS-01–02). Remaining: pickups/icons (ROAD-TOOLS-03–04) and GrantedToolRoles (ROAD-TOOLS-14).
4. ROAD-P02-04 Remaining: Inventory the implemented survival rules versus the full-sim design; carry durable save work to P07 and full treatment/feedback work to P12.

Exit / acceptance: Every baseline inventory operation has an implementation/evidence reference or an explicit remaining task; no duplicate/lost item in owner multi-client regression. Baseline closure does not imply all survival effects are implemented.

Canonical specifications and detailed tasks: Inventory & Items FEAT-INVENTORY; Item IDs ITEM-DB; Held tools slice; Survival System FEAT-SURVIVAL; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION

Phase 03 — CommonUI, visual system and functional HUD baseline

ROAD-P03 Complete

Entry / dependencies: Existing G0/G1/G2/G3 baseline; completion is limited to recorded KBM scope.

Current evidence: TECH-HUD-UI-IMPLEMENTATION records completed G0/G1, core G2 and G3 tasks. MCP lists WBP_UIRoot, WBP_HUDRoot and HUD children. Physical Xbox/PlayStation checks remain outside this completed KBM baseline, tracked in P28; wet materials remain P12.

Work packages

1. ROAD-P03-01 Complete: G0: retain approved visual tokens, 64-icon source kit, Thai-capable Google Sans and documented regression baseline.
2. ROAD-P03-02 Complete: G1: retain CommonUI root/layers, modal-first Back, cursor and gameplay-input restoration contracts.
3. ROAD-P03-03 Complete: Core G2: retain imported styles/fonts/icons and recorded Thai/English, HUD scale and safe-zone evidence.
4. ROAD-P03-04 Complete: G3: retain event-driven eight-stat HUD, hands/quick slots, compass/minimap, reticle, prompts and local screen effects; no hit/headshot/kill markers.

Exit / acceptance: Recorded baseline is closed within its evidence scope. Reopen only affected contracts after changes; do not reimplement completed tasks. Full controller and artwork acceptance are separate phases.

Canonical specifications and detailed tasks: HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; HUD & UI System FEAT-HUD-UI

Phase 04 — Core screens, death/respawn, pause and settings

ROAD-P04 Complete

Entry / dependencies: P03; corresponds to the complete G4 gate.

Current evidence: G4 is recorded closed on 2026-09-13. Seven task rows are Complete; UI-CORE-003 intentionally belongs to G4.2. Owner results cover Tab, map controls, death/bed/fresh spawn, pause and Settings. Sandbox town markers are not a production map.

Work packages

1. ROAD-P04-01 Complete: UI-CORE-001/002: activatable inventory lifecycle and validated commands; keep new visual transfer layout in P05.
2. ROAD-P04-02 Complete: UI-CORE-004: full-map pan/zoom/center, category filters, ping and clipping; retain north-up minimap behavior.
3. ROAD-P04-03 Complete: UI-CORE-005/006: nested death bag, loot interaction, overlay reset, Last Bed and four-town Fresh Spawn test flow.
4. ROAD-P04-04 Complete: UI-CORE-007/008: multiplayer world-continues menu, standalone pause, staged Settings/Display Revert and language/font behavior; G4 Text Scale remains locked at 1.0.

Exit / acceptance: Owner-reported G4 exit evidence remains canonical in the UI task register. This gate is closed; do not merge G4.2 artwork into its completion claim.

Canonical specifications and detailed tasks: HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; HUD & UI System FEAT-HUD-UI

Phase 05 — Inventory UMG layout and texture integration

ROAD-P05 Complete

Entry / dependencies: P04 closed; G4.2 / UI-CORE-003 entered and completed.

Current evidence: G4.2 closed by owner-reported pass 2026-09-14. Night Ops replaced the former Rescue Equipment presentation while preserving the approved 36/64 hierarchy, responsive Worn flow and retained commands. The owner accepted the final visual correction plus drag, split, sort, drop, hand/Q1/Q2 and Player/Target transfer. Search failed and was removed by explicit owner decision; the owner then passed the field-free header and retained layout. Development Game/Editor builds, the field-free WBP_Inventory compile/save/readback, removal of Rescue references and focused non-PIE Inventory automation 3/3 pass.

Work packages

1. ROAD-P05-01 Complete: Use the approved Character + Container Focus layout and three RawResource/UI/Inventory/UMG PNG sources.
2. ROAD-P05-02 Complete: Import textures with documented UI settings; assign panel/slot Box brushes and focus overlay.
3. ROAD-P05-03 Complete: Designer hierarchy, C++ layout/transfer, WBP_ContainerTransfer reparent, and MCP compile/save against the rebuilt Editor.
4. ROAD-P05-04 Complete: Owner passed KBM Inventory/loot visual and retained-interaction flows plus the final Search-free header. Controller validation stays deferred.

Exit / acceptance: Complete. UI-CORE-003 passed its G4.2 exit checklist, including Take All/Transfer All presentation, focus, item-state preservation and final Search-free header. G4.3 may start.

Canonical specifications and detailed tasks: HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; HUD & UI System FEAT-HUD-UI; Inventory & Items FEAT-INVENTORY

Phase 06 — HUD and core-menu Night Ops presentation

ROAD-P06 Complete

Entry / dependencies: P05 / G4.2 is closed. Sequential closure of G4.3 / UI-HUD-018 followed by G4.4 / UI-MENU-001 is satisfied; P06 no longer blocks G5.

Current evidence: G4.3 owner-correction revision 3 and G4.4 Pause/Settings Option B feedback revision passed their complete owner PIE checklists on 2026-09-14. HUD revision 3 enforces equal hand-card sizing, square Quick Slots, four-segment Stats with exact current values, themed Weight and compact Compass spacing. G4.4 adds a 340×820 Pause tactical rail and 1480×820 Settings workbench without changing session/settings behavior; the owner-feedback revision removes visible world-continues warning copy and renders language choices white as English/ภาษาไทย while retaining internal en/th. The latest Editor build succeeds, headless non-PIE Lambeer.HUD passes 24/24, and both menu Widget Blueprints compile/save/read back cleanly.

Work packages

1. ROAD-P06-01 Complete: Replace olive/brass chrome with the owner-directed Night Ops source/runtime strategy; preserve rejected ImageGen attempts outside the project.
2. ROAD-P06-02 Complete: Import six alpha textures with verified UI settings and caps; stage their canonical HUD bindings.
3. ROAD-P06-03 Complete: Native Night Ops stat/card/quick-slot/prompt/minimap/reticle/screen-effect presentation is compiled while preserving G3/G4 adapters and aim visibility; Editor build, non-PIE HUD automation 24/24 and all eight affected Widget Blueprint compile/save/readbacks pass.
4. ROAD-P06-04 Complete — owner-reported 2026-09-14: all G4.3 checks and the complete G4.4 Pause/Settings Option B dedicated-server/Standalone, Settings, stacking and responsive EN/TH matrix passed.

Exit / acceptance: Complete. G4.3 / UI-HUD-018 and G4.4 / UI-MENU-001 are closed; G5 may begin when authorized. World rain VFX and material wetness are still P12; presentation work alone does not complete them.

Canonical specifications and detailed tasks: HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; HUD & UI System FEAT-HUD-UI

Phase 07 — Durable player persistence and world index

ROAD-P07 Complete

Entry / dependencies: P06 before G5-dependent work; P00/P02 provide authority and item schemas. [CONFIRMED 2026-09-14] TBD-HUD-UI-003 is resolved: SP uses embedded NM_Standalone. Persistence policies live in TECH-NETWORK-ARCH.

Current evidence: Closed-Editor LambeerEditor Win64 Development compiled and linked. Headless non-PIE Lambeer.Persistence passed 6/6 with zero failures (report: Saved/Automation/P07Persistence) and Lambeer.HUD stayed 24/24. Runtime uses one SQLite database per world under Saved/Lambeer/Worlds/<id>/world.db. UE 5.8 SQLiteCore is compiled with SQLITE_OMIT_WAL, so crash-safety is committed BEGIN IMMEDIATE transactions plus the engine rollback journal rather than WAL. Dirty flush is 30 seconds of world-up time, with immediate flushes on logout, graceful shutdown, death-bag spawn, death itself, authored pickup collection and runtime world-drop spawn. In-memory backend remains only while no world is open. Player rows key on pie-{PIEInstance} for Preview clients. Map-placed AWorldItemPickup actors stay collected after pickup. A dead player record reopens spawn select instead of a locked corpse. Owner-reported pass 2026-09-14 on Dedicated Server + two Preview clients: restart/rejoin restored position/items, collected map pickups stayed gone, and a post-death save opened spawn select. P08 Main Menu / Save World Select screens remain out of this phase.

Work packages

1. ROAD-P07-01 Complete: Retain ISaveBackend/USaveSubsystem as the persistence boundary; SQLite is installed only while a world is open.
2. ROAD-P07-02 Complete: Versioned SQLite schema v1, migrate-up / refuse-newer, integrity probe, 30-second dirty flush and critical flushes are implemented; automation covers schema, migrate/refuse, checksum and rollback.
3. ROAD-P07-03 Complete — owner-reported 2026-09-14: Capture/restore covers identity/appearance/transform/last bed, nested inventory/equipment/hands, survival, blood/wet, Q1–Q0 item-id refs, rain intensity, death bags and runtime drops with 24-hour remaining world-up despawn. Dead records restore spawn select. Collected map-placed pickup ids stay gone. Observed chamber/magazine knowledge is not saved. Player rows key on login LambeerPlayerKey (pie-{PIEInstance} in PIE) instead of ephemeral Null-OSS ids.
4. ROAD-P07-04 Complete: Create/list/rename/delete/open and missing/corrupt/incompatible probes exist on USaveSubsystem; remembered-world pointer lives in ULambeerUserSettings. Delete requires confirmation. P08 screens that consume the index remain out of P07.

Exit / acceptance: Complete. Owner restart/rejoin restored the selected player/world state without item loss or duplication; save/load and failure tests are retained. Building/vehicle/queue records must be added when those systems land.

Canonical specifications and detailed tasks: Network Architecture TECH-NETWORK-ARCH; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; Character Creation & Appearance FEAT-CHARACTER-CREATION

Phase 08 — Frontend, sessions and character entry

ROAD-P08 Partial

Animation follow-up, 2026-09-17: the requested grip/ShoulderAim progress, owner RMB observation and Procedural Recoil work are recorded in the owning P09 progress table, with P10 dependencies for shot/action events. P08 remains the frontend/session/character-entry phase; this cross-link does not change its acceptance scope.

Owner-reported Single Player frontend pass, 2026-09-16: Owner reported ROAD-P08-01 / UI-FE-001/UI-FE-003, ROAD-P08-03 / UI-FE-006/UI-FE-007, UI-FE-009, remaining Character Creation visual checks, and remaining persistence/restart/rejoin checks passed. Dedicated Null/LAN advertise, Server Browser join and Pause disconnect are implemented; owner reported extra-client first-time follow camera, dedicated Pause MENU/ONLINE SESSION without Save, Exit to Main Menu while the dedicated world and client 2 continue, restore without Character Creation, and Server Browser Refresh/Join. Steam metadata, Feedback URL and the production gameplay destination remain blocked on TBD-HUD-UI-004/ROAD-P08-04. G5 and P08 stay open.

Spawn recovery follow-up, 2026-09-15; owner-reported pass 2026-09-16: Owner confirms Continue skips creation but reports no character. The legacy saved origin collides with geometry. GameMode now recovers through PlayerStart and existing-character town selection, or explicitly refuses entry without overwriting the row if fallback fails. Canonical recovery behavior and acceptance. Closed-Editor build and 36/36 non-PIE checks pass; owner later reported Continue/town/move/save/restart passed.

Latest persistence correction, 2026-09-15; owner-reported pass 2026-09-16: Owner retest rejected the previous flush-only fix. Successful player writes were followed by a false Missing result because RestartPlayer read before OnWorldBeginPlay enabled periodic persistence. Early reads now use the selected database independently of that flag; unavailable storage refuses entry. PlayerController teardown saves before unpossessing and pawnless snapshots preserve prior records. See canonical diagnosis and regression coverage. Owner later reported Continue/restart persistence passed.

Entry / dependencies: P06 and P07; complete the existing G5 gate before later UI gates.

Current evidence: Owner selected P08 frontend Option C “Survivor Dossier” on 2026-09-15. Main Menu, Save World Select, session adapter/browser, character-entry state and native character-creation presentation are implemented. Unreal MCP compiled/saved/read back WBP_MainMenu, WBP_SaveWorldSelect, WBP_ServerBrowser and WBP_CharacterCreation. Owner PIE exposed and then verified fixes for the aliased world-probe path and invisible post-travel Character Creation root. Later visual, spawn-recovery and persistence corrections are recorded in the canonical creation and network documents. On 2026-09-16 the owner reported the remaining Single Player frontend, Character Creation visual and persistence/restart checks passed, then extra dedicated-client first-time follow camera, dedicated Pause MENU/ONLINE SESSION without Save, Exit to Main Menu while the dedicated world and client 2 continue, restore without Character Creation, and Server Browser Refresh/Join. UE 5.8 Play As Client starts a hidden dedicated instance; one-process PIE lists that host by listen port because Null FindSessions cannot see the same-process beacon. Steam/platform metadata, Feedback URL and the production gameplay destination remain blocked, so G5 and P08 remain open.

Work packages

1. ROAD-P08-01 Complete — owner-reported 2026-09-16: Main Menu, Continue and Save World Select consume the P07 world index and surface missing/corrupt/incompatible reasons. Editor validation may fall back to L_Dev_Sandbox; packaged production destination stays with the deferred ROAD-P08-04 work.
2. ROAD-P08-02 Complete — owner-reported 2026-09-16: Online session adapter and Server Browser provide cancellable refresh, Official/Community metadata, favorites, ping/population, search/filters, join routing and explicit full/stale/version/timeout failures. Dedicated and listen persistable worlds advertise a Null/LAN session. One-process PIE lists those hosts by listen port because Null FindSessions cannot see the same-process beacon. UE 5.8 Play As Client starts that dedicated world automatically (hidden under one-process PIE). Owner reported Refresh/Join from the returned client after Exit to Main Menu. Development uses OnlineSubsystemNull; Steam/platform metadata stays with TBD-HUD-UI-004.
3. ROAD-P08-03 Complete — owner-reported 2026-09-16: WBP_CharacterCreation exists with native live preview controls; initial appearance commit is server-owned, starter-town selection follows first creation, and an existing character restores persisted state/position. Owner reported remaining visual, spawn-recovery and restart/rejoin checks passed, then extra dedicated-client first-time follow camera behind the pawn. Final environment assets and art lighting/time of day remain later content, not this package’s reopen.
4. ROAD-P08-04 Blocked: Resolve TBD-HUD-UI-004 Steam metadata/Feedback URL and configure the production gameplay destination. Owner-reported Null/LAN Server Browser join is recorded on ROAD-P08-02.

Exit / acceptance: G5 exit criteria pass with authoritative character-per-server identity and usable failure paths. The owner-accepted Single Player and Null/LAN dedicated session slice is not full G5 closure while deferred Steam/Feedback/production-map work remains.

Canonical specifications and detailed tasks: HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; Character Creation & Appearance FEAT-CHARACTER-CREATION; Servers & Hosting TECH-SERVERS-HOSTING

Phase 09 — Held-item grip, pose and body compatibility

ROAD-P09 Partial

Progress and remaining work — 2026-09-17

Status: Partial. The grip/animation foundation, placeholder file preparation and per-item hand-pose AnimBP wiring are complete; authored Pose Assets, animation binding, action playback and visual acceptance remain open; procedural recoil now has an event/debug implementation. Canonical current observation and diagnosis. Owner confirmed 2026-09-17 that each held item needs its own hand pose: TBD-INVENTORY-GRIP-003.

Recommended execution order: profile binding and aim-pose verification → per-item hand Pose Assets with grip/contact review (offset without finger pose is provisional) → montage/action integration → procedural recoil and current-frame support solve → full owner visual/network acceptance. ABP hand-pose blends are already wired. P10 shot/action gameplay contracts remain dependencies; exact buttons, recoil values and combat tuning are not invented.

Entry / dependencies: P01/P02; before final combat animation/content acceptance.

Historical grip-slice evidence (2026-09-16; current status above): The owner approved the shared character grip references, per-item placement/pose and body-specific corrections architecture on 2026-09-12, then the integration contract on 2026-09-16 under TBD-INVENTORY-GRIP-002. ROAD-P09-03 implemented those fields on ULambeerItemDefinition, KeepWorld attach, unauthored-left refusal, bone fallback, distinct inspect pivots, and ABP_Player Two Bone IK on hand_l. Headless Lambeer.HUD 25/25. First-slice Data Assets still store identity grips. Owner PIE and retargeted clips remain ROAD-P09-04.

Work packages

1. ROAD-P09-01 Complete: Retain the approved firearm, melee and physically held inspection scope; rigid items can remain Static Meshes. The Tools-folder Crowbar, FireAxe, Sledgehammer and WoodenMallet meshes are in that rigid-item scope; functional melee may use the current hand_r/hand_l attach until this phase’s mappings land.
2. ROAD-P09-02 Complete — 2026-09-16: Owner resolved socket names, item-definition transform storage, KeepWorld scale, left-hand eligibility, Two Bone IK and missing-socket fallback in FEAT-INVENTORY. Numeric grip offsets are still unauthored.
3. ROAD-P09-03 Complete — 2026-09-16: Implemented RightGripRelative / optional LeftGripRelative / optional SupportHandTarget / optional PresetId overrides; KeepWorld attach; refuse unauthored left-hand holds; bone fallback when a socket is missing; AnimBP Two Bone IK to the support target for two-handed items; keep UI preview pivots distinct. Headless Lambeer.HUD 25/25 including Lambeer.HUD.Backend.GripContract. MCP compiled and saved ABP_Player. No invented offset numbers; first-slice assets remain identity. Owner PIE is not claimed.
4. P09 expanded animation scope — 2026-09-16, foundation implemented / content pending: owner requests all-pose Carry/ShoulderAim/Attack/Fire layers, independent firearm hands, right-only mixed firearm/melee actions, shared animation profiles and per-item overrides. Design, folder/file plan and implementation status; Editor offset calibration guide. Native profile/context lookup, item overrides, free-left ShoulderAim support eligibility and three ABP Layered Blend nodes are implemented. Six empty profile assets are saved. Native build and HUD 26/26 passed; ABP compile/save/readback passed. ROAD-P09-03 retains its historical grip-slice completion; clips, measured grips, action/recoil playback and owner visual acceptance remain open.
5. P09 placeholder authoring — 2026-09-16: owner authorized temporary Stand-to-other-stance copies and explicit fallback sources. Sequence provenance and current completion status. Copied Fire aim poses are non-additive placeholders; no recoil behavior or final stance acceptance is implied.
6. ROAD-P09-05 Complete — 2026-09-17: Per-item hand pose runtime. Native Pose Asset fields, first-pose-name publish and ABP_Player Layered Blend for right fingers before support IK and left fingers after it. Closed-Editor LambeerEditor Win64 Development and headless Lambeer.HUD 26/26 (report: Saved/Automation/P09HandPoseNames). MCP compiled/saved ABP_Player and read back hand_r/hand_l BranchFilters. No Pose Assets were created or bound. Canonical contract: TBD-INVENTORY-GRIP-003.
7. ROAD-P09-04 User-only: Owner supplies required retargeted animations and per-item hand Pose Assets, and verifies selected bodies/items across hands, aim and movement; agent validates and binds assets through MCP.

Exit / acceptance: Selected slice equipment has stable placement and hand contact on approved bodies with explicit world-scale behavior; unsupported combinations fail according to the approved contract.

Canonical specifications and detailed tasks: Inventory & Items FEAT-INVENTORY; Combat System FEAT-COMBAT; Held tools slice; Art Direction & MetaHuman Pipeline ART-DIRECTION

Phase 10 — Authoritative firearm, melee and thrown combat

ROAD-P10 Partial

Entry / dependencies: P00/P01/P02/P09; resolve combat decisions before implementing the affected action.

Current evidence: Aim and instant GAS damage paths exist, as do firearm/magazine rule helpers. Tools-folder Static Meshes exist; Sledgehammer is an owner-passed hold/throw/two-hand/reticle item. This audit did not establish a complete firing/melee attack pipeline or its owner acceptance; console damage and melee reticle are not a gunplay test. Class and Data Asset work for the first melee set is specified in held tools slice.

Work packages

1. ROAD-P10-01 Blocked: Finalize the selected weapon firing model and open per-hand/dual-wield/improvised-object action rules in the combat specification; no example damage/RPM becomes approved tuning. Slice melee numeric fields are TBD-COMBAT-MELEE-001.
2. ROAD-P10-02 Remaining: Connect valid fire input, ammo/chamber consumption, authoritative hit/damage and recoil/aim presentation for the selected slice firearm set.
3. ROAD-P10-03 Remaining: Implement the Tools-slice melee pipeline in ROAD-TOOLS-05–10 (shared combat component + GAS ability; no per-item subclass). Combat-usable world-prop strike/throw remains a separate catalog under the improvised-weapon rules and is not implied by the Tools folder.
4. ROAD-P10-04 User-only: Owner verifies hits/misses, cover, lethal/nonlethal damage, remote views and rejected invalid actions on dedicated server + two clients, including the four Tools-slice items once they are registered.

Exit / acceptance: Selected guns and melee/throw actions form a playable combat loop with no client-authored damage or UI hit/headshot/kill markers. Wider weapon content remains P20/P27. Tools harvest/build/raid extras stay out of this P10 exit (ROAD-TOOLS-11–13). Tool-role vocabulary is resolved in FEAT-INVENTORY.

Canonical specifications and detailed tasks: Held tools slice; Combat System FEAT-COMBAT; Weapon Customization (Workbench & Field) FEAT-WEAPON-CUSTOMIZATION; Blood Visual (Stains, World Feedback, HUD) FEAT-BLOOD-VISUAL; Inventory & Items FEAT-INVENTORY

Phase 11 — Weapon customization, inspection and repair

ROAD-P11 Partial

Entry / dependencies: P08/P09/P10; G6 weapon tasks UI-SYS-005/006 follow backend readiness.

Current evidence: G3.2 records owner-passed L1810 magazine handling. Full attachment categories, workbench UI, advanced magazine planner, durability/repair and their integrated acceptance remain open.

Work packages

1. ROAD-P11-01 Evidence: Preserve existing magazine-as-item and chamber state; do not recreate the already tested L1810 flow.
2. ROAD-P11-02 Remaining: Implement compatible attachment install/remove and replicated meshes for the canonical slot types; add laser/light behavior with later AI-awareness integration.
3. ROAD-P11-03 Remaining: Build workbench/3D inspect and magazine planner; server sequence must match Head/Loop/Tail preview and reject incompatible ammunition.
4. ROAD-P11-04 Remaining: Connect durability and repair actions to approved kits/salvage and inventory costs; verify cancellation, hands, transfers and save/reload.

Exit / acceptance: Selected slice weapon customization and repair work end to end without lost/duplicated attachments or ammunition. Rail-position/stock-length depth stays in P21.

Canonical specifications and detailed tasks: Weapon Customization (Workbench & Field) FEAT-WEAPON-CUSTOMIZATION; Inventory & Items FEAT-INVENTORY; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION

Phase 12 — Full survival effects, world blood and rain presentation

ROAD-P12 Partial

Entry / dependencies: P02/P07/P10; material mappings and unresolved survival treatment/tuning must be approved before dependent work.

Current evidence: Owner evidence covers bed sleep, eight HUD bars and local rain-lens/shelter checks. UI-HUD-017 wet-material mapping is explicitly deferred; current materials lack WetAmount and rain VFX remains unauthored. The full disease/treatment simulation is not certified.

Work packages

1. ROAD-P12-01 Remaining: Finish approved hunger/thirst/temperature, injury, bleeding/infection/broken-bone and treatment rules; resolve unresolved probabilities/thresholds in survival docs.
2. ROAD-P12-02 Remaining: Integrate food/water/medical item use, shelter/clothing/heat and persistent status recovery across death/rejoin as designed.
3. ROAD-P12-03 Blocked: Author approved BloodAmount/WetAmount material mappings and world blood/rain VFX; preserve no-hit-marker and clear-view policies.
4. ROAD-P12-04 User-only: Owner verifies damage-to-world/mesh/HUD feedback, infection/treatment, shelter/exposure and reset behavior; distinguish visual checks from GAS simulation checks.

Exit / acceptance: The selected survival loop can be played, treated and restored after restart; world/mesh effects and HUD are individually accepted, with no placeholder mapping presented as approved tuning.

Canonical specifications and detailed tasks: Survival System FEAT-SURVIVAL; Blood Visual (Stains, World Feedback, HUD) FEAT-BLOOD-VISUAL; Wetness and Rain FEAT-WETNESS-RAIN

Phase 13 — World production decision and streaming prototype

ROAD-P13 Not started

Entry / dependencies: P00/P01 profiling baseline. TBD-WORLD-002 is resolved: limited proof area first. The bounded brief is the fictional Kit Proof Town. Final 100 km² lock remains TBD-WORLD-001 / WORLD-C10 and does not block this phase.

Current evidence: World concept is detailed but explicitly does not certify runtime implementation. MCP lists L_Dev_Sandbox and L_MainMenu; neither proves the authored seven-settlement World Partition target exists. Kit Proof Town is a documentation brief, not a verified map asset.

Work packages

1. ROAD-P13-01 Complete: Owner confirmed limited proof area first on 2026-09-13 under TBD-WORLD-002. Preserve the final seven-settlement/island target for P24–P26.
2. ROAD-P13-02 Remaining: Author a measured Kit Proof Town blockout using the 2026-09-15 world decisions: unlocked 100 km² baseline, no-build volumes, no travel-time targets, and above-ground/underground floor caps. Do not lock landscape production until WORLD-C10.
3. ROAD-P13-03 Remaining: Build the Kit Proof Town modular test block with World Partition/Data Layer/HLOD, interior visibility, navigation, shelter and loot integration evidence, including the 3–4 storey building plus one basement and the P13 no-build test set.
4. ROAD-P13-04 Remaining: Profile dense interiors, streaming boundaries and server relevancy before multiplying environment content; document kit and POI handoff contracts.

Exit / acceptance: Production order is approved; owner still approves the measured world blockout direction. Prototype streaming/navigation/shelter results exist; no full-map completion follows from a sandbox map or from Kit Proof Town.

Canonical specifications and detailed tasks: World Design FEAT-WORLD-DESIGN; Scope & Constraints GDD-SCOPE-CONSTRAINTS; Performance Profiling & Debugging TECH-PERFORMANCE-PROFILING

Phase 14 — Zombie AI and bounded encounter slice

ROAD-P14 Not evidenced

Entry / dependencies: P10/P12/P13; final AI architecture/tuning follows canonical decisions.

Current evidence: StateTree modules are enabled, but this audit found no Lambeer zombie gameplay source or named zombie/StateTree asset in the inspected /Game/Lambeer registry. Imported/template content elsewhere was not audited as implemented game AI.

Work packages

1. ROAD-P14-01 Remaining: Implement the selected baseline zombie types with authoritative health/damage and data-owned stats; finalize the StateTree recommendation before relying on it.
2. ROAD-P14-02 Remaining: Build patrol/wander, sight/hearing investigation, chase, attack, lose-target and return behaviors with navigation failure handling.
3. ROAD-P14-03 Remaining: Implement region density/global server multiplier, active spawn caps and relevancy/AI LOD; integrate firearm/light/noise awareness.
4. ROAD-P14-04 User-only: Owner validates selected encounters in interiors/outdoors and on two clients; retain server profiling and exploit/unstuck findings.

Exit / acceptance: A bounded selection of normal zombies threatens players, navigates the prototype area and respects measured caps; roster/boss expansion is separate.

Canonical specifications and detailed tasks: Zombie Design FEAT-ZOMBIE-DESIGN; Zombie & Boss Roster CHAR-DB-ZOMBIES; Performance Profiling & Debugging TECH-PERFORMANCE-PROFILING

Phase 15 — Crafting queues and station production

ROAD-P15 Not started

Entry / dependencies: P02/P07/P08; G6 UI-SYS-001/002. Resolve queue destruction overflow before dependent implementation.

Current evidence: G6 marks persistent crafting queues Blocked and the crafting screen Not started. No crafting gameplay component/service was found in Source/Lambeer.

Work packages

1. ROAD-P15-01 Remaining: Author approved recipe/blueprint/station data and discovery/unlock contracts without inventing economy values.
2. ROAD-P15-02 Remaining: Implement player/station queues with immediate reservation, source-specific inventory availability and cancel refunds.
3. ROAD-P15-03 Blocked: Resolve TBD-HUD-UI-005 destruction/overflow behavior; preserve queues through leave/logout/restart and handle missing outputs safely.
4. ROAD-P15-04 Remaining: Implement searchable recipe/detail/queue UI and validate queue ordering, concurrent access, full outputs and interrupted sessions.

Exit / acceptance: Player and station recipes consume exactly once, produce/refund correctly and persist; screens report authoritative availability and queue state.

Canonical specifications and detailed tasks: Crafting & Progression FEAT-CRAFTING-PROGRESSION; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; Network Architecture TECH-NETWORK-ARCH

Phase 16 — Building placement, ownership and minimal base kit

ROAD-P16 Not started

Entry / dependencies: P02/P13/P15; G6 UI-SYS-003/004. No-build categories and shapes are resolved in TBD-WORLD-003; per-volume buffer meters are authored during blockout.

Current evidence: UI register lists building backend Not started and radial widgets User-only. No building gameplay implementation was found in inspected Lambeer source/registry.

Work packages

1. ROAD-P16-01 Remaining: Select and author the minimal canonical piece/deployable set with costs, collision and snapping; keep exact catalog/tuning in the building specification. Place/upgrade/repair/demolish require held Tool.Role.Hammer (WoodenMallet) per FEAT-INVENTORY; Authorize does not.
2. ROAD-P16-02 Remaining: Implement client preview and server placement validation for range, support, obstruction, exclusions, rotation and resource spend.
3. ROAD-P16-03 Remaining: Implement base ownership/build privilege and Upgrade/Repair/Demolish/Authorize commands with tier state; add player-built door/window built-in lock state and installed Lock-item support on doors, windows and Player-built Storage per FEAT-LOCK-ACCESS.
4. ROAD-P16-04 Remaining: Connect build-selection/action radials and invalid-placement reasons; owner verifies remote visibility and hostile invalid requests.

Exit / acceptance: A player can construct and maintain a small valid base; clients cannot bypass placement or duplicate resources. Durable restart and raid destruction close in P17.

Canonical specifications and detailed tasks: Building System FEAT-BUILDING; Lock & Access FEAT-LOCK-ACCESS; Inventory & Items FEAT-INVENTORY; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; World Design FEAT-WORLD-DESIGN

Phase 17 — Base persistence, raid damage and recovery

ROAD-P17 Not evidenced

Entry / dependencies: P07/P10/P16; agree applicable raid rules before tuning them.

Current evidence: The existing save backend is memory-only and no building store/raid system was evidenced. Death-bag completion is not base persistence.

Work packages

1. ROAD-P17-01 Remaining: Extend versioned SQLite records to buildings, storage, ownership/privilege and structural relationships.
2. ROAD-P17-02 Remaining: Implement authorized raid damage, repair/destruction, container fallout, lifecycle cleanup and Lockpick against every confirmed lockable building/container target. Type-specific raid damage for Crowbar/FireAxe/Sledgehammer is follow-on work under ROAD-TOOLS-13, not implied by P10 melee.
3. ROAD-P17-03 Remaining: Make save/restore and destruction consistent so restart cannot resurrect demolished pieces, reroll initial lock state, lose/duplicate installed Lock items or duplicate stored loot.
4. ROAD-P17-04 User-only: Owner tests two-client raid, contested storage, death, restart, recovery and invalid authority; preserve database/build evidence.

Exit / acceptance: A constructed base and its complete storage survive restart; valid raids change durable state exactly once and recover without duplication.

Canonical specifications and detailed tasks: Building System FEAT-BUILDING; Lock & Access FEAT-LOCK-ACCESS; PvP, Raiding & Trading FEAT-PVP-RAIDING-TRADING; Network Architecture TECH-NETWORK-ARCH

Phase 18 — First boss, component reward and permanent buff

ROAD-P18 Not evidenced

Entry / dependencies: P07/P10/P14/P15; G6 boss presentation UI-SYS-010.

Current evidence: Boss roster/loop are documented; no implemented boss encounter, durable first-kill award service or completed boss HUD was evidenced.

Work packages

1. ROAD-P18-01 Remaining: Author one selected boss encounter and fixed POI with telegraphs, weak points and server-owned lifecycle.
2. ROAD-P18-02 Remaining: Implement authoritative eligibility, component reward and once-only first-kill permanent buff; persist award identity and restore it.
3. ROAD-P18-03 Remaining: Connect boss component to a craftable weapon recipe and confirm the reward loop uses the existing inventory/crafting services.
4. ROAD-P18-04 Remaining: Implement boss health/inspected respawn-state presentation; owner tests repeat kills, multiple eligible players, interrupted fights and restart.

Exit / acceptance: The owner can hunt the boss, receive the correct component and first-kill buff, craft the reward weapon and retain state after restart without duplicate permanent awards.

Canonical specifications and detailed tasks: Zombie Design FEAT-ZOMBIE-DESIGN; Crafting & Progression FEAT-CRAFTING-PROGRESSION; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION

Phase 19 — Squad cooperation and communication

ROAD-P19 Not started

Entry / dependencies: P08/P18 and the specific group/chat/voice backend dependencies. Owner approved G7 squad work before unrelated G6 Skills/Vehicles; G6 need not close as a whole first.

Current evidence: UI-SOC tasks are Blocked/Not started/User-only. Map ping exists, but that does not prove squad membership, text chat or voice services.

Work packages

1. ROAD-P19-01 Blocked: Resolve applicable group authority/name/log rules in TBD-HUD-UI-007 before shared group service work.
2. ROAD-P19-02 Remaining: Implement squad create/invite/accept/leave, authoritative membership and group-context map ping without adding a persistent squad-roster HUD.
3. ROAD-P19-03 Remaining: Implement canonical Server/Proximity/Squad chat and voice/PTT/mute/block states with membership validation and focus-safe screens.
4. ROAD-P19-04 User-only: Owner tests invitations, disconnect/rejoin, rejected actions and boss co-op; record available voice/device evidence and explicit unavailable states.

Exit / acceptance: Players can coordinate in the selected group flow with server-validated permissions. Clan territory depth is P22; the approved per-system G6/G7 sequencing retains each task’s own acceptance.

Canonical specifications and detailed tasks: Clans & Squads FEAT-CLANS-SQUADS; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; HUD & UI System FEAT-HUD-UI

Phase 20 — Integrated core-loop acceptance

ROAD-P20 Not evidenced

Entry / dependencies: P00–P19 exits and only the G6/G7 tasks needed for this slice; owner approved per-system dependency scheduling. Use the Kit Proof Town limited area approved under TBD-WORLD-002; P24–P26 expansion follows this acceptance.

Current evidence: Several foundational loops have owner results, but the complete join → survive → loot → build → boss → craft → death/raid → restart loop has no accepted evidence in this audit.

Work packages

1. ROAD-P20-01 Remaining: Assemble the selected guns/melee, zombies, boss, recipes, base kit, survival and squad flow into the approved test geography.
2. ROAD-P20-02 Remaining: Verify slice-required crafting/building/weapon/boss/squad UI tasks and their backend acceptance. Keep later Skills, Vehicles and clan-depth tasks open; do not claim the whole G6/G7 groups are complete.
3. ROAD-P20-03 User-only: Owner plays the complete dedicated-server loop with two clients and restart; record fun/readability defects as well as correctness failures.
4. ROAD-P20-04 Remaining: Close blocking defects and capture baseline CPU/GPU/memory/network/loading evidence; make the scope/go-forward decision explicit.

Exit / acceptance: The complete loop is owner-accepted with durable player/base state, loss/recovery and boss rewards. This is an acceptance milestone, not a new giant implementation phase.

Canonical specifications and detailed tasks: Core Gameplay Loop FEAT-CORE-LOOP; Scope & Constraints GDD-SCOPE-CONSTRAINTS; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; Risk Register PROD-RISK-REGISTER

Phase 21 — Skills, achievements and advanced weapon depth

ROAD-P21 Not started

Entry / dependencies: P20 accepted core loop; UI-SYS-007/008 and later weapon depth proceed on their own backend dependencies.

Current evidence: Skill/achievement/workbench extensions are Not started or Blocked in G6. Item state and GAS foundation are reusable, not evidence of progression completion.

Work packages

1. ROAD-P21-01 Remaining: Implement activity-driven per-skill XP/level/progress and persistence using the canonical skill catalog; no global character level.
2. ROAD-P21-02 Blocked: Resolve XP curves/caps/bonuses and TBD-E2F4910C achievement catalog/reward decisions in their owning documents.
3. ROAD-P21-03 Remaining: Implement progression/achievement views, unlock toasts and authoritative reward actions without client-awarded progress.
4. ROAD-P21-04 Remaining: Add approved rail-position and stock-length customization with data-owned effects, compatible preview and durable per-item state.

Exit / acceptance: Repeated actions produce valid skill progress and approved rewards across restart; advanced weapon edits survive transfer/reload and cannot bypass compatibility.

Canonical specifications and detailed tasks: Crafting & Progression FEAT-CRAFTING-PROGRESSION; Player Statistics & Achievements FEAT-PLAYER-STATISTICS-ACHIEVEMENTS; Weapon Customization (Workbench & Field) FEAT-WEAPON-CUSTOMIZATION; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION

Phase 22 — Clans, territory and raid policy

ROAD-P22 Not started

Entry / dependencies: P17/P19/P20; G7 shared group service is reused.

Current evidence: Clan/territory concepts exist; UI-SOC-001 remains Blocked and no completed clan registry was evidenced.

Work packages

1. ROAD-P22-01 Blocked: Finalize canonical clan roles/name/tag/log and offline-raid policy decisions before shipping the affected permissions.
2. ROAD-P22-02 Remaining: Extend group services with clan roles, promotion/kick and invite-only administration; implement the required roster/activity UI.
3. ROAD-P22-03 Remaining: Connect territory/build privileges and raid access to authoritative group state and durable membership changes.
4. ROAD-P22-04 User-only: Owner verifies permission escalation/revocation, conflicting invitations, leader/member disconnect and raid access after restart.

Exit / acceptance: Clan and territory permissions are durable and auditable; all rejected actions have reasons and no stale membership grants unauthorized construction or access.

Canonical specifications and detailed tasks: Clans & Squads FEAT-CLANS-SQUADS; PvP, Raiding & Trading FEAT-PVP-RAIDING-TRADING; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION

Phase 23 — First networked vehicle and full-state persistence

ROAD-P23 Not started

Entry / dependencies: P07/P13/P20; UI-SYS-009 follows the vehicle backend without blocking the earlier squad/core slice.

Current evidence: Vehicle design exists; no Lambeer vehicle runtime was evidenced and the vehicle HUD task is Not started. Enabled engine capabilities or purchased meshes are not a working vehicle.

Work packages

1. ROAD-P23-01 Remaining: Deliver one selected vehicle with the confirmed 90% initial cabin-lock roll, exact-ID/inserted key ignition, cabin Lockpick, permanent Hotwire, driver/passenger seats, entry/exit and networked movement.
2. ROAD-P23-02 Remaining: Integrate fuel, damage, component condition, storage, repair and supported parts/upgrades per the full vehicle contract, including the owner-requested bumpers and protective exterior steel frames; resolve part behavior and first-release coverage before implementation. Action.VehicleRepair requires inventory Jack + Screwdriver + Pliers roles; those ItemIds are not registered. Canonical roles: FEAT-INVENTORY.
3. ROAD-P23-03 Remaining: Persist the full vehicle record and linked item/key/container state, including original spawn point, initial/current cabin lock, inserted key and permanent Hotwire; reject stale ownership and invalid access without rerolling.
4. ROAD-P23-04 Remaining: Connect vehicle HUD and owner-test passenger views, collision, seat changes, disconnect and restart with measured network behavior.

Exit / acceptance: One vehicle is drivable and recoverable after restart with all implemented state intact; it meets approved measured budgets before multiplying variants.

Canonical specifications and detailed tasks: Vehicles FEAT-VEHICLES; Lock & Access FEAT-LOCK-ACCESS; Network Architecture TECH-NETWORK-ARCH; HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION

Phase 24 — Starter towns and rural world production

ROAD-P24 Not evidenced

Entry / dependencies: P13 approved kits/streaming, P14/P16 integration and P20 accepted core loop. Owner confirmed expansion after limited-area proof.

Current evidence: The four-town Fresh Spawn UI passed in the sandbox. The production four starter towns, surrounding rural areas and authored spawn perimeters were not verified.

Work packages

1. ROAD-P24-01 Remaining: Produce the four selectable starter towns and connected rural/resource routes according to the canonical world concept.
2. ROAD-P24-02 Remaining: Populate enterable buildings with navigation, loot families, shelter, lighting, doors/windows and authored spawn perimeters.
3. ROAD-P24-03 Remaining: Integrate region threat, map landmarks and no-build areas without turning starter towns into safe zones.
4. ROAD-P24-04 User-only: Owner verifies traversal, spawn safety rules, interior access, AI, streaming and representative loot runs; retain region acceptance reports.

Exit / acceptance: All four starter-town areas satisfy the world concept’s relevant acceptance criteria; sandbox markers are replaced with accepted geography and measured traversal.

Canonical specifications and detailed tasks: World Design FEAT-WORLD-DESIGN; Inventory & Items FEAT-INVENTORY; Performance Profiling & Debugging TECH-PERFORMANCE-PROFILING

Phase 25 — Mainland cities and Lamla progression spaces

ROAD-P25 Not evidenced

Entry / dependencies: P24 kits/region acceptance; mainland city production follows starter-town production.

Current evidence: Central City, West Regional City and Lamla are concept requirements; this audit found no proof of completed production POIs.

Work packages

1. ROAD-P25-01 Remaining: Produce Central City and West Regional City districts, required malls/hospital/civic/military/airport and surrounding infrastructure from the world specification.
2. ROAD-P25-02 Remaining: Author enterable vertical and underground routes, lighting, navigation, loot and fixed encounter locations; honor approved floor rules.
3. ROAD-P25-03 Remaining: Implement Lamla’s restricted laboratory and anti-bypass progression locks using the findable, single-use, non-unique key rules in TBD-WORLD-006.
4. ROAD-P25-04 User-only: Owner validates city traversal, laboratory access, broken-door/window rules and dense-POI streaming/server profiles.

Exit / acceptance: Required mainland city/POI checklist is accepted with no inaccessible required floors or bypassable progression locks; perf evidence covers representative dense interiors.

Canonical specifications and detailed tasks: World Design FEAT-WORLD-DESIGN; Performance Profiling & Debugging TECH-PERFORMANCE-PROFILING

Phase 26 — Island, bridges and full-world integration

ROAD-P26 Not evidenced

Entry / dependencies: P25 and approved island/bridge/exclusion decisions; P20 limited-area acceptance precedes full-world expansion.

Current evidence: Island resort city, prison, port, airport and two independent highway bridges remain concept scope without completed runtime evidence.

Work packages

1. ROAD-P26-01 Remaining: Produce the island’s required resort/port/prison/military/airport spaces and their enterable interiors.
2. ROAD-P26-02 Remaining: Connect the two independent bridge approaches/landings and enforce approved no-build zones.
3. ROAD-P26-03 Remaining: Integrate mainland-island streaming, navigation, progression, loot, map markers and vehicle routes across the full target.
4. ROAD-P26-04 User-only: Owner audits the world’s WORLD-C acceptance criteria and full-route traversal/performance; record incomplete addresses/POIs explicitly.

Exit / acceptance: The full seven-settlement/island concept has an auditable content/QA inventory and accepted connectivity; no planning density or area baseline is relabeled as shipped geometry.

Canonical specifications and detailed tasks: World Design FEAT-WORLD-DESIGN; Performance Profiling & Debugging TECH-PERFORMANCE-PROFILING

Phase 27 — Roster expansion, loot economy and balance

ROAD-P27 Not evidenced

Entry / dependencies: P20 core acceptance plus relevant P21–P26 systems/regions.

Current evidence: Zombie/boss/skill/item catalogs describe intended content. Their existence is not proof that the roster, rewards or economy are integrated and tuned.

Work packages

1. ROAD-P27-01 Remaining: Expand normal zombies, fixed bosses, components/buffs and selected weapon/item recipes through canonical catalogs and runtime data.
2. ROAD-P27-02 Remaining: Implement the approved horde/surge event design after cadence/trigger decisions; measure AI load before raising density.
3. ROAD-P27-03 Remaining: Author source-owned drop-rate tables for every loot source and tune drop-trade, crafting and raid resource sinks from playtest data.
4. ROAD-P27-04 User-only: Owner runs repeated survival/progression/raid sessions; record scarcity, recovery, dominant strategies and adjustments with before/after evidence.

Exit / acceptance: Every promised content family has integration/QA evidence and traceable loot sources; progression and raid economy are accepted without invented drop-rate claims.

Canonical specifications and detailed tasks: Zombie & Boss Roster CHAR-DB-ZOMBIES; Zombie Design FEAT-ZOMBIE-DESIGN; PvP, Raiding & Trading FEAT-PVP-RAIDING-TRADING; Crafting & Progression FEAT-CRAFTING-PROGRESSION

Phase 28 — Accessibility, input, localization and presentation polish

ROAD-P28 Partial

Entry / dependencies: Existing G2/G4 presentation foundations; G8 follows G5/G6/G7 closure.

Current evidence: Fonts, localization samples and core settings have owner evidence. G8 accessibility/rebind/subtitle tasks are Not started; physical controller validation is still an explicit carryover.

Work packages

1. ROAD-P28-01 Remaining: Implement canonical colorblind palettes, English/Thai subtitles, reduced camera shake and centralized flashing policy.
2. ROAD-P28-02 Remaining: Finish rebind/conflict handling and hold/toggle settings with persistence and resolved input glyphs.
3. ROAD-P28-03 User-only: With hardware available, owner completes Xbox/PlayStation navigation, device-switch focus and glyph checks deferred from G2; do not infer them from KBM.
4. ROAD-P28-04 Remaining: Polish audio/VFX/UX and approved cosmetic presentation; validate supported resolution/aspect/language/settings combinations, including text clipping and focus.

Exit / acceptance: G8 presentation/input acceptance matrix is recorded, all supported devices have evidence or an explicit owner-approved release-scope change, and remaining strings/effects follow central policy.

Canonical specifications and detailed tasks: HUD & UI Implementation Plan TECH-HUD-UI-IMPLEMENTATION; HUD & UI System FEAT-HUD-UI; Audio Direction AUDIO-DIRECTION

Phase 29 — Performance, authority and stability hardening

ROAD-P29 Not evidenced

Entry / dependencies: Profile throughout; final gate requires accepted representative systems/content from P20–P28.

Current evidence: A detailed profiling runbook exists; no production-capacity profiling or integrated anti-cheat acceptance was established in this audit. Config player counts are not approved performance results.

Work packages

1. ROAD-P29-01 Blocked: Resolve canonical target/budget decision TBD-BFF08134 and security/platform choices before claiming target-load acceptance.
2. ROAD-P29-02 Remaining: Measure and optimize server CPU, client GPU, memory/GC, network, AI, MetaHuman LOD, streaming/loading and UI against comparable baselines.
3. ROAD-P29-03 Remaining: Integrate approved anti-cheat; harden inventory/combat/build/save/session authority and malformed/stale request rejection.
4. ROAD-P29-04 User-only: Owner performs target-load and long-session tests; retain crash/trace reports, defect reproduction and before/after regression evidence.

Exit / acceptance: Approved performance/stability/security gates have measured results on declared builds/hardware/topology; unresolved budgets or missing load tests block release acceptance.

Canonical specifications and detailed tasks: Performance Profiling & Debugging TECH-PERFORMANCE-PROFILING; Network Architecture TECH-NETWORK-ARCH; Risk Register PROD-RISK-REGISTER

Phase 30 — Server operations, backups and player hosting

ROAD-P30 Not evidenced

Entry / dependencies: P07/P17/P23 durable schemas, P29 hardening; operational constraints/ownership remain Unassigned until supplied.

Current evidence: Server target and hosting design exist. Official fleet, monitoring, admin tooling, tested backups/migrations and player-hosted distribution were not verified.

Work packages

1. ROAD-P30-01 Remaining: Package documented Linux server distribution, configuration and approved admin/RCON operations for player hosting.
2. ROAD-P30-02 Remaining: Implement/validate versioned migrations, backups, restore drills and database maintenance supporting no scheduled wipes.
3. ROAD-P30-03 Remaining: Prepare official server provisioning, monitoring, crash/log collection, update and rollback runbooks with measured capacity/cost inputs.
4. ROAD-P30-04 User-only: Owner approves operational configuration and executes restore/update drills; record data integrity and recovery outcome before live deployment.

Exit / acceptance: A recoverable server release can be installed, monitored, upgraded and rolled back with persistent state preserved; actual hosting costs/credentials/owners are not invented.

Canonical specifications and detailed tasks: Servers & Hosting TECH-SERVERS-HOSTING; Network Architecture TECH-NETWORK-ARCH; Risk Register PROD-RISK-REGISTER

Phase 31 — Release candidate and launch acceptance

ROAD-P31 Not evidenced

Entry / dependencies: P20–P30 applicable gates closed; no unresolved release-blocking decision or defect.

Current evidence: No release candidate, launch acceptance or live build was evidenced. This phase authorizes no deployment by itself.

Work packages

1. ROAD-P31-01 Remaining: Freeze the accepted content/scope and produce traceable client/server release artifacts and release notes.
2. ROAD-P31-02 User-only: Owner completes installation, join/rejoin, full-loop, localization/accessibility and persistence regression against the candidate.
3. ROAD-P31-03 Remaining: Verify support/feedback, player-hosting documentation, monitoring and recovery readiness; classify remaining defects explicitly.
4. ROAD-P31-04 User-only: Obtain the owner’s concrete release/deployment decision for the reviewed candidate, then follow the authorized launch procedure.

Exit / acceptance: The reviewed buy-to-play release is explicitly accepted by the owner with evidence and known issues; deployment and live health are recorded separately from a successful build.

Canonical specifications and detailed tasks: Scope & Constraints GDD-SCOPE-CONSTRAINTS; Servers & Hosting TECH-SERVERS-HOSTING; Risk Register PROD-RISK-REGISTER