@teamscala/service-boot 0.23.498 → 0.23.500

package/package.json

@@ -1130,5 +1130,5 @@
   "repository": "https://github.com/teamgbg/service-boot",
   "sideEffects": false,
   "type": "module",
-  "version": "0.23.498"
+  "version": "0.23.500"
 }

package/src/proposal-authorized-emails.ts

@@ -18,6 +18,15 @@
  *     co-branded proposal. The partner is still branding-first; this is the one
  *     access edge it carries.
  *
+ * The partner clause casts to ::uuid because the two sides disagree in the
+ * database: client_database.company_id is `uuid` while proposals.partner_id is
+ * `text`. Postgres resolves operators at PLAN time, so `uuid = text` raises
+ * "operator does not exist" for EVERY proposal — including ones with no partner
+ * — the catch below swallows it, and the fail-closed empty Set then denies
+ * access to everyone. Measured 2026-09-10: no proposal could be unlocked by any
+ * email. The cast is correct once partner_id becomes `uuid` too (a no-op then);
+ * the column type is the real fix and is tracked separately.
+ *
  * Uses $queryRaw (raw SQL) deliberately: the per-service Prisma client is scoped
  * to that service's own models, so the proposals service's client has no
  * `member`/`user` model methods — but $queryRaw runs against the shared DB
@@ -48,7 +57,7 @@ export async function resolveProposalAuthorizedEmails(
 			UNION
 			SELECT lower(cd.primary_email) AS email
 			  FROM client_database cd
-			 WHERE cd.company_id = (SELECT partner_id FROM proposals WHERE id = ${proposalId})
+			 WHERE cd.company_id = (SELECT partner_id FROM proposals WHERE id = ${proposalId})::uuid
 			   AND cd.primary_email IS NOT NULL
 		` as { email: string }[];
 		return new Set(

package/src/register-registry-page-route/single-page-data.ts

@@ -127,7 +127,18 @@ export function singlePageData(
 			pageMetaTitle,
 			templateTitle: (meta.title as string) || undefined,
 			websiteName: (website.name as string) || undefined,
-			organisationName: (brand.companyName as string) || undefined,
+			// FRIENDLY NAME FIRST, matching region-slots-page-data and
+			// public-shell-page-data. This was the only one of the four call
+			// sites reading companyName alone, and the tab title is where it
+			// showed: a white-labelled quiz served brand_name "launcha" with
+			// the Launcha favicon while Chrome's tab read "GMG APAC: …" — the
+			// TENANT's registered name on a client-facing page. companyName is
+			// the legal/registered name; companyFriendlyName is what the brand
+			// presents as, so it is what a public tab must show.
+			organisationName:
+				(brand.companyFriendlyName as string) ||
+				(brand.companyName as string) ||
+				undefined,
 			pageName: pageName ?? ((pageRoot?.title as string) || undefined),
 			entityTitle: entityTitle || undefined,
 		},