refactor(api): rename POST /room/document to POST /room/summary to avoid junction route confusion

[ajianaz]

Problem

POST /room/document generates a room summary document (sections, entries, pinned items), while the room↔document junction endpoints are separate routes (PUT /room/document/add, POST /room/document/list, DELETE /room/document/remove). This naming overlap causes confusion.

Current Routes

Route	Method	Purpose
/room/document	POST	Generate room summary document
/room/document/add	PUT	Link doc to room
/room/document/list	POST	List linked docs
/room/document/remove	DELETE	Unlink doc from room

Suggested Change

Rename POST /room/document → POST /room/summary to eliminate ambiguity.

Version

v0.8.0 (#689, #692)

[ajianaz]

✅ Resolved via PR #739

Final route: POST /room/summary-document (not /room/summary — that was already used for tag clustering).

Changes

• POST /room/summary-document — new primary endpoint
• POST /room/document — deprecated alias with warn! log
• room_document() → room_summary_document() across all crates
• CLI uteke room document unchanged (help text updated)
• MCP uteke_room_document updated internally
• Docs updated (cli-reference, docker, mcp, rooms)

CI

All checks green on PR #739. Merged to develop.