@kernhq/module-hr 0.1.0

package/README.md

@@ -0,0 +1,71 @@
+# Module template
+
+Copy this to start a Kern module. It is a working module: a `Note` entity with list, create and
+delete, its own Postgres schema, row-level security, permissions, events, and a test that refuses to
+let the contract and the router drift apart.
+
+The fastest way to copy it correctly is not to copy it by hand:
+
+```bash
+cd repos/modules
+pnpm new-module crm          # generates this package *and* its half in the app
+```
+
+Read the rest of this file if you are doing it by hand, or if you want to know what the generator
+wrote.
+
+## What is in here
+
+| File | What it is |
+|---|---|
+| `src/contract.ts` | Zod models, the oRPC contract, events, permission keys, capabilities. Imported by both halves, so no Node code. |
+| `src/server/schema.ts` | Drizzle tables in `mod_<id>`. |
+| `src/server/_impl.ts` | The router. Separate from `index.ts` so the test can walk it without a kernel. |
+| `src/server/index.ts` | `defineServerModule` — schema, migrations, router, subscriptions. |
+| `src/client/index.ts` | The typed API client and module logic. **Ships as source.** |
+| `src/module.test.ts` | Contract-to-router parity and the authorisation guard. Keep it. |
+| `migrations/0000_init.sql` | Generated by `pnpm db:generate`. |
+| `migrations/0001_rls.sql` | Hand-written. Never generated. |
+
+## Copying it by hand
+
+Each of these has been got wrong before.
+
+1. **`package.json`** — set `name` to `@kernhq/module-<id>`, and **delete `"private": true`**. A
+   private package is skipped silently by changesets: the commit lands, CI is green, and nothing
+   publishes.
+2. **`files`** must cover every directory `./client` reaches — `src/client` *and* `src/contract`.
+   The client ships as source, so a re-export the tarball omits breaks the consumer and nothing
+   local notices, because the workspace resolves the file the package does not ship.
+   `pnpm check:pack` catches it.
+3. **The id agrees in four places**: `MODULE_ID`, `moduleSchema('<id>')`, `schemaFilter` in
+   `drizzle.config.ts`, and every permission and event prefix.
+4. **Version comes from the package**, never a literal: `packageVersion(import.meta.url)`. A literal
+   is not bumped by a release — chat once shipped as 0.2.0 while telling every admin it was 0.1.0,
+   and that literal is what `workspace_modules.installed_version` recorded.
+5. **Write the RLS migration.** `pnpm db:generate` will not. Copy `0001_rls.sql` and change the
+   table names; `rlsPolicySql` from `@kernhq/kernel` emits the same text.
+6. **Host it.** A module nothing imports is invisible: its tests pass, it publishes, and every call
+   404s. Add it to `featureModules` in the `core` repo's `src/service.ts`, or to whichever service
+   should hold it.
+7. **Register the client** in the app's `src/lib/modules/registry.ts`.
+
+## What a module can contribute
+
+The server half declares tables, migrations, a router, `procedures` other modules call through
+`kernel.call()`, `jobs`, `subscriptions`, search indexers and lifecycle hooks.
+
+The client half — the manifest in the app — declares `nav`, `commands`, `settingsPages`, `widgets`
+for the dashboard, and `sidebar` for the column beside the rail. Read the `kern-widget` skill before
+writing a widget, and `kern-module` for the whole sequence.
+
+## Before you call it done
+
+```bash
+pnpm typecheck && pnpm lint && pnpm test && pnpm build
+pnpm check:pack        # the tarball contains what ./client imports
+pnpm check:versions    # the manifest version matches package.json
+```
+
+Then use it through the interface, signed in, with the module enabled for a workspace. A module that
+has never served a request is not finished, whatever the type-checker says.

package/dist/contract/capabilities.d.ts

@@ -0,0 +1,45 @@
+/**
+ * How much HR this workspace has.
+ *
+ * HR is the module capabilities were built for. One company wants a staff directory and nothing
+ * else; a second wants leave, balances and approvals; a third runs shift rosters and clocks people
+ * in at a factory gate. Those are three products under one name, and the alternatives to this
+ * registry are a code fork per customer or a navigation rail full of features nobody uses.
+ *
+ * **A capability is declared here only once something is behind it.** A switch that changes nothing
+ * is worse than a missing switch: it teaches an administrator that the switchboard does not mean
+ * anything. So this list grows with the module rather than describing where the module is going —
+ * `leave`, `attendance`, `overtime`, `rosters`, `periods` and `payroll_export` arrive with the
+ * phases that implement them.
+ *
+ * Two rules that decide whether something belongs here at all:
+ *
+ * - **Not a permission.** "May Ayşe approve leave" is a permission — true for her, false for someone
+ *   else, in the same workspace. "Does this company do leave" is a capability: one answer for
+ *   everyone, the owner included.
+ * - **Reversible without a migration.** Switching one off writes a boolean into module settings;
+ *   the rows stay exactly where they are and switching it back on restores them. Anything that would
+ *   need data thrown away is not a capability, however much it looks like one.
+ */
+export declare const hrCapabilities: readonly {
+    id: string;
+    label: string;
+    dependsOn: string[];
+    defaultEnabled: boolean;
+    level: 3 | 1 | 2;
+    required: boolean;
+    description?: string | undefined;
+}[];
+export type HrCapabilityId = (typeof hrCapabilities)[number]['id'];
+/**
+ * Which procedures sit behind which capability.
+ *
+ * Declared as data because a missing `requiresCapability` is invisible: the procedure compiles,
+ * every other test passes, and the only symptom is a workspace calling a feature it switched off.
+ * `module.test.ts` reads this and fails when a procedure named here is not carrying the middleware.
+ *
+ * A procedure absent from this map belongs to the module as a whole and is reachable whenever HR is
+ * on — which for `core` is always, because it is `required`.
+ */
+export declare const hrCapabilityProcedures: Record<string, readonly string[]>;
+//# sourceMappingURL=capabilities.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"capabilities.d.ts","sourceRoot":"","sources":["../../src/contract/capabilities.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,eAAO,MAAM,cAAc;;;;;;;;GAiDzB,CAAA;AAEF,MAAM,MAAM,cAAc,GAAG,CAAC,OAAO,cAAc,CAAC,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,CAAA;AAElE;;;;;;;;;GASG;AACH,eAAO,MAAM,sBAAsB,EAAE,MAAM,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,CA4BpE,CAAA"}

package/dist/contract/capabilities.js

@@ -0,0 +1,114 @@
+import { defineCapabilities } from '@kernhq/contracts';
+/**
+ * How much HR this workspace has.
+ *
+ * HR is the module capabilities were built for. One company wants a staff directory and nothing
+ * else; a second wants leave, balances and approvals; a third runs shift rosters and clocks people
+ * in at a factory gate. Those are three products under one name, and the alternatives to this
+ * registry are a code fork per customer or a navigation rail full of features nobody uses.
+ *
+ * **A capability is declared here only once something is behind it.** A switch that changes nothing
+ * is worse than a missing switch: it teaches an administrator that the switchboard does not mean
+ * anything. So this list grows with the module rather than describing where the module is going —
+ * `leave`, `attendance`, `overtime`, `rosters`, `periods` and `payroll_export` arrive with the
+ * phases that implement them.
+ *
+ * Two rules that decide whether something belongs here at all:
+ *
+ * - **Not a permission.** "May Ayşe approve leave" is a permission — true for her, false for someone
+ *   else, in the same workspace. "Does this company do leave" is a capability: one answer for
+ *   everyone, the owner included.
+ * - **Reversible without a migration.** Switching one off writes a boolean into module settings;
+ *   the rows stay exactly where they are and switching it back on restores them. Anything that would
+ *   need data thrown away is not a capability, however much it looks like one.
+ */
+export const hrCapabilities = defineCapabilities([
+    {
+        id: 'core',
+        label: 'People',
+        description: 'The staff directory, employment records and reporting lines',
+        required: true,
+        level: 1,
+    },
+    {
+        id: 'offices',
+        label: 'Offices',
+        description: 'More than one place of work, each with its own country, timezone and holidays',
+        dependsOn: ['core'],
+        // Off by default, and invisible when off — but the *concept* is never absent. A workspace always
+        // has exactly one office, built from its country when HR is enabled, and everybody is assigned
+        // to it. Switching this on reveals the list and the assignment control; it does not migrate
+        // anything, because the shape was there from the first day. A workspace that only ever has one
+        // office never meets the word.
+        defaultEnabled: false,
+        level: 2,
+    },
+    {
+        id: 'legal_entities',
+        label: 'Legal entities',
+        description: 'Several employing companies, for a group operating across borders',
+        // Depends on offices rather than core: a single-site company has one employer by definition, and
+        // the question only becomes real once there is more than one place of work.
+        dependsOn: ['offices'],
+        defaultEnabled: false,
+        level: 3,
+    },
+    {
+        id: 'calendars',
+        label: 'Holiday calendars',
+        description: 'Public holidays, company closures and the working week',
+        dependsOn: ['core'],
+        // On by default. Every company has holidays, and a directory that does not know when people are
+        // off is answering a question nobody asked.
+        defaultEnabled: true,
+        level: 1,
+    },
+    {
+        id: 'documents',
+        label: 'Employee documents',
+        description: 'Contracts, identity documents and certificates against a person',
+        dependsOn: ['core'],
+        defaultEnabled: false,
+        level: 2,
+    },
+]);
+/**
+ * Which procedures sit behind which capability.
+ *
+ * Declared as data because a missing `requiresCapability` is invisible: the procedure compiles,
+ * every other test passes, and the only symptom is a workspace calling a feature it switched off.
+ * `module.test.ts` reads this and fails when a procedure named here is not carrying the middleware.
+ *
+ * A procedure absent from this map belongs to the module as a whole and is reachable whenever HR is
+ * on — which for `core` is always, because it is `required`.
+ */
+export const hrCapabilityProcedures = {
+    offices: [
+        'offices.list',
+        'offices.get',
+        'offices.create',
+        'offices.update',
+        'offices.archive',
+        'offices.setDefault',
+        'offices.assign',
+        'offices.unassign',
+        'offices.people',
+    ],
+    legal_entities: ['entities.list', 'entities.get', 'entities.create', 'entities.update', 'entities.archive'],
+    calendars: [
+        'calendars.list',
+        'calendars.get',
+        'calendars.create',
+        'calendars.update',
+        'calendars.archive',
+        'calendars.days.list',
+        'calendars.days.add',
+        'calendars.days.update',
+        'calendars.days.remove',
+        'calendars.pack.preview',
+        'calendars.pack.apply',
+        'calendars.workingDays',
+    ],
+    documents: ['documents.list', 'documents.attach', 'documents.remove'],
+};
+//# sourceMappingURL=capabilities.js.map

package/dist/contract/capabilities.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"capabilities.js","sourceRoot":"","sources":["../../src/contract/capabilities.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,kBAAkB,EAAE,MAAM,mBAAmB,CAAA;AAEtD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,kBAAkB,CAAC;IAC/C;QACE,EAAE,EAAE,MAAM;QACV,KAAK,EAAE,QAAQ;QACf,WAAW,EAAE,6DAA6D;QAC1E,QAAQ,EAAE,IAAI;QACd,KAAK,EAAE,CAAC;KACT;IACD;QACE,EAAE,EAAE,SAAS;QACb,KAAK,EAAE,SAAS;QAChB,WAAW,EAAE,+EAA+E;QAC5F,SAAS,EAAE,CAAC,MAAM,CAAC;QACnB,iGAAiG;QACjG,+FAA+F;QAC/F,4FAA4F;QAC5F,+FAA+F;QAC/F,+BAA+B;QAC/B,cAAc,EAAE,KAAK;QACrB,KAAK,EAAE,CAAC;KACT;IACD;QACE,EAAE,EAAE,gBAAgB;QACpB,KAAK,EAAE,gBAAgB;QACvB,WAAW,EAAE,mEAAmE;QAChF,iGAAiG;QACjG,4EAA4E;QAC5E,SAAS,EAAE,CAAC,SAAS,CAAC;QACtB,cAAc,EAAE,KAAK;QACrB,KAAK,EAAE,CAAC;KACT;IACD;QACE,EAAE,EAAE,WAAW;QACf,KAAK,EAAE,mBAAmB;QAC1B,WAAW,EAAE,wDAAwD;QACrE,SAAS,EAAE,CAAC,MAAM,CAAC;QACnB,gGAAgG;QAChG,4CAA4C;QAC5C,cAAc,EAAE,IAAI;QACpB,KAAK,EAAE,CAAC;KACT;IACD;QACE,EAAE,EAAE,WAAW;QACf,KAAK,EAAE,oBAAoB;QAC3B,WAAW,EAAE,iEAAiE;QAC9E,SAAS,EAAE,CAAC,MAAM,CAAC;QACnB,cAAc,EAAE,KAAK;QACrB,KAAK,EAAE,CAAC;KACT;CACF,CAAC,CAAA;AAIF;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,sBAAsB,GAAsC;IACvE,OAAO,EAAE;QACP,cAAc;QACd,aAAa;QACb,gBAAgB;QAChB,gBAAgB;QAChB,iBAAiB;QACjB,oBAAoB;QACpB,gBAAgB;QAChB,kBAAkB;QAClB,gBAAgB;KACjB;IACD,cAAc,EAAE,CAAC,eAAe,EAAE,cAAc,EAAE,iBAAiB,EAAE,iBAAiB,EAAE,kBAAkB,CAAC;IAC3G,SAAS,EAAE;QACT,gBAAgB;QAChB,eAAe;QACf,kBAAkB;QAClB,kBAAkB;QAClB,mBAAmB;QACnB,qBAAqB;QACrB,oBAAoB;QACpB,uBAAuB;QACvB,uBAAuB;QACvB,wBAAwB;QACxB,sBAAsB;QACtB,uBAAuB;KACxB;IACD,SAAS,EAAE,CAAC,gBAAgB,EAAE,kBAAkB,EAAE,kBAAkB,CAAC;CACtE,CAAA"}

package/dist/contract/events.d.ts

@@ -0,0 +1,74 @@
+import { z } from 'zod';
+/**
+ * `hr.<entity>.<action>`. Anything that emits one declares it here.
+ *
+ * These are what the rest of the product reacts to. Chat wants to know when somebody joins so it can
+ * add them to a channel; a future calendar wants office holidays; payroll wants an employment
+ * change. The payloads carry ids rather than rows on purpose — a subscriber that needs the record
+ * asks for it with its own principal, so an event cannot become a way to read data past a permission
+ * check.
+ */
+export declare const hrEvents: {
+    personCreated: import("@kernhq/contracts").EventDef<"hr.person.created", z.ZodObject<{
+        personId: z.ZodUUID;
+        workspaceId: z.core.$ZodBranded<z.ZodUUID, "WorkspaceId", "out">;
+        userId: z.ZodNullable<z.ZodUUID>;
+    }, z.core.$strip>>;
+    personUpdated: import("@kernhq/contracts").EventDef<"hr.person.updated", z.ZodObject<{
+        personId: z.ZodUUID;
+        workspaceId: z.core.$ZodBranded<z.ZodUUID, "WorkspaceId", "out">;
+        fields: z.ZodArray<z.ZodString>;
+    }, z.core.$strip>>;
+    /**
+     * Status moved — onboarding to active, active to terminated.
+     *
+     * Separate from `personUpdated` because the things that care about a lifecycle change (revoking
+     * access, closing a leave balance, ending a payroll line) do not want to filter every profile
+     * edit to find it.
+     */
+    personStatusChanged: import("@kernhq/contracts").EventDef<"hr.person.status_changed", z.ZodObject<{
+        personId: z.ZodUUID;
+        workspaceId: z.core.$ZodBranded<z.ZodUUID, "WorkspaceId", "out">;
+        from: z.ZodString;
+        to: z.ZodString;
+        on: z.ZodISODate;
+    }, z.core.$strip>>;
+    employmentChanged: import("@kernhq/contracts").EventDef<"hr.employment.changed", z.ZodObject<{
+        personId: z.ZodUUID;
+        workspaceId: z.core.$ZodBranded<z.ZodUUID, "WorkspaceId", "out">;
+        employmentId: z.ZodUUID;
+        effectiveFrom: z.ZodISODate;
+    }, z.core.$strip>>;
+    /**
+     * Somebody's office changed, or their primary did.
+     *
+     * Worth its own event because the primary office decides holidays, timezone and policy: anything
+     * holding a derived answer for this person has to recompute, and this is how it finds out.
+     */
+    officeAssignmentChanged: import("@kernhq/contracts").EventDef<"hr.office_assignment.changed", z.ZodObject<{
+        personId: z.ZodUUID;
+        workspaceId: z.core.$ZodBranded<z.ZodUUID, "WorkspaceId", "out">;
+        officeId: z.ZodUUID;
+        isPrimary: z.ZodBoolean;
+        effectiveFrom: z.ZodISODate;
+    }, z.core.$strip>>;
+    officeCreated: import("@kernhq/contracts").EventDef<"hr.office.created", z.ZodObject<{
+        officeId: z.ZodUUID;
+        workspaceId: z.core.$ZodBranded<z.ZodUUID, "WorkspaceId", "out">;
+        country: z.ZodString;
+    }, z.core.$strip>>;
+    /**
+     * A calendar's days changed — a holiday added, a pack applied.
+     *
+     * Everything derived from a calendar (working days, leave day counts, later the attendance day
+     * sheet) is stale from here. The payload names the date range touched so a consumer can recompute
+     * that window rather than everything.
+     */
+    calendarChanged: import("@kernhq/contracts").EventDef<"hr.calendar.changed", z.ZodObject<{
+        calendarId: z.ZodUUID;
+        workspaceId: z.core.$ZodBranded<z.ZodUUID, "WorkspaceId", "out">;
+        from: z.ZodNullable<z.ZodISODate>;
+        to: z.ZodNullable<z.ZodISODate>;
+    }, z.core.$strip>>;
+};
+//# sourceMappingURL=events.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"events.d.ts","sourceRoot":"","sources":["../../src/contract/events.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAA;AAEvB;;;;;;;;GAQG;AACH,eAAO,MAAM,QAAQ;;;;;;;;;;;IASnB;;;;;;OAMG;;;;;;;;;;;;;;IAoBH;;;;;OAKG;;;;;;;;;;;;;IAeH;;;;;;OAMG;;;;;;;CAUJ,CAAA"}

package/dist/contract/events.js

@@ -0,0 +1,63 @@
+import { defineEvent, WorkspaceId } from '@kernhq/contracts';
+import { z } from 'zod';
+/**
+ * `hr.<entity>.<action>`. Anything that emits one declares it here.
+ *
+ * These are what the rest of the product reacts to. Chat wants to know when somebody joins so it can
+ * add them to a channel; a future calendar wants office holidays; payroll wants an employment
+ * change. The payloads carry ids rather than rows on purpose — a subscriber that needs the record
+ * asks for it with its own principal, so an event cannot become a way to read data past a permission
+ * check.
+ */
+export const hrEvents = {
+    personCreated: defineEvent('hr.person.created', z.object({ personId: z.uuid(), workspaceId: WorkspaceId, userId: z.uuid().nullable() })),
+    personUpdated: defineEvent('hr.person.updated', z.object({ personId: z.uuid(), workspaceId: WorkspaceId, fields: z.array(z.string()) })),
+    /**
+     * Status moved — onboarding to active, active to terminated.
+     *
+     * Separate from `personUpdated` because the things that care about a lifecycle change (revoking
+     * access, closing a leave balance, ending a payroll line) do not want to filter every profile
+     * edit to find it.
+     */
+    personStatusChanged: defineEvent('hr.person.status_changed', z.object({
+        personId: z.uuid(),
+        workspaceId: WorkspaceId,
+        from: z.string(),
+        to: z.string(),
+        on: z.iso.date(),
+    })),
+    employmentChanged: defineEvent('hr.employment.changed', z.object({
+        personId: z.uuid(),
+        workspaceId: WorkspaceId,
+        employmentId: z.uuid(),
+        effectiveFrom: z.iso.date(),
+    })),
+    /**
+     * Somebody's office changed, or their primary did.
+     *
+     * Worth its own event because the primary office decides holidays, timezone and policy: anything
+     * holding a derived answer for this person has to recompute, and this is how it finds out.
+     */
+    officeAssignmentChanged: defineEvent('hr.office_assignment.changed', z.object({
+        personId: z.uuid(),
+        workspaceId: WorkspaceId,
+        officeId: z.uuid(),
+        isPrimary: z.boolean(),
+        effectiveFrom: z.iso.date(),
+    })),
+    officeCreated: defineEvent('hr.office.created', z.object({ officeId: z.uuid(), workspaceId: WorkspaceId, country: z.string() })),
+    /**
+     * A calendar's days changed — a holiday added, a pack applied.
+     *
+     * Everything derived from a calendar (working days, leave day counts, later the attendance day
+     * sheet) is stale from here. The payload names the date range touched so a consumer can recompute
+     * that window rather than everything.
+     */
+    calendarChanged: defineEvent('hr.calendar.changed', z.object({
+        calendarId: z.uuid(),
+        workspaceId: WorkspaceId,
+        from: z.iso.date().nullable(),
+        to: z.iso.date().nullable(),
+    })),
+};
+//# sourceMappingURL=events.js.map

package/dist/contract/events.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"events.js","sourceRoot":"","sources":["../../src/contract/events.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,WAAW,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAA;AAC5D,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAA;AAEvB;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG;IACtB,aAAa,EAAE,WAAW,CACxB,mBAAmB,EACnB,CAAC,CAAC,MAAM,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE,EAAE,WAAW,EAAE,WAAW,EAAE,MAAM,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE,EAAE,CAAC,CACxF;IACD,aAAa,EAAE,WAAW,CACxB,mBAAmB,EACnB,CAAC,CAAC,MAAM,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE,EAAE,WAAW,EAAE,WAAW,EAAE,MAAM,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,EAAE,CAAC,CACxF;IACD;;;;;;OAMG;IACH,mBAAmB,EAAE,WAAW,CAC9B,0BAA0B,EAC1B,CAAC,CAAC,MAAM,CAAC;QACP,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE;QAClB,WAAW,EAAE,WAAW;QACxB,IAAI,EAAE,CAAC,CAAC,MAAM,EAAE;QAChB,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE;QACd,EAAE,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE;KACjB,CAAC,CACH;IACD,iBAAiB,EAAE,WAAW,CAC5B,uBAAuB,EACvB,CAAC,CAAC,MAAM,CAAC;QACP,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE;QAClB,WAAW,EAAE,WAAW;QACxB,YAAY,EAAE,CAAC,CAAC,IAAI,EAAE;QACtB,aAAa,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE;KAC5B,CAAC,CACH;IACD;;;;;OAKG;IACH,uBAAuB,EAAE,WAAW,CAClC,8BAA8B,EAC9B,CAAC,CAAC,MAAM,CAAC;QACP,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE;QAClB,WAAW,EAAE,WAAW;QACxB,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE;QAClB,SAAS,EAAE,CAAC,CAAC,OAAO,EAAE;QACtB,aAAa,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE;KAC5B,CAAC,CACH;IACD,aAAa,EAAE,WAAW,CACxB,mBAAmB,EACnB,CAAC,CAAC,MAAM,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAC,IAAI,EAAE,EAAE,WAAW,EAAE,WAAW,EAAE,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAChF;IACD;;;;;;OAMG;IACH,eAAe,EAAE,WAAW,CAC1B,qBAAqB,EACrB,CAAC,CAAC,MAAM,CAAC;QACP,UAAU,EAAE,CAAC,CAAC,IAAI,EAAE;QACpB,WAAW,EAAE,WAAW;QACxB,IAAI,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;QAC7B,EAAE,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,QAAQ,EAAE;KAC5B,CAAC,CACH;CACF,CAAA"}

package/dist/contract/index.d.ts

@@ -0,0 +1,15 @@
+/**
+ * What HR offers, as data.
+ *
+ * Imported by **both** halves — the server implements it, the client calls it — so nothing here may
+ * touch Node. The contract is the only thing that crosses that line, which is why a procedure that
+ * exists here and not in the router is a lie that compiles. `module.test.ts` checks exactly that,
+ * and also that every procedure listed in `hrCapabilityProcedures` carries its capability guard.
+ */
+export * from './capabilities.js';
+export * from './events.js';
+export * from './models.js';
+export * from './permissions.js';
+export * from './router.js';
+export * from './settings.js';
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/contract/index.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AACH,cAAc,mBAAmB,CAAA;AACjC,cAAc,aAAa,CAAA;AAC3B,cAAc,aAAa,CAAA;AAC3B,cAAc,kBAAkB,CAAA;AAChC,cAAc,aAAa,CAAA;AAC3B,cAAc,eAAe,CAAA"}

package/dist/contract/index.js

@@ -0,0 +1,15 @@
+/**
+ * What HR offers, as data.
+ *
+ * Imported by **both** halves — the server implements it, the client calls it — so nothing here may
+ * touch Node. The contract is the only thing that crosses that line, which is why a procedure that
+ * exists here and not in the router is a lie that compiles. `module.test.ts` checks exactly that,
+ * and also that every procedure listed in `hrCapabilityProcedures` carries its capability guard.
+ */
+export * from './capabilities.js';
+export * from './events.js';
+export * from './models.js';
+export * from './permissions.js';
+export * from './router.js';
+export * from './settings.js';
+//# sourceMappingURL=index.js.map

package/dist/contract/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/contract/index.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AACH,cAAc,mBAAmB,CAAA;AACjC,cAAc,aAAa,CAAA;AAC3B,cAAc,aAAa,CAAA;AAC3B,cAAc,kBAAkB,CAAA;AAChC,cAAc,aAAa,CAAA;AAC3B,cAAc,eAAe,CAAA"}