NiceEval pull requests

Read the PR template as the content authority and the Repository Tools design for ownership.

Run pnpm pr:body --help for current syntax. The next managed lifecycle surface separates local status, local discard, and authorized remote close: none of those states implies either of the others. Keep the managed draft in the worktree's Git-private draft location. Do not invent a tracked draft path, pass --source, or import an authored Markdown body; do not edit the managed Markdown file directly.

For a new PR, use the current branch's default draft: run pnpm pr:body init --base main, then enter pnpm pr:body edit --help. Set the four Problem fields; record every product Use Case as Added, Changed, or Removed with edit use-case; add each real Before/After/User impact surface case; and add every changed canonical test selector with edit test. Test input is path#caseId: the renderer resolves its current testing owner and final Feature or leaf Use Case, rejects stale relations, emits one readable narrative per case, and expands each file's source once. Complete source is default; edit test set --source-mode link is explicit: before a PR exists, local render/check is an offline pending-publication preview without GitHub links; existing PR commands resolve --pr, and first create resolves the pending base repository through gh plus the current branch's GitHub upstream, then verifies the created PR identity. Do not enter Owner/Covers fields or edit the managed Markdown. The editor emits only populated template sections and directions. Run pnpm pr:body render for preview and pnpm pr:body check for validation. After commit and push, run pnpm pr:body create --title <title> --base main; create applies the body and verifies the remote HEAD and body before returning.

Before choosing the new-PR path, check whether the current branch already has an open PR. For an existing PR, prefer its numbered draft; when none exists, check --pr <number> and apply --pr <number> reuse the current branch draft. Use init --pr <number> only when neither draft exists or a separate numbered draft is intentional. Finish with check --pr <number>, apply --pr <number>, and check --pr <number> --remote. Pass --source only when the user selected another empty draft path; never import an authored Markdown body.

Before a remote mutation, verify the intended diff, explicit commit paths, branch, base, title language, and user authorization. Use the compiler's local check before commit and push; remote comparison is opt-in through check --remote for an existing PR.

The PR body contains only sections with real changes. Show concrete before and after package-command behavior for contributor tooling; do not invent a NiceEval product use case for repository maintenance.