Sync public snapshot from freebuff-private

Source: CodebuffAI/freebuff-private@5959a34ba5c16dfc53718c30bc18ac5ee5d0cfcc

Author: github-actions[bot]

bun.lock

@@ -2220,6 +2220,25 @@ export function freebuffUpdateRequiredAvailabilityLabel(): string {
   return 'only on this version of Freebuff Desktop — update it to resume your purchased time without another charge'
 }
 
+/**
+ * What a client that understands `purchasesPaused` says: purchased Desktop
+ * sessions are paused, the model is fine, and nothing about the user's build
+ * or pick needs changing.
+ */
+export function freebuffPurchasesPausedModelMessage(id: string): string {
+  const model = SUPPORTED_FREEBUFF_MODELS.find((m) => m.id === id)
+  const name = model?.displayName ?? id
+  return `Purchased Desktop sessions are paused right now, so a new one for ${name} can't be started yet — the model itself is fine. Try again shortly.`
+}
+
+/** The same fact shaped to sit inside "<model> isn't available right now (…)",
+ *  which is the only sentence a binary that predates `purchasesPaused` can
+ *  build. Scopes the unavailability to purchased sessions, so the reader is
+ *  not told the model is down. */
+export function freebuffPurchasesPausedAvailabilityLabel(): string {
+  return 'purchased sessions are paused right now — the model itself is fine; try again shortly'
+}
+
 /** Suffix-tolerant like the other model predicates, so a dated provider
  *  snapshot of a paused model cannot slip past the pause. */
 export function isFreebuffPausedFreeModelId(

common/src/constants/freebuff-models.ts

@@ -889,6 +889,22 @@ export type FreebuffSessionAdmissionResponse = (
        * working onto whatever was not.
        */
       updateRequired?: boolean
+      /**
+       * The MODEL is fine; minting NEW purchased Desktop sessions is paused
+       * server-side (FREEBUFF_DESKTOP_PURCHASE_ADMISSION), so an up-to-date
+       * build that needs a fresh purchase is refused rather than charged for
+       * an hour it could not be issued. Not an update problem and not a
+       * model problem: the pick works again as soon as the pause lifts, on
+       * the build the user already has. Set only on the Desktop
+       * multi-session path.
+       *
+       * Older clients ignore it and still render `availableHours`, which is
+       * worded so the sentence they build around it does not blame the model.
+       * The refusal it replaces read "<model> isn't available right now
+       * (Purchased Desktop sessions are temporarily unavailable …)", which a
+       * reader takes as the model being down and switches away from.
+       */
+      purchasesPaused?: boolean
     }
   | {
       /** Account is banned. Returned from every endpoint so banned bots can't