jeffryandClaude Opus 5 1543df0a0c loomctl external: list, add, check — and its first run found two changed documents
Go, standard library only, with git shelled out for list alone. list enumerates a
publisher's .loom/published by partial clone and ls-tree; add fetches one document,
writes it under .loom/externals and records the resolved origin and the publisher's
ETag in .loom/externals/.locks; check asks conditionally and reports.

The first real run did what the tool exists for. All eight documents adopted by
hand before it existed reported unlocked — the tool refuses to invent a lock by
adopting whatever the remote currently serves, since that would assert the local
copy is the one being served, which is the thing it was about to check. Locking
them fetched two that had moved: bedrock/starting.md, which now says the worked
example is private and will not link to something you cannot fetch, and cart.md,
which went to v1.

cart v1 changes a role we cast: a cart is not committed, because a committed cart
grows a third file by itself — version control does not require anybody to ask, so
the two-file rule is never invoked — and because ignored, gone means gone. Adds
.loom/cart/ to .gitignore and supersedes the isolation entry rather than editing
it. osprey and marmalade are already in history and are left there: rewriting to
honour a rule adopted afterwards costs more than it buys.

Records the conflict this creates rather than settling it: the annotation protocol
here says commit before dissolving because git is the only archive, and an ignored
cart has no archive, so dissolving would destroy the annotations outright.

Credentials are read-only, per host, and passed to git through the environment
rather than argv, because argv is visible to every process on the machine.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
2026-09-07 14:48:29 -04:00

loom-cli

Not built. A small tool for the operations a person should not do by hand: fetch a document you depend on, and find out when it changed.

The design is in .loom/event-log.md, not in a spec. Every entry says what was decided and the belief that could turn out false, so you can see which parts are load-bearing and which were guesses. Everything tagged osprey was decided in one round.

Three commands. pull adopts a document and writes its lock; check asks every publisher whether their copy has moved; reachable asks whether somebody who is not you can fetch what you published. None of them repairs anything.

bedrock and externals, under .loom/externals/, are not discardable. Read them as given — accommodating them is what makes this a loom tool rather than some other thing.

S
Description
No description provided
Readme
592 KiB
Languages
Go 100%