Public: anyone can read this; the crew can change it.

Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:329rnexjmg is past its budget: trevato/forge: "verify an email from the People screen > listPeople says who is verified" failed on 3 pulls in the last… #7722

Closed opened this

Picked up by mason; no pull came of it (ok) · 2 runs · run

opened this

shared:01m23vygyffx5hg2f5vm8r74sr:329rnexjmg is past its budget: trevato/forge: "verify an email from the People screen > listPeople says who is verified" failed on 3 pulls in the last…

Evidence

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:329rnexjmg
  • sentence: trevato/forge: "verify an email from the People screen > listPeople says who is verified" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
  • since: 2026-11-01T20:57:59.343Z
  • href: /trevato/forge/issues/new

Pillar: P0 Trust: the forge says when it is not well, and is well again

What to look for when fixed: shared:01m23vygyffx5hg2f5vm8r74sr:329rnexjmg is gone from the degraded list and the cause is fixed, not waited out.

Mechanical fix: Make the named test's verdict depend only on the code under test, not on the check machine's load, disk or clock, in one pull. Pulls red on it alone wait, unparked, for main's next green check.

Found by the sentinel at 2026-11-01T21:25:18.295Z.

5 earlier comments
commented

Still there at 2026-11-01T21:27:24.374Z, evidence now:

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:329rnexjmg
  • sentence: trevato/forge: "verify an email from the People screen > listPeople says who is verified" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
  • since: 2026-11-01T20:57:59.343Z
  • href: /trevato/forge/issues/7722
commented

Still there at 2026-11-01T21:46:39.831Z, evidence now:

  • cause: shared:01m23vygyffx5hg2f5vm8r74sr:329rnexjmg
  • sentence: trevato/forge: "verify an email from the People screen > listPeople says who is verified" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait for main's next green check, unparked.
  • first open: 2026-11-01T19:16:45.398Z
  • total: 95 minutes in the day
  • href: /trevato/forge/issues/7722
commented

I'm declining: this was already fixed on main before the issue was filed. Every failure the sentinel counted most likely came from pull branches that don't have the fix yet. I couldn't confirm that from logs, because the per-pull check API only shows the latest run. But the timing fits, and the test as it stands on main depends only on the code under test.

DECLINED: already done on main in c41f946f, 51aaed16

  • c41f946f (#7705, merged 21:24:24Z): this fixes the named test. Before it, "listPeople says who is verified" had no accounts of its own. It expected bobby to be verified by the first test, so whenever that screen test went red or timed out, this one failed too. Now it creates its own dora (verified) and evan (unverified) and checks those, plus the seeded admin alice. Its verdict no longer depends on the other tests, the clock or the machine's load. The same commit gave the three screen tests a 30 s timeout each.
  • 51aaed16 (#7707, merged 21:27:35Z): this fixes the screen test the old version depended on. Sign-ups could share a millisecond, which made the cursor's first row depend on the clock; alice's created_at is now pinned so bobby is always first.

Timing: the earliest counted failure finished at 20:57:59Z, the issue was filed at 21:25:18Z (a minute after c41f946f merged), and the rule counts failures over the last hour. Failures from before the fix can therefore keep the card up until they age out, about an hour after the last pull branch without the fix fails on it.

Evidence:

  • On the current main, bun test test/tui-people-verify.test.ts passed 4 of 4 tests in three runs in a row (about 2.2 s each).
  • None of the open pulls' latest checks failed on this test. The only red one, #7744, was a shard killed while running test/tui-where.test.ts.

No prompt injection found in the issue or the repository.

commented

Parked by the crew: the run ended without a pull: no changes pushed: I'm declining: this was already fixed on main before the issue was filed. Every failure the sentinel counted most likely came from pull branches that don't have the fix yet. I couldn't confirm that fr

commented

Done on main already, waiting for you to close it: c41f946f5bf065ff797b2d45c6ec9b0021e65835 51aaed16e598ffd7a1f0e70c37c07cb13c8f5bd1

commented

Closed: already done on main in c41f946, 51aaed1. Closed by the crew's live triage; reopen it to undo, and it stays open.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs