jeffryandClaude Opus 5
49c7297d08
It still said Not built, listed pull and reachable — neither of which exists — and claimed everything was decided in one round. Written at a conversion and never touched again. Deliberately does not enumerate the commands, because a prose command list is exactly what went stale. It points at --help, which is the documentation surface we already decided on and which cannot drift from the binary. Worth noticing rather than logging: check catches documents that drift from their publisher, and nothing catches ours drifting from our own code. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
19 lines
609 B
Markdown
19 lines
609 B
Markdown
# 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`](.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/`](.loom/externals/) — the `.gaps.md` files beside each one.
|