REVIEWED_TREE: dda86f6e4afb68e4be895be6eeea57febd860e6b /workspace/gstack
{"severity":"INFORMATIONAL","path":"capy/skill/gstack/SKILL.md","line":58,"summary":"The fix list says it dropped one clause, but it dropped two more. The first is 'with Capy's subscribe tool', which was the only place the Capy skill named that tool (grep finds no other 'subscribe' in the file). A lane whose PR was opened by its /ship subagent owns no PR watch, so 'subscribes to the PR' no longer says it has to subscribe explicitly; a reader could assume it inherits the PR-create watch, or fall back to polling with gh. The second is 'With the subscription in place', which required the subscription to exist before the subagent is stopped; only the list order implies that now. No test asserts either phrase."}
{"severity":"INFORMATIONAL","path":"capy/skill/gstack/SKILL.md","line":58,"summary":"'keeps that one subscription' became '(renewed on expiry, cancelled at merge or close)'. The 'one' was the guard against duplicate subscriptions, and it is gone, so a lane that re-READYs (or renews after expiry) gets no wording that stops it from adding a second watch next to the first. Each duplicate watch is a wasted wake. Nothing reads this as a failure."}

Checked: the one-line diff in b19fc09; the cross-references in docs/captain.md:313-336 and captain/templates/brief.md:36, which still carry the red-check clause the fix list says it dropped; the anchor #plan-approve-ship, which is unchanged; and test assertions on the bullet (captain-skill.test.ts only matches the section structure, and no test matches removed wording). I reran context-budget-ratchet, captain-skill, capy-skill-wrapper and review-declared-risk at this tree: 75 pass, 0 fail. Nothing reaches the CRITICAL floor.
