update-progresslisted

1. **Locate the handoff.** Use the path given; else the newest file in the repo's `skilleddocs/handoffs/`; else the newest handoff-looking file in the OS temp dir. 2. **Verify its claims.** `git log` since the session's start commit, and run the repo's test suite if it has an obvious one (detect from `package.json` scripts, `pytest.ini`/`pyproject.toml`, etc. — don't assume a specific runner exists). Don't take the handoff's word for "tests pass" — check. 3. **Code review, if code changed.** If product code (not just docs) changed, call the Skill tool with `"code-review"` over the session's commits before treating anything as done. 4. **Update docs, if the repo has them.** A roadmap doc gets its checkboxes ticked; a status doc gets its component rows and dated "what changed" entry; a decisions doc (`skilleddocs/decisions.md`, or `docs/decisions.md` / an ADR folder if the repo uses one) gets a row only if the handoff records a decision. Otherwise: Check for a README "Status"/"Progress" section, a `CHANGELOG.md`, or a `docs/` folder — update whatever actually exists. Don't invent doc structure the repo doesn't have. A roadmap/README **"current phase" marker follows where merges are landing, not where the last checkbox is.** If this session's merges belong to a later phase than the marker, move it and mark the earlier phase "done except gated (#…)" listing its open gated/parked items — a phase with gated leftovers never "finishes", so waiting for that leaves the marker sta