jeffryandClaude Opus 5
b41148f369
The sidebar named its four sections by hand, so adopting from a new repository needed a config edit — a second place to update, which is exactly what the autogenerated directories were already avoiding one level down. It is written from the locks now and astro.config.mjs names nothing. guarantees.usages.md is the first usages facet here with a short real answer, because this site is built with the tool: check-reports-does-not-fix is what lets npm run check run in CI, and the etag being the publisher's verbatim is what the guide stamps are. It also records what we lean on that the page explicitly does not promise — the command surface, quoted in our README. A renamed command breaks our documentation and not our build, and no check will catch it, because the thing that moved is not a document we adopted. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
.loom — loom/docs
This repository publishes nothing. It is a reader.
What is here is externals/ — a copy of every document the loom
organisation publishes, locked to the version it was fetched at. The site at
loom.hypertheory-labs.dev is those copies,
rendered, plus four hand-written section fronts.
Nothing in externals/ is edited here. A copy that differs from its source
is the only evidence that something moved while nobody was watching, so editing
one destroys the mechanism this repository exists to demonstrate.
What we hold about a document goes in a facet beside it — .usages.md for what
of ours depends on it, .gaps.md for what we expected and did not find.