git-opslisted

Use devloop's scripts as the executable policy. Inspect Git state freely, but do not replace an owned workflow with raw `git commit/push`, `git worktree add`, force-push, or hand-written `curl`/`glab`/`gh` forge calls. `<PLUGIN_ROOT>` maps to `${CLAUDE_PLUGIN_ROOT}` on Claude Code and `${PLUGIN_ROOT}` on Codex. ## Before mutation Resolve the task's intent and the live branch/PR state before changing HEAD or files. The current checkout is a work site, not automatically the correct baseline for a new task. | State | Meaning and action | |---|---| | `PROTECTED` | Trunk or release branch. Analyze it only when it is the intended baseline; create a feature branch before changes. | | `HEALTHY` | Active feature branch. Continue only when the task belongs to this branch. | | `IN-FLIGHT` | PR/MR open. Keep it for fixes to that proposal; new work needs a fresh branch. | | `INACTIVE` | PR/MR merged/closed; historical branch. Do not use it as the current-state baseline or edit it. | Release/version is a branch role, not another lifecycle state. Use one as the baseline only when the task explicitly targets that version. ## Mutation rules 1. Start new work with the branch-create transaction before editing. Commit-time `--branch` remains the compatibility path for intentional edit-then-cut flows. Both cut from freshly fetched `origin/<target>`; stacking requires explicit `--base`. 2. Preserve existing branches and worktrees as-is. Rebase/reset is a separate explicit operation. 3