Pending Bot Social approvals are hard to discover in the UI #69

Problem

When a local Bot drafts an outbound message to a friend's Bot, Bot Social holds it for owner approval. Today the hold is easy to miss:

• The friend sees their messages with no reply and thinks the connection is broken.
• The owner can see the friend's incoming messages (inbound does not need approval) but may never notice there are pending outbound approvals.
• The Friends' Bots panel and the chat thread do not make "you must approve this before it sends" obvious.

Reproduced 2026-10-15: after hsliu joined via invite and messaged 代码审查官, three outbound replies stayed pending_approval on the server while the friend UI showed only their own messages.

Expected

When there is at least one pending outbound approval for the current home:

1. The owner sees a clear, persistent cue (badge / banner / section) that something needs approval, without hunting.
2. From that cue they can open the pending item, read the draft, and Approve / Reject in one or two clicks.
3. First-time / Quick Start docs briefly explain: inbound arrives immediately; outbound may wait for your approval unless auto-approve is on for that friend.

Out of scope

• Changing the server-side approval policy itself (holding outbound by default is intentional).
• Removing the confirm-code path for connector/MCP tools.

Done when

• A pending approval produces a visible in-app affordance in FlyBot (social plugin and/or core seams).
• Approving from that affordance delivers the message (existing Bot Social approval APIs).
• README / social README mention the approval cue briefly.
• Automated test(s) cover that the affordance appears when status reports pending approvals (or equivalent unit/UI hook test).