Suggest the room: a department offers, the founder convenes

[TruongGiang2000]

Step 3 of "one founder runs the whole company", after #247 (a department answers as itself) and #248 (it keeps a notebook).

What

Since #247, a department answering in Ask is told to say "this one needs Marketing too", but the founder had no way to act on that. Now the department can offer to bring the others in, and one press convenes that room.

• Chat tool suggest_room. It is offered only on a turn that answers as a known department. coerceRoomOffer keeps 2–4 known keys, removes duplicates and caps the list, and clips question/why. An invalid offer is dropped without failing the turn. The offer rides the done frame as room_offer and costs nothing until the founder presses it.
• Card. It shows "Bring Finance + Sales in →" plus the department's reason. One press convenes the room through sendChat(convenesRoom:requestedAgents:), which sets VirtualCompanyRequest.agents. The card is disabled while a turn is in flight and cannot be used twice.
• The room honours the pick (applyRequestedAgents). With 2–4 valid departments the routing is forced to multi_agent with exactly those, so the room never takes the escape hatch. chief_of_staff, the red team and Product can't be requested. The router's real_question is kept, and so is devils_advocate if the router named it. The routing panel is made consistent with the forced room: picked departments leave "not in the room", each gets a ✓ reason, and there is no "Missing:" line. Without agents, behaviour is unchanged.
• SSE contract (the authority): adds the agents field and the rule that a founder-picked room never escapes.

Spec: docs/superpowers/specs/2026-10-09-suggest-room-design.md · Plan: docs/superpowers/plans/2026-10-09-suggest-room.md

Verified

• jest 1086/1086. Covers the coercion, the tool being offered only on department turns, room_offer on the done frame, validateRunPayload, and applyRequestedAgents, including a run whose router returns single_agent but which still convenes the requested room.
• Swift RoomOfferWireTests (decode, and agents omitted when nil) and RoomInviteTests (the offer lands on the reply; one press convenes exactly finance+sales on the offer's question, and a second press does nothing). The existing RoomOfferTests, CompanyStoreChatTests, CompanyStoreVirtualCompanyTests and ApprovalParityTests pass.
• A fresh whole-branch review found no Critical issues. Of the two Important findings, the routing panel is fixed (test red → green). The other, a press that could burn the offer, is unreachable: both busy flags are set and cleared together on the main actor with no await between them.
• Not yet tried in the running app. The machine was in use. Steps: ask "Ask Finance: should we discount the Pro plan by 30% this month to close more sales?", check that the card appears, press it, and check that the room convenes with Finance and Sales.

Deferred minors

• JS prototype keys (toString) get past in ROOM_AGENT_FOR. A model would have to emit one.
• An offer is not required to include the answering department.
• The press posts the question as a founder bubble plus a generic chat reply, as Plan does.
• The Swift key-map test is a Swift-side copy.
• ChatTailAction was not updated (harmless).
• One escape-path test is a regression pin rather than a guard.

🤖 Generated with Claude Code

[TruongGiang2000]

Checked in the running app at 71fd6dc, real account with a project folder linked:

• "Ask Finance: Marketing wants to spend $5,000 on paid ads… Sales wants that money for a demo contractor. Which should we fund?" → Crash · Finance answered, and the card Bring Finance + Marketing + Sales in → appeared under the reply with its reason.
• Pressing it convened the room with Finance, Marketing and Sales, all three answering.

What testing found, and fixed:

1. No card at first. Traced layer by layer:

   • the app sent dept_key=fin;
   • the bundled sidecar had the tool;
   • claude's init listed mcp__codepet__suggest_room with the MCP server connected;
   • the model simply never called it.

   Replaying the app's exact request gave 3/3 offers without the linked folder and 0/3 with it. The role framing only told the model to say another department was needed. The role block now tells it to answer and call suggest_room. Same request, folder linked: 4/4. A one-department question (runway from burn and cash): 0/3, so it doesn't over-trigger. (2dc8429)

2. Copy. The reply said "press the room button above", but the card sits below. The tool description and the role block now both say below. (71fd6dc)

jest 1089/1089.