archilyzer

commit 5080cbdc27d24bb197aabb4a33e6d3755b0583e2
parent 5c3e2336b07bf14aa99a27f7cafc482287f2bd61
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Tue, 11 Aug 2026 02:10:54 -0400

Point main's new archived-bucket retry test at the Download stage

main added "Retry on an archived bucket job re-derives the bucket's current
members" while this branch was in flight, so the ?stage= migration never saw it.
It asserts the "Partial downloads (1)" heading on /channels/<slug>, which now
lives behind ?stage=download — the channel page shows one stage at a time.

Verified as a real regression rather than a flake: the test passes 2/2 on main
alone and failed 2/2 on the merge before this change.

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

Diffstat:
M
editor/e2e/jobs-retry.spec.ts
 | 
12
++++++++++--

1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/editor/e2e/jobs-retry.spec.ts b/editor/e2e/jobs-retry.spec.ts
@@ -6,7 +6,13 @@
 
 import { mkdir, rename, writeFile } from "node:fs/promises";
 import { test, expect } from "@playwright/test";
-import { generateReport, pathExists, resetData, resolvePath } from "./helpers";
+import {
+  channelStage,
+  generateReport,
+  pathExists,
+  resetData,
+  resolvePath,
+} from "./helpers";
 import { baseUrl } from "./baseUrl";
 
 async function invalidateCache() {
@@ -114,7 +120,9 @@ test("Retry on an archived bucket job re-derives the bucket's current members", 
     resolvePath(`${ROOT}/data/vidB/audio.m4a.part`),
   );
   await generateReport(page, CHANNEL);
-  await page.goto(`/channels/${CHANNEL}`); // regenerates the snapshot when absent
+  // The partial-downloads bucket lives on the Download stage, and the channel
+  // page shows one stage at a time.
+  await page.goto(channelStage(CHANNEL, "download"));
   await expect(
     page.getByRole("heading", { name: /Partial downloads \(1\)/ }),
   ).toBeVisible();