PR Readiness Checklist

• Confirm the branch is based on current main.
• Confirm the diff matches the stated scope.
• Confirm no secrets, logs, temp files, or unrelated refactors are included.
• Confirm make pre-commit passed for code, behavior, CI, runtime configuration, security-sensitive, migration, storage, auth, networking, or other high-risk changes.
• For documentation-only, agent-instruction-only, or local developer-tooling-only changes, confirm focused verification covered the changed surface and the PR body explains why the full gate was not run.
• Confirm extra verification commands are listed for risky changes.
• Confirm the PR title uses Conventional Commits and stays within 72 characters.
• Confirm the PR title does not use tool-specific prefixes such as [codex].
• Confirm the PR body is in English.
• Confirm the PR body keeps the exact headings from .github/pull_request_template.md.
• Confirm non-applicable sections are filled with N/A.
• Confirm the PR body does not include local absolute paths unless explicitly required.
• Confirm multiline GitHub CLI commands use --body-file.
• Confirm new hardcoded string literals were not introduced for values already represented by existing constants/enums (including protocol labels, error identifiers, headers, and metric names), or record a justified exception.