tegwick
51efe55d14
Some checks failed
ci / check (push) Failing after 4s
Tier S (fixes inside a boundary; chaos d8=3, no override). Two observations from play, both about what the page says has happened. The controls moved BELOW the log: you read what happened, then decide what to do next. They were above it, which asks for the decision first. And sealing now marks the WHOLE PAGE inert, not just the controls. A greyed-out button beside a full-colour table still reads as a live game with one broken control; the session has ended and everything on screen is a record of it. The status line stays legible on purpose -- it is the one thing still worth reading. THE STUB NEEDED A BODY classList TO MAKE THAT TESTABLE. Without it "the session visibly ended" would have been a claim about CSS with nothing checking it, which is precisely CB-WP-0016's finding: a stub too thin to express a failure is how the failure survives. The harness reports the sealed page through the status channel with a NUL-separated marker -- ugly, deliberate, and documented, because widening the return type would touch every caller for one boolean. Both directions asserted: a `closed` reply seals the page, an `ok: dealing` reply does NOT -- otherwise the seal test would pass for a page that greys itself whenever it is touched, breaking `play again`. 63 render tests, 26 cb-play, check and loop-lint clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| benchmarks | ||
| crates | ||
| decisions | ||
| editions/ground-darvo-r0 | ||
| evidence | ||
| games/ground | ||
| history | ||
| research | ||
| scenarios | ||
| specs | ||
| tools | ||
| trials | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| clippy.toml | ||
| facts.toml | ||
| gates.toml | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| rust-toolchain.toml | ||
| WORK-RECORDS.md | ||
clay-borg
A rebuild from scratch simulation and games engine framework set up to assimilate and optimize techniques and implementations useful for games, simulations, robotics.
Licensed under the Target Revenue Source License (TRSL V1C1) — see LICENSE; canonical text lives in the org's target-revenue repository.
Running the gates
make all # every gate, from a clean shell
make -C /path/to/clay-borg all # …or from any other directory
There is no environment setup step. No cd, no export PATH, no
activation script. make locates the repo from its own path and cargo
from the standard rustup locations; the Python tools do the same via
tools/repo.py. The only prerequisites are a rustup toolchain and Python
3.11+.
This is deliberate and enforced: make env-test runs every tool from /
with a PATH containing no cargo, and make all includes it. CB-RES-0003
measured 84 agent turns and $15.33 spent prefixing commands with cd and
export PATH before that friction was fixed at the root (CB-WP-0004 T01).
Other useful targets: make cost (spend per task), make cost-budget
(spend since the last commit), make cost-mix (mechanical vs judgment
turns), make loop-lint (executable InnerLoop rules), make self-tests
(every tool's positive control).
GROUND
The first product vertical is a virtual tabletop implementation of GROUND — A Game of Bonds and Rivalry: DARVO Edition. The boardgame itself (rules, editions, content) is at home in the sister repository ground-game — that repo is authoritative for what GROUND is; clay-borg implements the engine that runs it.