Implement Homeworld mechanics through Caladan reinforcement checkpoint
Connect typed Homeworld custody, transport, battle, income, revival and Caladan reinforcement flows with private multiplayer recovery and controls. Preserve the optimized test workflow and keep unfinished rules modes gated. Verified with 3682 offline tests, typecheck, lint, production build and 40 HTTP tests; existing saved games remain unchanged.
This commit is contained in:
1 parent
3be49512f7
commit
28ba1618ba
266 files changed
+47680
-16851
No files matched your search
@@ -30,16 +30,21 @@ An uncertain saved-kit recovery keeps its exact retry details in memory and prev
|
||||
|
||||
## Verify changes
|
||||
|
||||
Run the development server before the persisted multiplayer suite:
|
||||
Use the [development guide](docs/DEVELOPMENT.md) for architecture, focused tests
|
||||
and the verification workflow. Tests are discovered automatically; the default
|
||||
suite includes in-memory persistence recovery and needs no server:
|
||||
|
||||
```sh
|
||||
npm test
|
||||
npm run test:multiplayer
|
||||
npm run typecheck
|
||||
npm run lint
|
||||
npm test -- ecaz-collection ecaz-spice
|
||||
npm run check
|
||||
npm run build
|
||||
```
|
||||
|
||||
Run `npm run test:integration` against a development server for HTTP/session
|
||||
changes. `npm run test:multiplayer` remains available for recovery plus HTTP
|
||||
checks; `npm run test:recovery` runs only in-memory persistence tests. All test
|
||||
commands accept filename fragments and `--list` after `--`.
|
||||
|
||||
The production build is written to `dist`. `npm start` runs that build with Wrangler; apply its database migrations to the intended storage environment before use. The included local migration command targets the development database, not a remote deployment.
|
||||
|
||||
Reproduce the current AI study with:
|
||||
|
||||
Reference in new issue
Block a user