e837a284af
Three load-bearing gaps between the agent RFC and the MCP surface: - RFC §9 Fleet Mode describes the 6-digit pairing-code bootstrap as the primary way an unauthenticated node provisions its first AgentApiKey. `handleAuthLogin` existed as an Action but never surfaced as an MCP tool, so IDE/CLI callers had to shell out. Adds `agentic_auth_login` under `registerPlatformTools` with a thin wrapper over the existing handler so the platform contract stays single-sourced. - `RegisterTools` was double-registering `agentic_scan` (bare `mcp.AddTool` before the CORE_MCP_FULL gate, then again via `AddToolRecorded` inside the gate). The second call silently replaced the first and bypassed tool-registry accounting, so REST bridging and metrics saw a zero for scan. Collapses both into a single recorded registration before the gate. - `registerPlanTools` and `registerWatchTool` were also fired twice in the CORE_MCP_FULL branch. Removes the duplicates so the extended registration list mirrors the always-on list exactly once. - Switches `agentic_prep_workspace` from bare `mcp.AddTool` to `AddToolRecorded` so prep-workspace participates in the same accounting as every other RFC §6 tool. TestPrep_RegisterTools_Good_RegistersCompletionTool now asserts all three `agentic_auth_*` tools surface, covering the new login registration alongside provision/revoke. Co-Authored-By: Virgil <virgil@lethean.io> |
||
|---|---|---|
| .. | ||
| agentic | ||
| brain | ||
| lib | ||
| messages | ||
| monitor | ||
| runner | ||
| setup | ||
| .DS_Store | ||