House Starshine / website release
Play a little.
Remember what happened.
Published · ready for shared playtesting
One place for Joel and a friend to record the details that matter, without turning a play session into a room-by-room audit.
Open the shared playtest board ↗Green: done. Amber: in progress or staged. Red: not yet done. Human acceptance is never inferred from deployment.
Accounts and shared storage
Private admin and tester accounts, persistent shared results, named changes and reports. Signing in protects the catalogue and feedback; it is not stored only in one browser.
Feature-first playtest catalogue
35 focused cases across 27 map filters and 7 feature groups. Each case has practical actions, expected results and a route to the right place. Glimmer remains a known closure, not an invitation to reproduce its crash.
A small session is enough
Filter by feature or map, open a case for its steps, and record one result. Bulk updates handle several selected cases. Bugs, ideas and questions can be tied to a case or location.
Shared edits and future releases
Concurrent edits are checked rather than silently overwritten. The release refresher preserves comments and history, marks tests affected by known changed resources, and flags incomplete release history honestly.
Website publication
The login page and authenticated service are verified through the public HTTPS address before this step is marked complete. Existing game state and playtest results are not reset.