@teamscala/service-boot 0.23.459 → 0.23.460

package/package.json

@@ -6,7 +6,7 @@
   },
   "name": "@teamscala/service-boot",
   "type": "module",
-  "version": "0.23.459",
+  "version": "0.23.460",
   "sideEffects": false,
   "imports": {
     "#service-boot/*": "./src/*",

package/src/two-phase-minimal-app.ts

@@ -281,13 +281,16 @@ export async function buildMinimalApp(
 	}
 
 	const { components, loaded, skipped } = discovered;
-	if (loaded.length === 0) {
-		throw new BootFatalError(
-			"ui-service.page-manifest",
-			serviceSlug,
-			"Zero Puck components loaded from src/page-manifest.ts. Fix service_install.block_packages or block_schema, regenerate the page manifest, then boot again.",
-		);
-	}
+	// REPORT THE DISCOVERY BEFORE JUDGING IT. This used to throw BootFatalError
+	// on `loaded.length === 0` ABOVE these two log lines, so the one boot that
+	// most needed the diagnosis was the only boot that printed none of it: the
+	// operator saw "Zero Puck components loaded" and nothing about WHICH rows
+	// were considered or WHY each was rejected. Measured 2026-09-03: 91 active
+	// block_schema rows, zero loaded, zero skip lines — and the absence of skip
+	// lines was itself unreadable, because "no candidate survived the install
+	// pre-filter" and "every candidate failed to import" are indistinguishable
+	// when neither prints. Hours went into re-deriving from outside the process
+	// what these lines already knew.
 	if (loaded.length > 0) {
 		log.info(
 			`[two-phase-boot:${serviceSlug}] Discovered ${loaded.length} block(s): ${loaded.join(", ")}`,
@@ -299,6 +302,23 @@ export async function buildMinimalApp(
 				`(missing componentPath/componentExport or import failed): ${skipped.join(", ")}`,
 		);
 	}
+	// SOFT-CRASH, NEVER HARD-CRASH (operator ruling 2026-09-03: "it's meant to
+	// soft crash with errors, so why the fuck is it hard crashing"). A service
+	// that refuses to start serves NOTHING — no page, no health endpoint, no
+	// error page — so a block-discovery problem presents to a client as a 502
+	// from a dead port, which is strictly less information than a served page
+	// with its blocks missing. The degraded state is loud (ERROR, both counts,
+	// every skip reason) and inspectable over HTTP, which is what makes it
+	// fixable; refusing the boot only hid the cause. `no-uncontrolled-repetition-
+	// or-cascade` is unaffected — nothing restarts, the process stays up.
+	if (loaded.length === 0) {
+		log.error(
+			`[two-phase-boot:${serviceSlug}] DEGRADED: zero Puck components loaded ` +
+				`from ${skipped.length} considered block_schema row(s). Pages will render ` +
+				`without blocks until this is fixed. Check service_install.block_packages, ` +
+				`the block_schema rows, and the skip reasons logged above.`,
+		);
+	}
 
 	// Run boot hooks BEFORE serving - some hooks may register routes and must
 	// run before Hono's matcher is compiled by the first request