Public: anyone can read this; the crew can change it.
A failed production probe files one defect carrying the URL, status, bytes and time, once per day #13273
Check · Review · Land · Live done — Landed and live in production.
When the weekly production proof fails, it now opens one issue per run instead of one per probe. If it fails again while that issue is open, including a second run the same day, it adds a comment instead of a second issue. Main didn't already do this: it filed Defect of # : … for each failing probe.
shipped production is serving it deploy 59903fa
When the weekly production proof fails, it now opens one issue per run instead of one per probe. If it fails again while that issue is open, including a second run the same day, it adds a comment instead of a second issue. Main didn't already do this: it filed Defect of #<probe>: … for each failing probe.
- What the issue holds (
src/maintain/proven.ts): the title isDefect of the production proof: <n> lines fail. The body lists each failing line, each with its evidence block (URL, status, bytes, ms, time), and the stable keyProbe key: v1-proven/run. Repeat failures go on as a comment ("Still failing on <date>") listing that run's lines. A run where every probe passes leaves one "Passing again" note and does not close the issue; a person does. - Cannot reach: probes that got no HTTP answer at all become one line,
cannot reach <origin>: k of n probes got no answer. When that's the only failure the title is… cannot reach <origin>, so an unreachable forge files one line, not twelve. - Older per-probe defects: one still open (found by its old key or title) keeps taking its own probe's comments, so nothing already filed gets a duplicate.
- Deliberately not done: once the issue is closed, a new failure opens a new issue, even on the same day. Adding a comment to a closed issue would hide a red line nobody reads, which is what this issue is about.
Tests (test/maintain-v1-proven.test.ts): three new tests:
- A run with three failures, run twice the same day, makes one issue and one comment listing all three.
- An unreachable forge files a single
cannot reachdefect. - A run's defect gets one "Passing again" note.
Three existing tests changed because the behaviour changed on purpose, not because they were wrong:
- "two probes failing open two issues" now expects one issue listing both lines.
- The first-failure test expects the new title.
- The "passing" test now passes every probe; before, one other probe was still failing and kept the run red.
The test helpers that list and close defects also match by the body key now, so a defect a person renamed is still found.
docs/features/v1-proven.md describes the new behaviour. bun scripts/gate.ts --fix, bun x tsc --noEmit and the 97 test files named by scripts/fast.ts pass (1575 tests, 0 failing).
To try it: bun test test/maintain-v1-proven.test.ts.
🤖 Generated with Claude Code
Clean. A run files one defect listing each failing line with its evidence block. A repeat run, including one the same day, comments instead of filing. An unreachable forge folds into one cannot-reach line. Legacy per-probe defects keep getting comments. The removed exports defectTitle and probeKey have no other users. The how-to is in docs/features/v1-proven.md and the README is untouched. The change reads duty-run output only and adds no new door, input or dependency. The three new tests would fail without the change. I did not run the preview: the change is a maintenance duty with no page of its own.
When the weekly production proof fails, it now opens one issue per run instead of one per probe. If it fails again while that issue is open, including a second run the same day, it adds a comment instead of a second issue. Main didn't already do this: it filed
Defect of #<probe>: …for each failing probe.src/maintain/proven.ts): the title isDefect of the production proof: <n> lines fail. The body lists each failing line, each with its evidence block (URL, status, bytes, ms, time), and the stable keyProbe key: v1-proven/run. Repeat failures go on as a comment ("Still failing on <date>") listing that run's lines. A run where every probe passes leaves one "Passing again" note and does not close the issue; a person does.cannot reach <origin>: k of n probes got no answer. When that's the only failure the title is… cannot reach <origin>, so an unreachable forge files one line, not twelve.Tests (
test/maintain-v1-proven.test.ts): three new tests:cannot reachdefect.Three existing tests changed because the behaviour changed on purpose, not because they were wrong:
The test helpers that list and close defects also match by the body key now, so a defect a person renamed is still found.
docs/features/v1-proven.mddescribes the new behaviour.bun scripts/gate.ts --fix,bun x tsc --noEmitand the 97 test files named byscripts/fast.tspass (1575 tests, 0 failing).To try it:
bun test test/maintain-v1-proven.test.ts.🤖 Generated with Claude Code
Closes #13265