fast-pr-workflowlisted

# Fast PR Workflow Prepare a focused branch and pull request without disturbing unrelated work or crossing an unrequested merge boundary. ## Rules - **Protected-branch hard stop:** Never push directly to `main`, `master`, `develop`, or the repository's default or protected branch unless the current request explicitly names that branch and asks for a direct push. - General requests to ship, release, finish, approve, or synchronize work do not authorize a protected-branch push. Preserve or reconcile the work on a topic branch and open a PR. - Never merge into a protected branch (`main`, `master`, `develop`, or the repository default) unless the current user message explicitly names that branch as the merge target and asks to merge it. Otherwise, leave the PR open or draft. - Before an authorized merge, verify the head is current with its base using the repository's normal status checks or compare API. Resolve stale-base conflicts on the topic branch and rerun validation first. - Respect repository and host guardrails. Never bypass hooks, branch protection, required checks, or review requirements. - Do not merge branches, create merge commits, rebase branches, or push merge results unless the user explicitly asks for that exact operation. - Never commit secrets, local env files, dependency caches, build artifacts, or unrelated generated output. - Assume repo changes are intentional when they fit the current task. Do not over-audit every line. - Prefer one focused commit for t