docs(skills): clean up local skill audit drift

.codex/skills/code-review-breaking-changes/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: code-breaking-changes
+name: code-review-breaking-changes
 description: Breaking changes
 ---
 

.codex/skills/code-review-context/SKILL.md

@@ -3,11 +3,15 @@ name: code-review-context
 description: Model visible context
 ---
 
-Codex maintains a context (history of messages) that is sent to the model in inference requests.
+Every Code maintains a context, the history of messages sent to the model in
+inference requests.
 
 1. No history rewrite - the context must be built up incrementally.
 2. Avoid frequent changes to context that cause cache misses.
-3. No unbounded items - everything injected in the model context must have a bounded size and a hard cap. 
+3. No unbounded items - everything injected in the model context must have a
+   bounded size and a hard cap.
 4. No items larger than 10K tokens.
-5. Highlight new individual items that can cross >1k tokens as P0. These need an additional manual review.
-6. All injected fragments must be defined as structs in `core/context` and implement ContextualUserFragment trait
+5. Highlight new individual items that can cross >1k tokens as P0. These need
+   an additional manual review.
+6. All injected fragments must be defined as structs in `core/context` and
+   implement the `ContextualUserFragment` trait.

.codex/skills/code-review-testing/SKILL.md

@@ -3,10 +3,14 @@ name: code-review-testing
 description: Test authoring guidance
 ---
 
-For agent changes prefer integration tests over unit tests. Integration tests are under `core/suite` and use `test_codex` to set up a test instance of codex.
+For Every Code agent changes, prefer integration tests over unit tests.
+Integration tests are under `core/suite` and use `test_codex` to set up a test
+instance.
 
 Features that change the agent logic MUST add an integration test:
-- Provide a list of major logic changes and user-facing behaviors that need to be tested.
+
+- Provide a list of major logic changes and user-facing behaviors that need to
+  be tested.
 
 If unit tests are needed, put them in a dedicated test file (*_tests.rs).
 Avoid test-only functions in the main implementation.

.codex/skills/remote-tests/SKILL.md

@@ -9,7 +9,7 @@ commands:
   - name: list-devboxes
     source: external
     example_argv: ["applied_devbox", "ls"]
-    purpose: List available devboxes before selecting one with codex in the name.
+    purpose: List available devboxes before selecting one with code or codex in the name.
   - name: connect-devbox
     source: external
     example_argv: ["ssh", "<devbox_name>"]
@@ -23,14 +23,19 @@ workflow_defaults:
     description: Reuse the devbox checkout and keep SHA and modified files in sync.
 ---
 
-Some codex integration tests support a running against a remote executor.
-This means that when CODEX_TEST_REMOTE_ENV environment variable is set they will attempt to start an executor process in a docker container CODEX_TEST_REMOTE_ENV points to and use it in tests.
+Some Every Code integration tests support running against a remote executor.
+This means that when `CODEX_TEST_REMOTE_ENV` is set they will attempt to start
+an executor process in a Docker container `CODEX_TEST_REMOTE_ENV` points to and
+use it in tests.
 
 Docker container is built and initialized via ./scripts/test-remote-env.sh
 
-Currently running remote tests is only supported on Linux, so you need to use a devbox to run them
+Currently running remote tests is only supported on Linux, so you need to use a
+devbox to run them.
 
-You can list devboxes via `applied_devbox ls`, pick the one with `codex` in the name.
+You can list devboxes via `applied_devbox ls`, pick the one with `code` or
+`codex` in the name.
 Connect to devbox via `ssh <devbox_name>`.
-Reuse the same checkout of codex in `~/code/codex`. Reset files if needed. Multiple checkouts take longer to build and take up more space.
+Reuse the same checkout in `~/code/codex`. Reset files if needed. Multiple
+checkouts take longer to build and take up more space.
 Check whether the SHA and modified files are in sync between remote and local.

.codex/skills/test-tui/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test-tui
-description: Guide for testing Codex TUI interactively
+description: Guide for testing Every Code TUI interactively
 commands:
   - name: start-tui
     source: repo
@@ -15,7 +15,7 @@ workflow_defaults:
     description: Send text first, then Enter as a separate write when driving the TUI programmatically.
 ---
 
-You can start and use Codex TUI to verify changes. 
+You can start and use Every Code TUI to verify changes.
 
 Important notes: