{
  "id": "page:docs-adapters-terminology-and-structure-gaps-binary-renames",
  "_kind": "Page",
  "_file": "wiki/docs/adapters/terminology-and-structure-gaps/binary-renames.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/adapters/terminology-and-structure-gaps/binary-renames.md",
    "sourceKind": "repo-docs",
    "title": "Binary Renames",
    "displayName": "Binary Renames",
    "slug": "docs/adapters/terminology-and-structure-gaps/binary-renames",
    "articlePath": "wiki/docs/adapters/terminology-and-structure-gaps/binary-renames.md",
    "article": "\n# Binary Renames\n\n> **Superseded by spec 15** (`docs/specs/platform-gaps/15-private-isolation-rename.md` §3\n> \"Single-bin policy\" and the §3.1 \"Bin(s)\" column), executed by WP-RN-06\n> (`docs/specs/platform-gaps/phase1/rn-06-bins.md`). The original plan below aligned the\n> public `@a5c-ai/*` train on an `adapters-{feature}` pattern with one-major deprecated\n> aliases; the private `@fabricstack/*` train ships neutral per-component bin names and\n> **drops every legacy alias instead of aliasing it** (D10: no compatibility shims; D17: the\n> public repo keeps the old bins for old users). This table is the tool input of\n> `scripts/check-binary-renames.cjs` (`npm run test:binary-renames`).\n\n## Private-train bins (spec 15 §3.1, shipped)\n\n| Bin | Package | Entry (file names keep their RN-1 spelling; RN-4 renames identifiers) | Replaces (public train, dropped) |\n|---|---|---|---|\n| `orchestrator` | `@fabricstack/orchestrator` | `bin/babysitter.js` | `babysitter` |\n| `orchestrator-sdk` | `@fabricstack/orchestrator-sdk` | `dist/cli/main.js` | `babysitter-sdk`, `babysitter` (duplicate) |\n| `orchestrator-mcp` | `@fabricstack/orchestrator-sdk` | `dist/cli/mcpServeEntry.js` | `babysitter-mcp-server`; the `adapters`/`adapters-hooks` re-export shims are dropped |\n| `observer` | `@fabricstack/observer` | `dist/cli.js` | `babysitter-observer-dashboard` |\n| `harness` | `@fabricstack/harness-sdk` | `dist/bin/adapters.js` | `adapters` |\n| — | `@fabricstack/harness-cli` | delegates to `@fabricstack/harness-sdk` | — (none today) |\n| `harness-mock` | `@fabricstack/harness-mock` | `dist/bin/adapters-harness-mock.js` | `adapters-harness-mock`, `mock-harness` |\n| `harness-tasks` | `@fabricstack/harness-tasks` | `dist/cli/index.js` | `adapters-tasks`, `tasks-adapter` |\n| `harness-triggers` | `@fabricstack/harness-triggers` | `dist/cli.js` | `adapters-triggers`, `triggers-adapter` |\n| `harness-channels` | `@fabricstack/harness-channels` | `dist/cli.js` | `adapters-channels`, `mcp-channels` |\n| `harness-extensions` | `@fabricstack/harness-extensions` | `dist/cli.js` | `adapters-extensions`, `extensions-adapter` |\n| `model-gateway` | `@fabricstack/model-gateway` | `dist/bin/adapters-transport-proxy.js` | `adapters-transport-proxy`, `adapters-proxy` |\n| `harness-hooks` | `@fabricstack/harness-hooks-cli` | `dist/cli/main.js` | `adapters-hooks`, `a5c-hooks-adapter` |\n| `agent-runtime` | `@fabricstack/agent-runtime-cli` | `dist/cli/main.js` | `genty` |\n| `console-tui` | `@fabricstack/console-tui` | `dist/bin/adapters-tui.js` | `adapters-tui` |\n| `catalog` | `@fabricstack/catalog` | `dist/cli.js` | `atlas`, `a5c-atlas` |\n| `control-plane-server` | `@fabricstack/control-plane` | `bin/kradle-server.mjs` | `kradle-server` (also resolved the collision with the private `@fabricstack/control-plane-cli` dev bin) |\n| `control-plane-demo` | `@fabricstack/control-plane` | `bin/kradle-demo.mjs` | `kradle-demo` |\n| `operator` | `@fabricstack/operator` | `dist/cli.js` | `kradle-install` |\n\nPrivate (non-publishable) §3.2 workspaces keep their dev-only bins (`kip`, `kip-mcp`,\n`kradle`, `kradle-server`, `kradle-jitsi-agent-*`); they never reach a registry and are\nsubject only to the duplicate-bin rule of G5.\n\n## Backward compatibility\n\nNone. The public `a5c-ai/babysitter` repository keeps publishing the old bins under\n`@a5c-ai/*` (D17); the private train never installs alongside them under the same names\n(spec 15 §4.3 G5 `public-train-bin`), so `npm i -g` of a public and a private package can\nnever `EEXIST` on each other.\n\n## Historical plan (public train, before D17)\n\n8 CLI binaries were to be aligned to an `adapters-{feature}` pattern with a deprecated alias\nprinting `[adapters] \"<old>\" is deprecated, use \"<new>\" instead.` for one major cycle\n(`adapters-proxy` → `adapters-transport-proxy`, `a5c-hooks-adapter` → `adapters-hooks`,\n`extensions-adapter` → `adapters-extensions`, `triggers-adapter` → `adapters-triggers`,\n`tasks-adapter` → `adapters-tasks`, `mock-harness` → `adapters-harness-mock`; `adapters` and\n`adapters-tui` unchanged). That alias guidance predates the two-repo model and is retired.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-adapters-terminology-and-structure-gaps",
      "to": "page:docs-adapters-terminology-and-structure-gaps-binary-renames",
      "kind": "contains_page"
    }
  ]
}