atomic-issues-prs

# Atomic Issues and PRs Publish a change-set as atomic GitHub objects: one issue/PR per logical change, never bundled. The layer above `commit-push`. It opens the PRs (and optionally issues) that skill never touches. ## Phase 0 - Preflight & canonical-repo resolution Run `gh auth status`. If unauthenticated, stop and ask the user to run `gh auth login`. Resolve the canonical (upstream) slug **explicitly before any permission check**. `gh repo view`'s default inspects the *current* repo, which is the fork in a fork clone. - Read remotes: `git remote -v`. Pick the contribution target: `upstream` if present, else `origin`. - Detect a fork relationship: `gh repo view <slug> --json nameWithOwner,parent,defaultBranchRef`. A non-null `parent` means `<slug>` is itself a fork, so the canonical slug is `parent.nameWithOwner`. - **Ambiguity → ask.** Prompt the user for the target repo only when there is no clear single upstream (no `upstream` remote and ≥2 plausible non-origin candidates, or `gh`'s detected `parent` disagrees with the `upstream` remote) **or** `origin` has genuinely diverged from upstream (no common merge-base, or `origin` was re-created/renamed/renewed). Plain fork-behind, where `origin` is merely behind `upstream` with a shared merge-base, is not ambiguity and must never prompt. - Query permission on the canonical slug: `gh repo view <canonical-slug> --json viewerPermission`. `viewerPermission` ∈ {ADMIN, MAINTAIN, WRITE} ⇒ **direct mode**; otherwise...