Repository navigation
Project Tracker
What is outstanding in RoomCAD: open work and open decisions, one row per item.
Nothing else is listed. Finished work is the git history — one commit per thing — and
the facts that are easy to get wrong twice live in AGENTS.md, this repository's one
instruction file. Rows that were finished, decided against, or only worth knowing have
been removed; this wiki's own git history is where they went.
Gate: ./tests/run.sh — the whole suite, 41 files and 2405 checks. CI runs it on
every push and pull request. Nothing is closed until that is green.
Numbering: a number is assigned in the order the item was raised and is never
reused, so a gap means that item is closed — not that the list was renumbered. The
earlier ids (T17, H1, and the D*/N* rows) came from a longer table that also
carried completed, declined and reference rows; that table is in this wiki's git
history, not here.
Status: Open = work to do · Waiting = blocked on a human action.
Counts: 0 Open · 2 Waiting.
| Task | Item | Status | Detail |
|---|---|---|---|
| T-01 | Ship 10.8: the live site is still 10.7
|
Waiting | The repository is at 10.8 (roomcad/web/version.js is the only release source, enforced by tests/version.test.mjs) and the deployed site has not been updated, so it does not carry the current source. Everything that can be checked without touching the host has been: tests/deploy-config.test.mjs is 101/0 (the CSP hash of the inline import map matches both Caddyfiles), both Caddyfiles pass caddy validate, and the whole suite is green. roomcad/server/deploy.sh is the only thing that ships it: it validates the candidate Caddyfile with the VPS's own Caddy, aborts before installing anything if that fails, and refuses to report success until the live URL answers. It now also syncs roomcad/server/roomcad_api/ — server.py is a facade and importing it without the package fails — with --delete, so a module dropped here disappears there too. The one thing missing is SSH access. main carries the work and CI is green on it, but root@91.99.176.243 answers Permission denied (publickey,password) for the only private key on the machine that would run the deploy, so it stops there. To clear it, either append ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIM4uhv+KQmP4FOaQgvWsnw48LDyd59j1cUdBxXfG3oqm node1@Node1.local to /root/.ssh/authorized_keys on the VPS, or run cd roomcad/server && ./deploy.sh yourself. A deploy is not a release: it creates no tag, no archive and no notes. |
| T-03 | Look at the 3D in a WebGPU browser, at night | Waiting | Nothing in this repository renders the scene: Walk3D needs WebGPU and cannot be instantiated headlessly, and tests/boot.test.mjs deliberately stops at the module graph. The lighting paths are covered without a browser — tests/audit-walk3d.test.mjs drives the real prototype's methods with fake resources, tests/plan-seal.test.mjs resolves every shadow.bias in the walkthrough and refuses a negative one, and the shadow-map sizes and the light pool are checked by tests/room-lights.test.mjs — and the city's own lamps are checked by tests/city-fuzz.test.mjs (bright in daylight, brighter after dark, brakes brighter than tail lights). What no check can see is what it looks like: if the normal bias derived for the street lamp's 512² map is wrong for its reach, the symptom would be shadow acne on lit street surfaces. This needs a human with a WebGPU browser after dark. |