docs(codex): say what Allow network access leaves alone

The owner's answer to the PR's open question: the switch does not also pass
--sandbox workspace-write. Settings, wiki, skill and release note now state
the consequence: a folder Codex runs read-only keeps the network closed and
asks per command. A golden test pins the decision by name, and the stale
launch-defaults comments now name networkAccess.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

plugins/codeman/skills/codeman/SKILL.md

@@ -78,9 +78,10 @@ retrying.
   command** once that way, never a different one; if the user declines, stop. For lasting
   access in Codex, the user turns on **Allow network access** (Codeman App Settings,
   Codex) and starts a new Codex session: it opens the network wherever Codex runs the
-  folder workspace-write, and keeps the sandbox and approvals. A folder Codex runs
-  read-only still needs the per-command approval (or `/permissions`). **Bypass approvals
-  and sandbox** works everywhere but drops the sandbox and approvals.
+  folder workspace-write, and keeps the sandbox and approvals. It does not change the
+  sandbox mode: a folder Codex runs read-only keeps the network closed, so each call
+  still needs the per-command approval (or `/permissions`). **Bypass approvals and
+  sandbox** works everywhere but drops the sandbox and approvals.
 - **`"${CURL[@]}" -o /dev/null -w '%{http_code}' "$API/api/v1/sessions/$SELF"` prints
   `404`.** The commands you run do not carry this session's environment: Codex can run them in a shared background
   process another session started, so `$CODEMAN_SESSION_ID` (and with it `$SELF` and