feat(agent): make coordination routes opt-in and address review

Gate inspect, stage and submit behind the synced agentCoordinationEnabled
setting (default OFF, App Settings > Cross-session features, zh-CN
strings). While off, all three routes answer 403 FORBIDDEN naming the
setting, checked before session lookup; the CLI verbs print it verbatim.

Remember the attributed Codex rollout per session and re-verify only its
head on later calls, rescanning only date directories not older than it
for a /new conflict. The first walk reads 1 KiB prefixes first, so a
store of 2,100+ unrelated rollouts still attributes.

Answer unexpected inspection errors with 422 OPERATION_FAILED and log
the session id and error code only.

Read the guarded composer glyph and footer from the CLI registry: codex
workDetect.promptGlyph and a new workDetect.composerFooterLine
capability, compiled through compileVersionRegex. Codex footer effort
words are one shared list with modelDetect.screenLine.

Fix the wiki API reference link, frame the versioning policy entry as a
case of the experimental rule, join the CLAUDE.md Agent CLI paragraph,
and update the changeset, skill reference and architecture notes.

plugins/codeman/skills/codeman/reference/inspection-and-staging.md

@@ -2,11 +2,16 @@
 
 **Experimental:** `codeman agent inspect`, `stage` and `submit`, and their
 `/api/v1/sessions/:id/inspect|stage|submit` routes (including `/api` aliases),
-are excluded from the stable CLI/HTTP contract. Their commands, flags, paths,
+are labeled experimental and so are not part of the stable CLI/HTTP contract. Their commands, flags, paths,
 payloads and behavior may change or be removed in a minor or patch release.
 Pin a compatible Codeman version when automating them. Authentication and
 session ownership checks still apply.
 
+They are also opt-in: until the user turns on **Experimental agent coordination**
+in App Settings (`agentCoordinationEnabled`, off by default), every one of them
+fails with `FORBIDDEN: ... (HTTP 403)` naming that setting. That is not something
+to retry or work around: tell the user, or use `send`/`read` instead.
+
 Use these commands inside a Codeman session. They use its authenticated HTTP API.
 They supplement `send`, `wait` and `read` over the same HTTP transport; no direct
 tmux access is required.

plugins/codeman/skills/codeman/reference/verbs.md

@@ -816,10 +816,11 @@ Rules that matter:
 
 ## Experimental bounded inspection and guarded submission
 
-These three commands and their HTTP routes may change or be removed in minor or
-patch releases; they are excluded from the stable CLI/HTTP contract.
-
-Use `codeman agent inspect` for bounded evidence and incremental local Codex cursors.
+These three commands and their HTTP routes are labeled experimental, so they may
+change or be removed in minor or patch releases. They are also opt-in
+(`agentCoordinationEnabled`, off by default: a 403 naming it until the user turns
+it on). Use `codeman agent inspect` for bounded evidence and incremental local
+Codex cursors.
 Use `codeman agent stage --message-file` followed by one hash-confirmed
 `codeman agent submit --stage-id --confirm-sha` when the exact local Codex
 composer and caret can be verified. Other targets provide labeled snapshots or