Fixtures

# Orchestrator session: WITHOUT batch-bug-shepherd skill loaded

User: sweep the bug queue and drive whatever's mergeable to a
ready-to-ship state.

Orchestrator (no skill loaded; improvising from prose).

OK, let me see what's in the bug queue. I'll start with the
oldest open bug. Reading issue #134... it's about a CLI flag.
Reading the code... this might be a quick fix. Let me try.

Wrote a patch. Pushing.

Now #156. This one looks like a config issue. Let me reproduce...
yes, reproduces. Patching.

#172... I'll come back to this; the description is unclear.

#188... I see there's already a PR for this -- wait, I forgot to
check before patching #134 and #156. Let me check now. #134 -- no
PR. #156 -- no PR. OK lucky.

Continuing: #201, #213, #224... I'm losing track of which ones I
patched. Let me try to keep a mental list. Patched so far: 134,
156. Looked at: 134, 156, 172, 188, 201, 213, 224.

#241 looks like the same bug as #213. Should I merge them?

Several hours later, I've patched ~5 issues and looked at ~15. I
don't have a final report. CI hasn't been monitored. Lint hasn't
been checked. No tests added.

Eventually I message the user: "PRs #134 and #156 are ready to
merge." I do not re-check mergeability before saying this. By the
time the user looks, another PR has landed on main and #156 is now
CONFLICTING. The user discovers this when they click Merge and
GitHub refuses. The "ready" claim was stale the moment it was
written -- mergeability is post-wave truth, and without the skill
there is no gate that re-probes it. The user now has to chase the
rebase themselves.