@managemint-solutions/sdk 0.38.0 → 0.38.1

package/README.md

@@ -10,7 +10,7 @@ npm install @managemint-solutions/sdk @supabase/supabase-js
 ```
 
 `@supabase/supabase-js` (^2.103.0), `class-validator` (^0.15) and `class-transformer` (^0.5)
-are peer dependencies — the request DTOs (`AddStatusDto`, `UpdateStatusDto`, `StatusIdDto`,
+are peer dependencies - the request DTOs (`AddStatusDto`, `UpdateStatusDto`, `StatusIdDto`,
 `GetStatusesDto`, `AddAdditionalDetailsDto`, `UpdateAdditionalDetailsDto`,
 `AdditionalDetailsIdDto`, `GetAdditionalDetailsDto`, `AddNoteDto`, `NoteIdDto`,
 `GetNotesDto`, `SupportingFileIdDto`, `GetSupportingFilesDto`, `GetClientsDto`, `ClientIdDto`,
@@ -39,7 +39,7 @@ const supabase = createSupabaseClient({
 
 // Inputs and outputs are the shared types from @managemint-solutions/entities.
 const statuses: StatusEntity[] = await supabase.statuses.list(StatusEntityTypes.PROJECT);
-// `is_complete` marks the finished state and is optional — it defaults to false on create and
+// `is_complete` marks the finished state and is optional - it defaults to false on create and
 // is left unchanged on update when omitted. `is_fail` and `is_triage` are read back on every
 // status but are not settable through the SDK yet.
 const created = await supabase.statuses.create({
@@ -100,7 +100,7 @@ import { SupportingFilesEntityTypes } from '@managemint-solutions/entities/suppo
 // Supporting files hang off another entity, and cover Supabase Storage as well as the table.
 const files = await supabase.supportingFiles.list(SupportingFilesEntityTypes.PROJECT, projectId);
 await supabase.supportingFiles.upload(SupportingFilesEntityTypes.PROJECT, projectId, {
-  files: uploaded, // web `File`s — uploaded to the `supporting-files` bucket, then rowed up
+  files: uploaded, // web `File`s - uploaded to the `supporting-files` bucket, then rowed up
 });
 const { url, ttl } = await supabase.supportingFiles.getPresignedUrl(files[0].mms_id); // 5 min
 await supabase.supportingFiles.remove(files[0].mms_id); // deletes the row and the object
@@ -128,7 +128,7 @@ await supabase.clients.getById(client.mms_id);
 await supabase.clients.update(client.mms_id, { ...client, name: 'Acme Ltd' });
 await supabase.clients.archive(client.mms_id);   // archived + archived_at/by
 await supabase.clients.unarchive(client.mms_id); // archived = false + unarchived_at/by
-await supabase.clients.remove(client.mms_id);    // soft delete — deleted + deleted_at/by
+await supabase.clients.remove(client.mms_id);    // soft delete - deleted + deleted_at/by
 await supabase.clients.restore(client.mms_id);   // deleted = false + restored_at/by
 ```
 
@@ -145,7 +145,7 @@ const page = await supabase.projects.list({
   client_id: clientId, // a UUID, or the base64-JSON option value a select sends
 });
 // `search` matches name/specification; `created_*`, `start_date_*` and `end_date_*` bound the
-// date columns, and `status_id_in` filters by status. `status_id_not_in` is the exclusion form —
+// date columns, and `status_id_in` filters by status. `status_id_not_in` is the exclusion form -
 // it keeps rows with no status, which `status_id_in` cannot express. `completed` is carried but
 // not acted on here: the api resolves it to status ids against the statuses catalogue first.
 
@@ -182,7 +182,7 @@ const page = await supabase.tasks.list({
 });
 // `search` matches name/description, and `client_id`, `assigned_to_id`, the date ranges and
 // `status_id_in` narrow it further. `status_id_not_in` excludes statuses while keeping rows with
-// no status; `completed` is carried but not acted on here — the api resolves it to status ids
+// no status; `completed` is carried but not acted on here - the api resolves it to status ids
 // against the statuses catalogue first.
 
 const task = await supabase.tasks.create({
@@ -209,11 +209,11 @@ task carries its embedded `status`, `assigned_to`, `project` and `client`.
 
 The client decodes `{ mms_id, organization_id }` from the JWT itself and scopes every query
 by `organization_id`. `supabase.supabase` is the raw `@supabase/supabase-js` client
-(`TypedSupabaseClient`) — the escape hatch for queries not yet covered by a resource.
+(`TypedSupabaseClient`) - the escape hatch for queries not yet covered by a resource.
 
 ## Audit
 
-Every write a resource makes is logged to `audit_logs` by the SDK itself — there are no database
+Every write a resource makes is logged to `audit_logs` by the SDK itself - there are no database
 triggers and no audit code in any feature. A write records one row carrying the action
 (`INSERT` / `UPDATE` / `ARCHIVE` / `UNARCHIVE` / `DELETE` / `RESTORE`), the entity type and id, who
 did it, and a `changes` diff of the flat table row as real JSON (`{ field: { old, new } }`).
@@ -245,7 +245,7 @@ const supabase = createSupabaseClient({
 ```
 
 With the Nest decorator there is nowhere to pass config per request, so the handler is registered
-once at startup — after Sentry is initialised, before the app listens:
+once at startup - after Sentry is initialised, before the app listens:
 
 ```ts
 import { configureSupabaseUserClient } from '@managemint-solutions/sdk/nest';
@@ -254,8 +254,8 @@ configureSupabaseUserClient({ onAuditError: (error) => Sentry.captureException(e
 ```
 
 Service-role work with no caller (webhooks, the queue worker, provisioning) goes through the
-service client's organization scope, which supplies the audit actor — `mms_id: null` for system
-work — and hands out audited tables for anything the SDK has no resource for:
+service client's organization scope, which supplies the audit actor - `mms_id: null` for system
+work - and hands out audited tables for anything the SDK has no resource for:
 
 ```ts
 import { createSupabaseServiceClient } from '@managemint-solutions/sdk';
@@ -274,20 +274,20 @@ await users.transition(userId, AuditTrailAction.DELETE, { deleted: true }); // r
 const deleted = await users.remove(userId);                              // hard delete; returns the old row
 ```
 
-Cross-tenant lookups — the organization behind a Paystack code, a ledger row by id, every
-organization with a Paystack customer — hang off `service` itself, because a webhook or cron does
+Cross-tenant lookups - the organization behind a Paystack code, a ledger row by id, every
+organization with a Paystack customer - hang off `service` itself, because a webhook or cron does
 not know its tenant until it looks one up.
 
 `update` / `transition` / `remove` pre-read the flat row (by `mms_id`, and by `organization_id`
-unless `scopeByOrganization: false` — the `organizations` table is its own tenant), so a missing
+unless `scopeByOrganization: false` - the `organizations` table is its own tenant), so a missing
 row surfaces as the usual 406. The write itself still throws `SupabaseClientError` on failure;
 only the audit insert is swallowed.
 
-Only what goes through the SDK/API is logged — a raw PostgREST write or a dashboard edit is not.
+Only what goes through the SDK/API is logged - a raw PostgREST write or a dashboard edit is not.
 
 ## Auth
 
-`SupabaseClient` needs the caller's JWT, which the auth flows are there to produce — so sign-in,
+`SupabaseClient` needs the caller's JWT, which the auth flows are there to produce - so sign-in,
 refresh and the password-reset exchanges live on a separate `SupabaseAuthClient`, built from the
 publishable key alone.
 
@@ -296,7 +296,7 @@ import { createSupabaseAuthClient } from '@managemint-solutions/sdk';
 
 const auth = createSupabaseAuthClient({
   url: process.env.SUPABASE_URL!,
-  key: process.env.SUPABASE_PUBLISHABLE_KEY!, // no caller token — these callers are logged out
+  key: process.env.SUPABASE_PUBLISHABLE_KEY!, // no caller token - these callers are logged out
 });
 
 const { access_token, refresh_token } = await auth.signIn({ email, password });
@@ -314,7 +314,7 @@ await auth.resetPassword({ password, access_token, refresh_token });
 client carrying the fresh access token; a failed stamp never fails the login. `signOut` takes the
 caller's access token because this client holds no session of its own: GoTrue's logout endpoint
 authenticates with the token itself, and the `local` scope ends that device's session only. Build
-one of these per request — supabase-js keeps the session `signIn`, `verifyOtp` and `setSession`
+one of these per request - supabase-js keeps the session `signIn`, `verifyOtp` and `setSession`
 produce in the client's memory, so a shared instance would leak sessions between callers.
 `auth.supabase` is the raw `@supabase/supabase-js` client.
 
@@ -361,7 +361,7 @@ and reads rows only.
 ## Pricebooks
 
 The price catalog (`pricebooks`, `pricebook_modules`, `billing_modules`) is readable by `anon`
-by design — an unauthenticated signup prices against it — so `pricebooks` hangs off the same
+by design - an unauthenticated signup prices against it - so `pricebooks` hangs off the same
 bearer-less `SupabaseAuthClient` as the auth flows, takes no auth context and scopes by nothing.
 
 ```ts
@@ -381,7 +381,7 @@ row joined with its `billing_modules` catalog entry). Exactly one pricebook is a
 
 ## Configs
 
-`public.configs` holds global named JSON configs — one `value` object per row, with no
+`public.configs` holds global named JSON configs - one `value` object per row, with no
 organization on it. Every signed-in caller may read, and only the service role may write, so
 `configs` hangs off the caller's client and the service client alike and a write on the former
 fails at the database (Scott edits the rows in Supabase Studio for now). A feature-flag set is
@@ -405,9 +405,9 @@ await service.configs.remove('maintenance');   // hard delete, service role only
 The first slice of the HR module: `leave_types`, `leave_entitlements` and `leave_requests`, one
 org-scoped audited resource each on the caller's client. Every date is a calendar date
 (`YYYY-MM-DD`, the columns are `date`), and the DTOs refuse anything else; body fields are
-required keys, with `null` for an empty one. Balances are never stored — an entitlement's
+required keys, with `null` for an empty one. Balances are never stored - an entitlement's
 `days_used` / `days_pending` / `days_remaining` are computed on read from the approved and pending
-requests of that user and type whose start date falls in its period — and a request's `days` is
+requests of that user and type whose start date falls in its period - and a request's `days` is
 a snapshot taken when it was filed, so a holiday added later does not rewrite approved history.
 
 The calendar arithmetic is plain exported functions, shared with the api:
@@ -452,7 +452,7 @@ accepts `leave_requests` and `leave_entitlements` alongside the CRM entity types
 
 The public-holiday calendar, `public_holidays`, on the caller's client as `supabase.publicHolidays`.
 Global like configs: there is no organization on a row, every signed-in caller reads the same
-list, and only the service role may write — Scott maintains it in Supabase Studio, so the SDK is
+list, and only the service role may write - Scott maintains it in Supabase Studio, so the SDK is
 read-only here. Several holidays may share a date; only the ones with `religion` null count as a
 day off for everyone.
 
@@ -467,7 +467,7 @@ Every error the SDK throws is a `SupabaseClientError` carrying the HTTP `status`
 with and the client-facing body, `toResponse()` → `{ error, message }`. Postgrest/Postgres
 errors are mapped by code: `PGRST*` codes to their documented statuses, an RLS or grant denial
 (`42501`) to **403**, a unique or foreign-key violation (`23505`, `23503`) to **409**, a not-null,
-check or malformed-literal failure (`23502`, `23514`, `22P02`) to **400**, anything else 500 —
+check or malformed-literal failure (`23502`, `23514`, `22P02`) to **400**, anything else 500 -
 the message is always Postgrest's own. Storage errors carry the storage error's own HTTP status
 (500 when it has none); Supabase Auth errors likewise, as `Authentication Error`; a rejected or
 missing JWT is `401 Authentication Error`. Consumers return these as-is instead of mapping
@@ -505,7 +505,7 @@ once a day however busy it is. Every other call is one round trip. Values are JS
 by the client; `get<T>` / `getField<T>` are the caller's promise about what was written, not a
 check.
 
-The client takes its URL and token as config — the SDK reads no environment variables — and
+The client takes its URL and token as config - the SDK reads no environment variables - and
 retries once with a three-second timeout per request. It **throws** on a failed call: what a
 failure means is the caller's decision, and both callers today fail open (a miss on the portal,
 a Sentry report on the api). The key prefix and TTL for the profile hash live in
@@ -533,7 +533,7 @@ malformed token becomes an `UnauthorizedException`. The DTOs work with Nest's gl
 `ValidationPipe` as-is (`whitelist`, `forbidNonWhitelisted`, `transform`).
 
 `toHttpException(error)` converts a `SupabaseClientError` into an `HttpException` with the
-same status and body — call it from your global exception filter so services can let SDK
+same status and body - call it from your global exception filter so services can let SDK
 errors propagate without any try/catch.
 
 ## Development
@@ -541,7 +541,7 @@ errors propagate without any try/catch.
 ```bash
 npm install
 npm test        # jest + ts-jest; specs live in src/<resource>/tests/*.spec.ts
-npm run build   # tsc -p tsconfig.build.json (excludes specs), CommonJS output in dist/ — the type gate
+npm run build   # tsc -p tsconfig.build.json (excludes specs), CommonJS output in dist/ - the type gate
 ```
 
 The SDK carries no generated database types: the schema of record is the api's

package/dist/audit/dto.js

@@ -67,7 +67,7 @@ __decorate([
     (0, class_validator_1.IsOptional)(),
     (0, validators_1.IsNullable)()
     // Still v4: `audit_logs.created_by` is a `users.mms_id`, which is the GoTrue auth uid the
-    // signup trigger copies out of `auth.users.id` — the table's uuidv7 default never fires.
+    // signup trigger copies out of `auth.users.id` - the table's uuidv7 default never fires.
     ,
     (0, class_validator_1.IsUUID)('4', { message: 'Created by must be a valid UUID v4' }),
     __metadata("design:type", Object)

package/dist/audit/index.d.ts

@@ -6,17 +6,17 @@ import type { GetAuditTrailDto } from './dto';
 export * from './dto';
 /**
  * Who a write is attributed to. `AuthContext` is assignable to it; the api's admin-client
- * modules build one by hand (system jobs pass `mms_id: null` — `created_by` is nullable).
+ * modules build one by hand (system jobs pass `mms_id: null` - `created_by` is nullable).
  */
 export type AuditActor = {
     mms_id: string | null;
     organization_id: string;
 };
-/** A flat database row — always `select('*')`, never an entity shape with embedded joins. */
+/** A flat database row - always `select('*')`, never an entity shape with embedded joins. */
 export type AuditRow = Record<string, unknown>;
 /**
  * Drops the internal `id bigint` from a row on its way out of the SDK. Every table has one
- * alongside its public `mms_id uuid`, and only the database is meant to see it — a caller that
+ * alongside its public `mms_id uuid`, and only the database is meant to see it - a caller that
  * never learns the sequence cannot come to depend on it, or leak how many rows there are.
  */
 export declare const withoutInternalId: <T extends Record<string, unknown>>(row: T) => Omit<T, "id">;
@@ -42,12 +42,12 @@ export type AuditErrorHandler = (error: unknown, entries: AuditEntry[]) => void;
 export declare const AUDIT_EXCLUDED_COLUMNS: ReadonlySet<string>;
 /**
  * Columns whose *value* never reaches the trail. `audit_logs` is readable by any member with
- * `read_logs`, so a value copied into `changes` is a value published to the whole organization —
+ * `read_logs`, so a value copied into `changes` is a value published to the whole organization -
  * and these are either provider credentials and identifiers (the `paystack_*` customer and
  * subscription codes, card metadata, tokens, an idempotency key that would let a replay be
  * forged) or content the base table deliberately withholds (`authenticated` has no grant on
  * `notifications.rendered_content`, so the rendered email must not arrive by the back door).
- * The column still shows up in the trail — that it changed is the point — with both sides
+ * The column still shows up in the trail - that it changed is the point - with both sides
  * replaced by `'[redacted]'`.
  */
 export declare const AUDIT_REDACTED_COLUMNS: ReadonlySet<string>;
@@ -57,18 +57,18 @@ export declare const isRedactedColumn: (name: string) => boolean;
  * The fields that differ between two flat rows, as `{ field: { old, new } }`. Values stay real
  * JSON (booleans stay booleans, jsonb stays an object) and are compared by serialized value, so
  * arrays and objects are equal when their contents are. A redacted column is compared on its
- * real values and only then redacted, so it is reported when — and only when — it truly moved.
+ * real values and only then redacted, so it is reported when - and only when - it truly moved.
  */
 export declare const diffChanges: (before: AuditRow, after: AuditRow) => AuditChanges;
 /**
- * A whole row as a change set — `'new'` for an insert, `'old'` for a hard delete — so the trail
+ * A whole row as a change set - `'new'` for an insert, `'old'` for a hard delete - so the trail
  * stays self-contained once the row is gone. Columns that hold nothing are left out; a redacted
  * column that holds something is present, as `'[redacted]'`.
  */
 export declare const snapshotChanges: (row: AuditRow, side: "new" | "old") => AuditChanges;
 /**
  * The `audit_logs` table. Reads are the audit trail endpoint; writes go through `record`, which
- * every audited write calls for itself — no feature ever writes an audit line by hand.
+ * every audited write calls for itself - no feature ever writes an audit line by hand.
  */
 export declare class AuditResource {
     private readonly supabase;
@@ -76,7 +76,7 @@ export declare class AuditResource {
     private readonly onError?;
     constructor(supabase: SupabaseJsClient, actor: AuditActor, onError?: AuditErrorHandler | undefined);
     /**
-     * Writes the audit row(s) — one insert, however many entries. **Never throws**: a logging
+     * Writes the audit row(s) - one insert, however many entries. **Never throws**: a logging
      * problem must not fail the business write, so a failure goes to `onAuditError`
      * (default `console.error`) instead.
      */
@@ -97,7 +97,7 @@ type AuditedPayload = AuditRow | ((before: AuditRow) => AuditRow);
 /** The keyed update every audited write builds, before any caller-supplied guard. */
 declare const buildUpdate: (supabase: SupabaseJsClient, table: string, id: string, payload: AuditRow, organizationId: string | null) => import("@supabase/postgrest-js").PostgrestFilterBuilder<any, any, any, null, string, unknown, "PATCH", false>;
 /**
- * Narrows an audited update to the rows it may still touch — the compare-and-set half of a
+ * Narrows an audited update to the rows it may still touch - the compare-and-set half of a
  * guarded write, e.g. `(query) => query.eq('billing_status', expectedFrom)`.
  */
 export type AuditGuard = (builder: ReturnType<typeof buildUpdate>) => ReturnType<typeof buildUpdate>;
@@ -106,10 +106,10 @@ export type AuditedTable = {
     insertMany(payloads: AuditRow[]): Promise<AuditRow[]>;
     update(id: string, payload: AuditedPayload): Promise<AuditRow>;
     /**
-     * An update that only lands while `guard` still holds — the filter *is* the concurrency
+     * An update that only lands while `guard` still holds - the filter *is* the concurrency
      * control, not just a key. Resolves to `null` when the guard matched nothing (someone else
      * moved the row first): nothing was written, so nothing is audited. Use it wherever losing
-     * the race must be a no-op rather than an overwrite — billing status moves, the
+     * the race must be a no-op rather than an overwrite - billing status moves, the
      * send-exactly-once gates, first-occurrence-only delivery rollups.
      */
     updateWhere(id: string, guard: AuditGuard, payload: AuditedPayload): Promise<AuditRow | null>;

package/dist/audit/index.js

@@ -21,7 +21,7 @@ const transforms_1 = require("../transforms");
 __exportStar(require("./dto"), exports);
 /**
  * Drops the internal `id bigint` from a row on its way out of the SDK. Every table has one
- * alongside its public `mms_id uuid`, and only the database is meant to see it — a caller that
+ * alongside its public `mms_id uuid`, and only the database is meant to see it - a caller that
  * never learns the sequence cannot come to depend on it, or leak how many rows there are.
  */
 const withoutInternalId = (row) => {
@@ -56,12 +56,12 @@ exports.AUDIT_EXCLUDED_COLUMNS = new Set([
 ]);
 /**
  * Columns whose *value* never reaches the trail. `audit_logs` is readable by any member with
- * `read_logs`, so a value copied into `changes` is a value published to the whole organization —
+ * `read_logs`, so a value copied into `changes` is a value published to the whole organization -
  * and these are either provider credentials and identifiers (the `paystack_*` customer and
  * subscription codes, card metadata, tokens, an idempotency key that would let a replay be
  * forged) or content the base table deliberately withholds (`authenticated` has no grant on
  * `notifications.rendered_content`, so the rendered email must not arrive by the back door).
- * The column still shows up in the trail — that it changed is the point — with both sides
+ * The column still shows up in the trail - that it changed is the point - with both sides
  * replaced by `'[redacted]'`.
  */
 exports.AUDIT_REDACTED_COLUMNS = new Set([
@@ -87,7 +87,7 @@ const normalize = (value) => value ?? null;
  * The fields that differ between two flat rows, as `{ field: { old, new } }`. Values stay real
  * JSON (booleans stay booleans, jsonb stays an object) and are compared by serialized value, so
  * arrays and objects are equal when their contents are. A redacted column is compared on its
- * real values and only then redacted, so it is reported when — and only when — it truly moved.
+ * real values and only then redacted, so it is reported when - and only when - it truly moved.
  */
 const diffChanges = (before, after) => {
     const changes = {};
@@ -106,7 +106,7 @@ const diffChanges = (before, after) => {
 };
 exports.diffChanges = diffChanges;
 /**
- * A whole row as a change set — `'new'` for an insert, `'old'` for a hard delete — so the trail
+ * A whole row as a change set - `'new'` for an insert, `'old'` for a hard delete - so the trail
  * stays self-contained once the row is gone. Columns that hold nothing are left out; a redacted
  * column that holds something is present, as `'[redacted]'`.
  */
@@ -134,7 +134,7 @@ const AUDIT_TRAIL_SELECT = `
       `;
 /**
  * The `audit_logs` table. Reads are the audit trail endpoint; writes go through `record`, which
- * every audited write calls for itself — no feature ever writes an audit line by hand.
+ * every audited write calls for itself - no feature ever writes an audit line by hand.
  */
 class AuditResource {
     supabase;
@@ -146,7 +146,7 @@ class AuditResource {
         this.onError = onError;
     }
     /**
-     * Writes the audit row(s) — one insert, however many entries. **Never throws**: a logging
+     * Writes the audit row(s) - one insert, however many entries. **Never throws**: a logging
      * problem must not fail the business write, so a failure goes to `onAuditError`
      * (default `console.error`) instead.
      */
@@ -257,7 +257,7 @@ const auditedTable = (supabase, actor, audit, options) => {
             throw (0, errors_1.mapPostgrestError)(error);
         const after = data;
         await recordWrite(id, action, before, after);
-        // `before` stays whole — it is internal to the diff — but what the caller gets does not
+        // `before` stays whole - it is internal to the diff - but what the caller gets does not
         // carry the internal `id`.
         return (0, exports.withoutInternalId)(after);
     };
@@ -269,7 +269,7 @@ const auditedTable = (supabase, actor, audit, options) => {
             .maybeSingle();
         if (error)
             throw (0, errors_1.mapPostgrestError)(error);
-        // The guard lost the race — the row is untouched, so there is nothing to audit.
+        // The guard lost the race - the row is untouched, so there is nothing to audit.
         if (!data)
             return null;
         const after = data;

package/dist/auth-client/index.d.ts

@@ -27,13 +27,13 @@ export declare class SupabaseAuthClient {
      * other sessions alone.
      */
     signOut(accessToken: string): Promise<void>;
-    /** `redirectTo` is passed in — the SDK reads no environment variables. */
+    /** `redirectTo` is passed in - the SDK reads no environment variables. */
     sendPasswordResetEmail(input: SendPasswordResetEmailDto, redirectTo: string): Promise<void>;
     exchangeRecoveryToken(input: ExchangeTokenHashDto): Promise<ExchangeTokenResponse>;
     exchangeConfirmToken(input: ExchangeTokenHashDto): Promise<ExchangeTokenResponse>;
     resetPassword(input: ResetPasswordDto): Promise<void>;
     /**
-     * Stamps `users.last_logged_in` as the user who just signed in — the users UPDATE policy
+     * Stamps `users.last_logged_in` as the user who just signed in - the users UPDATE policy
      * allows `auth.uid() = mms_id`, so the write goes through a throwaway client carrying the
      * fresh access token rather than this session-less one. Parity with the api: the result is
      * ignored, a failed stamp must not fail the login.

package/dist/auth-client/index.js

@@ -74,7 +74,7 @@ class SupabaseAuthClient {
         if (error)
             throw (0, errors_1.mapAuthError)(error);
     }
-    /** `redirectTo` is passed in — the SDK reads no environment variables. */
+    /** `redirectTo` is passed in - the SDK reads no environment variables. */
     async sendPasswordResetEmail(input, redirectTo) {
         const { error } = await this.supabase.auth.resetPasswordForEmail(input.email, { redirectTo });
         if (error)
@@ -116,7 +116,7 @@ class SupabaseAuthClient {
             throw (0, errors_1.mapAuthError)(updateError);
     }
     /**
-     * Stamps `users.last_logged_in` as the user who just signed in — the users UPDATE policy
+     * Stamps `users.last_logged_in` as the user who just signed in - the users UPDATE policy
      * allows `auth.uid() = mms_id`, so the write goes through a throwaway client carrying the
      * fresh access token rather than this session-less one. Parity with the api: the result is
      * ignored, a failed stamp must not fail the login.

package/dist/auth.d.ts

@@ -1,7 +1,7 @@
 import { type SupabaseClient as SupabaseJsClient } from '@supabase/supabase-js';
 /**
- * A raw supabase-js client, built the one way the SDK ever needs one: server-side and stateless —
- * nothing is stored, refreshed or read out of a URL — carrying the caller's bearer token when
+ * A raw supabase-js client, built the one way the SDK ever needs one: server-side and stateless -
+ * nothing is stored, refreshed or read out of a URL - carrying the caller's bearer token when
  * there is one, so RLS sees them.
  */
 export declare const createRawClient: (url: string, key: string, accessToken?: string) => SupabaseJsClient;
@@ -42,7 +42,7 @@ export type VerifyAccessTokenConfig = {
 /**
  * Establishes who the caller is, from a token whose signature is actually checked.
  *
- * Identity comes from the verified JWT and tenancy comes from `public.users` — never from
+ * Identity comes from the verified JWT and tenancy comes from `public.users` - never from
  * `user_metadata`, which the end user can rewrite through GoTrue. The profile read runs under the
  * caller's own RLS (a user may read their own row), so the `organization_id` returned here is the
  * same one `current_user_organization_id()` gives every policy.

package/dist/auth.js

@@ -4,8 +4,8 @@ exports.verifyAccessToken = exports.createRawClient = void 0;
 const supabase_js_1 = require("@supabase/supabase-js");
 const errors_1 = require("./errors");
 /**
- * A raw supabase-js client, built the one way the SDK ever needs one: server-side and stateless —
- * nothing is stored, refreshed or read out of a URL — carrying the caller's bearer token when
+ * A raw supabase-js client, built the one way the SDK ever needs one: server-side and stateless -
+ * nothing is stored, refreshed or read out of a URL - carrying the caller's bearer token when
  * there is one, so RLS sees them.
  */
 const createRawClient = (url, key, accessToken) => (0, supabase_js_1.createClient)(url, key, {
@@ -21,7 +21,7 @@ const authError = (message) => new errors_1.SupabaseClientError({ status: 401, e
 /**
  * Establishes who the caller is, from a token whose signature is actually checked.
  *
- * Identity comes from the verified JWT and tenancy comes from `public.users` — never from
+ * Identity comes from the verified JWT and tenancy comes from `public.users` - never from
  * `user_metadata`, which the end user can rewrite through GoTrue. The profile read runs under the
  * caller's own RLS (a user may read their own row), so the `organization_id` returned here is the
  * same one `current_user_organization_id()` gives every policy.

package/dist/billing/dto.js

@@ -85,7 +85,7 @@ __decorate([
     __metadata("design:type", String)
 ], PaymentIdDto.prototype, "paymentId", void 0);
 // `status_in` and `type_in` arrive as CSV strings and are transformed to enum values, so
-// they are omitted from the implemented contract — the same exception GetInvoicesQueryDto makes.
+// they are omitted from the implemented contract - the same exception GetInvoicesQueryDto makes.
 class GetPaymentsQueryDto {
     page = 1;
     page_size = 25;

package/dist/billing/index.d.ts

@@ -8,7 +8,7 @@ export * from './dto';
 /**
  * The readable half of the ledger. `billing_transactions` and `billing_events` are org-scoped
  * for READ, and the catalog is readable by `anon`, so all of this runs perfectly well on the
- * caller's own client — and should, so that RLS is what scopes it rather than a filter the api
+ * caller's own client - and should, so that RLS is what scopes it rather than a filter the api
  * remembered to add.
  */
 export declare class BillingReadsResource {
@@ -24,15 +24,15 @@ export declare class BillingReadsResource {
      * status. RLS scopes the rows; the eq is belt-and-braces.
      */
     listPayments(query: GetPaymentsQueryDto): Promise<MmsList<PaymentSummary>>;
-    /** The full payment record, or null — RLS makes another tenant's id look missing. */
+    /** The full payment record, or null - RLS makes another tenant's id look missing. */
     paymentById(paymentId: string): Promise<PaymentEntity | null>;
     /** Whether a catalog module is still on sale. The catalog is public, not tenant-scoped. */
     isModuleActive(moduleId: string): Promise<boolean>;
 }
 /**
  * The ledger writes, on the service client only. Every write policy on `billing_transactions`
- * and `billing_events` is `false` for `authenticated` — the ledger is written by the billing
- * service and by webhooks, never by a caller — so these are deliberately not reachable from
+ * and `billing_events` is `false` for `authenticated` - the ledger is written by the billing
+ * service and by webhooks, never by a caller - so these are deliberately not reachable from
  * `SupabaseClient`.
  */
 export declare class BillingResource extends BillingReadsResource {

package/dist/billing/index.js

@@ -25,7 +25,7 @@ const BILLING_TRANSACTIONS_TABLE = {
     table: 'billing_transactions',
     entityType: enum_1.AuditTrailEntityType.BILLING_TRANSACTIONS,
 };
-/** The wire shape of a payment list row — never the internal bigint id, never the checkout secrets. */
+/** The wire shape of a payment list row - never the internal bigint id, never the checkout secrets. */
 const PAYMENT_SUMMARY_SELECT = 'mms_id, created_at, transaction_type, transaction_status, amount_minor, currency, paid_at, failure_reason';
 /**
  * PaymentEntity, column for column, plus the renewal's invoice through the unique
@@ -36,7 +36,7 @@ const PAYMENT_ENTITY_SELECT = `${PAYMENT_SUMMARY_SELECT}, updated_at, active_sea
 /**
  * The readable half of the ledger. `billing_transactions` and `billing_events` are org-scoped
  * for READ, and the catalog is readable by `anon`, so all of this runs perfectly well on the
- * caller's own client — and should, so that RLS is what scopes it rather than a filter the api
+ * caller's own client - and should, so that RLS is what scopes it rather than a filter the api
  * remembered to add.
  */
 class BillingReadsResource {
@@ -97,7 +97,7 @@ class BillingReadsResource {
             throw (0, errors_1.mapPostgrestError)(error);
         return (0, transforms_1.toMmsList)(data, page, pageSize, count);
     }
-    /** The full payment record, or null — RLS makes another tenant's id look missing. */
+    /** The full payment record, or null - RLS makes another tenant's id look missing. */
     async paymentById(paymentId) {
         const { data, error } = await this.supabase
             .from('billing_transactions')
@@ -130,8 +130,8 @@ class BillingReadsResource {
 exports.BillingReadsResource = BillingReadsResource;
 /**
  * The ledger writes, on the service client only. Every write policy on `billing_transactions`
- * and `billing_events` is `false` for `authenticated` — the ledger is written by the billing
- * service and by webhooks, never by a caller — so these are deliberately not reachable from
+ * and `billing_events` is `false` for `authenticated` - the ledger is written by the billing
+ * service and by webhooks, never by a caller - so these are deliberately not reachable from
  * `SupabaseClient`.
  */
 class BillingResource extends BillingReadsResource {

package/dist/billing/invoices/dto.js

@@ -24,7 +24,7 @@ __decorate([
     __metadata("design:type", String)
 ], InvoiceIdDto.prototype, "invoiceId", void 0);
 // `status_in` arrives as a CSV string and is transformed to enum values, so it is omitted
-// from the implemented contract — the same exception GetUsersQueryDto makes for active_in.
+// from the implemented contract - the same exception GetUsersQueryDto makes for active_in.
 class GetInvoicesQueryDto {
     page = 1;
     page_size = 25;

package/dist/billing/invoices/index.d.ts

@@ -6,7 +6,7 @@ import type { GetInvoicesQueryDto } from './dto';
 export * from './dto';
 /**
  * The readable half. `invoices` is SELECT-only for `authenticated` with an org-predicate
- * policy — the same posture as the ledger it mirrors — so reads run on the caller's own
+ * policy - the same posture as the ledger it mirrors - so reads run on the caller's own
  * client and RLS is what scopes them.
  */
 export declare class InvoicesReadsResource {
@@ -15,14 +15,14 @@ export declare class InvoicesReadsResource {
     constructor(supabase: TypedSupabaseClient, actor: AuditActor);
     /** The organization's invoices, newest first. RLS scopes the rows; the eq is belt-and-braces. */
     list(query: GetInvoicesQueryDto): Promise<MmsList<InvoiceSummary>>;
-    /** The full invoice document data, or null — RLS makes another tenant's id look missing. */
+    /** The full invoice document data, or null - RLS makes another tenant's id look missing. */
     byId(invoiceId: string): Promise<InvoiceEntity | null>;
 }
 /**
- * The document writes, on the service client only — every write policy on `invoices` is
+ * The document writes, on the service client only - every write policy on `invoices` is
  * `false` for `authenticated`. Rows are written by the api's billing service beside a
- * renewal's ledger write — a renewal is inserted already paid, so an invoice never moves
- * status after it is issued — never by a caller.
+ * renewal's ledger write - a renewal is inserted already paid, so an invoice never moves
+ * status after it is issued - never by a caller.
  */
 export declare class InvoicesResource extends InvoicesReadsResource {
     private readonly invoices;
@@ -32,7 +32,7 @@ export declare class InvoicesResource extends InvoicesReadsResource {
     /**
      * The organization's highest invoice number, 0 when it has none. The api assigns
      * `max + 1` and lets the `(organization_id, invoice_number)` unique index arbitrate a
-     * concurrent insert — the retry lives there, not here.
+     * concurrent insert - the retry lives there, not here.
      */
     maxNumber(): Promise<number>;
 }

package/dist/billing/invoices/index.js

@@ -24,13 +24,13 @@ const INVOICES_TABLE = {
     table: 'invoices',
     entityType: enum_1.AuditTrailEntityType.INVOICE,
 };
-/** The wire shape of an invoice list row — never the internal bigint id. */
+/** The wire shape of an invoice list row - never the internal bigint id. */
 const INVOICE_SUMMARY_SELECT = 'mms_id, invoice_number, transaction_type, status, issued_at, paid_at, amount_minor, currency';
 /** InvoiceEntity, column for column: the summary plus the frozen document data. */
 const INVOICE_ENTITY_SELECT = `${INVOICE_SUMMARY_SELECT}, billing_transaction_id, paystack_reference, period_start, period_end, line_items, billed_to`;
 /**
  * The readable half. `invoices` is SELECT-only for `authenticated` with an org-predicate
- * policy — the same posture as the ledger it mirrors — so reads run on the caller's own
+ * policy - the same posture as the ledger it mirrors - so reads run on the caller's own
  * client and RLS is what scopes them.
  */
 class InvoicesReadsResource {
@@ -61,7 +61,7 @@ class InvoicesReadsResource {
             throw (0, errors_1.mapPostgrestError)(error);
         return (0, transforms_1.toMmsList)(data, page, pageSize, count);
     }
-    /** The full invoice document data, or null — RLS makes another tenant's id look missing. */
+    /** The full invoice document data, or null - RLS makes another tenant's id look missing. */
     async byId(invoiceId) {
         const { data, error } = await this.supabase
             .from('invoices')
@@ -76,10 +76,10 @@ class InvoicesReadsResource {
 }
 exports.InvoicesReadsResource = InvoicesReadsResource;
 /**
- * The document writes, on the service client only — every write policy on `invoices` is
+ * The document writes, on the service client only - every write policy on `invoices` is
  * `false` for `authenticated`. Rows are written by the api's billing service beside a
- * renewal's ledger write — a renewal is inserted already paid, so an invoice never moves
- * status after it is issued — never by a caller.
+ * renewal's ledger write - a renewal is inserted already paid, so an invoice never moves
+ * status after it is issued - never by a caller.
  */
 class InvoicesResource extends InvoicesReadsResource {
     invoices;
@@ -94,7 +94,7 @@ class InvoicesResource extends InvoicesReadsResource {
     /**
      * The organization's highest invoice number, 0 when it has none. The api assigns
      * `max + 1` and lets the `(organization_id, invoice_number)` unique index arbitrate a
-     * concurrent insert — the retry lives there, not here.
+     * concurrent insert - the retry lives there, not here.
      */
     async maxNumber() {
         const { data, error } = await this.supabase