5 Commits

Include renames

Author	SHA1	Message	Date
mika kuns	d258ab4164	test(worker): start_list_handler ins erwartete MCP-Tool-Inventar aufnehmen	2026-09-02 21:57:16 +02:00
Mika Kuns	2330b426c6	feat(claude-do): Expose HandoffRoundTracker budget via an MCP tool (e.g. get_ ... The handoff-budget task (round/remaining/final now surfaced in the handoff.md brief via HandoffRoundTracker.GetStatus, wired through InteractiveLaunchSpecService.BuildForMergeHelperHandoffAsync) only reaches the session at the start of a handoff round. There is no way to query the current round/remaining budget for a handler task mid-session or from outside (e.g. the UI, or a script). Consider add ClaudeDo-Task: 0a185f8e-823d-42fc-9a5b-97c5eb91c616	2026-09-02 14:43:44 +02:00
Mika Kuns	a0c277100e	test(worker): assert the full external MCP tool-name inventory ... Guardrail for the upcoming ExternalMcpService.cs topic split: proves the move is name-preserving by pinning the complete set of registered tool names (computed via the SDK's own McpServerTool.Create, not a reimplementation of the naming rule) before any file is moved.	2026-09-02 13:02:10 +02:00
mika kuns	2a3133efad	feat(worker): accept #123 task numbers as MCP tool input ... TaskIdResolver resolves a #123/bare-123 taskId parameter to its GUID before any lookup, across every External/ MCP tool that takes a task id, including the batch tools' id arrays (via delegation to the already-resolving single-entity methods) and update_task's dependsOnTaskId (empty string still passes through unchanged as the clear-link sentinel). An unknown number throws a clear error instead of a silent null. McpToolDocs.TaskNumberHint tells the agent to refer to tasks as #<number> when reporting to the user, added to the description of get_task, list_tasks, add_task, update_task_status and review_task.	2026-08-11 13:10:49 +02:00
mika kuns	d7ebafd556	fix(worker): make external MCP filter params optional, surface tool errors ... Nullable filter/patch params across the External/ MCP tool classes (ListTasks, UpdateTask, AddSubtask, ReviewTask, SetMyDay, SetListConfig/SetTaskConfig, CreateList/UpdateList) lacked C# default values, so the generated tool schema marked them required — MCP clients omitting them (the common case) failed. Gave every such parameter a default value. Also registered a call-tool filter (ExternalMcpExceptionFilter) on the external MCP host that translates InvalidOperationException/ArgumentException into McpException, since the SDK's own catch-all discards ex.Message for any other exception type and returns a generic "An error occurred invoking 'X'." string. Added a reflection-based schema test sweeping every [McpServerToolType] class to guard against reintroducing a required-but-nullable parameter.	2026-07-23 18:21:46 +02:00