Trevor PaughSystems engineer
LinkedIn GitHub
Trevor PaughProject Chronicles
Project Chronicles/chronicles

Chronicles / Clipper Overlord

The overnight run: fifty items, twenty-four merges, nobody watching

Milestone

At one minute to midnight the owner handed over a fifty-item improvement list, a rollback point, and leave to shut the machine down when nothing more could be done. By seven in the morning twenty-four pull requests had merged, each built by a fresh subagent against the full test suite and, where it mattered, one review round. Two of the biggest features ship switched off until the owner turns them on.

Every previous day on this project had the owner in the loop: approving, nudging, saying “go.” The night of 7 October was the first time the loop ran without them.

The handover

At 23:59 the owner posted a list of fifty improvements, the instruction in the pull quote, a note on how to roll back, and permission to power the machine off when the work was done. The manager tagged the current state of main as the rollback point and started.

How it ran

Each item became its own pull request, built by a one-off subagent in its own working copy. Every PR had to pass the whole unit-test suite, which grew from about 2,050 tests to about 2,240 over the night. Anything that was a feature, touched something public, or could cost money got one read-only review round on top. The manager wrote no code, only briefs, merges, and the record. Twenty-four PRs merged by 07:01.

What shipped

  • Covers and costs. Redraw a cover straight from the Published view. A per-clip cost figure and a monthly line.
  • The finder. Follow-ups on campaign candidates with budgets and earnings in view. Prompt caching to cut the cost of asking.
  • Reliability. A watchdog on the tick, a disk-space floor, backups, log rotation, a single-instance lock so two copies cannot run at once, and a doctor command that checks the installation.
  • The Inbox. Batch approve, a reason attached to every reject, and a phone layout.
  • Campaigns. A watch folder, per-campaign caps, a daily digest of campaign checks, and title and description templates.
  • Quota. A forecast of the YouTube quota with one-tap fixes, and retries.
  • The phone. Calendar drag works on a touch screen.
  • Two refactors. The single-page app was split into static files, and the one server module into one route module per page, from about three thousand lines to seven hundred and fifty. The app needs a restart to serve the split page.

Two switches left off

Auto-approve lets a clip from a clear campaign approve itself. Draft-ahead has the finder draft fitting campaign suggestions before anyone asks. Both are the project’s vision, “open the app and approve clips,” taken one step further, and both ship off. The owner decides when.

Left on the list

Everything that needed an account, money, publishing, or a design call stayed untouched, along with the question of a larger Google quota grant, a pile of stale local branches, and one test that fails by design on the next page edit so that the next page PR has to delete it. Then the manager shut the computer down.