jeffryandClaude Opus 5
73b3a97dce
The config becomes kubectl-shaped — named contexts with one current, each holding a host, its flavor and a read-only token — and a bare owner/repo resolves against it. The point is where the details live: a host's raw-file route belongs to the host so it sits in the context, the published directory belongs to the convention so it sits in the code, and what is left is which repository and which document, which is the only part a person knows. Measured rather than assumed, because the three hosts differ. Gitea redirects its short raw form to the resolved branch, so the lock records a branch without anybody naming one. GitHub and GitLab accept HEAD and do not redirect, which would put a moving ref in the lock — the hazard already recorded and nearly built anyway — so those resolve the default branch with git ls-remote --symref first, one round trip and no clone. That supersedes the claim that list is the only command needing git, which is now wrong for two of three flavors and would otherwise read as still true. Adds loomctl config, which says which context is current and where the credential came from without printing it, so that "my token is not being used" is answerable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
loom-cli
loomctl fetches the documents this repository depends on, and tells you when
they change. It reports; it never repairs.
go build -o loomctl .
./loomctl --help
check only reads. Nothing here writes over the network, so a credential it is
given never needs write scope.
Why it is the way it is: .loom/event-log.md. Every
entry says what was decided and the belief that could turn out to be false.
What it depends on, and what we could not tell from those documents:
.loom/externals/ — the .gaps.md files beside each one.