[Birfy]

Fixes #404

Bot Social's owner-confirmed extend_conversation MCP tool is live (bot-social de57a91, production 7fb211c), so a paused friend chat can be recovered inside FlyBot instead of removing and re-adding the friend.

• Paused notice: a send that Bot Social refuses with conversation_paused (direct chat or a Bot's send through the transport) marks that friend's chat paused. The friend's chat shows a Chat paused card in the session dock (social-paused) with one button, Extend….
• Approval card: Extend… makes Bot Social's first extend_conversation call (extra_turns: 4; changes nothing, returns a one-time code). The code stays on the host (never sent to the browser or a model); the browser shows the normal approval card Waiting for approval / Extend this chat by 4 turns / 20 of 20 turns used. with Approve · Reject. Only Approve makes the confirming call with the code and the same arguments; Reject drops the code and calls nothing on the server. A decided card cannot be used again. No model tool, no typed approval ([Feature RFC] Agent inbox board: one place for tasks, approvals and failures (personal first, team second) #349).
• The paused conversation is found with list_conversations (the error names none): newest paused_* conversation between one of my members and that Bot.
• The notice clears on a successful send, on Extend, or on a conversation.resumed event for that conversation. After Extend the owner sends again; nothing is resent automatically.
• Wording: mapSendError returns a structured error (code: 'conversation_paused', paused, extendable) that names Extend; notSentLine (core remote-chat.js, patches regenerated) says "Not sent: this chat is paused. Use Extend below to add turns, or remove and re-add this friend to start a new chat." only for an extendable error. Still no pointer to the Bot Social console.
• Docs: social.md (invariant 3 + "Extend a paused friend chat"), core-host.md. Changelog: changelog.d/404-in-chat-extend.added.md. Mocks copy the server's answers (bot-social de57a91).

Owner-delegated details (recorded on #404): 4 extra turns per Extend (server default), card buttons Approve / Reject like every other approval card, no automatic resend.

Ran at the tip: ARCH_DOCS_BASE=upstream/main TZ=UTC npm run verify → pass (core 959, social 260, tree 56, timeline 80, scripts 88, interop 37, live-e2e 16; arch-docs OK). The three new #404 tests fail without the change.
Not run: smoke bench, live run against production Bot Social (a real paused chat), Desktop.

[Birfy]

Self-review (Birfy, owner's Bot)

Read the full diff of #429 against main. Findings:

• A paused friend chat (conversation_paused) is recorded per handle and cleared on a successful send or conversation.resumed; the conversation id comes from list_conversations (the paused error does not carry it).
• Extend is two explicit steps in the chat: Extend… asks Bot Social for the confirmation (code kept on the host, never sent to the browser), then Approve / Reject buttons; only Approve makes the second extend_conversation call with the code bound to the same args. No typed-reply approval, no auto resend.
• notSentLine for an extendable pause points to Extend; other errors unchanged. Patches regenerated.
• No blocking issues found.

Tip SHA: c4b9b30
Ran: ARCH_DOCS_BASE=upstream/main TZ=UTC npm run verify → pass (all suites, arch-docs OK); CI green at this head.
Not run: smoke bench; two-instance live run against prod Bot Social (real pause + extend); Desktop app.
Verdict: PASS