issue-updatelisted

# Issue Update Close the loop: after the code ships, the tracker must reflect it without anyone updating it by hand. This skill speaks to whichever tracker is configured in `.claude/dev-kit.json` (`tracker.type`). ## Preconditions - `.claude/dev-kit.json` exists with a `tracker` block (otherwise run `dev-kit-setup` first). - The adapter's backend is authenticated (MCP connector authorized, or `gh`/`az` logged in) — otherwise tell the user how to authenticate and stop. - A PR URL and a product-facing summary of the delivered work are available from the delivery flow. ## 1. Comment the delivery summary **Audience: product owners and other non-technical readers.** The comment explains what was delivered and why, in user terms — no test counts, coverage percentages, lint, or tooling jargon. All technical evidence lives in the PR, which is linked. Post a comment (via the adapter below) containing: ``` Pull request: <PR URL> What was delivered: - <the new behavior, described as a user would experience it — one bullet per acceptance criterion addressed> Decisions taken: - <each meaningful decision or interpretation made during implementation, in plain language, with the reason> Out of scope / follow-ups: - <anything deliberately left out or worth a future ticket, or "Nothing pending."> ``` Keep it factual and grounded in what was actually built — never a template filled with assumptions. If an acceptance criterion was NOT met, say so here plainly. ## 2. Ensure the item h