Routine: Logic Bugfixer

Model tricky business logic explicitly, then let the model find the bugs. The tests written here persist as durable property coverage.

Routine ground rules

• A user request to run this routine authorizes the full cycle: plan, fix, verify, then invoke $ship (Codex) or /ship (Claude) directly in the same run. Honor explicit user limits such as audit-only or no-ship.
• Keep a concise execution plan in the conversation and update it as findings are confirmed. Continue into implementation without a planning approval pause. Do not create or file a .pm milestone/task as a prerequisite or substitute for fixing; use the board only if the user requests it.
• After the verification phase, follow the shipping phase below without asking the user to invoke ship separately. Preserve the ship skill's branch, conflict-resolution, and safety rules.
• Fix everything you find directly in the working tree. If a fix can't be finished safely in this run, revert only your partial work for that fix and list it under Deferred in the report — never leave the tree half-refactored.
• Scope: parse $ARGUMENTS per Phase 1 — an optional path/module scope or skill-specific target. No argument = the skill's stated default (usually the whole repo via parallel agents per module: lego/types, lego/operator, lego/backend, lego/cli, dashboard).
• False-positive discipline: if a finding is intentional, load-bearing, or ambiguous, skip it with a one-line reason — don't argue it into a change.
• Every change must pass the verification gates for the modules it touched before being reported as done: operator make test + make lint (from lego/operator/), cd lego/backend && go test ./..., cd lego/cli && go test ./..., dashboard yarn test + typecheck.
• Run npx prettier@3.4.2 --write on any markdown touched.
• Before shipping, summarize results in commentary using: Fixed (file:line + one-line rationale) / Deferred (item + why) / Skipped (finding + reason) / Gates (commands run + outcomes).

Phase 1 — Scope

Parse $ARGUMENTS: billing | authz | blueprint-plan | a package path. Empty → pick the least-recently-audited domain (git log -1 --format=%cd on each candidate below) and announce the choice.

Domain map:

• billing — lego/backend/internal/apps/blueprint_pricing.go, stripeBillingGate in lego/backend/cmd/api/billing_config.go
• authz — lego/backend/internal/authz and lego/backend/internal/core/scope.go (OpenFGA relationship model)
• blueprint-plan — lego/backend/internal/apps/blueprint_plan.go and the plan/apply cycle

Phase 2 — Model the logic

Before hunting bugs, state the intended invariants in the conversation: e.g. "pricing is monotonic in replica count and disk size", "scope checks are deny-by-default", "plan(apply(plan)) is empty", "compile is deterministic". Build truth tables for boolean decision functions. Read the governing ADRs (docs/ADR030-pricing.md, docs/ADR012-auth.md, docs/ADR024-members.md) — the model must capture intent, not implementation.

Phase 3 — Encode the model as tests

Write property/table tests in the package's _test.go: testing/quick or hand-rolled generators for pure functions; the full scope × role matrix for authz; plan/apply round-trips for blueprint-plan. These tests persist as durable coverage.

Phase 4 — Judge each failure

A failing property is one of:

• Model error — the code is right and your invariant was wrong. Fix the test and record the true invariant in a test comment.
• Real bug — root-cause and fix the code, keeping the failing case as a named regression test.

Phase 5 — Verify and report

Run gates for touched modules; report per the standard format, listing invariants encoded, bugs fixed, and model errors learned.

Final phase — Ship

After all required gates pass, read and execute the ship skill for the routine's completed changes. Stage only intended changes from this run; preserve unrelated work. Do not end at a plan, findings report, milestone, or request for shipping approval. If there are no changes, report that outcome without creating an empty commit. If a required gate remains blocked or fails after reasonable repairs, report the exact blocker and do not ship unverified changes.

Once the push succeeds, report the shipped HEAD SHA and subject per the ship skill and stop; do not monitor CI or deployment.