[bfs2021]

Fixes #610, option 1 from the issue.

Problem

move_task and bulk_move_tasks PUT { target_view_id, target_status_id, target_position } to the task-positions routes. The API reads { position, group_key } (and { items: [...] } for the bulk route), so it bound position: 0 and ignored the rest, while the tools replied "Task moved successfully".

Fix

• move_task now takes projectId, viewId, taskId, position, optional groupKey, and PUTs { position, group_key } to /views/{viewId}/task-positions/{taskId}.
• bulk_move_tasks takes projectId, viewId, items: [{ taskId, position, groupKey? }] and PUTs { items } to /views/{viewId}/task-positions.
• Tool descriptions say these set a task's order within one view; sprint/status changes stay with update_task.
• PacaAPIViewsClient gains moveTaskPosition; bulkMoveTasks now calls the bulk route. The duplicated MoveTaskInput type is replaced accordingly.

Testing

• npx vitest run in apps/mcp: 631 passed.
• src/__tests__/api/views-client.test.ts asserts both request URLs and bodies; src/__tests__/tools/view-tools.test.ts asserts the new schemas, mapping and replies (including that move_task no longer calls the bulk method).
• npx tsc --noEmit reports four errors in unrelated files (zod inference in other tool schemas), none in the files this PR touches.

[pullfrog]

ℹ️ No critical issues — one small consolidation suggestion inline, plus a docs note below. The fix matches the API contract and is well covered by tests.

Reviewed changes

• move_task and bulk_move_tasks now match the API wire contract — move_task takes {projectId, viewId, taskId, position, groupKey?} and PUTs {position, group_key} to /views/{viewId}/task-positions/{taskId}; bulk_move_tasks takes items: [{taskId, position, groupKey?}] and PUTs {items} to /views/{viewId}/task-positions. Descriptions now state these set a task's order within one view (sprint/status stay with update_task), and both replies report what changed.
• PacaAPIViewsClient updated — new moveTaskPosition; bulkMoveTasks rewritten to hit the bulk route with an items body.
• Type changes — removed the duplicated MoveTaskInput; BulkMoveTasksInput is now the items array; added MoveTaskPositionInput.
• Tests — both routes asserted by URL and body, plus tool-level schema/mapping/reply assertions (including that move_task no longer calls the bulk method).

I verified the contract against services/api/internal/transport/http/dto/view_dto.go (MoveTaskRequest{position, group_key}, BulkMoveTasksRequest{items}), the routes in router.go:622-624, and the 204 responses the client already handles. The two touched suites pass (83 tests), npm run lint is clean, and the npx tsc --noEmit errors are confined to the unrelated member-tools.ts.

ℹ️ Tool reference docs still describe the pre-fix behavior

The tool descriptions in view-tools.ts were updated to make clear these tools only set an order within a view, but the tool documentation was not. docs/guides/mcp-server-setup.md:197 still tells users bulk_move_tasks "Moves all tasks to the new sprint" — the exact misunderstanding behind #610 — and apps/mcp/README.md:329 / apps/mcp/ALL_TOOLS.md:75-76 still describe them as generic moves. Updating the setup example is worth doing while the semantics are fresh.

Technical details

# Stale tool docs after the semantic fix

## Affected sites
- `docs/guides/mcp-server-setup.md:197` — "`bulk_move_tasks` - Moves all tasks to the new sprint" (never true, and contradicts the new description)
- `apps/mcp/README.md:329` — "`bulk_move_tasks` - Bulk move tasks in a view"
- `apps/mcp/ALL_TOOLS.md:75-76` — generic "move" wording for both tools

## Required outcome
- Docs reflect that both tools set a task's manual position within a single view, and that sprint/status changes use `update_task`.

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}

[bfs2021]

Done in db7d522: bulkMoveTasks now delegates to bulkMoveViewTaskPositions, and the setup guide, apps/mcp/README.md and ALL_TOOLS.md say these tools set a task position within one view, with update_task named for sprint/status changes. npx vitest run still passes (631).

[pullfrog]

✅ No new issues found.

Reviewed changes

This run re-reviewed the delta since the prior pullfrog review (commit db7d522). Both prior concerns are addressed.

• bulkMoveTasks now delegates — PacaAPIViewsClient.bulkMoveTasks calls bulkMoveViewTaskPositions(projectId, viewId, input.items) instead of duplicating the { items } PUT, so the bulk contract lives in one place.
• Tool docs reworded — apps/mcp/README.md, apps/mcp/ALL_TOOLS.md, and docs/guides/mcp-server-setup.md now describe move_task / bulk_move_tasks as setting a task's manual position within a view, with sprint/status changes handled by update_task.

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}

[pikann]

LGTM! Thank you for the contribution! 🚀