Overnight PR batch with reviewable control
The operator can wake up to a compact batch of merged public slices, see what changed, and still trust that gates, validation, and evidence boundaries were not bypassed.
Case context
This case is not about an agent being busy. It is about keeping high-throughput autonomous work reviewable. The repository anchors the public evidence window to 2026-06-27 01:29 through 11:29 +08:00 instead of relying on private queues, screenshots, or operator notes.
Public Git history in that window shows 22 merged commits, 60 touched files, 6695 insertions, 223 deletions, and 10 commit messages with explicit PR numbers. The page only claims what those public facts support.
Repository evidence
High-throughput multi-lane work can remain PR-sized, reviewable, and merge-safe.
todo claim, review packet, self-merge boundary, focused smoke, public-boundary scan
2026-06-27 01:29 to 11:29 +08:00, a 10-hour Git evidence window.
22 merged commits across docs, runtime, status/quota, benchmark contracts, smokes, and release/runtime guardrails.
Work landed as PR-sized slices instead of one broad diff that maintainers would have to trust blindly.
The case document gives `git log --since ... --until ...` and `git log --numstat` commands.
LoopX behavior
- 1LoopX ties each lane to todo ownership, validation, review policy, and public evidence.
- 2Runtime, docs, and focused smokes move together when a control-plane contract changes.
- 3Self-merge remains limited to narrow validated changes; larger or unclear work preserves review gates.
- 4Public-boundary scans keep internal screenshots, local state, raw logs, and private planning out of the showcase.
What the user sees
The user wakes up to reviewable, traceable, explainable public slices rather than raw agent output.
The operator can inspect validation and remaining gates for each slice without relying on chat memory.
Repository sources
docs/showcases/cases/0627-overnight-pr-batch.mdcatalog workload signaldocs/showcases/showcase-catalog.jsonEvidence boundary. Public Git evidence only; no private documents, internal screenshots, raw chats, local active-state bodies, raw logs, credentials, or machine-specific paths.