@learnorama/mozaik-sdk 0.1.0-staging.11.1

package/README.md

@@ -0,0 +1,94 @@
+# @learnorama/mozaik-sdk
+
+Mozaik's typed API client, generated with Orval from the deployed OpenAPI schema.
+Native fetch functions and optional TanStack Query v5 hooks are published as ESM
+with TypeScript declarations. Import only the API areas your application uses.
+
+## Install
+
+```sh
+npm install @learnorama/mozaik-sdk@staging
+```
+
+For React, also install `@tanstack/react-query` v5.102.8 or later in v5. React 18.3
+and React 19 are supported. React dependencies are optional for plain API consumers.
+Modern browsers and Node.js 22 or later provide the fetch APIs used by this package.
+
+## Configure and call the API
+
+```ts
+import { createClient } from '@learnorama/mozaik-sdk';
+import { readMe } from '@learnorama/mozaik-sdk/api/auth';
+
+// Supply the token from your application's session manager.
+export function apiClient(getAccessToken: () => Promise<string | undefined>) {
+  return createClient({
+    baseUrl: 'https://api.stg.mozaik.co',
+    getAccessToken,
+  });
+}
+
+// const me = await readMe({ client: apiClient(session.getAccessToken) });
+```
+
+The token getter runs for every request, so refreshing a token does not require
+recreating the client. Clients can also supply default headers and a custom fetch
+implementation. Request options accept headers and an AbortSignal.
+
+There is no global token storage, automatic sign-in or automatic replay of failed
+writes. The application owns its PKCE flow and session refresh. Backend-owned
+Keycloak client secrets must never be supplied to this SDK.
+
+## React
+
+Wrap the application in TanStack Query's `QueryClientProvider`. Within it:
+
+```tsx
+import type { Client } from '@learnorama/mozaik-sdk';
+import { useReadMe } from '@learnorama/mozaik-sdk/react/auth';
+
+export function CurrentAccount({ client }: { client: Client }) {
+  const me = useReadMe({ request: { client }, query: { staleTime: 30_000 } });
+  if (me.isPending) return <p>Loading…</p>;
+  if (me.isError) return <p>Could not load your account.</p>;
+  return <p>{me.data.account.email}</p>;
+}
+```
+
+GET operations generate queries; write operations generate mutations. Query keys
+and query/mutation options are exported for prefetching and explicit invalidation.
+For example, `getReadMeQueryOptions` works with `queryClient.fetchQuery`.
+React entrypoints include `"use client"` for frameworks that use React Server Components.
+
+Create a separate client and QueryClient for each server-side request. Clear the
+query cache on logout, account change, or a change of acting-as/tenant context;
+generated query keys do not contain credentials or identify the current user.
+
+## Models and errors
+
+```ts
+import { ApiError } from '@learnorama/mozaik-sdk';
+import type { MeRead } from '@learnorama/mozaik-sdk/models';
+```
+
+Successful requests return the response data directly. HTTP failures reject with
+`ApiError`, exposing `status`, `data` and response `headers`. Network and cancellation
+errors retain the native fetch error. Empty 204 responses return `undefined`.
+
+Modules include `auth`, `profiles`, `account`, `biblio-catalogue`, `cvs-documents`,
+`tutoring-requests`, `admin-tenants`, and other OpenAPI tags, under both `/api/<tag>`
+and `/react/<tag>`. Orchestrator health checks and encoding webhooks are excluded.
+
+## Version and traceability
+
+Backend and SDK release versions start together at 0.1.0. The `staging` npm tag
+tracks staging SDK publications. Pin an exact version when reproducible installs
+are required; the backend commit SHA is metadata, not the package version.
+
+```ts
+import { apiVersion, backendRevision, schemaSha256 } from '@learnorama/mozaik-sdk';
+```
+
+TypeScript types describe the API contract; they do not validate response bodies
+at runtime. The package contains the client and type declarations, not application
+credentials or backend implementation code.

package/dist/api/account.d.ts

@@ -0,0 +1,75 @@
+
+import { $r as AccountDetailRead, B as ServiceListRead, Zr as AccountUpdateWrite } from "../chunks/index.js";
+import { c as request } from "../chunks/client.js";
+//#region src/api/account/account.d.ts
+export declare const getDeleteAccountUrl: () => string;
+/**
+ * Close the account (E17). Anonymises; does not erase.
+ *
+ * The spec asked for the password to be re-submitted. We do not hold one, and
+ * assurance is the better guard anyway: a password check would have passed for a
+ * session that arrived through a partner handing over a static key in a URL,
+ * and ``RequireHighAssurance`` refuses exactly that. The legacy required no
+ * confirmation of any kind and accepted the call from a sub-profile (defect D8).
+ *
+ * **What survives, and why.** The row stays, with identity cleared and
+ * ``is_anonymous`` set. Consumption history, loans and billing records point at
+ * this user, and deleting the row would either cascade them away — destroying
+ * the library's statutory reporting — or orphan them. Clearing the identifying
+ * columns satisfies erasure of personal data while leaving the countable facts
+ * countable. The retained set is: which tenant, when they registered, and what
+ * they consumed, with no name, login, email, birth date or member number.
+ *
+ * Sub-profiles go with the holder: they are people on the same membership and
+ * cannot outlive it. Their rows are anonymised too, not deleted, for the same
+ * reason.
+ *
+ * **The broker is disabled first, and a failure aborts the whole thing.** The
+ * credential lives in Keycloak, so anonymising locally while leaving it enabled
+ * would let the same person sign in tomorrow and be provisioned a fresh account
+ * — erasure that erases nothing. Disabling before any local write means the
+ * failure mode is "nothing happened", which is recoverable, rather than "half
+ * happened", which is not.
+ *
+ * Still missing, and not safe to ship without: no audit record is written.
+ * @summary Delete Account
+ */
+export declare const deleteAccount: (options?: Parameters<typeof request>[1]) => Promise<void>;
+export declare const getReadAccountUrl: () => string;
+/**
+ * The authenticated account (E15).
+ *
+ * No query, no join: ``CurrentUserDep`` has already resolved the row behind the
+ * token. The endpoint the legacy should have had here has been returning ``500``
+ * on every request for as long as anyone has looked (defect D1).
+ * @summary Read Account
+ */
+export declare const readAccount: (options?: Parameters<typeof request>[1]) => Promise<AccountDetailRead>;
+export declare const getUpdateAccountUrl: () => string;
+/**
+ * Partially update the account (E16).
+ *
+ * ``exclude_unset`` is what separates PATCH from PUT here: a field the client
+ * omitted is left alone, which is not the same as a field it sent as null. The
+ * response is built from the persisted row rather than the submitted body.
+ * @summary Update Account
+ */
+export declare const updateAccount: (accountUpdateWrite: AccountUpdateWrite, options?: Parameters<typeof request>[1]) => Promise<AccountDetailRead>;
+export declare const getListServicesUrl: () => string;
+/**
+ * Third-party services this account's establishment offers (E27).
+ *
+ * Under ``/me`` rather than ``/biblio/me`` because it is not a catalogue: these
+ * are the establishment's own service tiles, and they belong to the tenant
+ * whichever catalogue that tenant reads from. It is also the one place the
+ * biblio spec describes something the *CVS* schema models, which is why it sat
+ * in the wrong module until the prefixes made the mismatch visible.
+ *
+ * Date-windowed. A service outside its window is absent rather than disabled:
+ * the client should not have to know the difference, and a visible dead link is
+ * worse than no link.
+ * @summary List Services
+ */
+export declare const listServices: (options?: Parameters<typeof request>[1]) => Promise<ServiceListRead>;
+//#endregion
+//# sourceMappingURL=account.d.ts.map

package/dist/api/account.js

@@ -0,0 +1,117 @@
+
+import { r as request } from "../chunks/client.js";
+//#region src/api/account/account.ts
+const getDeleteAccountUrl = () => {
+	return `/me`;
+};
+/**
+* Close the account (E17). Anonymises; does not erase.
+*
+* The spec asked for the password to be re-submitted. We do not hold one, and
+* assurance is the better guard anyway: a password check would have passed for a
+* session that arrived through a partner handing over a static key in a URL,
+* and ``RequireHighAssurance`` refuses exactly that. The legacy required no
+* confirmation of any kind and accepted the call from a sub-profile (defect D8).
+*
+* **What survives, and why.** The row stays, with identity cleared and
+* ``is_anonymous`` set. Consumption history, loans and billing records point at
+* this user, and deleting the row would either cascade them away — destroying
+* the library's statutory reporting — or orphan them. Clearing the identifying
+* columns satisfies erasure of personal data while leaving the countable facts
+* countable. The retained set is: which tenant, when they registered, and what
+* they consumed, with no name, login, email, birth date or member number.
+*
+* Sub-profiles go with the holder: they are people on the same membership and
+* cannot outlive it. Their rows are anonymised too, not deleted, for the same
+* reason.
+*
+* **The broker is disabled first, and a failure aborts the whole thing.** The
+* credential lives in Keycloak, so anonymising locally while leaving it enabled
+* would let the same person sign in tomorrow and be provisioned a fresh account
+* — erasure that erases nothing. Disabling before any local write means the
+* failure mode is "nothing happened", which is recoverable, rather than "half
+* happened", which is not.
+*
+* Still missing, and not safe to ship without: no audit record is written.
+* @summary Delete Account
+*/
+const deleteAccount = async (options) => {
+	return request(getDeleteAccountUrl(), {
+		...options,
+		method: "DELETE"
+	});
+};
+const getReadAccountUrl = () => {
+	return `/me`;
+};
+/**
+* The authenticated account (E15).
+*
+* No query, no join: ``CurrentUserDep`` has already resolved the row behind the
+* token. The endpoint the legacy should have had here has been returning ``500``
+* on every request for as long as anyone has looked (defect D1).
+* @summary Read Account
+*/
+const readAccount = async (options) => {
+	return request(getReadAccountUrl(), {
+		...options,
+		method: "GET"
+	});
+};
+const getUpdateAccountUrl = () => {
+	return `/me`;
+};
+/**
+* Partially update the account (E16).
+*
+* ``exclude_unset`` is what separates PATCH from PUT here: a field the client
+* omitted is left alone, which is not the same as a field it sent as null. The
+* response is built from the persisted row rather than the submitted body.
+* @summary Update Account
+*/
+const updateAccount = async (accountUpdateWrite, options) => {
+	const getHeaders = (h) => {
+		if (!h) return {};
+		if (h instanceof Headers) return Object.fromEntries(h.entries());
+		if (Symbol.iterator in h) return Object.fromEntries(Array.from(h, (entry) => Array.from(entry)));
+		const headers = {};
+		for (const [name, value] of Object.entries(h)) if (value !== void 0) headers[name] = value;
+		return headers;
+	};
+	return request(getUpdateAccountUrl(), {
+		...options,
+		method: "PATCH",
+		headers: {
+			"Content-Type": "application/json",
+			...getHeaders(options?.headers)
+		},
+		body: JSON.stringify(accountUpdateWrite)
+	});
+};
+const getListServicesUrl = () => {
+	return `/me/services`;
+};
+/**
+* Third-party services this account's establishment offers (E27).
+*
+* Under ``/me`` rather than ``/biblio/me`` because it is not a catalogue: these
+* are the establishment's own service tiles, and they belong to the tenant
+* whichever catalogue that tenant reads from. It is also the one place the
+* biblio spec describes something the *CVS* schema models, which is why it sat
+* in the wrong module until the prefixes made the mismatch visible.
+*
+* Date-windowed. A service outside its window is absent rather than disabled:
+* the client should not have to know the difference, and a visible dead link is
+* worse than no link.
+* @summary List Services
+*/
+const listServices = async (options) => {
+	return request(getListServicesUrl(), {
+		...options,
+		method: "GET"
+	});
+};
+//#endregion
+export { deleteAccount, getDeleteAccountUrl, getListServicesUrl, getReadAccountUrl, getUpdateAccountUrl, listServices, readAccount, updateAccount };
+
+//# sourceMappingURL=account.js.map

package/dist/api/account.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"account.js","names":[],"sources":["../../src/api/account/account.ts"],"sourcesContent":["/**\n * Generated by orval 🍺\n * Do not edit manually.\n * Mozaik backend\n * Four products behind one API — Biblio, Médiathèques, the partner catalogues (Nextory and YouScribe) and Prof Express. Authentication is Keycloak SSO only, once, for all of them: see the **auth** section below for the browser flow and the three failure modes.\n * OpenAPI spec version: 0.1.0\n */\nimport type {\n  AccountDetailRead,\n  AccountUpdateWrite,\n  ServiceListRead\n} from '../../models';\n\nimport { request } from '../../client';\n\nexport const getDeleteAccountUrl = () => {\n\n\n\n\n  return `/me`\n}\n\n/**\n * Close the account (E17). Anonymises; does not erase.\n *\n * The spec asked for the password to be re-submitted. We do not hold one, and\n * assurance is the better guard anyway: a password check would have passed for a\n * session that arrived through a partner handing over a static key in a URL,\n * and ``RequireHighAssurance`` refuses exactly that. The legacy required no\n * confirmation of any kind and accepted the call from a sub-profile (defect D8).\n *\n * **What survives, and why.** The row stays, with identity cleared and\n * ``is_anonymous`` set. Consumption history, loans and billing records point at\n * this user, and deleting the row would either cascade them away — destroying\n * the library's statutory reporting — or orphan them. Clearing the identifying\n * columns satisfies erasure of personal data while leaving the countable facts\n * countable. The retained set is: which tenant, when they registered, and what\n * they consumed, with no name, login, email, birth date or member number.\n *\n * Sub-profiles go with the holder: they are people on the same membership and\n * cannot outlive it. Their rows are anonymised too, not deleted, for the same\n * reason.\n *\n * **The broker is disabled first, and a failure aborts the whole thing.** The\n * credential lives in Keycloak, so anonymising locally while leaving it enabled\n * would let the same person sign in tomorrow and be provisioned a fresh account\n * — erasure that erases nothing. Disabling before any local write means the\n * failure mode is \"nothing happened\", which is recoverable, rather than \"half\n * happened\", which is not.\n *\n * Still missing, and not safe to ship without: no audit record is written.\n * @summary Delete Account\n */\nexport const deleteAccount = async ( options?: Parameters<typeof request>[1]): Promise<void> => {\n\n  return request<void>(getDeleteAccountUrl(),\n  {\n    ...options,\n    method: 'DELETE'\n\n\n  }\n);}\n\n\nexport const getReadAccountUrl = () => {\n\n\n\n\n  return `/me`\n}\n\n/**\n * The authenticated account (E15).\n *\n * No query, no join: ``CurrentUserDep`` has already resolved the row behind the\n * token. The endpoint the legacy should have had here has been returning ``500``\n * on every request for as long as anyone has looked (defect D1).\n * @summary Read Account\n */\nexport const readAccount = async ( options?: Parameters<typeof request>[1]): Promise<AccountDetailRead> => {\n\n  return request<AccountDetailRead>(getReadAccountUrl(),\n  {\n    ...options,\n    method: 'GET'\n\n\n  }\n);}\n\n\nexport const getUpdateAccountUrl = () => {\n\n\n\n\n  return `/me`\n}\n\n/**\n * Partially update the account (E16).\n *\n * ``exclude_unset`` is what separates PATCH from PUT here: a field the client\n * omitted is left alone, which is not the same as a field it sent as null. The\n * response is built from the persisted row rather than the submitted body.\n * @summary Update Account\n */\nexport const updateAccount = async (accountUpdateWrite: AccountUpdateWrite, options?: Parameters<typeof request>[1]): Promise<AccountDetailRead> => {\n\n    const getHeaders = (h?: NonNullable<RequestInit['headers']>): Record<string, string | readonly string[]> => {\n    if (!h) return {};\n    if (h instanceof Headers) return Object.fromEntries(h.entries());\n    if (Symbol.iterator in h) {\n      return Object.fromEntries(\n        Array.from(h as Iterable<Iterable<string>>, (entry) => Array.from(entry) as [string, string]),\n      );\n    }\n    const headers: Record<string, string | readonly string[]> = {};\n    for (const [name, value] of Object.entries<string | readonly string[] | undefined>(h)) {\n      if (value !== undefined) headers[name] = value;\n    }\n    return headers;\n  };\nreturn request<AccountDetailRead>(getUpdateAccountUrl(),\n  {\n    ...options,\n    method: 'PATCH',\n    headers: { 'Content-Type': 'application/json', ...getHeaders(options?.headers) },\n    body: JSON.stringify(accountUpdateWrite)\n  }\n);}\n\n\nexport const getListServicesUrl = () => {\n\n\n\n\n  return `/me/services`\n}\n\n/**\n * Third-party services this account's establishment offers (E27).\n *\n * Under ``/me`` rather than ``/biblio/me`` because it is not a catalogue: these\n * are the establishment's own service tiles, and they belong to the tenant\n * whichever catalogue that tenant reads from. It is also the one place the\n * biblio spec describes something the *CVS* schema models, which is why it sat\n * in the wrong module until the prefixes made the mismatch visible.\n *\n * Date-windowed. A service outside its window is absent rather than disabled:\n * the client should not have to know the difference, and a visible dead link is\n * worse than no link.\n * @summary List Services\n */\nexport const listServices = async ( options?: Parameters<typeof request>[1]): Promise<ServiceListRead> => {\n\n  return request<ServiceListRead>(getListServicesUrl(),\n  {\n    ...options,\n    method: 'GET'\n\n\n  }\n);}\n\n\n"],"mappings":";;;AAeA,MAAa,4BAA4B;CAKvC,OAAO;AACT;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAiCA,MAAa,gBAAgB,OAAQ,YAA2D;CAE9F,OAAO,QAAc,oBAAoB,GACzC;EACE,GAAG;EACH,QAAQ;CAGV,CACF;AAAE;AAGF,MAAa,0BAA0B;CAKrC,OAAO;AACT;;;;;;;;;AAUA,MAAa,cAAc,OAAQ,YAAwE;CAEzG,OAAO,QAA2B,kBAAkB,GACpD;EACE,GAAG;EACH,QAAQ;CAGV,CACF;AAAE;AAGF,MAAa,4BAA4B;CAKvC,OAAO;AACT;;;;;;;;;AAUA,MAAa,gBAAgB,OAAO,oBAAwC,YAAwE;CAEhJ,MAAM,cAAc,MAAwF;EAC5G,IAAI,CAAC,GAAG,OAAO,CAAC;EAChB,IAAI,aAAa,SAAS,OAAO,OAAO,YAAY,EAAE,QAAQ,CAAC;EAC/D,IAAI,OAAO,YAAY,GACrB,OAAO,OAAO,YACZ,MAAM,KAAK,IAAkC,UAAU,MAAM,KAAK,KAAK,CAAqB,CAC9F;EAEF,MAAM,UAAsD,CAAC;EAC7D,KAAK,MAAM,CAAC,MAAM,UAAU,OAAO,QAAgD,CAAC,GAClF,IAAI,UAAU,KAAA,GAAW,QAAQ,QAAQ;EAE3C,OAAO;CACT;CACF,OAAO,QAA2B,oBAAoB,GACpD;EACE,GAAG;EACH,QAAQ;EACR,SAAS;GAAE,gBAAgB;GAAoB,GAAG,WAAW,SAAS,OAAO;EAAE;EAC/E,MAAM,KAAK,UAAU,kBAAkB;CACzC,CACF;AAAE;AAGF,MAAa,2BAA2B;CAKtC,OAAO;AACT;;;;;;;;;;;;;;;AAgBA,MAAa,eAAe,OAAQ,YAAsE;CAExG,OAAO,QAAyB,mBAAmB,GACnD;EACE,GAAG;EACH,QAAQ;CAGV,CACF;AAAE"}

package/dist/api/admin-catalogue.d.ts

@@ -0,0 +1,68 @@
+
+import { C as ThemeWrite, E as ThemeRead, T as ThemeListRead, sn as ListThemesParams, w as ThemeOrderWrite } from "../chunks/index.js";
+import { c as request } from "../chunks/client.js";
+//#region src/api/admin-catalogue/admin-catalogue.d.ts
+export declare const getListThemesUrl: (params?: ListThemesParams) => string;
+/**
+ * Every theme, or one pillar's, in display order.
+ *
+ * Not paginated. There are 27 of them, and a client that has to page through
+ * a list it is about to reorder cannot reorder it.
+ * @summary List Themes
+ */
+export declare const listThemes: (params?: ListThemesParams, options?: Parameters<typeof request>[1]) => Promise<ThemeListRead>;
+export declare const getCreateThemeUrl: () => string;
+/**
+ * Add a theme.
+ *
+ * ``409`` on a duplicate ``(pillar, title)``: that pair is unique in the
+ * schema, and two themes with the same name in the same pillar are
+ * indistinguishable to everyone downstream.
+ *
+ * With no ``sortOrder`` it goes last, which is what the legacy's form does by
+ * defaulting the field to the current maximum plus one.
+ * @summary Create Theme
+ */
+export declare const createTheme: (themeWrite: ThemeWrite, options?: Parameters<typeof request>[1]) => Promise<ThemeRead>;
+export declare const getReorderThemesUrl: () => string;
+/**
+ * Set the display order for a set of themes, in one transaction.
+ *
+ * The legacy renumbers one theme per request, so dragging an item in a list of
+ * thirty was thirty requests — and closing the tab halfway left the order
+ * half-applied, with two themes claiming the same position and the listing
+ * silently choosing between them.
+ *
+ * Ids not named keep their relative order after the ones that are, so a client
+ * may send only what moved. An unknown id is ``404`` and nothing is written:
+ * a partially applied reorder is the failure this endpoint exists to prevent.
+ * @summary Reorder Themes
+ */
+export declare const reorderThemes: (themeOrderWrite: ThemeOrderWrite, options?: Parameters<typeof request>[1]) => Promise<void>;
+export declare const getDeleteThemeUrl: (themeId: number) => string;
+/**
+ * Remove a theme.
+ *
+ * ``409`` when works still carry it. The legacy deletes and leaves the
+ * references dangling, which is how a catalogue ends up with items filed under
+ * a theme that no longer exists and no screen that can find them.
+ *
+ * Idempotent otherwise: deleting something already gone is ``204``, because
+ * the caller wanted it gone and it is gone.
+ * @summary Delete Theme
+ */
+export declare const deleteTheme: (themeId: number, options?: Parameters<typeof request>[1]) => Promise<void>;
+export declare const getReadThemeUrl: (themeId: number) => string;
+/**
+ * One theme.
+ * @summary Read Theme
+ */
+export declare const readTheme: (themeId: number, options?: Parameters<typeof request>[1]) => Promise<ThemeRead>;
+export declare const getAmendThemeUrl: (themeId: number) => string;
+/**
+ * Amend a theme. Same uniqueness rule as creating one.
+ * @summary Amend Theme
+ */
+export declare const amendTheme: (themeId: number, themeWrite: ThemeWrite, options?: Parameters<typeof request>[1]) => Promise<ThemeRead>;
+//#endregion
+//# sourceMappingURL=admin-catalogue.d.ts.map

package/dist/api/admin-catalogue.js

@@ -0,0 +1,155 @@
+
+import { r as request } from "../chunks/client.js";
+//#region src/api/admin-catalogue/admin-catalogue.ts
+const getListThemesUrl = (params) => {
+	const normalizedParams = new URLSearchParams();
+	Object.entries(params || {}).forEach(([key, value]) => {
+		if (value !== void 0) normalizedParams.append(key, value === null ? "null" : String(value));
+	});
+	const stringifiedParams = normalizedParams.toString();
+	return stringifiedParams.length > 0 ? `/admin/themes?${stringifiedParams}` : `/admin/themes`;
+};
+/**
+* Every theme, or one pillar's, in display order.
+*
+* Not paginated. There are 27 of them, and a client that has to page through
+* a list it is about to reorder cannot reorder it.
+* @summary List Themes
+*/
+const listThemes = async (params, options) => {
+	return request(getListThemesUrl(params), {
+		...options,
+		method: "GET"
+	});
+};
+const getCreateThemeUrl = () => {
+	return `/admin/themes`;
+};
+/**
+* Add a theme.
+*
+* ``409`` on a duplicate ``(pillar, title)``: that pair is unique in the
+* schema, and two themes with the same name in the same pillar are
+* indistinguishable to everyone downstream.
+*
+* With no ``sortOrder`` it goes last, which is what the legacy's form does by
+* defaulting the field to the current maximum plus one.
+* @summary Create Theme
+*/
+const createTheme = async (themeWrite, options) => {
+	const getHeaders = (h) => {
+		if (!h) return {};
+		if (h instanceof Headers) return Object.fromEntries(h.entries());
+		if (Symbol.iterator in h) return Object.fromEntries(Array.from(h, (entry) => Array.from(entry)));
+		const headers = {};
+		for (const [name, value] of Object.entries(h)) if (value !== void 0) headers[name] = value;
+		return headers;
+	};
+	return request(getCreateThemeUrl(), {
+		...options,
+		method: "POST",
+		headers: {
+			"Content-Type": "application/json",
+			...getHeaders(options?.headers)
+		},
+		body: JSON.stringify(themeWrite)
+	});
+};
+const getReorderThemesUrl = () => {
+	return `/admin/themes/order`;
+};
+/**
+* Set the display order for a set of themes, in one transaction.
+*
+* The legacy renumbers one theme per request, so dragging an item in a list of
+* thirty was thirty requests — and closing the tab halfway left the order
+* half-applied, with two themes claiming the same position and the listing
+* silently choosing between them.
+*
+* Ids not named keep their relative order after the ones that are, so a client
+* may send only what moved. An unknown id is ``404`` and nothing is written:
+* a partially applied reorder is the failure this endpoint exists to prevent.
+* @summary Reorder Themes
+*/
+const reorderThemes = async (themeOrderWrite, options) => {
+	const getHeaders = (h) => {
+		if (!h) return {};
+		if (h instanceof Headers) return Object.fromEntries(h.entries());
+		if (Symbol.iterator in h) return Object.fromEntries(Array.from(h, (entry) => Array.from(entry)));
+		const headers = {};
+		for (const [name, value] of Object.entries(h)) if (value !== void 0) headers[name] = value;
+		return headers;
+	};
+	return request(getReorderThemesUrl(), {
+		...options,
+		method: "PUT",
+		headers: {
+			"Content-Type": "application/json",
+			...getHeaders(options?.headers)
+		},
+		body: JSON.stringify(themeOrderWrite)
+	});
+};
+const getDeleteThemeUrl = (themeId) => {
+	return `/admin/themes/${themeId}`;
+};
+/**
+* Remove a theme.
+*
+* ``409`` when works still carry it. The legacy deletes and leaves the
+* references dangling, which is how a catalogue ends up with items filed under
+* a theme that no longer exists and no screen that can find them.
+*
+* Idempotent otherwise: deleting something already gone is ``204``, because
+* the caller wanted it gone and it is gone.
+* @summary Delete Theme
+*/
+const deleteTheme = async (themeId, options) => {
+	return request(getDeleteThemeUrl(themeId), {
+		...options,
+		method: "DELETE"
+	});
+};
+const getReadThemeUrl = (themeId) => {
+	return `/admin/themes/${themeId}`;
+};
+/**
+* One theme.
+* @summary Read Theme
+*/
+const readTheme = async (themeId, options) => {
+	return request(getReadThemeUrl(themeId), {
+		...options,
+		method: "GET"
+	});
+};
+const getAmendThemeUrl = (themeId) => {
+	return `/admin/themes/${themeId}`;
+};
+/**
+* Amend a theme. Same uniqueness rule as creating one.
+* @summary Amend Theme
+*/
+const amendTheme = async (themeId, themeWrite, options) => {
+	const getHeaders = (h) => {
+		if (!h) return {};
+		if (h instanceof Headers) return Object.fromEntries(h.entries());
+		if (Symbol.iterator in h) return Object.fromEntries(Array.from(h, (entry) => Array.from(entry)));
+		const headers = {};
+		for (const [name, value] of Object.entries(h)) if (value !== void 0) headers[name] = value;
+		return headers;
+	};
+	return request(getAmendThemeUrl(themeId), {
+		...options,
+		method: "PATCH",
+		headers: {
+			"Content-Type": "application/json",
+			...getHeaders(options?.headers)
+		},
+		body: JSON.stringify(themeWrite)
+	});
+};
+//#endregion
+export { amendTheme, createTheme, deleteTheme, getAmendThemeUrl, getCreateThemeUrl, getDeleteThemeUrl, getListThemesUrl, getReadThemeUrl, getReorderThemesUrl, listThemes, readTheme, reorderThemes };
+
+//# sourceMappingURL=admin-catalogue.js.map

package/dist/api/admin-catalogue.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"admin-catalogue.js","names":[],"sources":["../../src/api/admin-catalogue/admin-catalogue.ts"],"sourcesContent":["/**\n * Generated by orval 🍺\n * Do not edit manually.\n * Mozaik backend\n * Four products behind one API — Biblio, Médiathèques, the partner catalogues (Nextory and YouScribe) and Prof Express. Authentication is Keycloak SSO only, once, for all of them: see the **auth** section below for the browser flow and the three failure modes.\n * OpenAPI spec version: 0.1.0\n */\nimport type {\n  ListThemesParams,\n  ThemeListRead,\n  ThemeOrderWrite,\n  ThemeRead,\n  ThemeWrite\n} from '../../models';\n\nimport { request } from '../../client';\n\nexport const getListThemesUrl = (params?: ListThemesParams,) => {\n  const normalizedParams = new URLSearchParams();\n\n  Object.entries(params || {}).forEach(([key, value]) => {\n\n    if (value !== undefined) {\n      normalizedParams.append(key, value === null ? 'null' : String(value))\n    }\n  });\n\n  const stringifiedParams = normalizedParams.toString();\n\n  return stringifiedParams.length > 0 ? `/admin/themes?${stringifiedParams}` : `/admin/themes`\n}\n\n/**\n * Every theme, or one pillar's, in display order.\n *\n * Not paginated. There are 27 of them, and a client that has to page through\n * a list it is about to reorder cannot reorder it.\n * @summary List Themes\n */\nexport const listThemes = async (params?: ListThemesParams, options?: Parameters<typeof request>[1]): Promise<ThemeListRead> => {\n\n  return request<ThemeListRead>(getListThemesUrl(params),\n  {\n    ...options,\n    method: 'GET'\n\n\n  }\n);}\n\n\nexport const getCreateThemeUrl = () => {\n\n\n\n\n  return `/admin/themes`\n}\n\n/**\n * Add a theme.\n *\n * ``409`` on a duplicate ``(pillar, title)``: that pair is unique in the\n * schema, and two themes with the same name in the same pillar are\n * indistinguishable to everyone downstream.\n *\n * With no ``sortOrder`` it goes last, which is what the legacy's form does by\n * defaulting the field to the current maximum plus one.\n * @summary Create Theme\n */\nexport const createTheme = async (themeWrite: ThemeWrite, options?: Parameters<typeof request>[1]): Promise<ThemeRead> => {\n\n    const getHeaders = (h?: NonNullable<RequestInit['headers']>): Record<string, string | readonly string[]> => {\n    if (!h) return {};\n    if (h instanceof Headers) return Object.fromEntries(h.entries());\n    if (Symbol.iterator in h) {\n      return Object.fromEntries(\n        Array.from(h as Iterable<Iterable<string>>, (entry) => Array.from(entry) as [string, string]),\n      );\n    }\n    const headers: Record<string, string | readonly string[]> = {};\n    for (const [name, value] of Object.entries<string | readonly string[] | undefined>(h)) {\n      if (value !== undefined) headers[name] = value;\n    }\n    return headers;\n  };\nreturn request<ThemeRead>(getCreateThemeUrl(),\n  {\n    ...options,\n    method: 'POST',\n    headers: { 'Content-Type': 'application/json', ...getHeaders(options?.headers) },\n    body: JSON.stringify(themeWrite)\n  }\n);}\n\n\nexport const getReorderThemesUrl = () => {\n\n\n\n\n  return `/admin/themes/order`\n}\n\n/**\n * Set the display order for a set of themes, in one transaction.\n *\n * The legacy renumbers one theme per request, so dragging an item in a list of\n * thirty was thirty requests — and closing the tab halfway left the order\n * half-applied, with two themes claiming the same position and the listing\n * silently choosing between them.\n *\n * Ids not named keep their relative order after the ones that are, so a client\n * may send only what moved. An unknown id is ``404`` and nothing is written:\n * a partially applied reorder is the failure this endpoint exists to prevent.\n * @summary Reorder Themes\n */\nexport const reorderThemes = async (themeOrderWrite: ThemeOrderWrite, options?: Parameters<typeof request>[1]): Promise<void> => {\n\n    const getHeaders = (h?: NonNullable<RequestInit['headers']>): Record<string, string | readonly string[]> => {\n    if (!h) return {};\n    if (h instanceof Headers) return Object.fromEntries(h.entries());\n    if (Symbol.iterator in h) {\n      return Object.fromEntries(\n        Array.from(h as Iterable<Iterable<string>>, (entry) => Array.from(entry) as [string, string]),\n      );\n    }\n    const headers: Record<string, string | readonly string[]> = {};\n    for (const [name, value] of Object.entries<string | readonly string[] | undefined>(h)) {\n      if (value !== undefined) headers[name] = value;\n    }\n    return headers;\n  };\nreturn request<void>(getReorderThemesUrl(),\n  {\n    ...options,\n    method: 'PUT',\n    headers: { 'Content-Type': 'application/json', ...getHeaders(options?.headers) },\n    body: JSON.stringify(themeOrderWrite)\n  }\n);}\n\n\nexport const getDeleteThemeUrl = (themeId: number,) => {\n\n\n\n\n  return `/admin/themes/${themeId}`\n}\n\n/**\n * Remove a theme.\n *\n * ``409`` when works still carry it. The legacy deletes and leaves the\n * references dangling, which is how a catalogue ends up with items filed under\n * a theme that no longer exists and no screen that can find them.\n *\n * Idempotent otherwise: deleting something already gone is ``204``, because\n * the caller wanted it gone and it is gone.\n * @summary Delete Theme\n */\nexport const deleteTheme = async (themeId: number, options?: Parameters<typeof request>[1]): Promise<void> => {\n\n  return request<void>(getDeleteThemeUrl(themeId),\n  {\n    ...options,\n    method: 'DELETE'\n\n\n  }\n);}\n\n\nexport const getReadThemeUrl = (themeId: number,) => {\n\n\n\n\n  return `/admin/themes/${themeId}`\n}\n\n/**\n * One theme.\n * @summary Read Theme\n */\nexport const readTheme = async (themeId: number, options?: Parameters<typeof request>[1]): Promise<ThemeRead> => {\n\n  return request<ThemeRead>(getReadThemeUrl(themeId),\n  {\n    ...options,\n    method: 'GET'\n\n\n  }\n);}\n\n\nexport const getAmendThemeUrl = (themeId: number,) => {\n\n\n\n\n  return `/admin/themes/${themeId}`\n}\n\n/**\n * Amend a theme. Same uniqueness rule as creating one.\n * @summary Amend Theme\n */\nexport const amendTheme = async (themeId: number,\n    themeWrite: ThemeWrite, options?: Parameters<typeof request>[1]): Promise<ThemeRead> => {\n\n    const getHeaders = (h?: NonNullable<RequestInit['headers']>): Record<string, string | readonly string[]> => {\n    if (!h) return {};\n    if (h instanceof Headers) return Object.fromEntries(h.entries());\n    if (Symbol.iterator in h) {\n      return Object.fromEntries(\n        Array.from(h as Iterable<Iterable<string>>, (entry) => Array.from(entry) as [string, string]),\n      );\n    }\n    const headers: Record<string, string | readonly string[]> = {};\n    for (const [name, value] of Object.entries<string | readonly string[] | undefined>(h)) {\n      if (value !== undefined) headers[name] = value;\n    }\n    return headers;\n  };\nreturn request<ThemeRead>(getAmendThemeUrl(themeId),\n  {\n    ...options,\n    method: 'PATCH',\n    headers: { 'Content-Type': 'application/json', ...getHeaders(options?.headers) },\n    body: JSON.stringify(themeWrite)\n  }\n);}\n\n\n"],"mappings":";;;AAiBA,MAAa,oBAAoB,WAA+B;CAC9D,MAAM,mBAAmB,IAAI,gBAAgB;CAE7C,OAAO,QAAQ,UAAU,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,KAAK,WAAW;EAErD,IAAI,UAAU,KAAA,GACZ,iBAAiB,OAAO,KAAK,UAAU,OAAO,SAAS,OAAO,KAAK,CAAC;CAExE,CAAC;CAED,MAAM,oBAAoB,iBAAiB,SAAS;CAEpD,OAAO,kBAAkB,SAAS,IAAI,iBAAiB,sBAAsB;AAC/E;;;;;;;;AASA,MAAa,aAAa,OAAO,QAA2B,YAAoE;CAE9H,OAAO,QAAuB,iBAAiB,MAAM,GACrD;EACE,GAAG;EACH,QAAQ;CAGV,CACF;AAAE;AAGF,MAAa,0BAA0B;CAKrC,OAAO;AACT;;;;;;;;;;;;AAaA,MAAa,cAAc,OAAO,YAAwB,YAAgE;CAEtH,MAAM,cAAc,MAAwF;EAC5G,IAAI,CAAC,GAAG,OAAO,CAAC;EAChB,IAAI,aAAa,SAAS,OAAO,OAAO,YAAY,EAAE,QAAQ,CAAC;EAC/D,IAAI,OAAO,YAAY,GACrB,OAAO,OAAO,YACZ,MAAM,KAAK,IAAkC,UAAU,MAAM,KAAK,KAAK,CAAqB,CAC9F;EAEF,MAAM,UAAsD,CAAC;EAC7D,KAAK,MAAM,CAAC,MAAM,UAAU,OAAO,QAAgD,CAAC,GAClF,IAAI,UAAU,KAAA,GAAW,QAAQ,QAAQ;EAE3C,OAAO;CACT;CACF,OAAO,QAAmB,kBAAkB,GAC1C;EACE,GAAG;EACH,QAAQ;EACR,SAAS;GAAE,gBAAgB;GAAoB,GAAG,WAAW,SAAS,OAAO;EAAE;EAC/E,MAAM,KAAK,UAAU,UAAU;CACjC,CACF;AAAE;AAGF,MAAa,4BAA4B;CAKvC,OAAO;AACT;;;;;;;;;;;;;;AAeA,MAAa,gBAAgB,OAAO,iBAAkC,YAA2D;CAE7H,MAAM,cAAc,MAAwF;EAC5G,IAAI,CAAC,GAAG,OAAO,CAAC;EAChB,IAAI,aAAa,SAAS,OAAO,OAAO,YAAY,EAAE,QAAQ,CAAC;EAC/D,IAAI,OAAO,YAAY,GACrB,OAAO,OAAO,YACZ,MAAM,KAAK,IAAkC,UAAU,MAAM,KAAK,KAAK,CAAqB,CAC9F;EAEF,MAAM,UAAsD,CAAC;EAC7D,KAAK,MAAM,CAAC,MAAM,UAAU,OAAO,QAAgD,CAAC,GAClF,IAAI,UAAU,KAAA,GAAW,QAAQ,QAAQ;EAE3C,OAAO;CACT;CACF,OAAO,QAAc,oBAAoB,GACvC;EACE,GAAG;EACH,QAAQ;EACR,SAAS;GAAE,gBAAgB;GAAoB,GAAG,WAAW,SAAS,OAAO;EAAE;EAC/E,MAAM,KAAK,UAAU,eAAe;CACtC,CACF;AAAE;AAGF,MAAa,qBAAqB,YAAqB;CAKrD,OAAO,iBAAiB;AAC1B;;;;;;;;;;;;AAaA,MAAa,cAAc,OAAO,SAAiB,YAA2D;CAE5G,OAAO,QAAc,kBAAkB,OAAO,GAC9C;EACE,GAAG;EACH,QAAQ;CAGV,CACF;AAAE;AAGF,MAAa,mBAAmB,YAAqB;CAKnD,OAAO,iBAAiB;AAC1B;;;;;AAMA,MAAa,YAAY,OAAO,SAAiB,YAAgE;CAE/G,OAAO,QAAmB,gBAAgB,OAAO,GACjD;EACE,GAAG;EACH,QAAQ;CAGV,CACF;AAAE;AAGF,MAAa,oBAAoB,YAAqB;CAKpD,OAAO,iBAAiB;AAC1B;;;;;AAMA,MAAa,aAAa,OAAO,SAC7B,YAAwB,YAAgE;CAExF,MAAM,cAAc,MAAwF;EAC5G,IAAI,CAAC,GAAG,OAAO,CAAC;EAChB,IAAI,aAAa,SAAS,OAAO,OAAO,YAAY,EAAE,QAAQ,CAAC;EAC/D,IAAI,OAAO,YAAY,GACrB,OAAO,OAAO,YACZ,MAAM,KAAK,IAAkC,UAAU,MAAM,KAAK,KAAK,CAAqB,CAC9F;EAEF,MAAM,UAAsD,CAAC;EAC7D,KAAK,MAAM,CAAC,MAAM,UAAU,OAAO,QAAgD,CAAC,GAClF,IAAI,UAAU,KAAA,GAAW,QAAQ,QAAQ;EAE3C,OAAO;CACT;CACF,OAAO,QAAmB,iBAAiB,OAAO,GAChD;EACE,GAAG;EACH,QAAQ;EACR,SAAS;GAAE,gBAAgB;GAAoB,GAAG,WAAW,SAAS,OAAO;EAAE;EAC/E,MAAM,KAAK,UAAU,UAAU;CACjC,CACF;AAAE"}

package/dist/api/admin-consumption.d.ts

@@ -0,0 +1,27 @@
+
+import { in as LiveLeaseListRead, zn as LeaseCloseWrite } from "../chunks/index.js";
+import { c as request } from "../chunks/client.js";
+//#region src/api/admin-consumption/admin-consumption.d.ts
+export declare const getListLiveLeasesUrl: () => string;
+/**
+ * What is open right now, within the caller's tenant scope.
+ *
+ * Read from the ledger rather than the Redis live set: this is a diagnostic and
+ * must show the truth even when the cache is cold, and it runs once when
+ * somebody opens a screen rather than on every read.
+ * @summary List Live Leases
+ */
+export declare const listLiveLeases: (options?: Parameters<typeof request>[1]) => Promise<LiveLeaseListRead>;
+export declare const getForceCloseLeaseUrl: (eventId: number) => string;
+/**
+ * Force-close somebody else's lease. The legacy's ``FermeSessionAdherent``.
+ *
+ * Audited, which the legacy's was not: a button that ends a stranger's reading
+ * session and leaves no trace is indistinguishable from abuse of the same
+ * button. Tenant-scoped like every staff action, so a lease outside the
+ * caller's scope is ``404`` rather than ``403``.
+ * @summary Force Close Lease
+ */
+export declare const forceCloseLease: (eventId: number, leaseCloseWrite: LeaseCloseWrite, options?: Parameters<typeof request>[1]) => Promise<void>;
+//#endregion
+//# sourceMappingURL=admin-consumption.d.ts.map

package/dist/api/admin-consumption.js

@@ -0,0 +1,55 @@
+
+import { r as request } from "../chunks/client.js";
+//#region src/api/admin-consumption/admin-consumption.ts
+const getListLiveLeasesUrl = () => {
+	return `/admin/consumption/live`;
+};
+/**
+* What is open right now, within the caller's tenant scope.
+*
+* Read from the ledger rather than the Redis live set: this is a diagnostic and
+* must show the truth even when the cache is cold, and it runs once when
+* somebody opens a screen rather than on every read.
+* @summary List Live Leases
+*/
+const listLiveLeases = async (options) => {
+	return request(getListLiveLeasesUrl(), {
+		...options,
+		method: "GET"
+	});
+};
+const getForceCloseLeaseUrl = (eventId) => {
+	return `/admin/consumption/${eventId}`;
+};
+/**
+* Force-close somebody else's lease. The legacy's ``FermeSessionAdherent``.
+*
+* Audited, which the legacy's was not: a button that ends a stranger's reading
+* session and leaves no trace is indistinguishable from abuse of the same
+* button. Tenant-scoped like every staff action, so a lease outside the
+* caller's scope is ``404`` rather than ``403``.
+* @summary Force Close Lease
+*/
+const forceCloseLease = async (eventId, leaseCloseWrite, options) => {
+	const getHeaders = (h) => {
+		if (!h) return {};
+		if (h instanceof Headers) return Object.fromEntries(h.entries());
+		if (Symbol.iterator in h) return Object.fromEntries(Array.from(h, (entry) => Array.from(entry)));
+		const headers = {};
+		for (const [name, value] of Object.entries(h)) if (value !== void 0) headers[name] = value;
+		return headers;
+	};
+	return request(getForceCloseLeaseUrl(eventId), {
+		...options,
+		method: "DELETE",
+		headers: {
+			"Content-Type": "application/json",
+			...getHeaders(options?.headers)
+		},
+		body: JSON.stringify(leaseCloseWrite)
+	});
+};
+//#endregion
+export { forceCloseLease, getForceCloseLeaseUrl, getListLiveLeasesUrl, listLiveLeases };
+
+//# sourceMappingURL=admin-consumption.js.map

package/dist/api/admin-consumption.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"admin-consumption.js","names":[],"sources":["../../src/api/admin-consumption/admin-consumption.ts"],"sourcesContent":["/**\n * Generated by orval 🍺\n * Do not edit manually.\n * Mozaik backend\n * Four products behind one API — Biblio, Médiathèques, the partner catalogues (Nextory and YouScribe) and Prof Express. Authentication is Keycloak SSO only, once, for all of them: see the **auth** section below for the browser flow and the three failure modes.\n * OpenAPI spec version: 0.1.0\n */\nimport type {\n  LeaseCloseWrite,\n  LiveLeaseListRead\n} from '../../models';\n\nimport { request } from '../../client';\n\nexport const getListLiveLeasesUrl = () => {\n\n\n\n\n  return `/admin/consumption/live`\n}\n\n/**\n * What is open right now, within the caller's tenant scope.\n *\n * Read from the ledger rather than the Redis live set: this is a diagnostic and\n * must show the truth even when the cache is cold, and it runs once when\n * somebody opens a screen rather than on every read.\n * @summary List Live Leases\n */\nexport const listLiveLeases = async ( options?: Parameters<typeof request>[1]): Promise<LiveLeaseListRead> => {\n\n  return request<LiveLeaseListRead>(getListLiveLeasesUrl(),\n  {\n    ...options,\n    method: 'GET'\n\n\n  }\n);}\n\n\nexport const getForceCloseLeaseUrl = (eventId: number,) => {\n\n\n\n\n  return `/admin/consumption/${eventId}`\n}\n\n/**\n * Force-close somebody else's lease. The legacy's ``FermeSessionAdherent``.\n *\n * Audited, which the legacy's was not: a button that ends a stranger's reading\n * session and leaves no trace is indistinguishable from abuse of the same\n * button. Tenant-scoped like every staff action, so a lease outside the\n * caller's scope is ``404`` rather than ``403``.\n * @summary Force Close Lease\n */\nexport const forceCloseLease = async (eventId: number,\n    leaseCloseWrite: LeaseCloseWrite, options?: Parameters<typeof request>[1]): Promise<void> => {\n\n    const getHeaders = (h?: NonNullable<RequestInit['headers']>): Record<string, string | readonly string[]> => {\n    if (!h) return {};\n    if (h instanceof Headers) return Object.fromEntries(h.entries());\n    if (Symbol.iterator in h) {\n      return Object.fromEntries(\n        Array.from(h as Iterable<Iterable<string>>, (entry) => Array.from(entry) as [string, string]),\n      );\n    }\n    const headers: Record<string, string | readonly string[]> = {};\n    for (const [name, value] of Object.entries<string | readonly string[] | undefined>(h)) {\n      if (value !== undefined) headers[name] = value;\n    }\n    return headers;\n  };\nreturn request<void>(getForceCloseLeaseUrl(eventId),\n  {\n    ...options,\n    method: 'DELETE',\n    headers: { 'Content-Type': 'application/json', ...getHeaders(options?.headers) },\n    body: JSON.stringify(leaseCloseWrite)\n  }\n);}\n\n\n"],"mappings":";;;AAcA,MAAa,6BAA6B;CAKxC,OAAO;AACT;;;;;;;;;AAUA,MAAa,iBAAiB,OAAQ,YAAwE;CAE5G,OAAO,QAA2B,qBAAqB,GACvD;EACE,GAAG;EACH,QAAQ;CAGV,CACF;AAAE;AAGF,MAAa,yBAAyB,YAAqB;CAKzD,OAAO,sBAAsB;AAC/B;;;;;;;;;;AAWA,MAAa,kBAAkB,OAAO,SAClC,iBAAkC,YAA2D;CAE7F,MAAM,cAAc,MAAwF;EAC5G,IAAI,CAAC,GAAG,OAAO,CAAC;EAChB,IAAI,aAAa,SAAS,OAAO,OAAO,YAAY,EAAE,QAAQ,CAAC;EAC/D,IAAI,OAAO,YAAY,GACrB,OAAO,OAAO,YACZ,MAAM,KAAK,IAAkC,UAAU,MAAM,KAAK,KAAK,CAAqB,CAC9F;EAEF,MAAM,UAAsD,CAAC;EAC7D,KAAK,MAAM,CAAC,MAAM,UAAU,OAAO,QAAgD,CAAC,GAClF,IAAI,UAAU,KAAA,GAAW,QAAQ,QAAQ;EAE3C,OAAO;CACT;CACF,OAAO,QAAc,sBAAsB,OAAO,GAChD;EACE,GAAG;EACH,QAAQ;EACR,SAAS;GAAE,gBAAgB;GAAoB,GAAG,WAAW,SAAS,OAAO;EAAE;EAC/E,MAAM,KAAK,UAAU,eAAe;CACtC,CACF;AAAE"}

package/dist/api/admin-licenses.d.ts

@@ -0,0 +1,21 @@
+
+import { $ as ReadPatronLicenseParams, R as StaffLicenseRead } from "../chunks/index.js";
+import { c as request } from "../chunks/client.js";
+//#region src/api/admin-licenses/admin-licenses.d.ts
+export declare const getReadPatronLicenseUrl: (params: ReadPatronLicenseParams) => string;
+/**
+ * Report one account's licence state. Never allocates, never repairs.
+ *
+ * Scoped like every other staff read: an agent who cannot see the account gets
+ * ``404``, the same answer as for an address nobody holds, so the endpoint
+ * cannot be used to test whether a member exists elsewhere.
+ *
+ * ``partner_active`` is ``None`` when the partner could not be reached. That is
+ * deliberately distinct from ``False`` — "we could not ask" and "they said the
+ * subscription is closed" lead a support agent to different actions, and
+ * collapsing them is how a working account gets re-provisioned.
+ * @summary Read Patron License
+ */
+export declare const readPatronLicense: (params: ReadPatronLicenseParams, options?: Parameters<typeof request>[1]) => Promise<StaffLicenseRead>;
+//#endregion
+//# sourceMappingURL=admin-licenses.d.ts.map