[udaychandra]

Spec: sail-project-dm. Paired with standardapplied/mast#134 (branch agent/sail-project-dm), which places the home room in Mast's sidebar.

What changes

• agent.member in the definition (agent, model, mode). It is optional, and each field has a default: agent.type, the agent's default model, and full. The member is validated when the definition is read, whether it is declared or comes from the agent.type default. A member the project does not install, an unknown mode, or a model that is not one shell-safe token is refused there, so project apply refuses before provisioning and names the field. A definition that names no agent has no member. Agent.installs() replaces three copies of the "install, else type" rule (apply, provisioner, reviewer roster).
• HomeRoom.ensure is the last step of ProjectApplyCommand.converge. It runs as the box's FDE (CliOperator) and goes through the API's own door, POST /v1/rooms, which now takes an optional member.
  • The member is admitted exactly as addRoomMember admits one: owner, trusted roster, a valid mode and model, the container Running, and the harness installed. The room is then written with the member already seated, in one revision.
  • A refused member creates no room and leaves nothing to sync, and the next apply creates the room seated. So an empty roster is only ever the owner's choice, and a room that already exists is never touched.
• The room id is HomeRoom.idOf(project, handle). It is <project>--<handle> when that is a valid room id.
  • Any other valid handle (upper case, '.', '_', or too long) is folded to the room id alphabet, cut to fit, and suffixed with the handle's CRC-32 (8 hex characters). Every FDE gets a home room, and ids stay in the room/spec namespace.
  • An existing room under that id that someone else owns refuses the apply and names the owner. An id a spec already holds refuses with the API's own sentence.
• sail project apply --json gains home_room: {id, created, engaged} (or {skipped}). GET /v1/projects/{p} gains member and the reader's home_room id, so Mast never derives the id itself.
• ARCHITECTURE.md gains the home-room contract H1–H6 with its tests. README and CHANGELOG are updated.
• Separate fix: AgentLogStreamer.pump dropped lines that a tail wrote between an empty ready() and its exit. pumpRelaysWhatTheTailWroteBetweenAnEmptyReadyAndItsExit reproduces it deterministically.

Tests

• HomeRoomTest runs against the real SailOperations with a scripted container shell. It covers:
  • the first apply, a second apply as a no-op, and an FDE's disengage winning;
  • the codex member with its model, and a later definition leaving the roster alone;
  • a refused member creating no room or revision, then the next apply creating it seated;
  • each FDE owning their own room;
  • a folded handle (Ada.L) getting a room, and the longest project and handle staying valid and distinct;
  • a squatted id, an id taken by a spec, an unreadable room, no handle, no agent, and a box without rooms.
• HomeRoomIT (real incus) runs the sequence: missing harness and no room, then install and the room created seated, then a no-op apply, then disengage, then an apply that leaves it disengaged.
• SailYamlTest covers the implicit member refused when not installed, no agent meaning no member, and a member block with nothing to fall back on.
• ApiRouterTest covers POST /v1/rooms with a member. SailOperationsTest covers member and home_room on the project response.

Departures from the spec

• The spec-collision refusal uses the API's actual sentence, "Spec 'acme--ada' already owns that conversation id.". The spec quoted a different sentence but said "the same sentence the API uses".
• Build step 4 says a refused engage leaves the room "created and unengaged, so the next apply engages it". Here a refused member creates no room, and the next apply creates it engaged. The outcome is the same, and it matches scenarios 5 and 6 ("no room is created"). It also means an empty roster never has to be told apart from a disengage.
• A handle that is not a valid room id is folded and given a digest suffix (HomeRoom.idOf), so the room id is not literally <project>--<handle> for those handles.