archilyzer

commit 7207e26c33055c82c0a7edce5d7ace7af6da790e
parent 99cc00a5c14ea40e0917fcd804713228c9e07a97
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Mon, 21 Sep 2026 02:57:05 -0400

umtool e2e: the digest spec must write the mark it asserts

Skipping "a mark resolves through the plan to the clip playing there" turned
"the digest is one paste with the whole picture in it" red — it was asserting
on a note the other test had POSTed and left behind, so the moment that test
started skipping on a machine with no song bulk data, this one failed for a
reason that had nothing to do with what it tests.

A spec that needs a row should write the row. Storing a note needs no plan and
no candidate, which is exactly why this one keeps running while the other skips.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Diffstat:
M
umtool/e2e/browse.spec.ts
 | 
11
+++++++++++

1 file changed, 11 insertions(+), 0 deletions(-)
diff --git a/umtool/e2e/browse.spec.ts b/umtool/e2e/browse.spec.ts
@@ -441,6 +441,17 @@ test("marks and notes follow the file through a promote", async ({ request }) =>
 });
 
 test("the digest is one paste with the whole picture in it", async ({ request }) => {
+  // THE MARK IS POSTED HERE, not inherited from the test above.
+  //
+  // It used to rely on "a mark resolves through the plan to the clip playing
+  // there" having run first and left this note behind — and the moment that
+  // test started SKIPPING on a machine with no song bulk data, this one failed
+  // for a reason that had nothing to do with what it tests. A spec that needs a
+  // row should write the row; storing a note needs no plan and no candidate,
+  // which is exactly why this one does not skip.
+  await request.post("/api/browse/notes", {
+    data: { song: "alpha", target: "moment:wide.mp4@2.00", note: "the kit is late here" },
+  });
   const r = await request.get("/api/browse/context?song=alpha");
   expect(r.headers()["content-type"]).toContain("text/plain");
   const md = await r.text();