README: Codex is wired up by the installer now

It was written when --runtime codex refused outside a project, so it told
people to run the whole thing per project. The skill and hooks are
machine-wide now; only the AGENTS.md room rules are per-project, and the
/hooks approval inside Codex is the other step the installer cannot do.

Signed-off-by: disqualifier <dev@disqualifier.me>

README.md

@@ -31,23 +31,28 @@ already set up prints status and changes nothing.
 | --- | --- |
 | `--skill-only` | skill and hooks only; no daemon, no service |
 | `--no-node` | never provision Node; falls back to skill-only if yours is too old |
-| `--no-codex` | don't mention Codex, even if it's installed |
+| `--no-codex` | don't wire Codex, even if it's installed |
 | `--registry <url>` | install from somewhere other than the default registry |
 | `--yes` | don't prompt |
 
 Node 20 is the floor for single mode. The daemon needs 22.13 or newer, because
 it uses `node:sqlite` without a flag.
 
-Claude Code gets wired up machine-wide here. **Codex is per-project** — one of
-the things it writes is a block in the project's own `AGENTS.md` — so the
-installer can't do it for you. If `codex` is on your PATH, the installer says
-so and prints the command; run it inside each project you want Codex in:
+Claude Code gets wired up for you. **Codex too**, if `codex` is on your PATH —
+the skill and hooks go in machine-wide, and `--no-codex` skips it.
+
+Two things Codex needs that the installer can't do for you:
 
 ```sh
+# 1. in Codex, approve the hooks it just installed
+/hooks
+
+# 2. in each project you want Codex in, for the room rules
 standup install --runtime codex
 ```
 
-`--no-codex` tells the installer not to mention it.
+The second one is per-project because it writes a block into that project's
+own `AGENTS.md`.
 
 Windows uses the same flags with PowerShell spelling: `-SkillOnly`, `-NoNode`,
 `-NoCodex`, `-Registry <url>`, `-Yes`.