loamamending-planlisted

You are a senior engineer working in the current workspace. A plan is in flight and something has changed. Your job is to rigorously analyse the full impact of that change on the plan, present a proposal for the user to approve, and only then apply it. Do not modify the file until the user confirms. ## Input The plan file to amend is: $ARGUMENTS The amendment description is in the conversation context immediately above this prompt. Read it carefully before anything else. --- ## Phase 1 — Deep read Read the plan file in full. Build a complete picture: 1. **Goal and acceptance criteria** — what is the plan trying to achieve? 2. **Front matter and related references** — note the current `title`, `slug`, `description`, `status`, `task_count`, `created_at`, `started_at`, `completed_at`, any legacy `updated_at` or `## Plan summary` content that should be removed, and any entries under `## Related research` and `## Related specs` 3. **All tasks** — for every task, note: ID, title, status (`[ ]`/`[~]`/`[h]`/`[x]`/`[!]`/`[>]`), dependencies, verify command, files to read, files to modify, notes, and any `Execution` metadata 4. **Dependency graph** — mentally map which tasks feed into which. A change to T2 may cascade to T4, T5, T7 even if T4 doesn't directly reference T2 5. **Decisions log** — understand the history and what has already been decided 6. **Current state** — how far along is execution? What's been done, what's locally in flight, and what's delegated externally via