Context
Surfaced by @neo-gpt's cross-family review of PR #13307 (redo Slice-2) as a non-blocking [KB_GAP] Approve+Follow-Up (§6.3.1). learn/agentos/NeuralLink.md is the human/agent-readable Neural Link tool guide; its tool tables + headline count have drifted from the live OpenAPI surface (ai/mcp/server/neural-link/openapi.yaml, which the guide itself names as the SSOT at line 186).
The Problem (V-B-A'd)
NeuralLink.md:184 claims the Neural Link "exposes 33 tools"; the live openapi has 41 operationIds.
- The domain tables OMIT 11 operations — critically the entire mutation surface:
create_component, remove_component, undo, redo, call_method. An agent reading the guide cannot discover it can create / remove / undo / redo components at all (it must fall through to the openapi). Also missing: get_drag_state, get_drag_trace, observe_motion, healthcheck, manage_connection, verify_component_consistency.
get_console_logs is listed twice (categories 4 and 6).
- Root cause: a hand-maintained count + hand-maintained tables drift every time a tool lands (the undo/redo Slice-1/2 work added 2 tools the guide never tracked).
The Fix
- Replace the fragile hardcoded count (line 184) with a drift-resistant statement that defers the exact, complete list to the openapi SSOT (already cited at line 186).
- Add the 11 missing tools to their domain tables: a Mutation grouping under Instance Manipulation for
create_component / remove_component / undo / redo / call_method; get_drag_state / get_drag_trace / observe_motion / verify_component_consistency under Interaction & Debugging / Introspection; healthcheck / manage_connection under Runtime & System.
- De-duplicate
get_console_logs.
Friction→Gold (stretch / future)
The deepest fix is a doc-generation step (openapi → the tables) so the guide can never drift again. Out of scope for this docs-refresh leaf; noted as a future MX enhancement.
Acceptance Criteria
Out of Scope
- An automated openapi→doc generation step (future MX enhancement).
- Any openapi / runtime change — this is docs-only (qualifies for the §6.1 pure-documentation micro-change exemption).
Related
Surfaced in PR #13307 review (Resolves #13304, redo Slice-2). Tool surface: ai/mcp/server/neural-link/openapi.yaml. Refs #13012 (the Agent Harness — the tool surface IS the agent's body-interface).
Origin Session ID: a0bc6b23-78c5-4bd7-b944-9db5e236f42d
Release classification: boardless (docs/KB hygiene — not v13-release-blocking; Approve+Follow-Up follow-up per §6.3.1).
Context
Surfaced by @neo-gpt's cross-family review of PR #13307 (redo Slice-2) as a non-blocking
[KB_GAP]Approve+Follow-Up (§6.3.1).learn/agentos/NeuralLink.mdis the human/agent-readable Neural Link tool guide; its tool tables + headline count have drifted from the live OpenAPI surface (ai/mcp/server/neural-link/openapi.yaml, which the guide itself names as the SSOT at line 186).The Problem (V-B-A'd)
NeuralLink.md:184claims the Neural Link "exposes 33 tools"; the live openapi has 41 operationIds.create_component,remove_component,undo,redo,call_method. An agent reading the guide cannot discover it can create / remove / undo / redo components at all (it must fall through to the openapi). Also missing:get_drag_state,get_drag_trace,observe_motion,healthcheck,manage_connection,verify_component_consistency.get_console_logsis listed twice (categories 4 and 6).The Fix
create_component/remove_component/undo/redo/call_method;get_drag_state/get_drag_trace/observe_motion/verify_component_consistencyunder Interaction & Debugging / Introspection;healthcheck/manage_connectionunder Runtime & System.get_console_logs.Friction→Gold (stretch / future)
The deepest fix is a doc-generation step (openapi → the tables) so the guide can never drift again. Out of scope for this docs-refresh leaf; noted as a future MX enhancement.
Acceptance Criteria
create_component/remove_component/undo/redo/call_method) are documented.get_console_logsappears once.Out of Scope
Related
Surfaced in PR #13307 review (Resolves #13304, redo Slice-2). Tool surface:
ai/mcp/server/neural-link/openapi.yaml. Refs #13012 (the Agent Harness — the tool surface IS the agent's body-interface).Origin Session ID: a0bc6b23-78c5-4bd7-b944-9db5e236f42d
Release classification: boardless (docs/KB hygiene — not v13-release-blocking; Approve+Follow-Up follow-up per §6.3.1).