pr-watch-as-authorlisted

# pr-watch-as-author — bounded PR review watch loop > Follow `skills/principle-progress-tracking/SKILL.md`: this procedure has more than two steps — > seed one todo item per step below before starting and mark each complete as you go. `pr-watch-as-author` closes the gap between "PR open" and "ship it". It promotes the PR out of draft, takes a baseline snapshot, and polls GitHub on a bounded cycle. When new review feedback arrives, it runs the triage procedure in `skills/pr-open-comments/SKILL.md`. The session stays dedicated to the watch while it is armed — that trade-off is accepted by design. The user can interrupt at any time, and each individual command stays small and observable. Feedback arrives in two shapes and both are triaged: - an **inline review thread**, anchored to a diff line and carrying a resolved/unresolved bit. - a **plain PR comment** on the conversation tab, carrying no resolution bit at all. Whole-PR reviews — a summary review, a bot's findings, an automated review posted as one body — land here. The distinction matters because the unresolved-thread set cannot represent a plain comment. A comment is triaged **once**, keyed by its id, and is done when it has been triaged; it never joins a gate waiting to be resolved, because nothing can resolve it. Treating one as a thread would leave the watch waiting forever on a bit that does not exist; ignoring one would silently drop real feedback, which is the failure this shape is most prone to. ## Inpu