archilyzer

commit cb76eb6cd85938fc65083d4f5148b71bed59dea7
parent 4e09aa50f8ff5e62df1db2037e1e873ae7a8e6ac
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Sat, 22 Aug 2026 19:56:15 -0400

channel-line: the em-dash fixture runs with no speaker operation on

That test seeds a pre-`eligible` snapshot on the DEFAULT settings, where
diarization is off — so the station's honest label is the derived generic one,
not "Speakers". It cannot claim a group whose operations are all disabled, which
is the same rule the lane-off test one screen down already asserts.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Diffstat:
M
editor/e2e/channel-line.spec.ts
 | 
8
+++++---

1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/editor/e2e/channel-line.spec.ts b/editor/e2e/channel-line.spec.ts
@@ -138,9 +138,11 @@ test("a pre-`eligible` snapshot renders an em dash, not 0%", async ({
   const line = page.getByLabel("channel line");
   await expect(line.getByLabel("Digest through")).toHaveText("—");
   await expect(line.getByLabel("Digest coverage", { exact: true })).toHaveText("—");
-  // "Speakers", not "Backfill": the station is named after the operations it
-  // holds, not after the queue key three of them happen to share.
-  await expect(line.getByLabel("Speakers through")).toHaveText("—");
+  // NOT "Backfill": the station is named after the operations it holds, not
+  // after the queue key they happen to share. This fixture runs on the default
+  // settings, where no speaker operation is enabled — so the honest label is
+  // the derived generic one, and it cannot claim "Speakers".
+  await expect(line.getByLabel("Derived data through")).toHaveText("—");
   // The negative assertion is the point: a 0% here is the bug.
   await expect(line.getByLabel("Digest coverage", { exact: true })).not.toContainText("0%");
 });