Add /context-size command to set context window for local providers

.prettierignore

@@ -4,3 +4,7 @@ vendor/
 scratch/
 node_modules/
 CHANGELOG.md
+
+tmp/
+.claude/
+.tmp/

AGENTS.md

@@ -34,6 +34,7 @@ When refactoring replaces an old path, delete the old one. No back-compat shims,
 - Bug fixes start with a failing test that reproduces the bug. Do not start by patching.
 - `tests/unit/` shared unit tests and helpers · co-located `src/**/*.test.ts` for module logic · `tests/fixtures/` fixture repos · `tests/integration/` reactor/permission harness. Planned: `tests/e2e/` (fixture-repo runs).
 - A test must not depend on another file having run, or on the default file order. It must pass under `bun test ./src ./tests ./evals --randomize`. If a test mutates module-level state or calls `mock.module`, it must restore that state itself (`afterEach`/`afterAll`), not rely on the process happening to reset it. When capturing a module's real exports to restore later, shallow-copy them (`{ ...moduleNamespace }`) at capture time, whether the namespace came from `await import(path)` or a static `import * as ns from "path"` — Bun mutates the live namespace object in place when the module is mocked, so holding a bare reference to it (either form) silently turns into the mocked exports.
+- Never call `mock.module` directly. Bun runs every test file in one process, so a `mock.module` call without its own teardown stays installed for the rest of the run and silently replaces the real module for other files — producing failures in files the change never touched, with no obvious link to the cause and no signal from `tsc` or a per-file run (CL-6967). Use `withMockedModule`/`withMockedModuleDuring` from `tests/helpers/mock-module.ts`, which capture the real module and register their own restore. An eslint rule (`no-restricted-syntax` in `eslint.config.js`) rejects bare `mock.module` calls in `*.test.ts` files.
 
 ## Build & Validation
 

README.md

@@ -90,7 +90,7 @@ Corbits Code defaults to **auto mode** (`auto = true`). Workspace file writes/ed
 
 - Dependency installs and remote runners (`npm install` / `i` / `ci` / `add`, `pip install`, `cargo add`, `brew install`, `npx` / `bunx`, …)
 - Recursive `rm` (`-r` / `-R` / `--recursive`)
-- Git worktree boundary changes (`add` / `remove` / `prune`; read-only `git worktree list` is fine)
+- Force or uncontained git worktree add/remove/prune (contained non-force add/remove/prune and read-only `git worktree list` auto-allow)
 - Shell that references sensitive paths (`.env`, private keys, certs, credential files, …)
 - Opaque shell wrappers the policy cannot statically inspect (variable expansion or command substitution in a wrapper payload)
 - Paths outside the workspace, writes under the session state root, mutating MCP tools, and unknown built-ins
@@ -111,19 +111,19 @@ Details live in `docs/PRODUCT.md` (safety model) and `docs/ARCHITECTURE.md` (per
 bun install
 bun run typecheck
 bun run build
-bun test
+bun run test
 ```
 
 ## Agent Workspace
 
-Corbits Code keeps repository guidance and sub-agent profiles separate:
+Corbits Code keeps repository guidance and the closed director fleet separate:
 
 - `AGENTS.md` — shared startup instructions and project context
 - `CLAUDE.md` — Claude-specific workspace notes
-- `src/agent/default-agents.ts` — built-in sub-agent profiles shipped with Corbits Code (`greybeard`, `critique`)
-- `.agents/agents/` — optional local profile overrides or additions; this directory is not required and may be absent
+- `src/agent/directors/` — closed spawn catalog (`directorProfiles()`). Skywalker is the primary orchestrator; spawnable directors include builder, explorer, counsel, intern, critic, greybeard, and the rest of `DIRECTOR_IDS`. Closed ids cannot be overridden by plugins or local files.
+- `.agents/agents/` — optional local profile additions; this directory is not required and may be absent
 
-Named `task` sub-agents resolve from built-ins first, then enabled agent plugins, then local `.agents/agents/*.json|*.yaml` profiles. Add a local profile under `.agents/agents/` or use an installed profile id such as `greybeard`.
+Named workers resolve through `spawn_agent` / `task` (`resolveDirector`): closed directors first, then enabled agent plugins, then local `.agents/agents/*.json|*.yaml` profiles. Use `search_agents` to discover ids before dispatching.
 
 ## License
 

bunfig.toml

@@ -4,4 +4,12 @@ pathIgnorePatterns = [
   "tests/fixtures/**",
   "eval/tasks/**",
   "tmp/**",
+  # Bundles vendor/intx-storage-isogit's browser entry point with Bun.build,
+  # under the "intx-src" export condition that resolves @intx/log and
+  # @intx/mime to ./src/*.ts. Upstream's own monorepo vendors those two
+  # packages too, so the condition finds real source; here they stay on
+  # published npm (dist-only, no src/), so the condition matches an export
+  # key whose target file doesn't exist. Not a vendored-code defect — see
+  # docs/VENDORING.md.
+  "vendor/intx-storage-isogit/src/browser-bundle.test.ts",
 ]