Backlog Operations In Explorer

Explorer needs structured task and backlog workflows that can mutate repository files safely, but those rules should not be distributed across buttons, modal presenters, and ad-hoc file operations in the user interface (UI).

Backlog Boundary For Explorer

tasksAgent centralizes that responsibility behind Model Context Protocol (MCP) tools for configuration, listing, retrieval, mutation, history, and reorder operations. It owns repository path boundaries and file-extension rules so backlog state changes are validated before they touch the workspace.

Runtime Behavior

Task operations execute through tasksAgent/tools/tasks_tool.sh and tasks_tool.mjs, while Explorer integration enters through tasksAgent/IDE-plugins/tasks-tool-button/. The user interface collects intent and renders results; the agent remains responsible for file semantics and mutation workflows.

Validation rule: run the tasks agent tests under tasksAgent/tests for code changes, together with documentation and specification updates.