report a source that is quiet rather than broken, instead of a bare 0

The build log prints a count per source, and CI now declines to fail on a page that states its own emptiness — which leaves that source showing an unexplained 0, reading as exactly the fault the gate just decided it was not. The zero we are content with is the one that has to say why. It is also the only line that would ever prompt anyone to ask whether a lane quiet for a month is a game between patches or a wiki that reworded the sentence a statesNoEvents check is still matching. Nothing else in the pipeline can tell those apart. The test count in the layout block was stale at 898 and moves with these two commits, so it is corrected here. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
2026-09-06 18:03:46 +02:00
parent 1156c358a7
commit 8f3e851274
5 changed files with 60 additions and 4 deletions
@@ -81,12 +81,17 @@ jobs:
            // and it was not: it read eventCount, which is counted after
            // expiry, so a page whose events had all simply ended reddened the
            // build. Behaviour belongs where behaviour can be exercised.
-            const { brokenSources, staleSources } = await import("./src/shared/feed.ts");
+            const { brokenSources, quietSources, staleSources } = await import("./src/shared/feed.ts");
            for (const s of staleSources(feed.sources)) {
              console.log(
                `  note: ${s.sourceId} parsed ${s.parsedCount} events, all of them ended — stale page, not a fault`,
              );
            }
+            for (const s of quietSources(feed.sources)) {
+              console.log(
+                `  note: ${s.sourceId} parsed nothing and the page says so itself — between versions, not a fault`,
+              );
+            }
            const broken = brokenSources(feed.sources);
            if (broken.length > 0) {
              throw new Error(