[fujibee]

Release of 1.6.0-rc.10 from integration/agmsgd-beta.

• VERSION bump + synced package.json / .claude-plugin/plugin.json
• CHANGELOG.md deliberately untouched — prerelease notes come from release.yml's own git-cliff --latest

Changes since rc.9:

Choosing how notices arrive

• The delivery choice after joining a team, and /agmsg delivery, now offer agmsgd first as the recommended option, with monitor (legacy), turn, both and off after it, for both Claude Code and Codex. The screen says agmsgd registers a resident service and how to turn it off. Where agmsgd cannot run here (an old Node, JSONL storage, an unsupported Codex on Windows), it is not offered and the reason is shown (Offer agmsgd as the recommended delivery choice; add agmsg delivery #1717).
• /agmsg delivery is the command's name; /agmsg mode keeps working as an alias, and agmsg delivery does the same from a shell. With no argument it shows both agmsgd's state for the install and this project's choice. agmsgd is reported as on only when it is actually running (Offer agmsgd as the recommended delivery choice; add agmsg delivery #1717).
• Choosing monitor (legacy) for a project now really keeps agmsgd away from it: neither channel sends there, and daemon status says so. Projects that never made a choice behave as before (Make monitor (legacy) a real opt-out from agmsgd for the project #1719).
• Choosing agmsgd says that the current session keeps receiving through a Monitor watch until agmsgd confirms its destination (Explain the Monitor instruction when agmsgd is chosen #1724, Say agmsgd takes over once it confirms the session's destination #1725).
• Nothing asks at install time and nothing is enabled by it. An install or update ends with one line on how to turn agmsgd on, when it is off (README: agmsgd Windows Claude Code notes; installer: point at agmsgd while it is off #1715). After an update, the first Claude Code or Codex session start shows a one-time notice that agmsgd is available; nothing changes until the user switches (session-start: introduce agmsgd once to an install that has not turned it on #1716).

Docs

• README (English and Japanese) and the reference docs now match current behaviour: monitor (legacy) naming for both agents, Codex receiving through the bridge, agmsgd as an opt-in service on macOS, Linux and Windows (Claude Code 2.1.302 or later on Windows), and removed team.sh repair flags no longer described (README: agmsgd Windows Claude Code notes; installer: point at agmsgd while it is off #1715, docs: align wording on Monitor, agmsgd and the daemon; fix stale details #1720, docs/design: note what changed in 1.6.0 at the top of the agmsgd records #1721, README.ja.md: translate the missing sections and fix stale wording #1723).

Merging this and pushing v1.6.0-rc.10 triggers the publish pipeline (npm + GitHub Release).