update-task-loglisted

# Update Task Log ## When to use this skill Invoke this skill **after every meaningful change** during task implementation: - A subtask's files have been edited (one entry per logical commit-sized unit) - A test was added or updated - A command was run that affected state (`pnpm install X`, a migration, a refactor pass) - A HIGH/CRITICAL permission was granted and acted on - A blocker was hit (record it and stop) **Do not use this skill** for trivial intermediate edits while iterating on the same change — one entry per shipped unit, not per keystroke. ## Instructions Append one YAML entry to `tasks/active/{ID}/TASK {ID}.md` under the `## Implementation Log` heading. Format is fixed — the Reviewer and the `generate-timesheet` skill parse these entries. ### Procedure 1. **Locate the log file** at `tasks/active/{ID}/TASK {ID}.md`. If it doesn't exist (task isn't `PLANNED`), stop and route the user to `plan-task` instead. 2. **Compose the entry** using the shape below. Be specific in `summary` and `why` — these become the source material for the Tempo sugar-coater. 3. **Append at the end** of the file under `## Implementation Log`. Each entry is wrapped in `### ENTRY START` for grep-ability. 4. **If this entry records a HIGH/CRITICAL approval**, include a `governance` field with the user's verbatim approval string. The Reviewer checks for this when validating. 5. **If this entry records a blocker**, also update the top-level `Status:` line in the same file to `BLOCKED` an