unity-open-mcp 0.6.1 → 0.8.2

package/dist/capabilities/build-capabilities.d.ts

@@ -3,6 +3,40 @@ import type { RuleCapability, FixCapability, CapabilityStatus } from "./rule-cat
 import { type CostHintsBlock } from "./cost-hints.js";
 import { type LifecycleClass, type LifecycleBlock } from "./lifecycle.js";
 export type RoutePolicy = "live" | "offline" | "offline-first" | "compressible";
+/**
+ * The handful of tools whose category intentionally diverges from their
+ * group, plus the always-visible meta-tools (group=null) that need a real
+ * category. Two cases:
+ *
+ *   1. **Grouped tools where category ≠ group** — historical reasons where
+ *      the session-visibility group and the capability-classification
+ *      category split (e.g. `compile_check` is in the `gate-and-verify`
+ *      group for session visibility but classified as `diagnostics`).
+ *
+ *   2. **Meta-tools (group=null)** — always-visible server meta-tools that
+ *      are not in any group (they bypass the manage_tools visibility
+ *      system) but still need a category label for the capabilities surface.
+ *
+ * Documented exhaustively so the parity test can enforce that every entry
+ * here is a real, deliberate exception. Exported so the parity test can
+ * inspect the override surface directly.
+ */
+export declare const TOOL_CATEGORY_OVERRIDES: Record<string, string>;
+/**
+ * Tools that intentionally carry the default `"other"` category. Two flavors:
+ *
+ *   - **Meta-tools** (group=null) — always-visible operator/debug surfaces
+ *     that have no group assignment and no override. The parity test allows
+ *     them through `"other"` explicitly so a NEW tool that lands in neither
+ *     bucket fails loudly.
+ *
+ *   - **Grouped tools whose override is `"other"`** — `dependencies` and
+ *     `reimport_package` (preserved pre-change behavior; see overrides).
+ *
+ * Documented; adding one means updating both this set and the test. Exported
+ * so the parity test can enumerate the allowed-other surface.
+ */
+export declare const ALLOWED_OTHER_CATEGORY_TOOLS: ReadonlySet<string>;
 export interface PlannedTool {
     name: string;
     category: string;
@@ -11,8 +45,8 @@ export interface PlannedTool {
 }
 export declare const PLANNED_TOOLS: PlannedTool[];
 /**
- * Static routing narrative. Mirrors `docs/api/mcp-tools.md` §Route
- * policy + §Batch support + the `BATCH_TOOL_NAMES` / blocked-tool
+ * Static routing narrative. Mirrors `docs/api/routing-lifecycle.md` plus the
+ * `BATCH_TOOL_NAMES` / blocked-tool
  * lists in `batch-spawn.ts`. Kept concise; per-tool `batchCapable`
  * flags live on each {@link ToolCapability}.
  */
@@ -118,7 +152,7 @@ export interface CapabilitiesResult {
         rulesPlanned: number;
         fixesImplemented: number;
         fixesPlanned: number;
-        /** M18 Plan 2 — count of groups enabled by default (`core` only). */
+        /** Count of catalog groups enabled by default for a fresh session. */
         toolGroupsDefaultEnabled: number;
         /** M18 Plan 2 — total group count. */
         toolGroupsTotal: number;
@@ -161,8 +195,8 @@ export interface CapabilitiesResult {
 }
 /**
  * Compact routing summary embedded in the capabilities response. This
- * is the agent-facing counterpart of `docs/api/mcp-tools.md` §Route
- * policy / §Batch support — it does NOT duplicate the full prose.
+ * is the agent-facing counterpart of `docs/api/routing-lifecycle.md` — it
+ * does NOT duplicate the full prose.
  */
 export interface RoutingSummary {
     /** Most tools prefer the live bridge when it is connected. */