feat(tools): advertise one posix wire set

docs/IMPLEMENTATION.md

@@ -165,7 +165,7 @@ Twenty packages under `src/agent/directors/<id>/` register in `DIRECTOR_REGISTRY
 
    **Grok infer envelope.** `loadSessionChatPrompt` always appends `loadAgentContextExtensions` (`AGENTS.md`, capped at `MAX_AGENTS_MD_BYTES`) and advertises CORE+CATALOG full schemas via `advertisedToolNamesForSessionMode`. That assembly is family-agnostic — Grok does not substitute the trimmed director prompt (`buildSubAgentSystemPrompt` + `formatDirectorSystemPrompt`). Workers already use that trimmed path (no `AGENTS.md`, mounted-tool schemas only). Keep the infer envelope on Grok; do not strip `AGENTS.md` or core schemas. Measure in `src/agent/prompt-sizes.ts` (`assembleSkywalkerInferEnvelope` vs `assembleDirectorPrompt("skywalker", "grok")`).
 
-   **Codex tool proxies.** When the active provider is Codex (`isCodexProviderName`), `createAgentToolset` and `runSubAgent` mount `apply_patch`, `shell`, and `update_plan` stringTools from `createCodexToolProxies`, all forwarding through the same posix `ToolRunner` seam (`runTool`) so permission plugins still apply. `apply_patch` parses the Codex envelope and forwards each op (`write_file` / `delete_file` / `read_file`). `shell` — the native Codex name is `shell`, not `exec_command` — normalizes Codex's `command` (string or `["bash","-lc",script]`-style argv array), `workdir`, and `timeout_ms` onto `run_shell`'s `{command, cwd?, timeout?}` and is gated by `allowShellFromCapabilities` (mirrors `allowDeleteFromCapabilities` against `run_shell`). `update_plan` maps Codex's `plan: [{step, status}]` onto `manage_tasks(action: "create")`; `pending`/`in_progress`/`completed` map to `todo`/`doing`/`done` — `manage_tasks`'s `cancelled` status has no Codex equivalent and is never produced by this proxy. Primary strips `apply_patch` after mount (Corbits DIY stays on `write_file` / `edit_file` / `delete_file`); `shell` and `update_plan` stay on primary (same classification as `run_shell` / `manage_tasks`). Build and docs worker allowlists (`BUILD_TOOLS` / `DOCS_TOOLS`) include `apply_patch` so Codex workers keep the proxy after the capability filter. `CORE_TOOL_NAMES` does not list it.
+   **One advertised posix set (CL-8400).** Registry engines stay posix-named (`read_file`, `write_file`, `edit_file`, `delete_file`, `run_shell`, `search_files`, `grep`). Advertise is a 1:1 projection onto wire names (`read`, `write`, `edit`, `delete`, `bash`, `glob`, `grep`) plus the unchanged control-plane. Incoming aliases (wire names, old posix ids, Codex `shell` → `run_shell`, `update_plan` → `manage_tasks`) canonicalize onto the engine id for dispatch and grants. `apply_patch` is neither advertised nor dispatched (not an alias of `edit`). `list_dir` stays mounted and unadvertised. Director `tools.allow` stays engine names. Codex does not dual-publish `shell`+`run_shell`. Hidden `shell` coerces Codex `command` (string or `["bash","-lc",script]` argv), `workdir`, and `timeout_ms` onto `run_shell`. Hidden `update_plan` maps `plan: [{step, status}]` onto `manage_tasks(action: "create")` (`pending`/`in_progress`/`completed` → `todo`/`doing`/`done`).
 
 6. There is no static write-path declaration on packages or profiles (CL-6952 removed it — no shipped director ever set one). Instead, `agent-fleet.ts` tracks each running dispatch by cwd; a new mutating dispatch that lands on the same cwd as a live mutating peer (`pending_init`/`running`, and not a declared read-only `modelRole` of `explore`/`plan`/`review`/`test`) records at most one `concurrent-lane-overlap` entry per cwd wave in `intervention-log.ts` (class `conflict`). The wave flag clears when no live mutating writer remains for that cwd. Terminal-but-unsettled lanes (for example cancelled with `finishedAt` set while the run promise has not reached `finally`) are pruned from the map and do not warn. This is advisory only — it never blocks the spawn, since cwd overlap does not prove the two lanes touch the same files.
 7. Spawn effort: pin > package `modelRole` default (`defaultEffortForDirector`; intern=low; plan/review/orchestrator=high; implement/explore/docs/test=medium) > orchestrator/worker binary > parent inheritance. Attached skills (style + philosophy on directors that listed both; never intern or Skywalker primary) are injected into the worker system prompt at spawn from plugin skill dirs only (no project-local `.agents`/`.claude`/`.codex` fallback). Optional skills are listed in the identity header for awareness; workers mount `skill_search` + `use_skill` on every family, scoped to the union of `attachedSkills` and `optionalSkills`. `use_skill` refuses names already attached or already loaded this session and does not return the body again. Primary mounts `use_skill` for its own skill list (same in-session refuse; no attached set).

packages/prompt-variance/src/rows.test.ts

@@ -74,7 +74,7 @@ describe("prompt-variance family rows", () => {
     expect(grokRow.residual).toContain("prefer the structured report");
     expect(grokRow.residual).toContain("re-open paths you already read");
     expect(grokRow.residual).toContain("done-definition is met");
-    expect(grokRow.residual).toContain("never run_shell");
+    expect(grokRow.residual).toContain("never bash");
   });
 
   test("each ceremony line appears exactly once in the grok row (P2 invariant)", () => {

packages/prompt-variance/src/rows.ts

@@ -64,7 +64,7 @@ export const grokRow: PromptVarianceRow = {
     "- Once you can answer the dispatch brief, prefer the structured report over another speculative tool call.",
     "- If the next call would only re-open paths you already read, write the report instead.",
     "- When the dispatch brief's done-definition is met, write the report envelope instead of making one more search or micro-edit.",
-    "- Route file and web work through the dedicated tools, never run_shell — mining showed grok reaching for shell first when a typed tool already covered the job.",
+    "- Route file and web work through the dedicated tools, never bash — mining showed grok reaching for shell first when a typed tool already covered the job.",
     "- Never run git add, git commit, git stash, or any other state-changing git command unless the user asks.",
     "- Do not narrate a plan before acting on a small task; act, then report.",
     "- Verify with the test command once at the end, not after every edit.",

plugins/corbits-skills/skills/native-integration/SKILL.md

@@ -16,7 +16,7 @@ Do not delete Corbits-only skills (`plan`, `git-worktrees`, `idiot-proof`). They
 
 Corbits tests use `bun:test` (`bun test`, `bun run test`), not GaaS `tap` (`import t from "tap"`). When the typescript skill shows tap examples, map them to bun:test (`import { expect, test } from "bun:test"`). Do not fork the typescript skill body.
 
-GaaS opsh scripts are bash (`#!/usr/bin/env opsh`, `lib::import`) and use TAP via `prove` (`test-harness`). That harness is not Corbits `bun:test`. Write scripts with `write_file`/`edit_file`; agent commands use `run_shell`. Do not fork the GaaS opsh body.
+GaaS opsh scripts are bash (`#!/usr/bin/env opsh`, `lib::import`) and use TAP via `prove` (`test-harness`). That harness is not Corbits `bun:test`. Write scripts with `write`/`edit`; agent commands use `bash`. Do not fork the GaaS opsh body.
 
 ## Tool mapping
 
@@ -32,14 +32,14 @@ When a GaaS skill names a Claude/GaaS tool, use the Corbits equivalent. Do not c
 | `@critic` / `@critique` | `spawn_agent(agent="critic")`                      |
 | `@intern`               | `spawn_agent(agent="intern")`                      |
 | `@explorer`             | `spawn_agent(agent="explorer")`                    |
-| Read / Write / Edit     | `read_file` / `write_file` / `edit_file`           |
-| Glob / Grep             | `search_files` / `grep`                            |
-| Bash                    | `run_shell`                                        |
+| Read / Write / Edit     | `read` / `write` / `edit`                          |
+| Glob / Grep             | `glob` / `grep`                                    |
+| Bash                    | `bash`                                             |
 | WebFetch / WebSearch    | `web_fetch` / `web_search`                         |
 
 `intent="general"` is not a Corbits spawn. Use a closed director id.
 
-GaaS ast-grep invokes `sg` as a CLI. Corbits extras: run `sg` via `run_shell`. Do not fork the GaaS ast-grep body.
+GaaS ast-grep invokes `sg` as a CLI. Corbits extras: run `sg` via `bash`. Do not fork the GaaS ast-grep body.
 
 Slash names that differ from GaaS skill ids: `/review` is GaaS `code-review`; `/create-issue` is GaaS `linear-create`. Keep those Corbits names.
 
@@ -67,7 +67,7 @@ GaaS linear-issue-workflow inlines `git worktree add` and marks In Progress afte
 
 GaaS `style` refuses to operate outside a git repo. Corbits does not: a folder without `.git` is a valid working directory (scratch, unpacked tarball, new project). Git-using skills (`implement`, `review`, `git-rebase`, `pull-request-review`) still no-op or ask when they need a repo. Do not invent a git repo to satisfy those skills.
 
-When GaaS git-rebase writes `/tmp` editor scripts, Corbits still plans on the primary and intern executes sequenced git via `run_shell`; intern may use inline `GIT_SEQUENCE_EDITOR` instead of write_file editor scripts. Do not fork the GaaS git-rebase body.
+When GaaS git-rebase writes `/tmp` editor scripts, Corbits still plans on the primary and intern executes sequenced git via `bash`; intern may use inline `GIT_SEQUENCE_EDITOR` instead of write editor scripts. Do not fork the GaaS git-rebase body.
 
 ## Tracker-agnostic issues
 

plugins/corbits-skills/skills/native-runtime/SKILL.md

@@ -5,13 +5,13 @@ disable-model-invocation: true
 description: Compact Corbits worker runtime invariants for baked prompts.
 ---
 
-Use Corbits tool names: `read_file`, `write_file`, `edit_file`, `delete_file`,
-`grep`, `search_files`, `run_shell`, `web_search`, `web_fetch`,
+Use Corbits tool names: `read`, `write`, `edit`, `delete`,
+`grep`, `glob`, `bash`, `web_search`, `web_fetch`,
 `manage_tasks`, and `ask_director` for worker questions.
 
 Use file tools for file reads, edits, writes, and deletions. Never use shell
 redirects, heredocs, `echo`, `cat`, stream editors, or remove commands as
-substitutes for file tools. Use bounded `grep` and `search_files` instead of
+substitutes for file tools. Use bounded `grep` and `glob` instead of
 unbounded recursive shell searches. Use web tools for URLs; never use curl or
 wget.
 

scripts/eval-capability.test.ts

@@ -381,8 +381,8 @@ describe("buildEvalDiagnostics", () => {
     const diagnostics = await buildEvalDiagnostics(
       sampleConfig({ providerName: "openai" }),
     );
-    expect(diagnostics.advertisedTools).toContain("read_file");
-    expect(diagnostics.advertisedTools).toContain("run_shell");
+    expect(diagnostics.advertisedTools).toContain("read");
+    expect(diagnostics.advertisedTools).toContain("bash");
     expect(diagnostics.advertisedTools).not.toContain("ask_operator");
     expect(diagnostics.reasoningEffort).toBeNull();
   });
@@ -394,7 +394,7 @@ describe("buildEvalDiagnostics", () => {
         sampleConfig({ providerName }),
       );
       expect(diagnostics).not.toHaveProperty("codexInstructionsHash");
-      expect(diagnostics.advertisedTools).toContain("read_file");
+      expect(diagnostics.advertisedTools).toContain("read");
     },
   );