anyray-connect 0.11.231 → 0.11.232

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +8 -0
  2. package/dist/index.js +281 -281
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -297,6 +297,14 @@ metadata counters exposed by `doctor --json` / `status --json` are documented in
297
297
  [Connect reference](../docs/docs/tools/connect-reference.md#claude-code-source-trims).
298
298
  The [paired benchmark protocol](./HOOK-POLICY-BENCH.md) gates any default change.
299
299
 
300
+ Optional MCP client tools sit in a separate `clientToolPolicies` subtree of the same
301
+ profile, and `doctor --json` reports each one's resolved state under `clientTools`. They
302
+ gate a tool ADVERTISEMENT — bytes in every prefix, every turn — so the `false` direction is
303
+ the Rule 0 off-switch and is what the tests guard. `readBatch` ships **on**; what that
304
+ default is and is not backed by is [BATCH-READ-EXPERIMENT.md](./BATCH-READ-EXPERIMENT.md).
305
+ A switch never rides the MCP registration's argv: see `RECLAIMABLE_MCP_SERVER_ARGS` in
306
+ `src/tools/sharedHooks.ts` for what that cost.
307
+
300
308
  ```bash
301
309
  # From the monorepo root; Connect's build embeds the sibling VS Code extension.
302
310
  corepack pnpm install