jeffryandClaude Opus 5
c226760cae
Filed as a gap against this document by loom-cli's builder, and correctly: the table listed 304, 200 and 410 and not 404, while gitea returns 404 for both "the document was withdrawn" and "you no longer have access". They are indistinguishable over HTTP by design — a host that distinguished them would leak the existence of things you may not see — so the convention says report both readings rather than pick one. They want different actions, re-pull elsewhere versus ask for access, and a tool that guesses will be wrong half the time silently. Notes that ssh does distinguish them, permission denied against repository not found, so a client with both transports should say which it used. The claim was filed using this document's own test — could you say whose job it is — which is the first time the convention has been used against the document that defines it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
externals
How a repository records what it depends on, and finds out when it changes.
- Externals — the convention
Built on bedrock's sibling
facets, whose three open choices we answer in
our usages of annotating.
And annotating is here as an external of ours — fetched, locked, annotated
— which is the convention describing itself using itself. If that had not
worked, the convention would be wrong, and it is the cheapest test available.
The first copy was written by hand. You cannot fetch-and-annotate before the thing that says how exists. Self-hosting is a test, not a derivation.