Add kanban flow tools
Problem
Agents need flow-aware tools to pull work, get context, and submit for review. The key differentiator is context assembly — agents shouldn't have to figure out their own context.
Solution
CLI commands
`pyrite sw claim ` — Claim a backlog item (atomic transition to in_progress, set assignee). Agents and humans use the same command.
`pyrite sw review-queue` — Show items awaiting human review, sorted by wait time. Computed from backlog items in `review` status.
`pyrite sw submit ` — Transition item from in_progress to review.MCP tools
`sw_pull_next` (read tier) — Recommend what to work on given current WIP state. Reads board config for WIP limits, considers priority, dependencies. Returns item + context preview.
`sw_context_for_item` (read tier) — Given a backlog item ID, assemble the full context bundle: relevant ADRs, component docs, programmatic validations, development conventions, and dependencies.
`sw_review_queue` (read tier) — Surface items awaiting human review: what needs attention, wait time, what's blocking downstream work.
`sw_validate` (write tier) — Run all relevant `programmatic_validation` entries against proposed changes. Returns pass/fail per validation.
`sw_claim` (write tier) — Atomic claim of backlog item (same as CLI `sw claim`).REST API endpoints
`GET /api/sw/review-queue` — Review queue with age/priority sorting
`GET /api/sw/board` — Board state (items per lane, WIP usage)
`POST /api/sw/claim/{item_id}` — Claim a backlog item
`POST /api/sw/submit/{item_id}` — Submit for reviewAcceptance Criteria
All five MCP tools registered (3 read, 2 write)
`sw_pull_next` respects WIP limits and returns item + context preview
`sw_context_for_item` assembles complete context bundle with links to all relevant entries
`sw_validate` runs programmatic validation checks and returns structured pass/fail
CLI commands work for both human and agent users
REST API endpoints match CLI/MCP functionality
Integration tests for each tool and command