Backlog tools refuse short ticket ids, and the not-found error misdirects

Short (8-hex) ticket ids are refused by the backlog tools, and the refusal gives a false reason. Reproduced read-only on AgentsRoom-MCP 1.206.0: the desktop bridge is reachable, the session is bound to the correct project, and the tickets exist (confirmed with their full UUIDs). backlog_update and backlog_internal_comment were not called, so their short-id refusals are reported, not re-run.

AgentsRoom diagnostics

• App version: 1.212.0
• OS: win32 10.0.26200 (x64)
• Agent CLI: omp
• App language: system

Expected behavior

A short id is either accepted by every backlog tool (a unique prefix), or refused by every backlog tool with one error shape that names the full-UUID requirement. A refusal must never say that a ticket is absent when it exists.

Actual behavior

backlog_internal_comments(taskId=<8-hex>) returns an error: "Task <id> is not in this project's backlog. Check the id with backlog_list." The same call with the full UUID returns the comments. backlog_get(taskId=<8-hex>) returns plain text with no error flag: "Task <id> not found in project <uuid>." backlog_list defaults to 50 of 281 tasks, has no id filter, and its hint never mentions the limit parameter.

Steps to reproduce

1. Pick a ticket that exists in the bound project. 2. Call backlog_get and backlog_internal_comments with its first 8 hex characters. 3. Call the same two tools with its full UUID. 4. Call backlog_list with the default limit, then with limit=500, and look for the ticket.

Version or build

AgentsRoom-MCP 1.206.0

Errors and logs

backlog_internal_comments: isError true, "Task <id> is not in this project's backlog. Check the id with backlog_list." backlog_get: isError false, "Task <id> not found in project <uuid>."