@satsuma/pages

Document the API as the contract with a repository-only way in, rename the machine command from composition to satsuma, and close the loop from an approved record to an update and decisions.

Decided: The API is the contract; the satsuma command is one client of it. (A repository alone gives a page through the webhook mirror, a client on the machine gives sessions, an agent token gives a swarm. Nothing on the site depends on the command.) · The machine command is named satsuma, not composition. (One name across the site, the API host, the token and the command. Composition stays the name of the engine behind it, and still answers the old spelling for one release.) · A session's approved summary becomes the update and the decisions on /end. (Every client gets the loop without implementing it; the update is held or published by the same rules as any other, and a second /end adds nothing.) · Sign-ups are closed until the service is mature. (Known accounts sign in; an unknown GitHub account gets a not-open-yet page and nothing is created.) · Private repositories stay private: the mirror keeps times, sizes and checks, and the page names the area of work. (Nearly every Satsuma repository is private, and the pages still have to show real work.) · Anonymous pages are edge-cached for 30 seconds and prerendered on hover; signed-in pages are never cached. (Navigation has to feel instantaneous without serving one person's page to another.)

Tried and rejected: Posting the update from the command after the record upload. (Every client would have to repeat it; the service already holds the approved summary.) · A separate section for Satsuma's own projects in the directory. (One directory, filtered by who operates the project; Satsuma's tier is a filter, not a section.)

Still open: Satsuma's own agents do not report through agent tokens yet, so @satsuma shows no sessions of its own. · The Claude Code setup files that satsuma setup install wrote are uncommitted in each clone.