@teamscala/service-boot 0.23.319 → 0.23.320

package/src/two-phase-health-gate-client-only.test.ts

@@ -1,77 +0,0 @@
-/**
- * @system service-boot
- * @status handwritten
- * @edit edit directly
- *
- * A CLIENT-ONLY service (`render_mode=client`) must reach ready, even though it
- * never registers an SSR page handler.
- *
- * Separate file from `two-phase-health-gate.test.ts` on purpose: `fullAppReady`
- * is module state that only transitions false -> true and has no reset hook, so
- * the two ready-paths cannot both be exercised in one module instance. A reset
- * hook would exist only for tests.
- *
- * THE REGRESSION THIS LOCKS (measured 2026-08-07 on scala-agents-ui). Readiness
- * used to be flipped INSIDE `setPageHandler`, which was honest while every
- * service was SSR. `render_mode=client` made a service that completes phase 2
- * and never calls it, so `/health` answered `{"status":"starting"}` FOREVER
- * while the process was healthy and serving — boot completed in 5023ms, "Full
- * app built: 50 block(s)" logged, `GET /` correctly 302'd to sign-in, and three
- * untouched UI services reported ok beside it.
- *
- * That is precisely what `readiness-gated-boot` forbids ("binary: fully-ready or
- * cleanly-unavailable"): a permanently-un-ready health signal makes the
- * activator's wake gate and every health-gated router treat a working service as
- * down. Exercised through a real Hono request against the REAL exported handler
- * (`proxy-is-not-behaviour`) — a source grep would prove the call exists, never
- * that the endpoint answers 200.
- */
-
-import { beforeAll, describe, expect, test } from "bun:test";
-import { Hono } from "hono";
-import {
-	__resetPhase2StateForTest,
-	getPageHandlerState,
-	healthHandler,
-	markFullAppReady,
-} from "./two-phase-boot.ts";
-
-/** Mount the real handler exactly as buildMinimalApp does. */
-const app = new Hono().get("/health", healthHandler);
-
-describe("/health for a client-only service", () => {
-	// Bun shares one module instance across every test file in a run, so the SSR
-	// readiness test's setPageHandler leaks into this file when both run together.
-	// Without this reset the suite passes file-by-file and fails in CI.
-	beforeAll(() => {
-		__resetPhase2StateForTest();
-	});
-
-	test("before phase 2 completes it reports 503, not ready", async () => {
-		expect(getPageHandlerState().ready).toBe(false);
-
-		const res = await app.request("/health");
-
-		expect(res.status).toBe(503);
-		expect(await res.json()).toEqual({ status: "starting" });
-	});
-
-	test("reaches ready without an SSR page handler", async () => {
-		// The real client-only phase-2 path: buildFullApp finishes and marks the
-		// app ready WITHOUT setPageHandler, because there is no SSR handler.
-		markFullAppReady();
-
-		const state = getPageHandlerState();
-		expect(state.ready).toBe(true);
-		// The discriminator: ready is true while hasHandler stays false. Asserting
-		// both is what separates this from the SSR path — a fix that flipped ready
-		// by registering a dummy handler would pass `ready` and fail here.
-		expect(state.hasHandler).toBe(false);
-
-		const res = await app.request("/health");
-
-		expect(res.status).toBe(200);
-		expect(res.ok).toBe(true);
-		expect(await res.json()).toEqual({ status: "ok" });
-	});
-});