xarmian b459892d8b fix(search): the collection filter resolves exact-first per workspace in scope, so a collection named task is no longer shadowed by tasks (BUG-2659, BUG-2839) (#1576) ...

* fix(search): the collection filter resolves exact-first per workspace in scope, so a collection named `task` is no longer shadowed by `tasks` (BUG-2659, BUG-2839)

/search matched its collection filter as a literal slug, so shorthand
found nothing and both clients normalised it first, which rewrote `task`
to `tasks` even where a `task` collection existed. The handler now
resolves the filter with resolveItemCollectionSlug in every workspace in
scope and filters the store on the resulting collection IDs; one slug
cannot express that, since the same input can resolve differently per
workspace. The capability endpoint advertises
search_collection_resolution, and the CLI sends the name as typed only
to a server that does. The in-process remote MCP mapper stops
normalising outright.

Also corrects cascadeTitleRename's doc comment, which named
links.ReplaceTitle for a cascade that rewrites through
links.RewriteBracketsAt (BUG-2839).

* chore(mcp): tool surface 0.55 — pad_item.search's collection resolves exact-first per workspace (BUG-2659)

Lead-ruled BEHAVIOR bump on the v0.36/v0.40 grounds: in a workspace
holding both task and tasks, the same call now answers from task.

2026-09-26 12:20:58 -04:00

..

loadtest-collab

fix(collab): WebSocket dials get their own per-user bucket and a per-user socket cap, and the editor jitters its reconnects (BUG-1308) (#1499)

2026-09-24 04:51:57 -04:00

pad

fix(search): the collection filter resolves exact-first per workspace in scope, so a collection named task is no longer shadowed by tasks (BUG-2659, BUG-2839) (#1576)

2026-09-26 12:20:58 -04:00