Fix task directory gap in upgrade process

The additive extension model refactor moved prompts/contracts/scripts into
.automaton/ but never addressed where tasks live. Two conventions existed:
framework keeps tasks in .automaton/tasks/, Orchestrator creates project
tasks at tasks/.

Fixes:
- Dashboard _find_tasks_dir() now scope-aware: framework mode prefers
  .automaton/tasks/, project mode prefers tasks/ at project root
- migrate-project.sh: if tasks exist in .automaton/tasks/ (old model),
  move them to tasks/ (project root)
- Orchestrator prompt: documents that tasks location depends on scope

prompts/orchestrate.md

@@ -19,7 +19,7 @@ Specifically:
 7. {project}/.automaton/extensions/contracts/*.md — Additive extensions loaded after global contracts
 8. ~/.automaton/scripts/*.sh — Always from global framework
 9. {project}/.automaton/extensions/scripts/*.sh — Additive extensions loaded before global scripts (pre-processing)
-10. Any existing files under {project}/tasks/
+10. {project}/tasks/ — Project tasks (project mode) or ~/.automaton/tasks/ (framework mode)
 
 ## VRAM Detection
 
@@ -201,7 +201,10 @@ If the user says "orchestrate" or "continue" with no new task description, the O
 #### New tasks from user input
 If {task-description} contains a description for a NEW task, the Orchestrator MUST:
 1. Generate a kebab-case task name from the description (e.g., "add user auth" → `add-user-auth`)
-2. Create the task folder: `{project}/tasks/{task-name}/` (empty — no artifact files)
+2. Create the task folder. Task location depends on scope:
+   - **Framework mode** (inside ~/.automaton/): `~/.automaton/tasks/{task-name}/`
+   - **Project mode** (in a user project): `{project}/tasks/{task-name}/`
+   The dashboard reads from both locations automatically.
 3. **Immediately drive it to completion** using the auto-execution loop
 
 Note: `IMPLEMENTATION.md` is the artifact produced by the implementation phase, not the Orchestrator. Do not pre-create it. **Do not create an empty `IMPLEMENTATION.md` for new tasks** — this is inconsistent with the Orchestrator's own rule and can confuse the Research phase.
@@ -237,7 +240,9 @@ In manual mode, the Orchestrator only **reports** the current state and the next
 
 ## State Determination
 
-Examine the tasks/ directory and determine the state of each task folder. Check from the most advanced state backward. **Important**: Always check that artifacts are non-empty before considering them as indicators of task state.
+Examine the tasks/ directory and determine the state of each task folder. The tasks directory is:
+- **Framework mode**: `~/.automaton/tasks/`
+- **Project mode**: `{project}/tasks/` Check from the most advanced state backward. **Important**: Always check that artifacts are non-empty before considering them as indicators of task state.
 
 1. Has `VERDICT.md` with `PASS` (non-empty) → **Complete**
 2. Has `VERDICT.md` with `NEEDS_REVIEW` or `FAIL` (non-empty) → **Human Intervention**