@kernhq/module-inventory 0.1.2 → 0.3.0

package/dist/contract/models.js

@@ -0,0 +1,320 @@
+import { WorkspaceId } from '@kernhq/contracts';
+import { z } from 'zod';
+/**
+ * The nouns this module owns, and the shapes that cross the wire.
+ *
+ * Imported by **both** halves — the server implements against them, the client calls against them —
+ * so nothing here may touch Node. Types only; the procedures live in `router.ts`.
+ */
+/** Lowercase, 2-32 characters. Names the API prefix, the Postgres schema `mod_<id>` and every event. */
+export const MODULE_ID = 'inventory';
+/**
+ * An asset's lifecycle. `in_stock` and `assigned` follow custody (an open row in `custody_periods`
+ * means assigned); `under_repair` follows an open repair; `reserved` follows a booking that has not
+ * been collected; `lost` and `retired` are set by hand when an item stops being usable.
+ *
+ * Stored rather than derived, because every list filter asks for it — and kept in step inside the
+ * same transaction that writes the row it derives from, never by a job afterwards.
+ *
+ * **`under_repair` belongs to the `repairs` capability**, so a workspace with that switch off never
+ * has an asset in it: the procedure that ends a repair answers 404 there, and a status nothing can
+ * move an item out of is a register the workspace cannot correct. The one thing a job does here is
+ * bring the rows *nobody touches* back into step after that switch moves, in both directions —
+ * `deriveStatus` in `src/server/services/status.ts` argues it, and nothing is destroyed either way.
+ */
+export const AssetStatus = z.enum(['in_stock', 'assigned', 'reserved', 'under_repair', 'lost', 'retired']);
+/**
+ * A value a workspace defined for itself, stored under its `key` in `assets.custom`.
+ *
+ * `unknown` rather than a union: the field definition says what the type is, and validating a value
+ * against a definition the client may not have loaded yet would fail honest input. The server checks
+ * it against `field_defs` before writing.
+ */
+export const CustomValues = z.record(z.string(), z.unknown());
+/**
+ * A workspace's own grouping of what it owns — Laptops, Furniture, Cameras.
+ *
+ * Archived rather than deleted, and `archivedAt` is the whole reason: `assets.category_id` is a
+ * plain uuid with no foreign key, so a deleted category leaves every asset filed under it pointing
+ * at a row that is not there. The list column goes blank and the timeline entry that recorded the
+ * move loses the name it recorded. Archiving takes it out of every picker and every filter and
+ * leaves each asset able to say what it is.
+ */
+export const Category = z.object({
+    id: z.uuid(),
+    workspaceId: WorkspaceId,
+    name: z.string().min(1).max(120),
+    /** Where it sits in a picker. Equal orders fall back to the name, so a workspace that never
+     *  reorders anything still gets an alphabetical list rather than an arbitrary one. */
+    order: z.number().int(),
+    createdAt: z.string(),
+    updatedAt: z.string(),
+    archivedAt: z.string().nullable(),
+});
+export const CategoryInput = z.object({
+    name: z.string().trim().min(1).max(120),
+    order: z.number().int().min(0).max(9999).optional(),
+});
+/**
+ * One stretch of time during which one person held one asset.
+ *
+ * Effective-dated, exactly as HR keeps employments: nothing is ever updated in place, a change
+ * closes the open row and inserts a new one. `effectiveTo === null` means "still holding it", and
+ * `inventory_custody_no_overlap` — a GiST exclusion constraint on
+ * `(asset_id =, tstzrange(effective_from, effective_to, '[)') &&)` — makes two of those for one
+ * asset impossible in the database rather than merely unlikely in the service.
+ */
+export const CustodyPeriod = z.object({
+    id: z.uuid(),
+    workspaceId: WorkspaceId,
+    assetId: z.uuid(),
+    /**
+     * The member who held it. A plain uuid — a cross-schema foreign key is what the module boundary
+     * exists to prevent — resolved against core membership at read time, which is also why a person
+     * who has since left the workspace still has readable history.
+     */
+    userId: z.uuid(),
+    note: z.string().max(500).nullable(),
+    effectiveFrom: z.string(),
+    effectiveTo: z.string().nullable(),
+    /** Who did the handing over, which is not always who received it. */
+    createdBy: z.uuid().nullable(),
+    createdAt: z.string(),
+});
+/**
+ * One entry in an asset's timeline.
+ *
+ * `action` is a **plain string, deliberately not an enum**. The rows are append-only and outlive
+ * the image that wrote them: an instance rolled back to a previous release would fail to parse its
+ * own history the moment a newer image had written an action the older enum does not list — a
+ * timeline that 500s rather than one that says a little less. The client renders a sentence per
+ * action it knows and a neutral one for anything else. What is written today is `created`,
+ * `updated`, `assigned`, `transferred`, `returned`, `retired`, `restored`, `repair_logged`,
+ * `repair_completed`, `attachment_added` and `attachment_removed`.
+ */
+export const AssetHistoryEntry = z.object({
+    id: z.uuid(),
+    assetId: z.uuid(),
+    /** Null for anything the platform did rather than a person. */
+    actorId: z.uuid().nullable(),
+    action: z.string().max(40),
+    changes: z.array(z.object({ field: z.string(), from: z.unknown(), to: z.unknown() })),
+    /** Action-specific ids — who received an item, who handed it over. Never a row. */
+    data: z.record(z.string(), z.unknown()),
+    occurredAt: z.string(),
+});
+export const Asset = z.object({
+    id: z.uuid(),
+    workspaceId: WorkspaceId,
+    /** Human-facing asset tag (`INV-0001`), assigned by the server, unique per workspace. */
+    code: z.string().min(1).max(40),
+    name: z.string().min(1).max(200),
+    description: z.string().max(4000),
+    categoryId: z.uuid().nullable(),
+    status: AssetStatus,
+    /**
+     * The member currently holding the item. A plain uuid — cross-schema foreign keys are what the
+     * module boundary exists to prevent — resolved against core membership at read time.
+     */
+    custodianUserId: z.uuid().nullable(),
+    custodySince: z.string().nullable(),
+    serialNumber: z.string().max(200).nullable(),
+    location: z.string().max(200).nullable(),
+    purchasedOn: z.string().nullable(),
+    purchasedFrom: z.string().max(200).nullable(),
+    /** Minor units (cents), the convention billing established; formatted on the client. */
+    priceMinor: z.number().int().nullable(),
+    currency: z.string().length(3).nullable(),
+    warrantyUntil: z.string().nullable(),
+    photoFileId: z.uuid().nullable(),
+    custom: CustomValues,
+    createdAt: z.string(),
+    updatedAt: z.string(),
+    archivedAt: z.string().nullable(),
+});
+/**
+ * What a custody procedure answers with: the asset as it now stands, and the period this call
+ * opened.
+ *
+ * Both, because a screen needs both and fetching the asset again afterwards is a second round trip
+ * that can read a row somebody else has changed in between — the panel would then show a handover
+ * that has already been undone. `period` is null on a return: something closed, nothing opened.
+ */
+export const CustodyResult = z.object({
+    asset: Asset,
+    period: CustodyPeriod.nullable(),
+});
+/**
+ * One trip an item made to a repairer.
+ *
+ * `returnedOn === null` means it is still away, and that single fact is what puts the asset in
+ * `under_repair` — see `deriveStatus` in `src/server/services/status.ts`, which is the only place
+ * the three columns that drive a status are read together.
+ *
+ * **A repair is not custody, and neither one cancels the other.** A laptop assigned to Dan that goes
+ * to the repairer is still Dan's responsibility: the custody period stays open, `custodianUserId`
+ * stays set, and only `status` moves. That is why a repair does not touch custody and custody does
+ * not refuse a repaired item — the two answer different questions ("who is answerable for it" and
+ * "where is it"), and collapsing them would mean an item could not come back to the person who sent
+ * it.
+ */
+export const Repair = z.object({
+    id: z.uuid(),
+    workspaceId: WorkspaceId,
+    assetId: z.uuid(),
+    summary: z.string().min(1).max(200),
+    detail: z.string().max(4000).nullable(),
+    vendor: z.string().max(200).nullable(),
+    /** Minor units, like `Asset.priceMinor` — one convention for money across the module. */
+    costMinor: z.number().int().nullable(),
+    currency: z.string().length(3).nullable(),
+    sentOn: z.string(),
+    /** Null while it is still away. Set by `repairs.complete` and by nothing else. */
+    returnedOn: z.string().nullable(),
+    createdBy: z.uuid().nullable(),
+    createdAt: z.string(),
+    updatedAt: z.string(),
+});
+/**
+ * A repair in a list, with the two things a reader needs to know *which item* it is about.
+ *
+ * **Joined at read time, never stored here.** `mod_inventory.repairs` holds no asset name, so
+ * renaming an asset renames it everywhere at once — a copied label is a label that goes stale, and
+ * this module already refuses to copy a person's name for the same reason. The join is inside one
+ * schema, which is the kind a module is allowed to make; the kind it is not is a join across the
+ * boundary into another module's tables.
+ *
+ * It extends `Repair` rather than replacing it, so a component that renders a repair renders one of
+ * these without knowing the difference. `create`, `update` and `complete` answer with a plain
+ * `Repair`: the caller of those already knows which asset it asked about.
+ */
+export const RepairListItem = Repair.extend({
+    assetCode: z.string().min(1).max(40),
+    assetName: z.string().min(1).max(200),
+});
+/**
+ * Everything a person can say about a repair.
+ *
+ * **No field here carries `.default()`, for the reason `AssetInput` spells out**: `update` is built
+ * from `.partial()`, and `.partial()` does not strip a default — zod still substitutes it for a key
+ * the request never sent, so a patch that renames a repair would silently re-date it. `sentOn` is
+ * optional rather than defaulted for the same reason; `repairs.create` fills today's date on the
+ * server, which is the only clock this module trusts.
+ */
+export const RepairInput = z.object({
+    summary: z.string().trim().min(1).max(200),
+    detail: z.string().max(4000).nullish(),
+    vendor: z.string().max(200).nullish(),
+    costMinor: z.number().int().min(0).nullish(),
+    currency: z.string().length(3).nullish(),
+    /** `sent_on` is `not null` in the database, so this is optional but never nullable. */
+    sentOn: z.iso.date().optional(),
+});
+export const RepairPatchInput = RepairInput.partial();
+/**
+ * What a repair mutation answers with: the repair, and the asset as it now stands.
+ *
+ * Both, for the reason `CustodyResult` carries both — sending an item away moves `assets.status`,
+ * and a screen that had to fetch the asset again afterwards would be reading a row somebody else
+ * may have changed in between.
+ */
+export const RepairResult = z.object({
+    repair: Repair,
+    asset: Asset,
+});
+/**
+ * A file recorded against an asset — a receipt, a warranty card, a manual.
+ *
+ * **The bytes are core's, not this module's.** A module does not upload: the browser uploads through
+ * core's file service and hands this module the id it was given, and reading one back is a download
+ * URL core signs. All that lives here is the fact that this asset has that file, plus the name and
+ * size copied at attach time so a list can be drawn without asking core once per row.
+ *
+ * `repairId` is what separates "the invoice for the screen replacement" from "the purchase receipt":
+ * null means it belongs to the asset itself.
+ */
+export const Attachment = z.object({
+    id: z.uuid(),
+    workspaceId: WorkspaceId,
+    assetId: z.uuid(),
+    repairId: z.uuid().nullable(),
+    fileId: z.uuid(),
+    name: z.string().max(300),
+    mimeType: z.string().max(200).nullable(),
+    /** Bytes, as core reported them when the file was attached. */
+    size: z.number().int().nullable(),
+    uploadedBy: z.uuid().nullable(),
+    createdAt: z.string(),
+});
+/**
+ * The register in numbers: what a page's count line and a dashboard card need in one request.
+ *
+ * `total` counts what the list shows by default — live rows — and `archived` is beside it rather
+ * than inside it, because a count line that silently included archived rows would disagree with the
+ * list under it.
+ *
+ * **`outForRepair` is null when the workspace does not track repairs.** Zero would be a claim
+ * ("nothing is away"), and a workspace with the `repairs` capability off has not made that claim —
+ * it has no opinion at all. The screens show the tile only when a number arrives, which is the same
+ * rule as hiding the Repairs tab, expressed in the data instead of in a second capability lookup.
+ */
+export const InventoryStats = z.object({
+    total: z.number().int().nonnegative(),
+    archived: z.number().int().nonnegative(),
+    /** Every status, zero-filled, so a screen can render the set without knowing which exist. */
+    byStatus: z.record(AssetStatus, z.number().int().nonnegative()),
+    outForRepair: z.number().int().nonnegative().nullable(),
+    /** Live assets nobody is holding — what is actually available to hand out. */
+    unassigned: z.number().int().nonnegative(),
+});
+/**
+ * How a list is ordered, and therefore what a page cursor is a bookmark *into*.
+ *
+ * Exported rather than written inline in `router.ts` because the server validates a cursor against
+ * this same list: a bookmark issued under one sort is meaningless under another, and the only way
+ * to say so is for both halves to read one enum.
+ */
+export const AssetSort = z.enum(['recent', 'name', 'code']);
+/**
+ * Everything a person can say about an asset. `create` requires `name`; `update` takes any subset.
+ *
+ * **No field here carries `.default()`, and that is load-bearing.** `update` is built from
+ * `AssetInput.partial()`, and `.partial()` does not strip a default — it only wraps the field in
+ * `optional`, so zod still substitutes the default for a key the request never sent. `description`
+ * had `.default('')`, so `PATCH {assetId, name}` reached the handler as
+ * `{assetId, name, description: ''}`; the service correctly read a present value as "set it" and a
+ * rename destroyed the text, writing a bogus `description` diff into `asset_history` as it went.
+ * The care the service takes over `undefined` versus `null` is defeated one layer above it, here.
+ * A value `create` should fill in belongs on `AssetCreateInput` below, which is never partialled.
+ */
+export const AssetInput = z.object({
+    name: z.string().min(1).max(200),
+    description: z.string().max(4000).optional(),
+    categoryId: z.uuid().nullish(),
+    serialNumber: z.string().max(200).nullish(),
+    location: z.string().max(200).nullish(),
+    purchasedFrom: z.string().max(200).nullish(),
+    purchasedOn: z.iso.date().nullish(),
+    warrantyUntil: z.iso.date().nullish(),
+    priceMinor: z.number().int().min(0).nullish(),
+    currency: z.string().length(3).nullish(),
+    photoFileId: z.uuid().nullish(),
+    // `custom` is deliberately absent: there is nothing to validate a value against until
+    // `fields.*` exists, and accepting arbitrary JSON into a column a workspace has not defined
+    // is how a schemaless field bag becomes permanent. It arrives with the field definitions.
+});
+/**
+ * What `create` accepts: the same fields, with the one value a new row may not go without.
+ *
+ * `description` is `not null` in the database, so a create with no description needs *something*.
+ * Defaulting it here rather than in `AssetInput` is what keeps `update` able to tell "leave it
+ * alone" from "clear it" — see the note above.
+ */
+export const AssetCreateInput = AssetInput.extend({
+    description: z.string().max(4000).default(''),
+});
+/** What `update` accepts: any subset, and nothing filled in for a key that never arrived. */
+export const AssetPatchInput = AssetInput.partial();
+/** Shared by every workspace-scoped procedure, which is all of them. */
+export const ws = z.object({ workspaceId: WorkspaceId });
+//# sourceMappingURL=models.js.map

package/dist/contract/models.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"models.js","sourceRoot":"","sources":["../../src/contract/models.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAA;AAC/C,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAA;AAEvB;;;;;GAKG;AAEH,wGAAwG;AACxG,MAAM,CAAC,MAAM,SAAS,GAAG,WAAW,CAAA;AAEpC;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,WAAW,GAAG,CAAC,CAAC,IAAI,CAAC,CAAC,UAAU,EAAE,UAAU,EAAE,UAAU,EAAE,cAAc,EAAE,MAAM,EAAE,SAAS,CAAC,CAAC,CAAA;AAG1G;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC,CAAA;AAG7D;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG,CAAC,CAAC,MAAM,CAAC;IAC/B,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE;IACZ,WAAW,EAAE,WAAW;IACxB,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC;IAChC;0FACsF;IACtF,KAAK,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE;IACvB,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;IACrB,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;IACrB,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;CAClC,CAAC,CAAA;AAGF,MAAM,CAAC,MAAM,aAAa,GAAG,CAAC,CAAC,MAAM,CAAC;IACpC,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,IAAI,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC;IACvC,KAAK,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,QAAQ,EAAE;CACpD,CAAC,CAAA;AAGF;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG,CAAC,CAAC,MAAM,CAAC;IACpC,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE;IACZ,WAAW,EAAE,WAAW;IACxB,OAAO,EAAE,CAAC,CAAC,IAAI,EAAE;IACjB;;;;OAIG;IACH,MAAM,EAAE,CAAC,CAAC,IAAI,EAAE;IAChB,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE;IACpC,aAAa,EAAE,CAAC,CAAC,MAAM,EAAE;IACzB,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IAClC,qEAAqE;IACrE,SAAS,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IAC9B,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;CACtB,CAAC,CAAA;AAGF;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,CAAC,MAAM,CAAC;IACxC,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE;IACZ,OAAO,EAAE,CAAC,CAAC,IAAI,EAAE;IACjB,+DAA+D;IAC/D,OAAO,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IAC5B,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,EAAE,CAAC;IAC1B,OAAO,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,CAAC,EAAE,KAAK,EAAE,CAAC,CAAC,MAAM,EAAE,EAAE,IAAI,EAAE,CAAC,CAAC,OAAO,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC;IACrF,mFAAmF;IACnF,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC;IACvC,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE;CACvB,CAAC,CAAA;AAGF,MAAM,CAAC,MAAM,KAAK,GAAG,CAAC,CAAC,MAAM,CAAC;IAC5B,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE;IACZ,WAAW,EAAE,WAAW;IACxB,yFAAyF;IACzF,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,EAAE,CAAC;IAC/B,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC;IAChC,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,IAAI,CAAC;IACjC,UAAU,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IAC/B,MAAM,EAAE,WAAW;IACnB;;;OAGG;IACH,eAAe,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IACpC,YAAY,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IACnC,YAAY,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE;IAC5C,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE;IACxC,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IAClC,aAAa,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE;IAC7C,wFAAwF;IACxF,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,QAAQ,EAAE;IACvC,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;IACzC,aAAa,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IACpC,WAAW,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IAChC,MAAM,EAAE,YAAY;IACpB,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;IACrB,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;IACrB,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;CAClC,CAAC,CAAA;AAGF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG,CAAC,CAAC,MAAM,CAAC;IACpC,KAAK,EAAE,KAAK;IACZ,MAAM,EAAE,aAAa,CAAC,QAAQ,EAAE;CACjC,CAAC,CAAA;AAGF;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,MAAM,GAAG,CAAC,CAAC,MAAM,CAAC;IAC7B,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE;IACZ,WAAW,EAAE,WAAW;IACxB,OAAO,EAAE,CAAC,CAAC,IAAI,EAAE;IACjB,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC;IACnC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,QAAQ,EAAE;IACvC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE;IACtC,yFAAyF;IACzF,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,QAAQ,EAAE;IACtC,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;IACzC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE;IAClB,kFAAkF;IAClF,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;IACjC,SAAS,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IAC9B,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;IACrB,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;CACtB,CAAC,CAAA;AAGF;;;;;;;;;;;;GAYG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,MAAM,CAAC,MAAM,CAAC;IAC1C,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,EAAE,CAAC;IACpC,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC;CACtC,CAAC,CAAA;AAGF;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,WAAW,GAAG,CAAC,CAAC,MAAM,CAAC;IAClC,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,IAAI,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC;IAC1C,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE;IACtC,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE;IACrC,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE;IAC5C,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE;IACxC,uFAAuF;IACvF,MAAM,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;CAChC,CAAC,CAAA;AAGF,MAAM,CAAC,MAAM,gBAAgB,GAAG,WAAW,CAAC,OAAO,EAAE,CAAA;AAGrD;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,CAAC,CAAC,MAAM,CAAC;IACnC,MAAM,EAAE,MAAM;IACd,KAAK,EAAE,KAAK;CACb,CAAC,CAAA;AAGF;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC;IACjC,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE;IACZ,WAAW,EAAE,WAAW;IACxB,OAAO,EAAE,CAAC,CAAC,IAAI,EAAE;IACjB,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IAC7B,MAAM,EAAE,CAAC,CAAC,IAAI,EAAE;IAChB,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC;IACzB,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE;IACxC,+DAA+D;IAC/D,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,QAAQ,EAAE;IACjC,UAAU,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;IAC/B,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE;CACtB,CAAC,CAAA;AAGF;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,CAAC,MAAM,CAAC;IACrC,KAAK,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,WAAW,EAAE;IACrC,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,WAAW,EAAE;IACxC,6FAA6F;IAC7F,QAAQ,EAAE,CAAC,CAAC,MAAM,CAAC,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,WAAW,EAAE,CAAC;IAC/D,YAAY,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,WAAW,EAAE,CAAC,QAAQ,EAAE;IACvD,8EAA8E;IAC9E,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,WAAW,EAAE;CAC3C,CAAC,CAAA;AAGF;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,SAAS,GAAG,CAAC,CAAC,IAAI,CAAC,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,CAAC,CAAC,CAAA;AAG3D;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,CAAC,MAAM,CAAC;IACjC,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC;IAChC,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,QAAQ,EAAE;IAC5C,UAAU,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,OAAO,EAAE;IAC9B,YAAY,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE;IAC3C,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE;IACvC,aAAa,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE;IAC5C,WAAW,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,OAAO,EAAE;IACnC,aAAa,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,OAAO,EAAE;IACrC,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE;IAC7C,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,OAAO,EAAE;IACxC,WAAW,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,OAAO,EAAE;IAC/B,sFAAsF;IACtF,4FAA4F;IAC5F,0FAA0F;CAC3F,CAAC,CAAA;AAGF;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG,UAAU,CAAC,MAAM,CAAC;IAChD,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;CAC9C,CAAC,CAAA;AAGF,6FAA6F;AAC7F,MAAM,CAAC,MAAM,eAAe,GAAG,UAAU,CAAC,OAAO,EAAE,CAAA;AAGnD,wEAAwE;AACxE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC,MAAM,CAAC,EAAE,WAAW,EAAE,WAAW,EAAE,CAAC,CAAA"}

package/dist/contract/notifications.d.ts

@@ -0,0 +1,24 @@
+import type { core } from '@kernhq/contracts';
+/**
+ * What Inventory will interrupt somebody about.
+ *
+ * Four things, and each of them changes what somebody has to *do*. That is the test: a rename, a new
+ * category, an item coming back — those are facts a screen shows when somebody looks, and a
+ * notification type nobody wants is a notification type everybody switches off along with the one
+ * that mattered.
+ *
+ * A type declared here and never sent is the same lie as a permission nothing checks. Each of these
+ * names its sender, and every one of them exists:
+ *
+ * - `custody.assigned` — `CustodyService`, on `assign` and `transfer`.
+ * - `warranty.expiring` — the `warranty-sweep` job, once per asset.
+ * - `repair.overdue` — the `repair-overdue` job, once per repair.
+ * - `custody.return_due` — the offboarding subscription, when HR says somebody has left or core says
+ *   they have been removed from the workspace.
+ *
+ * The keys keep their `inventory.custody.*` spelling rather than being renamed to
+ * `inventory.asset.*`: a notification type is the key a person's own preferences are stored under,
+ * so renaming one silently resets everybody who had switched it off.
+ */
+export declare const inventoryNotificationTypes: core.NotificationTypeDef[];
+//# sourceMappingURL=notifications.d.ts.map

package/dist/contract/notifications.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"notifications.d.ts","sourceRoot":"","sources":["../../src/contract/notifications.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,IAAI,EAAE,MAAM,mBAAmB,CAAA;AAE7C;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,eAAO,MAAM,0BAA0B,EAAE,IAAI,CAAC,mBAAmB,EAiDhE,CAAA"}

package/dist/contract/notifications.js

@@ -0,0 +1,72 @@
+/**
+ * What Inventory will interrupt somebody about.
+ *
+ * Four things, and each of them changes what somebody has to *do*. That is the test: a rename, a new
+ * category, an item coming back — those are facts a screen shows when somebody looks, and a
+ * notification type nobody wants is a notification type everybody switches off along with the one
+ * that mattered.
+ *
+ * A type declared here and never sent is the same lie as a permission nothing checks. Each of these
+ * names its sender, and every one of them exists:
+ *
+ * - `custody.assigned` — `CustodyService`, on `assign` and `transfer`.
+ * - `warranty.expiring` — the `warranty-sweep` job, once per asset.
+ * - `repair.overdue` — the `repair-overdue` job, once per repair.
+ * - `custody.return_due` — the offboarding subscription, when HR says somebody has left or core says
+ *   they have been removed from the workspace.
+ *
+ * The keys keep their `inventory.custody.*` spelling rather than being renamed to
+ * `inventory.asset.*`: a notification type is the key a person's own preferences are stored under,
+ * so renaming one silently resets everybody who had switched it off.
+ */
+export const inventoryNotificationTypes = [
+    {
+        /**
+         * Everybody who has ever found a laptop on their desk with no idea it was now theirs is the
+         * reason this is `urgent` and reaches email — an asset register that records a handover the
+         * recipient never learns about has recorded an argument for later.
+         */
+        type: 'inventory.custody.assigned',
+        label: 'An item was handed to you',
+        description: 'Somebody made you the holder of an asset in the register.',
+        defaults: { inapp: true, push: true, email: true },
+        urgent: true,
+    },
+    {
+        /**
+         * Not urgent, and email is off by default. A warranty running out in a month is a thing to plan
+         * for, not a thing to stop for — and it arrives on a schedule rather than because somebody did
+         * something, which is exactly the kind of message that trains people to ignore the rest.
+         */
+        type: 'inventory.warranty.expiring',
+        label: 'A warranty is about to run out',
+        description: "An item's warranty expires soon. Sent once per item, to whoever is holding it.",
+        defaults: { inapp: true, push: false, email: false },
+        urgent: false,
+    },
+    {
+        /**
+         * Push, because this one is an action somebody has to take — ring the repairer — and nobody
+         * goes looking for it. Still not urgent: a laptop that has been away a fortnight can wait until
+         * the phone is picked up.
+         */
+        type: 'inventory.repair.overdue',
+        label: 'A repair has been away too long',
+        description: 'An item sent for repair has not been logged as returned. Sent once per repair.',
+        defaults: { inapp: true, push: true, email: false },
+        urgent: false,
+    },
+    {
+        /**
+         * Somebody is leaving and still has company property. Email, because it is a list of things to
+         * collect from a person who may not be at their desk much longer, and an in-app badge nobody
+         * opens until Monday is how a laptop leaves the building.
+         */
+        type: 'inventory.custody.return_due',
+        label: 'Somebody leaving still holds company property',
+        description: 'A member has left, or is leaving, and items are still recorded as theirs.',
+        defaults: { inapp: true, push: true, email: true },
+        urgent: true,
+    },
+];
+//# sourceMappingURL=notifications.js.map

package/dist/contract/notifications.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"notifications.js","sourceRoot":"","sources":["../../src/contract/notifications.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,CAAC,MAAM,0BAA0B,GAA+B;IACpE;QACE;;;;WAIG;QACH,IAAI,EAAE,4BAA4B;QAClC,KAAK,EAAE,2BAA2B;QAClC,WAAW,EAAE,2DAA2D;QACxE,QAAQ,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE;QAClD,MAAM,EAAE,IAAI;KACb;IACD;QACE;;;;WAIG;QACH,IAAI,EAAE,6BAA6B;QACnC,KAAK,EAAE,gCAAgC;QACvC,WAAW,EAAE,gFAAgF;QAC7F,QAAQ,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE;QACpD,MAAM,EAAE,KAAK;KACd;IACD;QACE;;;;WAIG;QACH,IAAI,EAAE,0BAA0B;QAChC,KAAK,EAAE,iCAAiC;QACxC,WAAW,EAAE,gFAAgF;QAC7F,QAAQ,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,KAAK,EAAE,KAAK,EAAE;QACnD,MAAM,EAAE,KAAK;KACd;IACD;QACE;;;;WAIG;QACH,IAAI,EAAE,8BAA8B;QACpC,KAAK,EAAE,+CAA+C;QACtD,WAAW,EAAE,2EAA2E;QACxF,QAAQ,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE;QAClD,MAAM,EAAE,IAAI;KACb;CACF,CAAA"}

package/dist/contract/permissions.d.ts

@@ -0,0 +1,72 @@
+/**
+ * `<module>.<resource>.<action>`, each with the narrowest scope that works and the roles that hold
+ * it by default. A workspace can add or remove any of them afterwards with a custom role.
+ *
+ * A key with nothing checking it is a role editor full of switches that do nothing, so these arrive
+ * with the procedures that enforce them — `field.manage` and the stock and purchasing keys with
+ * their own phases.
+ *
+ * **Reading custody is `asset.view`, and that is a decision rather than an omission.** Who holds an
+ * item looks like a privacy question, and it is not one here: `custodianUserId` and `custodySince`
+ * are fields of `Asset`, returned by `assets.list` and `assets.get` under `asset.view` since the
+ * module existed, and `assets.list` has always taken a `custodianUserId` filter. A separate
+ * `custody.view` would be a lock on a door beside an open window — it would refuse the timeline
+ * while the row above it named the same person. "Who has the projector" is also the question an
+ * asset register exists to answer; a company where a member cannot find that out asks in chat
+ * instead, which is worse for whoever is holding it. A workspace that disagrees takes
+ * `inventory.asset.view` off `guest`, which is one switch and already there. Writing custody is
+ * `custody.manage`, because handing an item over makes somebody answerable for it.
+ */
+export declare const inventoryPermissions: readonly [{
+    readonly key: "inventory.asset.view";
+    readonly label: "View assets";
+    readonly scope: "workspace";
+    readonly defaultRoles: ["owner", "admin", "member", "guest"];
+    readonly dangerous: false;
+}, {
+    readonly key: "inventory.asset.manage";
+    readonly label: "Create and edit assets";
+    readonly scope: "workspace";
+    readonly defaultRoles: ["owner", "admin", "member"];
+    readonly dangerous: false;
+}, {
+    /**
+     * Not `asset.manage`: correcting a serial number and making a colleague answerable for a
+     * £2,000 laptop are different acts, and plenty of workspaces want the first from everybody and
+     * the second from the office manager. Held by `member` by default all the same — an office
+     * where only an admin may hand over a charger keeps its register by not using it.
+     */
+    readonly key: "inventory.custody.manage";
+    readonly label: "Hand assets over and take them back";
+    readonly scope: "workspace";
+    readonly defaultRoles: ["owner", "admin", "member"];
+    readonly dangerous: false;
+}, {
+    /**
+     * Sending an item away and recording what it cost, held by `member` for the same reason
+     * `custody.manage` is: the person who notices a broken screen is the person who should be able
+     * to log it, and an office where only an admin may do that keeps its repair record by not
+     * keeping one. Reading repairs rides `asset.view` — "where is the projector" is the question
+     * the register exists to answer, and a repair is one of the two answers.
+     *
+     * Not folded into `asset.manage`: correcting a serial number and committing the company to a
+     * £400 screen replacement are different acts, and the money is why.
+     */
+    readonly key: "inventory.repair.manage";
+    readonly label: "Log repairs";
+    readonly scope: "workspace";
+    readonly defaultRoles: ["owner", "admin", "member"];
+    readonly dangerous: false;
+}, {
+    /**
+     * Categories are workspace configuration — one list everybody's assets are filed against — so
+     * this sits with the people who set the workspace up rather than with everybody who may edit an
+     * asset. Reading them rides `asset.view`, because the picker on the asset form needs them.
+     */
+    readonly key: "inventory.category.manage";
+    readonly label: "Manage asset categories";
+    readonly scope: "workspace";
+    readonly defaultRoles: ["owner", "admin"];
+    readonly dangerous: false;
+}];
+//# sourceMappingURL=permissions.d.ts.map

package/dist/contract/permissions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"permissions.d.ts","sourceRoot":"","sources":["../../src/contract/permissions.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;IAgB7B;;;;;OAKG;;;;;;;IAQH;;;;;;;;;OASG;;;;;;;IAQH;;;;OAIG;;;;;;EAOL,CAAA"}

package/dist/contract/permissions.js

@@ -0,0 +1,79 @@
+import { definePermissions } from '@kernhq/contracts';
+/**
+ * `<module>.<resource>.<action>`, each with the narrowest scope that works and the roles that hold
+ * it by default. A workspace can add or remove any of them afterwards with a custom role.
+ *
+ * A key with nothing checking it is a role editor full of switches that do nothing, so these arrive
+ * with the procedures that enforce them — `field.manage` and the stock and purchasing keys with
+ * their own phases.
+ *
+ * **Reading custody is `asset.view`, and that is a decision rather than an omission.** Who holds an
+ * item looks like a privacy question, and it is not one here: `custodianUserId` and `custodySince`
+ * are fields of `Asset`, returned by `assets.list` and `assets.get` under `asset.view` since the
+ * module existed, and `assets.list` has always taken a `custodianUserId` filter. A separate
+ * `custody.view` would be a lock on a door beside an open window — it would refuse the timeline
+ * while the row above it named the same person. "Who has the projector" is also the question an
+ * asset register exists to answer; a company where a member cannot find that out asks in chat
+ * instead, which is worse for whoever is holding it. A workspace that disagrees takes
+ * `inventory.asset.view` off `guest`, which is one switch and already there. Writing custody is
+ * `custody.manage`, because handing an item over makes somebody answerable for it.
+ */
+export const inventoryPermissions = definePermissions([
+    {
+        key: 'inventory.asset.view',
+        label: 'View assets',
+        scope: 'workspace',
+        defaultRoles: ['owner', 'admin', 'member', 'guest'],
+        dangerous: false,
+    },
+    {
+        key: 'inventory.asset.manage',
+        label: 'Create and edit assets',
+        scope: 'workspace',
+        defaultRoles: ['owner', 'admin', 'member'],
+        dangerous: false,
+    },
+    {
+        /**
+         * Not `asset.manage`: correcting a serial number and making a colleague answerable for a
+         * £2,000 laptop are different acts, and plenty of workspaces want the first from everybody and
+         * the second from the office manager. Held by `member` by default all the same — an office
+         * where only an admin may hand over a charger keeps its register by not using it.
+         */
+        key: 'inventory.custody.manage',
+        label: 'Hand assets over and take them back',
+        scope: 'workspace',
+        defaultRoles: ['owner', 'admin', 'member'],
+        dangerous: false,
+    },
+    {
+        /**
+         * Sending an item away and recording what it cost, held by `member` for the same reason
+         * `custody.manage` is: the person who notices a broken screen is the person who should be able
+         * to log it, and an office where only an admin may do that keeps its repair record by not
+         * keeping one. Reading repairs rides `asset.view` — "where is the projector" is the question
+         * the register exists to answer, and a repair is one of the two answers.
+         *
+         * Not folded into `asset.manage`: correcting a serial number and committing the company to a
+         * £400 screen replacement are different acts, and the money is why.
+         */
+        key: 'inventory.repair.manage',
+        label: 'Log repairs',
+        scope: 'workspace',
+        defaultRoles: ['owner', 'admin', 'member'],
+        dangerous: false,
+    },
+    {
+        /**
+         * Categories are workspace configuration — one list everybody's assets are filed against — so
+         * this sits with the people who set the workspace up rather than with everybody who may edit an
+         * asset. Reading them rides `asset.view`, because the picker on the asset form needs them.
+         */
+        key: 'inventory.category.manage',
+        label: 'Manage asset categories',
+        scope: 'workspace',
+        defaultRoles: ['owner', 'admin'],
+        dangerous: false,
+    },
+]);
+//# sourceMappingURL=permissions.js.map

package/dist/contract/permissions.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"permissions.js","sourceRoot":"","sources":["../../src/contract/permissions.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,mBAAmB,CAAA;AAErD;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAG,iBAAiB,CAAC;IACpD;QACE,GAAG,EAAE,sBAAsB;QAC3B,KAAK,EAAE,aAAa;QACpB,KAAK,EAAE,WAAW;QAClB,YAAY,EAAE,CAAC,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,OAAO,CAAC;QACnD,SAAS,EAAE,KAAK;KACjB;IACD;QACE,GAAG,EAAE,wBAAwB;QAC7B,KAAK,EAAE,wBAAwB;QAC/B,KAAK,EAAE,WAAW;QAClB,YAAY,EAAE,CAAC,OAAO,EAAE,OAAO,EAAE,QAAQ,CAAC;QAC1C,SAAS,EAAE,KAAK;KACjB;IACD;QACE;;;;;WAKG;QACH,GAAG,EAAE,0BAA0B;QAC/B,KAAK,EAAE,qCAAqC;QAC5C,KAAK,EAAE,WAAW;QAClB,YAAY,EAAE,CAAC,OAAO,EAAE,OAAO,EAAE,QAAQ,CAAC;QAC1C,SAAS,EAAE,KAAK;KACjB;IACD;QACE;;;;;;;;;WASG;QACH,GAAG,EAAE,yBAAyB;QAC9B,KAAK,EAAE,aAAa;QACpB,KAAK,EAAE,WAAW;QAClB,YAAY,EAAE,CAAC,OAAO,EAAE,OAAO,EAAE,QAAQ,CAAC;QAC1C,SAAS,EAAE,KAAK;KACjB;IACD;QACE;;;;WAIG;QACH,GAAG,EAAE,2BAA2B;QAChC,KAAK,EAAE,yBAAyB;QAChC,KAAK,EAAE,WAAW;QAClB,YAAY,EAAE,CAAC,OAAO,EAAE,OAAO,CAAC;QAChC,SAAS,EAAE,KAAK;KACjB;CACF,CAAC,CAAA"}