docs: document --auth-token flag, OAuth callback security note, and TUI notification UX

[aheritier]

Summary

Catch-up documentation updates for code changes merged in the last 36 hours.

---

Commits

docs: document --auth-token flag and add OAuth callback security note (refs #2921)

Files: docs/features/api-server/index.md, docs/features/cli/index.md, docs/features/remote-mcp/index.md

• Added --auth-token to the docker agent serve api flags table in both the CLI reference and API server docs.
• Added a security callout in the Remote MCP OAuth section recommending --auth-token when docker agent serve api listens on a non-localhost interface, explaining the threat model for POST /api/mcp-oauth/callback.

docs: document TUI notification UX improvements (refs #2931)

File: docs/features/tui/index.md

Added a ## Notifications section documenting the updated notification behaviour:

• Notifications auto-dismiss unless the mouse hovers (hover pauses the timer)
• Clicking a notification copies its text to the clipboard
• The × close glyph turns red when hovered
• Hint text in the notification border shows available actions at a glance

---

PRs covered

Source PR	Title	Doc impact
#2921	Address review feedback on #2896	--auth-token flag documented in API server + CLI reference; OAuth callback security callout added to Remote MCP docs
#2931	TUI - Improve notifications	New Notifications section in TUI docs

PRs with no additional doc gaps

Source PR	Title	Reason
#2928	feat: add allow/block-list of servers to the mcp_catalog tool	Docs included in the PR itself (docs/tools/mcp-catalog/index.md)
#2925	fix(mcpcatalog): tell the model to proceed after enabling an OAuth server	Prompt-only fix, no user-facing feature to document
#2930	docs: update CHANGELOG.md for v1.70.0	Automated CHANGELOG update
#2918, #2926	chore: bump direct Go dependencies	Dependency bumps, no docs needed

[docker-agent]

Assessment: 🟢 APPROVE

Documentation PR adding --auth-token flag entries to two reference tables and a security callout to the Remote MCP OAuth section. The changes are factually sound and the security advice is appropriate. Two minor clarity/consistency notes are left as inline comments.