platform-types 1.10.707 → 1.10.709

package/dist/cjs/serviceOrder.js

@@ -180,6 +180,9 @@ exports.MAX_SERVICE_PICTURES = 20;
  *   someone else wrote the ticket between your read and your write, and nothing
  *   of yours was written. Refetch and let the operator retry against the new
  *   state — the body that lost was built on the old one.
+ *   `_EDIT_CHANGED` also answers a stale `expectedUpdatedAt`
+ *   ({@link ServiceOrderRevisionFence}) and carries the current row as
+ *   {@link ServiceOrderEditChangedRefusal}.
  * - `SERVICE_ORDER_ILLEGAL_TRANSITION` · 409 — the body is
  *   {@link ServiceOrderIllegalTransitionRefusal}; its `allowed[]` is the menu to
  *   offer instead.

package/dist/platform.d.ts

@@ -845,63 +845,22 @@ export interface TenantBillingRollupRow {
     historyError?: TenantBillingHistoryError;
 }
 /**
- * Why a plan's marketing copy disagrees with the entitlements actually backing
- * that tier. Advisory only — `PATCH /platform/billing/plans/{tier}` reports
- * these and still applies the write. It never blocks: plan copy is hand-tuned
- * between pricing decisions, so a mismatch is routinely the intended
- * intermediate state rather than an error. The entitlements themselves come
- * from the code matrix; that route refuses `features`.
- *
- * - `NUMERIC_MISMATCH` — a bullet advertises a number that differs from the
- *   numeric entitlement it maps to.
- * - `UNLIMITED_ADVERTISED_AS_CAPPED` — the entitlement is `-1` (unlimited) but
- *   the copy advertises a finite cap. Reported separately because the equality
- *   compare would otherwise render it as a nonsense mismatch against `-1`.
- * - `UNBACKED_CAPABILITY` — the copy names a capability the tier does not have
- *   `status: 'live'` and `enabled: true` for.
- * - `MISSING_FEATURE_ROW` — a bullet states a LIMIT for an entitlement the tier
- *   has no row for at all. Distinct from `UNBACKED_CAPABILITY` on purpose: that
- *   one means "the row exists but is not live/enabled in the matrix", whereas
- *   this one means the supplied catalogue lacks the backing row — a template
- *   PATCH cannot add it; the repair is the copy or a matrix change. Collapsing
- *   them (as the API briefly did) hides the more severe of the two behind the
- *   more common one.
+ * @deprecated Nothing produces one any more. The copy↔entitlement consistency
+ * check went with the free-text plan copy it checked, so the `warnings` array
+ * on the `POST` / `PATCH /platform/billing/plans` replies is ALWAYS empty. The
+ * type stays only so a consumer still naming it compiles; it will be removed
+ * together with that array.
  */
 export type CatalogWarningCode = 'NUMERIC_MISMATCH' | 'UNLIMITED_ADVERTISED_AS_CAPPED' | 'UNBACKED_CAPABILITY' | 'MISSING_FEATURE_ROW';
 /**
- * One disagreement between a plan's copy and its entitlements, or between the
- * declared feature catalog and a tier's stored rows.
- *
- * ⚠️ Absence of a warning is NOT a claim that the copy is correct. The matcher
- * pairs a bullet to a feature only on a single unambiguous keyword; a bullet
- * matching two keywords or none is skipped rather than guessed, so it
- * deliberately understates. Reading an empty array as "this tier's copy is
- * verified" inverts that design.
- *
- * ⚠️ That understatement had a second, larger hole: every check used to be
- * COPY-DRIVEN, so a declared feature key that no bullet happened to mention
- * could be missing its row on every tier and warn nothing. That is not
- * hypothetical — `storefront` was absent from all four production tiers, had no
- * marketing bullet, and therefore produced an empty `warnings` array while the
- * feature was locked for every tenant. `source: 'catalog'` exists so a check can
- * be driven by the declared key set instead of by what the copy happens to name.
+ * @deprecated See {@link CatalogWarningCode} — no writer emits one; the
+ * `warnings` array that carried it is always empty.
  */
 export interface CatalogWarning {
     code: CatalogWarningCode;
-    /**
-     * What produced it — one of the `bullets`, the `description`, or `'catalog'`
-     * for a check driven by the declared feature key set rather than by copy.
-     */
     source: 'bullets' | 'description' | 'catalog';
-    /**
-     * The offending bullet, or the description, verbatim. For `source:
-     * 'catalog'` there is no copy to quote — it carries the tier that was
-     * examined, which is the equivalent "what was checked" value.
-     */
     text: string;
-    /** The entitlement the copy was checked against. */
     featureKey: FeatureKey;
-    /** Human-readable, already safe to render as-is. */
     message: string;
 }
 /**

package/dist/serviceOrder.d.ts

@@ -1170,6 +1170,109 @@ declare global {
         message: string;
         allowed: readonly ServiceCustody[];
     }
+    /**
+     * Optional revision fence on `POST /services` `mode: 'edit'` and
+     * `mode: 'diagnosis'` — request-only, never persisted or returned.
+     *
+     * Send the `updatedAt` of the {@link ServiceOrder} the operator REVIEWED
+     * (from `GET /services/{id}`, a strong read; for a row carrying no
+     * `updatedAt`, its `createdAt`). The write is refused `409
+     * SERVICE_ORDER_EDIT_CHANGED` — body {@link ServiceOrderEditChangedRefusal},
+     * nothing written — when `updatedAt` has moved since, both at the handler's
+     * read and again at the commit. A refusal at the read uploads and deletes no
+     * photo; one at the commit deletes none, but bytes already uploaded for new
+     * photos stay in storage unreferenced.
+     *
+     * **What the fence sees.** `updatedAt` moves on every write of an
+     * operator-entered field, and only those: every `POST /services` mode that
+     * writes the row — `create`, `edit`, `diagnosis`, `hold`, `quote`, `parts`,
+     * `worklog`, `timer` (the stop that books the hours), `deposit`, `status`
+     * (including the delivery mint) and `disable`. It does NOT see system
+     * bookkeeping that leaves `updatedAt` alone, deliberately so a phone is not
+     * sent back to re-review for it: the appointment link
+     * (`appointmentId`/`appointmentDate`/`appointmentTime`, written by
+     * `/appointments`), the invoice stamp (`invoiceId`, written when a factura
+     * settles or is rejected), and notification bookkeeping (`notifiedAt`,
+     * appended by `status` and `renotify`). Those fields can differ from what the
+     * client reviewed while its fenced write still succeeds.
+     *
+     * **Chained writes.** A follow-up write in the same submission — a diagnosis
+     * then a photo edit — fences on the PREVIOUS write's success response,
+     * `data.updatedAt`, never on the revision first reviewed: the first write
+     * moved it, so echoing the original value refuses the second. Both success
+     * bodies carry it — `diagnosis` returns the committed row, `edit` the row
+     * with the `updatedAt` it committed.
+     *
+     * On `diagnosis` a TERMINAL ticket still answers its own codes first
+     * (`SERVICE_ORDER_TERMINAL` at the read, `SERVICE_ORDER_STATUS_CHANGED` when
+     * it closed mid-request), and the stored `diagnosedBy`/`diagnosedAt` stay
+     * server-stamped.
+     *
+     * Absent means today's behaviour: the handler's own read is the lock (`edit`)
+     * or no revision is asserted at all (`diagnosis`).
+     */
+    interface ServiceOrderRevisionFence {
+        expectedUpdatedAt?: number;
+    }
+    /**
+     * The `409 SERVICE_ORDER_EDIT_CHANGED` body of `POST /services`
+     * `mode: 'edit'` and `mode: 'diagnosis'`. `data.current` is the stored row as
+     * a strong read returns it now — without the read-time derivations
+     * (`customer`, `depositBalance`, `slaStatus`); refetch the point read for
+     * those.
+     *
+     * `data` is absent when the row could not be re-read (both modes), and on
+     * `edit` also when the row no longer exists — refetch the point read. A
+     * fenced `diagnosis` whose row is gone answers `SERVICE_ORDER_STATUS_CHANGED`
+     * instead, as it does unfenced.
+     */
+    interface ServiceOrderEditChangedRefusal {
+        error: 'SERVICE_ORDER_EDIT_CHANGED';
+        message: string;
+        data?: {
+            current: ServiceOrder;
+        };
+    }
+    /**
+     * The body of `POST /services` `mode: 'diagnosis'`: it REPLACES the stored
+     * `diagnosis` whole. `diagnosedBy`/`diagnosedAt` are not accepted — the api
+     * stamps the authorizer user and the server time. Success answers the
+     * committed {@link ServiceOrder} as `data`.
+     *
+     * Tied to the handler's schema by `AssertServiceOrderDiagnosisRequestMatchesSchema`
+     * (`stacks/lambdas/services/_diagnosis.ts`).
+     */
+    interface ServiceOrderDiagnosisRequest extends ServiceOrderRevisionFence {
+        mode: 'diagnosis';
+        serviceOrderId: string;
+        /** Internal technician notes, 1–4000 characters. Operator-only. */
+        notes: string;
+        /** What was actually wrong, as told to the customer — at most 4000 characters. */
+        faultFound?: string;
+    }
+    /**
+     * The photo-only body of `POST /services` `mode: 'edit'` — the edit a
+     * technician's phone sends. The mode accepts more fields; this names only the
+     * photo half, so a client typed on it cannot send anything else by accident.
+     *
+     * `pictures` ABSENT means "don't touch", `[]` means "clear"; it is the WHOLE
+     * array, at most {@link MAX_SERVICE_PICTURES} entries. An entry with `base64`
+     * is a new upload (its `url` is a placeholder the api replaces); one without
+     * is a pointer to a photo already on THIS ticket, and may not change its
+     * `stage`. `removePictures` names stored photos to delete after the commit.
+     * Success answers the updated {@link ServiceOrder} as `data`.
+     *
+     * Tied to the handler's schema by `AssertServiceOrderEditPicturesRequestMatchesSchema`
+     * (`stacks/lambdas/services/_edit.ts`).
+     */
+    interface ServiceOrderEditPicturesRequest extends ServiceOrderRevisionFence {
+        mode: 'edit';
+        serviceOrderId: string;
+        pictures?: ServiceOrderPicture[];
+        removePictures?: {
+            url: string;
+        }[];
+    }
 }
 /**
  * The legal moves on a service order. Exhaustive over `ServiceStatus` by
@@ -1294,6 +1397,9 @@ export declare const MAX_SERVICE_PICTURES = 20;
  *   someone else wrote the ticket between your read and your write, and nothing
  *   of yours was written. Refetch and let the operator retry against the new
  *   state — the body that lost was built on the old one.
+ *   `_EDIT_CHANGED` also answers a stale `expectedUpdatedAt`
+ *   ({@link ServiceOrderRevisionFence}) and carries the current row as
+ *   {@link ServiceOrderEditChangedRefusal}.
  * - `SERVICE_ORDER_ILLEGAL_TRANSITION` · 409 — the body is
  *   {@link ServiceOrderIllegalTransitionRefusal}; its `allowed[]` is the menu to
  *   offer instead.

package/dist/serviceOrder.js

@@ -177,6 +177,9 @@ export const MAX_SERVICE_PICTURES = 20;
  *   someone else wrote the ticket between your read and your write, and nothing
  *   of yours was written. Refetch and let the operator retry against the new
  *   state — the body that lost was built on the old one.
+ *   `_EDIT_CHANGED` also answers a stale `expectedUpdatedAt`
+ *   ({@link ServiceOrderRevisionFence}) and carries the current row as
+ *   {@link ServiceOrderEditChangedRefusal}.
  * - `SERVICE_ORDER_ILLEGAL_TRANSITION` · 409 — the body is
  *   {@link ServiceOrderIllegalTransitionRefusal}; its `allowed[]` is the menu to
  *   offer instead.

package/dist/subscription.d.ts

@@ -314,11 +314,11 @@ declare global {
          */
         features: PlanFeature[];
         /**
-         * Marketing-curated short bullets for the pricing card. Display order =
-         * array order; up to 6 entries, 80 chars each. Always present — empty array
-         * when unset (FE synthesizes a list from `features[]`). Lets marketing tweak
-         * copy via `PATCH /platform/billing/plans/{tier}` without a redeploy;
-         * replaces the FE-only `BULLET_LIST_BY_TIER`.
+         * @deprecated ALWAYS `[]`. The free-text card copy was retired: a plan
+         * card renders {@link Plan.highlights} instead, and no write accepts
+         * `bullets` any more (`POST`/`PATCH /platform/billing/plans` answer 400
+         * `VALIDATION_FAILED`). A value an old row still stores is ignored, never
+         * echoed. The key will be removed once the app's copy editor is gone.
          */
         bullets: string[];
         /**

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "platform-types",
-	"version": "1.10.707",
+	"version": "1.10.709",
 	"description": "Shared wire and entity contracts for the platform.",
 	"type": "module",
 	"main": "dist/index.js",