* feat(verify-pr): make "re-verify after update" a follow-up trigger
After a local verification round, a maintainer who sees the PR move says
"有更新了，重新验证". That phrase was not a documented trigger: the skill
could miss it entirely or start a fresh round, losing the previous-finding
status table and the delta classification. The local follow-up lookup only
searched PR comments, so a round that was never published was invisible and
silently degraded to a fresh round, and nothing checked whether the head had
actually moved before spending a full round.
Add the re-verification phrases to the skill description, and a manual
re-verification contract: resolve the PR from the session or the newest
local artifact dir (ask when ambiguous), take the previous verified head
from the newest substantive round across local artifacts and published
comments, and fetch the current head before scoping. An unchanged head gets
an answer, not a round — comments and CI results are data, the same rule the
watch gate applies. A moved head runs the existing follow-up protocol.
Coordinates inherit from the previous round; publishing stays a
per-invocation request. A completed manual round records its head in the
watch dedup file so an installed watch does not re-fire for it.
The local follow-up lookup now searches both sources and takes the newest
substantive round, so unpublished rounds participate in the protocol.
* fix(verify-pr): register a manual round in the watch state before it starts
The manual re-verification contract recorded its head in the shared watch
dedup file only after the round completed, covering just the watch-first
ordering. With the watch state still on the previous head, a manual round
running in another session registered nothing while it worked, so the next
watch fire read the stale head and started a second round for the same head.
Make the check-and-register a step of its own ahead of running the round:
read the shared file, defer when it already records the head or marks a
round in flight, otherwise write the head as in-flight before starting —
the same write-before-start rule the watch prompt follows — and record it
as verified once the round completes. Both orderings now dedup through the
one file.
Pin the contract, including the registration-before-round ordering, in the
skill-text suite so the race cannot return unnoticed.
Shaojin Wen
ca204559a7