monitor: gh-write target not pinned to plugin .repository — comment landed in upstream repo

[kborovik]

Skill: skills/monitor/SKILL.md — plugin sdd v1.1.0

Deviation: monitor's gh write posted a comment to anthropics/claude-code#67652 (the upstream FR opened for T12 / §V.62) instead of the plugin repo kborovik/spec-driven-dev. A skill-deviation report landed in a third-party repo.

Expected (skill body):

• TARGET (PROTOCOL step 4): issue repo ← ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json .repository, parsed to owner/repo.
• WRITE (PROTOCOL step 7): gh issue comment <n> --repo <target>.
• DEV-REPO ROUTING: cwd == plugin repo → route to backprop (§B row), file no issue.

Every monitor gh write must target the plugin's own .repository; a dev-repo deviation gets no issue at all.

Actual: <target> / <n> resolved against a repo named in the deviation context (the upstream FR anthropics/claude-code#67652), not the plugin's .repository. Nothing asserts the resolved <target> equals the plugin repo before the gh write, so a repo mentioned in the deviation excerpt can bleed into the write target.

Impact: deviation report published to the wrong (third-party) repo; DEDUP then searches the wrong repo, so recurrences won't dedup.

Fix direction:

• Pin <target> strictly to plugin .repository; never to a repo named in the deviation context/excerpt.
• Assert <target> == plugin .repository immediately before any gh issue create / gh issue comment.
• GATE (step 6) should surface the resolved <target> so a wrong-repo write is caught before confirm.