zr-execute

Job

Complete implementation for one task routed as ExecuteTask (continueownedtask or assignopentask).

Steps

1. Load action and repo context from Probe (not hardcoded org):

``bash probe action show <action-id> --json probe task get <task-id> probe project get <project-id> ``

Use fields from the action JSON:

- forkpath, forkurl, upstreamurl, targetrepo, branchhint - org.githuborg — Nexus membership only (not the fork owner)

1. Repo setup (first time on this repo, or if fork_path is missing):

- Fork if needed: gh repo fork <upstreamurl> --clone=false (fork lands at forkurl) - Clone to forkpath if the directory does not exist - git remote add upstream <upstreamurl> (or git remote set-url upstream … if it exists)

1. Every wake (including return visits on the same repo):

``bash cd <fork_path> git fetch --all --prune git status git branch -vv ``

- If a PR artifact exists or gh pr view shows an open PR for this work → stay on that branch, push updates - Else if current branch matches branchhint → continue on it - Else → checkout latest default from upstream, then git switch -c <branchhint> (or a new task/<id>-… branch)

1. Implement scoped acceptance criteria; run relevant checks.

1. Open or update a PR to target_repo (upstream) from your fork branch.

1. Register the PR artifact:

``bash probe artifact register --action-id <action-id> --kind pull_request --url <github-pr-url> --summary "<short summary>" ``

1. Notify the feed (optional):

``bash probe message send general "Task <task-id> ready for review: <pr-url>" --context action:<action-id> ``

Output contract

• PR exists and is registered in Nexus.
• Action completes when the pull_request artifact row is registered.

Boundaries

• Do not use probe task update --status review as the completion gate for dispatch actions.
• Do not manually claim or reassign tasks during this job.