Takeshi
5dde0c5ec2
Capture current source, content data, tests, asset licenses, and original-specification traceability. Original implementation remains incomplete. The accepted matching UI generation passed 154 suites and 12,253 checks, with eight rendered staff-contract screens reviewed. Latest native Windows and full-original acceptance remain outstanding.
5.3 KiB
Premium room normal registration (2026-09-29)
Status: partial P08/P10 progress, not whole-package acceptance.
Added premium_room to ORIGINAL_FACILITY_PATHS and normal Runtime registry (20 definitions), main construction palette, shared lodging icon, bedroom furniture and sleeping presentation. Original dimensions 4x1 remain canonical. Explicit customer capacity is 2. Approved initial daily upkeep formula ceil(900*0.005) gives 5G; this is a tuning value, not an original-spec numeric claim. Existing price220G, duration720minutes and mana demand1 remain unchanged.
Evidence:
- premium-service.log:15 checks PASS. Ordinary Runtime construction commands create reception and premium room without a test registry. Service request at definition price/duration starts, restores halfway, completes with one220G charge, balances ledger and restores at midnight. The payer is a service-wallet fixture; autonomous walking/admission is not tested here.
- premium-dashboard-final.log:136 native rendered checks PASS. Main palette selects the4x1 definition. premium-palette.png visually inspected: visible and selected premium-room button at900G/material10. Shared generic room icon is reused, not a finished unique art claim.
- premium-runtime-regression.log:20 PASS; premium-migration-regression.log:56 PASS; premium-stairs.log:65 PASS; premium-check.log:make check exit0.
Remaining: actual guest AI access/arrival and lodging after normal placement, full-day normal operation with capacity/outages, other original facilities, staff/transport-safe migration UI, Windows acceptance. No complete P08/P09/P10 claim.
Autonomous guest acceptance (2026-09-29)
Added test_premium_room_guest_flow.gd to make test-mvp. 30 checks PASS in premium-autonomous-final.log. Construction uses ordinary commands for reception, premium room and two guest stairs, with no direct geometry or route injection. Guests enter through the spawn command with controlled sleep needs and funds; target facility and path are not supplied. The real AI selects premium lodging and moves via the first stair landing before automatic queue/service creation.
Actual stair-save replay reproduces the complete arrival snapshot. Real guest lodging restores mid-service. Empty mana pauses elapsed service and avoids charging; a disposable disk snapshot restores the paused guest/service, then mana recovery completes the service with one220G charge. Midnight ledger and full snapshot restore pass. A second normal-built fixture sends three deciding guests; observed concurrent usage reaches2 but never exceeds2, the third guest is observed QUEUING separately, and crowded state restores exactly.
These are deterministic Runtime acceptance scenarios using controlled guest inputs, not natural production arrival distribution, physical UI pointer placement or Windows acceptance. Original-spec all-facility completion, other lodging/dining, prices and long-term balance remain pending. No new production behavior was changed in this verification increment.
Viewport input and natural opening day (2026-09-29)
Added tests/ui/test_original_build_pointer.gd to test-ui. Initial5000G, normal production loop and natural arrivals; no guest spawn, target/path injection or direct build/hire/assignment/save/load handler calls. Mouse events traverse viewport GUI hit testing for the palette, horizontal scroll, map placement, hire/assignment controls and save menu. Popup keyboard events use Input.parse_input_event and the target window ID. Time is advanced by the clock API, not real-time playback. This is synthesized engine input, not OS pointer automation or Windows acceptance.
The scenario builds reception, premium room and two stairs, hires Akane and assigns the receptionist, completes natural lodging for440G by first midnight, verifies the ledger, saves/loads via controls, compares facilities/economy/guest/staff/construction state and replays the next30minutes exactly. Native rendered run36 checks PASS. original-pointer.png visually inspected at Day2 00:30: premium room occupied, separate queue, guide reports first-day completion.
This exposed a production bug: opening guidance recognized only standard_room for room existence and first lodging sales. It now recognizes FRONT lodging definitions (service type or legacy lodging tag), and recognizes their active construction. Default recommended build remains the inexpensive standard room. Staff dormitories do not count as guest rooms.
Initial failures are retained in original-pointer-day*.log: infrastructure stairs belong to ConstructionService rather than FacilityService, and injecting keys directly into PopupMenu's viewport bypassed native popup processing. Those were test-harness issues; the guide's hard-coded standard-room checks were the production issue.
The previous Windows EXE/PCK predates this guide fix; do not treat its prior acceptance as validation of this revision. Remaining: actual OS/Windows input, other original lodging/dining facilities, broader seeds and long-term balance.
Final verification: original-pointer-day-complete.log36 checks PASS (headless, includes active premium construction guide); original-guide-standard-regression.log48 checks PASS, preserving ordinary standard-room opening through next-morning save/replay; original-guide-check.log make check exit0. Native36 run preceded the final active-construction hint adjustment; that adjustment is covered by the final headless run.