From de504f82863fbc9172d10b499b883185bbebd263 Mon Sep 17 00:00:00 2001 From: Void Date: Tue, 10 Nov 2026 02:24:13 +0000 Subject: [PATCH] scene: say what the sweep's mid-build assertion means when it fails Co-Authored-By: Claude Sonnet 5.5 --- src/app/features/scene/index.test.ts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/app/features/scene/index.test.ts b/src/app/features/scene/index.test.ts index f54e456f..23c6b297 100644 --- a/src/app/features/scene/index.test.ts +++ b/src/app/features/scene/index.test.ts @@ -225,7 +225,9 @@ describe('startBackgroundScene follows the sky state', () => { (p, k) => p.then(async (acc) => ((await changeAfter(k)) ? [...acc, k] : acc)), Promise.resolve([]) ); - expect(landed.length).toBeGreaterThan(0); + // This can fail after a correct refactor that changes the await count in create/skyKey and moves every offset + // off the build. Then widen the range of offsets until some land again; do not weaken the assertion. + expect(landed.length, 'at least one offset must land mid-build').toBeGreaterThan(0); }); it('leaves the ray-march scene alone: it has one fixed dusk', async () => { -- 2.47.3