validate-issue

# validate-issue Validate every current-behavior claim against code. Treat cited roots, lines, fixes, and prior verdicts as claims that need independent proof. Return one decision that covers behavior, cause, evidence, proposal, scope, and fix. ## Input Accept a full issue URL, `#N`, `N`, or `owner/repo#N`. With no input, resolve the newest open issue in the current repo and state the selected number. ### 0. Establish the default-branch baseline Do not create a worktree for validation or issue edits. Resolve and refresh the current default branch: ```bash DEFAULT=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name) git fetch origin "$DEFAULT" git branch --show-current git rev-list --left-right --count "origin/$DEFAULT...HEAD" ``` Read working-tree files only at `0 0`, or when `git diff --name-only HEAD "origin/$DEFAULT"` excludes every inspected path. Otherwise use `git show "origin/$DEFAULT":<path>`. State the baseline in the verdict. ### 1. Fetch the issue and linked pull requests Always fetch the body and comments with `gh issue view <N> --comments`. For omitted input, first resolve `gh issue list --limit 1 --json number --jq '.[0].number'`. Then inspect the issue timeline for cross-referenced pull requests; comment output does not include them: ```bash gh api "repos/<owner>/<repo>/issues/<N>/timeline" --paginate \ --jq '.[] | select(.event == "cross-referenced" and .source.issue.pull_request) | .source.issue' ``` Verify merged fixes against cur...