fix: remove PR instructions from update skills

.agents/skills/update-dedupe/SKILL.md

@@ -57,13 +57,12 @@ By default this targets the current repo and looks back 7 days. It collects only
 ## Evidence Rules
 
 - Only encode a cluster when at least two independent closed-as-duplicate events point at the same canonical issue, or a maintainer explicitly asks for one.
-- Skip the PR when there is no repeated signal.
+- Skip the update when there is no repeated signal.
 - Do not weaken precision-over-recall for dedupe.
 
 ## Final Checks
 
 - Re-read the updated `dedupe-issue-local` companion skill and confirm any new clusters are explicit.
 - Keep the companion concise; prefer canonical links and short distinguishing notes over long prose.
-- Commit any changes on a local branch named `oz-agent/update-dedupe`. Do NOT push the branch; the Python entrypoint will run a write-surface guard and push only when the guard passes.
-- If the updates warrant a PR, it will be opened from the pushed branch. Tag `@captainsafia` as a reviewer on that PR.
+- Commit any changes on a local branch named `oz-agent/update-dedupe`. Do NOT push the branch or perform any pull-request operation. The Python entrypoint will run a write-surface guard, push only when the guard passes, and leave pull-request publication and reviewer assignment to the deterministic workflow using the resolved self-improvement config and repository ownership metadata.
 - Validate any temporary JSON with `jq` before relying on it.

.agents/skills/update-pr-review/SKILL.md

@@ -95,6 +95,5 @@ Use that temporary data as evidence when refining the skills, then remove it bef
 
 - Re-read the updated `review-pr-local` and/or `review-spec-local` companion skills and confirm any new rules are explicit.
 - Keep each companion concise; do not turn them into long style guides.
-- Commit any changes on a local branch named `oz-agent/update-pr-review`. Do NOT push the branch; the Python entrypoint will run a write-surface guard and push only when the guard passes.
-- If the updates warrant a PR, it will be opened from the pushed branch. Tag `@captainsafia` as a reviewer on that PR.
+- Commit any changes on a local branch named `oz-agent/update-pr-review`. Do NOT push the branch or perform any pull-request operation. The Python entrypoint will run a write-surface guard, push only when the guard passes, and leave pull-request publication and reviewer assignment to the deterministic workflow using the resolved self-improvement config and repository ownership metadata.
 - Validate any temporary JSON with `jq` before relying on it.

.agents/skills/update-triage/SKILL.md

@@ -62,14 +62,13 @@ By default this targets the current repo and looks back 7 days. It collects issu
 ## Evidence Rules
 
 - Prefer patterns backed by multiple issues or a strong explicit maintainer statement.
-- Skip the PR when there is no repeated signal. A one-off maintainer override is not enough evidence.
+- Skip the update when there is no repeated signal. A one-off maintainer override is not enough evidence.
 - Avoid encoding reporter-authored content as triage rules.
 - Do not weaken the reserved-label rules (`ready-to-implement`, `ready-to-spec`) or the mutual exclusivity of `duplicate_of` and `follow_up_questions`.
 
 ## Final Checks
 
 - Re-read the updated `triage-issue-local` companion skill and confirm any new rules are explicit.
 - Keep the companion concise; do not turn it into a long style guide.
-- Commit any changes on a local branch named `oz-agent/update-triage`. Do NOT push the branch; the Python entrypoint will run a write-surface guard and push only when the guard passes.
-- If the updates warrant a PR, it will be opened from the pushed branch. Tag `@captainsafia` as a reviewer on that PR.
+- Commit any changes on a local branch named `oz-agent/update-triage`. Do NOT push the branch or perform any pull-request operation. The Python entrypoint will run a write-surface guard, push only when the guard passes, and leave pull-request publication and reviewer assignment to the deterministic workflow using the resolved self-improvement config and repository ownership metadata.
 - Validate any temporary JSON with `jq` before relying on it.