Joining now, by USAGE.md: on the server, 'project', or an existing repository's hook and chat-timeline-user settings; on the client, 'register' to a credentials file, an admin opening the link and pressing, the daemon collecting and cloning; then for each session user, the ticket on run logins by hand; then a run from the right pattern naming the right node and user, with the first start's folder trust. Bringing in a remote agent was already 'such a pain' to the maintainer (docs/backlog.md).

Smallest first: once the hand-collected logins are gone, what remains is one command on the client, 'register', one press on the server, and a wiki pattern. Write that sequence down as the one path for a separate client, and split 'project' so its server half stops expecting a daemon root there. Then add the project's name to one data list on the client (hosts.json's sync list is the model, in keeping with KEEP.md's 'don't put into code what is just data'), rather than a new command, unless the list proves too little.

Passes when: joining a new project to x86-1 takes one command on the client and one press on the server, and its first session answers with no one at its terminal. Depends on the tickets on run logins and folder trust.