the guide, reconciled — and the banner was confidently backwards

Adopts the loom-cli guide the builder wrote, and reconciles guarantees.md, which
grew an append-only "Surface changes" section: the promise is not that the command
surface holds, but that a change to it lands on the page we already lock. A rename
reports 200 here the day it happens.

The banner said "written against an older guarantees". It was wrong. The guide was
stamped against a version newer than our copy — the builder had pushed and we had
not reconciled — and the message claimed a direction it cannot possibly know,
because an etag is opaque and two of them cannot be ordered. That opacity is the
point of the lock. The banner now says only that the two differ, and names both
ways out.

It also means reconciling cleared this banner with no ack, which is correct: ack
is for a guide that is behind, and this one was ahead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

.loom/externals/.locks

@@ -11,4 +11,4 @@ git.hypertheory-labs.dev/loom/bedrock/sibling-facets.md	https://git.hypertheory-
 git.hypertheory-labs.dev/loom/bedrock/starting.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/starting.md	"b9eefba0f4668a496ccfc6a1377277f0721456d2"	public
 git.hypertheory-labs.dev/loom/cart/cart.md	https://git.hypertheory-labs.dev/loom/cart/raw/branch/main/.loom/published/cart.md	"15331f1a9cc81bf61a44830cfbb7c274f4c2b119"	public
 git.hypertheory-labs.dev/loom/externals/externals.md	https://git.hypertheory-labs.dev/loom/externals/raw/branch/main/.loom/published/externals.md	"50673ccffc14d57150ac0a9027b0712d9dcf940d"
-git.hypertheory-labs.dev/loom/loom-cli/guarantees.md	https://git.hypertheory-labs.dev/loom/loom-cli/raw/branch/main/.loom/published/guarantees.md	"432822b3f91ec7c7acd2c868490b7cdcde5db99a"	public
+git.hypertheory-labs.dev/loom/loom-cli/guarantees.md	https://git.hypertheory-labs.dev/loom/loom-cli/raw/branch/main/.loom/published/guarantees.md	"e8c697ea61df47838f38af7353e29d9ae3f7070c"

.loom/externals/git.hypertheory-labs.dev/loom/loom-cli/guarantees.md

@@ -88,6 +88,27 @@ has not earned.**
 **That anything is checked when you are not looking.** *Nothing here runs on a
 schedule, and a document nobody checks is a document nobody is checking.*
 
+## What is promised about the things that are not promised
+
+**The command surface may change. This page will say when it does.**
+
+*A consumer whose README tells a person to type `loomctl external add loom/<repo>
+<doc>.md` depends on that command by name — **not by parsing it, which is why no
+check would ever catch a rename**. The thing that moved would not be a document
+they adopted.*
+
+> **So the exclusion is narrower than "you are on your own".** *We do not promise
+> the surface holds; **we promise that a change to it lands here**, on a page you
+> can lock* — **and a lock on this page reports `200` the day a command is
+> renamed.**
+
+**That is the whole mechanism, and it costs one section:**
+
+### Surface changes
+
+*Append-only, newest last. Nothing yet — the commands have not been renamed since
+this page existed.*
+
 ---
 
 *Verified fetchable by somebody who is not us on 2026-09-08.*

.loom/externals/git.hypertheory-labs.dev/loom/loom-cli/guarantees.usages.md

@@ -22,6 +22,15 @@ not parse them, but a person following our README will type them.*
 > check will catch it*, **because the thing that moved is not a document we
 > adopted.**
 
-*Recorded rather than solved. It is the same class as the sub-page staleness limit
-in `HANDOFF.md`: the lock watches documents, and some of what we lean on is not a
-document.*
+**Half-closed upstream, 2026-09-08.** *`guarantees.md` grew an append-only
+`Surface changes` section.* **The promise is not that the surface holds — it is
+that a change to it lands on the page we already lock**, *so a rename reports
+`200` here the day it happens.*
+
+> **The record is not that the thing never changes. It is that the change is
+> findable by whoever depended on it.**
+
+**The half still open is ours and cannot be closed by them:** *our README tells a
+person to type a command, and a person typing is not a dependency any lock
+watches.* **Same class as the sub-page staleness limit: the lock watches
+documents, and some of what we lean on is not a document.**