feat(0.4.14): VSCode-kanban feature parity (restore_task, rename_label, undo, column-aware new task, TASKS_DIR)

[sabbah13]

Five regressions vs the original VSCode extension, all fixed.

1. restore_task MCP tool — undoes a delete by walking archived/, restoring the matching file, and re-publishing.
2. rename_label MCP tool — renames a label across config + every task using it. Idempotent. Returns updatedCount.
3. Toast undo for archive + delete — 5-second window with an Undo button.
4. Column-aware new-task hotkey — n while hovering a card opens the add-task form for THAT column.
5. TASKS_DIR env override — CLI honors process.env.TASKS_DIR so tasks can live next to code in a git repo.

Tests

• 10/10 mcp + 15/15 storage + 84/84 e2e green
• 4 new tests (2 mcp + 2 e2e)

[sabbah13]

Automated Code Review

Verdict: ⚠️ REQUEST CHANGES

Summary

Adds five features from the original VSCode kanban extension: restore_task MCP tool (undo delete), rename_label MCP tool (cascades across config + tasks), toast undo for archive and delete, column-aware n hotkey for new tasks, and a TASKS_DIR env override on the CLI. The architecture is clean, the new store methods are well-structured, and the 4 new tests are meaningful. Three issues need addressing before merge.

---

Issues (must fix before merge)

1. rename_label bypasses Zod schema validation [packages/mcp-server/src/server.ts]

   Every other handler uses a typed Zod parse (e.g. DeleteTaskArgs.parse(raw)), but rename_label uses a raw type assertion and manual truthiness check:

   const { from, to } = raw as { from?: string; to?: string };
   if (!from || !to) { … }

   A non-string value (from: 123) passes the !from guard and reaches store.renameLabel with an unchecked type. A small Zod schema would match the established pattern and satisfy strict mode:

   const RenameArgs = z.object({ from: z.string().min(1), to: z.string().min(1) });
   const { from, to } = RenameArgs.parse(raw);

2. PR template checklist missing

   The PR body is informative but omits the standard Type checkboxes and Checklist (typecheck / lint / test pass confirmations, conventional commit confirmation). PRs docs: contributor experience + PR review process #33 and others include these — worth filling in for consistency, especially for a feature PR.

3. README conflict risk with PR docs(readme): benchmark improvements from repo audit #34

   Both this branch and docs/readme-improvements (PR docs(readme): benchmark improvements from repo audit #34) make identical edits to README.md against the same main base. Whichever merges second will hit conflicts. Recommend rebasing one branch onto the other, or having PR docs(readme): benchmark improvements from repo audit #34's README changes dropped if this one lands first.

---

Suggestions (optional)

• Column-aware hotkey has an undocumented limitation. The PR description says "n while hovering a card opens the add-task form for THAT column" — but the implementation gates this on groupBy === 'status' only; other groupings fall back to effectiveColumns[0]. Worth noting in the PR body or the help dialog tooltip.

• No e2e test for the column-aware hotkey. The undo flow is well covered, but the n-key column-routing logic has no automated verification.

• No test for TASKS_DIR env override. A quick integration assertion that tasks land in a custom directory would guard this against silent regressions.

---

This review was generated automatically. A maintainer will follow up.

---

Generated by Claude Code