@teamscala/service-boot 0.23.513 → 0.23.514

package/package.json

@@ -1187,5 +1187,5 @@
   "repository": "https://github.com/teamgbg/service-boot",
   "sideEffects": false,
   "type": "module",
-  "version": "0.23.513"
+  "version": "0.23.514"
 }

package/src/capability-slug.test.ts

@@ -1,31 +1,30 @@
-// @system codegen
-// @status generated
-// @edit change the suite in the owned-suites band, then re-run codegen. Hand-edits are overwritten.
-//
-// This suite's assertions are OWNED by the codegen band: the band module
-// carries them verbatim, this file is the emission, and hand edits here are
-// overwritten on the next run. The rationale each assertion carries moved
-// with it into the band.
-
 import { describe, expect, test } from "bun:test";
 import { toCapabilitySlug } from "./capability-slug.ts";
 
 describe("toCapabilitySlug", () => {
 	test("strips the language+tier suffix from a dev deployable", () => {
-		expect(toCapabilitySlug("scala-projects-bun-dev")).toBe("scala-projects");
-		expect(toCapabilitySlug("scala-ai-bun-dev")).toBe("scala-ai");
+		expect(toCapabilitySlug("scala-projects-ts-dev")).toBe("scala-projects");
+		expect(toCapabilitySlug("scala-ai-ts-dev")).toBe("scala-ai");
 		expect(toCapabilitySlug("scala-image-optimizer-rust-dev")).toBe(
 			"scala-image-optimizer",
 		);
 	});
 
 	test("strips the language+tier suffix from a prod deployable", () => {
-		expect(toCapabilitySlug("scala-projects-bun-prod")).toBe("scala-projects");
+		expect(toCapabilitySlug("scala-projects-ts-prod")).toBe("scala-projects");
 		expect(toCapabilitySlug("scala-messaging-service-rust-prod")).toBe(
 			"scala-messaging-service",
 		);
 	});
 
+	test("strips the retired bun spelling to the same capability", () => {
+		// The fleet was renamed under -bun before the operator ruling of
+		// 2026-09-08 fixed the language segment at ts; rows or supervised
+		// names still carrying it converge rather than fail the join.
+		expect(toCapabilitySlug("scala-projects-bun-dev")).toBe("scala-projects");
+		expect(toCapabilitySlug("scala-ai-bun-prod")).toBe("scala-ai");
+	});
+
 	test("returns an already-capability slug unchanged", () => {
 		// The prod lane is still bare while the tier migration is in flight, so
 		// the SAME function must be correct before and after the rename lands.
@@ -35,11 +34,11 @@ describe("toCapabilitySlug", () => {
 
 	test("both lanes of one application normalize to the same identity", () => {
 		// This is the property the page_route join depends on.
-		expect(toCapabilitySlug("scala-projects-bun-dev")).toBe(
+		expect(toCapabilitySlug("scala-projects-ts-dev")).toBe(
 			toCapabilitySlug("scala-projects"),
 		);
-		expect(toCapabilitySlug("scala-quiz-bun-dev")).toBe(
-			toCapabilitySlug("scala-quiz-bun-prod"),
+		expect(toCapabilitySlug("scala-quiz-ts-dev")).toBe(
+			toCapabilitySlug("scala-quiz-ts-prod"),
 		);
 	});
 

package/src/capability-slug.ts

@@ -6,10 +6,12 @@
  * Deployable slug -> capability slug.
  *
  * A DEPLOYABLE is named `<capability>-<language>-<tier>`
- * (`deployables-carry-language-and-tier`): `scala-projects-bun-dev` and
- * `scala-projects-bun-prod` are two DEPLOYMENTS of one APPLICATION. The
- * ecosystem generator emits that name into `SERVICE_SLUG` per lane, so one
- * service arrives here under a DIFFERENT identity in each lane.
+ * (`deployables-carry-language-and-tier`, as amended by the operator ruling of
+ * 2026-09-08: "so actually the apps are ts, not bun" — the language segment
+ * spells the LANGUAGE, so Bun-launched services are `ts`): `scala-projects-ts-dev`
+ * and `scala-projects-ts-prod` are two DEPLOYMENTS of one APPLICATION. The
+ * ecosystem generator derives that name per lane, so one service arrives here
+ * under a DIFFERENT identity in each lane.
  *
  * A `page_route` row describes the APPLICATION url space, which is the same
  * in both lanes, so it carries the CAPABILITY name and there is exactly one
@@ -26,13 +28,17 @@
  * The suffix grammar is a CLOSED SET defined by doctrine and emitted by the
  * generator, so this is a parse of a documented contract rather than a
  * pattern heuristic. A slug that does not end in one is already a capability
- * name and is returned unchanged -- which is why this is correct both BEFORE
- * the tier migration completes (prod is still bare `scala-projects`) and
- * after it (prod becomes `scala-projects-bun-prod`).
+ * name and is returned unchanged.
+ *
+ * `bun` REMAINS IN THE SET AS RETIRED SPELLING TOLERANCE, mirroring the
+ * generator side (`ecosystem/deployable_identity.rs capability_of` strips
+ * `-ts`, `-bun` and `-rust`): the fleet was renamed under `-bun` and rows or
+ * supervised names still carrying it must converge to the same capability
+ * rather than fail the join during the migration window.
  */
 
-/** Language segment of a deployable name. */
-const LANGUAGES = ["bun", "rust"] as const;
+/** Language segment of a deployable name. `bun` is the retired spelling. */
+const LANGUAGES = ["ts", "bun", "rust"] as const;
 
 /** Tier segment of a deployable name. */
 const TIERS = ["dev", "prod"] as const;
@@ -43,8 +49,9 @@ type Tier = (typeof TIERS)[number];
 /**
  * The capability half of a deployable slug.
  *
- * `scala-projects-bun-dev`  -> `scala-projects`
- * `scala-projects-bun-prod` -> `scala-projects`
+ * `scala-projects-ts-dev`   -> `scala-projects`
+ * `scala-projects-ts-prod`  -> `scala-projects`
+ * `scala-projects-bun-dev`  -> `scala-projects` (retired spelling)
  * `scala-projects`          -> `scala-projects` (already a capability name)
  */
 export function toCapabilitySlug(slug: string): string {