refactor(rules): use agent-neutral language in shared rules

A non-Claude agent (Codex, a local model) reading the shared rules gets told it's "Claude" in prose that's really about whatever agent is running. I replaced the agent-as-actor references — "how Claude communicates," "when Claude needs the user to pick," a "wrong-context Claude session" — with "the agent."

Left untouched: file and path names (CLAUDE.md, .claude/, claude-rules/), and every reference in commits.md, which names Claude and Anthropic on purpose as the things never to attribute a commit to. Neutralizing those would invert the rule.

4 files changed, 7 insertions, 7 deletions

diff --git a/claude-rules/cross-project.md b/claude-rules/cross-project.md
index ed4a19c..caceec9 100644
--- a/claude-rules/cross-project.md
+++ b/claude-rules/cross-project.md
@@ -35,7 +35,7 @@ Two acceptable outcomes:
    ```
 
    Output filenames follow `YYYY-MM-DD-HHMM-from-<this-project>-<slug>.<ext>` automatically, so the target's next session sees the source + timestamp at a glance without you having to construct the name. Fall back to `Write`/`Edit` only when the script isn't available (e.g. a freshly-cloned project before the first startup-rsync).
-2. **"Switch projects"** — stop. Let the user reopen Claude in the right cwd.
+2. **"Switch projects"** — stop. Let the user reopen the agent session in the right cwd.
 
 Don't assume which one was meant. Either guess is wrong half the time and the cost of asking once is one short turn.
 
diff --git a/claude-rules/interaction.md b/claude-rules/interaction.md
index 1fd0334..9148b4f 100644
--- a/claude-rules/interaction.md
+++ b/claude-rules/interaction.md
@@ -2,11 +2,11 @@
 
 Applies to: `**/*`
 
-How Claude communicates with the user during a session — choice prompts, status updates, decision points.
+How the agent communicates with the user during a session — choice prompts, status updates, decision points.
 
 ## No Popup Menus for Choices
 
-When Claude needs the user to pick between options, **do not** use the AskUserQuestion popup. Present the options inline in chat as a numbered list and ask the user to reply with a number.
+When the agent needs the user to pick between options, **do not** use the AskUserQuestion popup. Present the options inline in chat as a numbered list and ask the user to reply with a number.
 
 **Why:** The popup menu UI sits at the bottom of the chat window and obscures the chat content directly above it — exactly the area the user needs to read to make the choice. Inline numbered options keep the question, the surrounding context, and the proposed text all visible in the same scrollback.
 
diff --git a/claude-rules/triggers.md b/claude-rules/triggers.md
index e45e660..a8d5e77 100644
--- a/claude-rules/triggers.md
+++ b/claude-rules/triggers.md
@@ -8,13 +8,13 @@ Trigger phrases the user can say from any session to invoke a cross-project acti
 
 Synonyms: "Launch X", "Open project X", "Switch to project X".
 
-**Action:** run the `ai` script (the Claude Code session launcher, installed at `~/.local/bin/ai`) in single-project mode targeting the named project.
+**Action:** run the `ai` script (the agent session launcher, installed at `~/.local/bin/ai`) in single-project mode targeting the named project.
 
 ```
 ai <project-path>
 ```
 
-The `ai` script handles tmux session creation, window placement, and the per-project Claude opening line — see `~/code/rulesets/claude-templates/bin/ai` for the canonical source.
+The `ai` script handles tmux session creation, window placement, and the per-project agent opening line — see `~/code/rulesets/claude-templates/bin/ai` for the canonical source.
 
 **Resolving X.** Match against project basenames discoverable by `ai` — directories under `~/code/`, `~/projects/`, and `~/.emacs.d` that contain `.ai/protocols.org`.
 
@@ -22,7 +22,7 @@ The `ai` script handles tmux session creation, window placement, and the per-pro
 - No match → list all available basenames, ask which to launch.
 - Multiple partial matches (X is a substring of two or more candidates) → list the matching basenames, ask which.
 
-Do not guess. The cost of asking once is one short turn; launching the wrong project is a wrong-context Claude session that has to be killed and restarted.
+Do not guess. The cost of asking once is one short turn; launching the wrong project is a wrong-context agent session that has to be killed and restarted.
 
 ## Why a separate file
 
diff --git a/claude-rules/working-files.md b/claude-rules/working-files.md
index 9a72702..2432268 100644
--- a/claude-rules/working-files.md
+++ b/claude-rules/working-files.md
@@ -120,7 +120,7 @@ When the task is marked done:
 - *Inbox content* — `inbox/` and `daily-prep/` follow their own
   conventions (dated filenames, processed and moved on cadence).
 
-## Implementation Note for Claude Sessions
+## Implementation Note for Agent Sessions
 
 When the user starts a new task that's going to produce file artifacts: