Skip to content

ci: add golden verification floor - #182

Merged
catomean merged 3 commits into
mainfrom
ci/golden-floor
Jul 17, 2026
Merged

ci: add golden verification floor#182
catomean merged 3 commits into
mainfrom
ci/golden-floor

Conversation

@catomean

Copy link
Copy Markdown
Collaborator

Rung 2 — the golden CI floor

Wires the shared verification floor (source: dotfiles/templates/ci/) so main is defended on every push and PR by lint → typecheck → test → build. All four steps are hermetic (no secrets/DB needed).

Why: the tests already existed but never ran on the shared branch — pure waste until now.

Test suites verified green locally before wiring.

🤖 Generated with Claude Code

Wires the shared CI floor (see dotfiles/templates/ci) so main is defended by
lint + typecheck + test + build on every push and PR. npm monorepo — gates frontend lint/typecheck/build (e2e deferred).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cursor

cursor Bot commented Jul 17, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

catomean and others added 2 commits July 17, 2026 10:16
…20+)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@catomean
catomean merged commit 6020f3e into main Jul 17, 2026
2 of 3 checks passed
@catomean
catomean deleted the ci/golden-floor branch July 17, 2026 08:32
github-actions Bot pushed a commit that referenced this pull request Aug 6, 2026
`gh pr list` returns newest-first, and the sweep merges the first eligible PR
then stops. So the newest green PR wins every sweep, and an older one can wait
indefinitely.

Observed in maonakamoto/fleetcrown on 2026-08-06: two consecutive sweeps merged
the two newest PRs while three older green ones sat untouched and were never
even evaluated. With several agent sessions opening PRs continuously that is
starvation — and it starves the worst candidate, since the longest-waiting PR
is the one whose checks were proven against the most now-stale base.

PR numbers increase monotonically with creation, so sorting ascending is FIFO.
The ordering was never a decision, just whatever gh happened to return.

Fixed upstream first (fleetcrown #182) and verified in production there: the
sweep immediately after it landed correctly took the oldest open PR rather than
the newest. This is that one-line change, applied to the fleet.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant