DarkRoom

`traceability-check` fails on master: the committed matrix does not match
what the generator produces, so the gate that exists to keep the two in
step is the thing reporting they are not.

Nothing was traced or untraced. Coverage is 51.4% (91/177) before and
after, the same 604 tags against the same 177 requirements; every one of
the 32 changed rows is a line number that moved when the clippy warnings
were cleared -- `adjust.rs:2150` is now 2164, 632 is 651, 751 is 770.
The matrix links to lines, so touching a file above a tag rewrites its
row without changing what it says.

Regenerated with `cargo run -p traceability -- report`, which is what the
failing step tells you to run.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-25 23:21:13 +02:00

architecture.md

No phone, so stop designing for one

2026-08-22 09:55:09 +02:00

catalog.md

Give a shard's remote name the client that wrote it

2026-08-16 21:15:12 +02:00

milestone-v0.1.md

Add thumbnail size classes and grid zoom; fix the scrub ordinal

2026-08-09 21:58:32 +02:00

requirements.md

Render a film stock on the GPU, and let it take over the rendering