polecat-pr-flow

A reference harness for rigs that gate polecat work on a GitHub PR rather than the canonical Refinery merge-queue flow.

It instructs polecats, after their final build/pre-verify passes, to push their branch and open (or confirm) a GitHub PR before running gt done.

What's in here

File	Purpose
polecat.md	Role directive for polecats in a PR-flow rig. Broad guardrail — applies to any formula a polecat runs.
mol-polecat-work.toml	Formula overlay that appends a PR-creation step to mol-polecat-work's submit-and-exit step. Surgical — only affects this formula.

Both layers are intentional: the directive sets the rig-level expectation ("open PRs, don't merge them yourself"), and the overlay wires the concrete commands into the workflow a polecat actually sees at gt prime time.

Install

# Role directive (rig-scoped)
mkdir -p ~/gt/<rig>/directives
cp polecat.md ~/gt/<rig>/directives/polecat.md

# Formula overlay (rig-scoped)
mkdir -p ~/gt/<rig>/formula-overlays
cp mol-polecat-work.toml ~/gt/<rig>/formula-overlays/mol-polecat-work.toml

Replace <rig> with your rig's name (e.g. gastown, longeye). For town-wide installation, drop the <rig>/ segment — but this is almost never what you want, since different rigs legitimately use different flows.

Verify it's active

# Validate overlay step IDs against the current formula
gt doctor
# Expect: overlay-health: N overlay(s) healthy

# Inspect the rendered formula with the overlay applied
gt formula overlay show mol-polecat-work --rig <rig>

# See the directive text that will be injected at prime time
gt directive show polecat --rig <rig>

# End-to-end: see what a polecat would see
gt prime --explain
# Expect: "Formula overlay: applying 1 override(s) for mol-polecat-work (rig=<rig>)"

What this does / does not do

Does:

• Tells the polecat to push and open a PR before gt done
• Sets a rig-level policy that a PR is the review artifact
• Surfaces gh pr create failure as an escalation to Witness, not a silent skip

Does not:

• Modify gt done behavior (no Go changes)
• Force PR creation via framework-level validation (agents can still misbehave)
• Merge the PR (that's a maintainer / merge-queue concern)
• Replace the directive or overlay if your rig also uses other customizations — merge this content with your existing files rather than overwriting them

When to fork this

If your rig needs additional PR-flow constraints (required reviewers, specific labels, CODEOWNERS enforcement, CI checks before gt done), copy this harness and adapt it. The point is a starting template, not a drop-in product.