# BUG_REPORT: move-completed-tasks-to-complete-folder

## Findings

### Bug 1 (LOW): `cmd_create_task` error message references old path

When creating a task with the same name as a completed task, the error message uses `task_path` which is now the completed task path (via `_task_dir` fallback). The message says "already exists at {task_path}" which shows the `tasks/complete/<name>/` path instead of `tasks/<name>/`. This is correct behavior but could be confusing to the user.

**Severity:** LOW (accurate but surprising path)
**Fix:** None needed for v1. The error message is factually correct.

### Bug 2 (INFO): Subtask paths not covered by fallback

The `_task_dir` fallback only applies to non-subtask paths (no "/" in the name). If a subtask is completed, `_task_dir` won't find it in `tasks/complete/<parent>/subtasks/<name>/`. However, subtasks are never independently transitioned to `complete` -- they are part of their parent task's lifecycle.

**Severity:** INFO (by design)
**Fix:** None needed.

## Summary

No correctness bugs found. One LOW (cosmetic error message) and one INFO (by design).

**Verdict: CLEAN**