@persei/perseed-api 5.0.22 → 5.0.24

package/dist/ecosystem-process-log.mjs

@@ -0,0 +1,234 @@
+import { Type } from "typebox";
+import { b as apiDateTime, a as API_DATETIME_EXAMPLE, A as API_DATETIME_ACCEPTED_NOTE, E as EMITTED_DATETIME_NOTE } from "./dates.schema-BqkBcmM6.js";
+const ProcessLogType = {
+  LOG: 0,
+  RESULT: 1,
+  WARNING: -1,
+  ERROR: -2
+};
+const processLogTypeSchema = Type.Enum(Object.values(ProcessLogType), {
+  title: "ProcessLogType",
+  description: "Severity of the log row (not a layout/kind marker): LOG, RESULT, WARNING or ERROR"
+});
+const ProcessLogCode = {
+  BULK_UPLOAD_BATCH: "bulk_upload_batch",
+  BULK_UPLOAD_SUCCESS: "bulk_upload_success",
+  BULK_UPLOAD_ERROR: "bulk_upload_error",
+  // Trigger engine (#348). Written by `TriggerEngineService` (`action-system` module): one
+  // `TRIGGER_EVALUATION` row per trigger evaluated, one `TRIGGER_ACTION` row per action it ran, and a
+  // `TRIGGER_ERROR` row when a trigger's evaluation throws.
+  TRIGGER_EVALUATION: "trigger_evaluation",
+  TRIGGER_ERROR: "trigger_error",
+  TRIGGER_ACTION: "trigger_action"
+};
+const processLogCodeSchema = Type.Enum(Object.values(ProcessLogCode), {
+  title: "ProcessLogCode",
+  description: "What kind of event a process_log row records, and what shape its extra_data takes"
+});
+const triggerEvaluationExtraDataSchema = Type.Object(
+  {
+    source: Type.String({ description: "What fired the event: a model row or a displayer/form save" }),
+    target: Type.Optional(
+      Type.Union([Type.String(), Type.Null()], { description: "Model/displayer name the trigger is bound to" })
+    ),
+    operation: Type.Optional(
+      Type.Union([Type.String(), Type.Null()], { description: "create/update/delete that fired the event" })
+    ),
+    matched: Type.Boolean({ description: "Whether the trigger conditions matched" }),
+    conditions: Type.Optional(
+      Type.Union([Type.Unknown(), Type.Null()], {
+        description: "jsonLogic conditions the trigger was configured with"
+      })
+    ),
+    relations: Type.Optional(
+      Type.Union([Type.Unknown(), Type.Null()], {
+        description: "Relations the trigger declared to load onto `current`"
+      })
+    ),
+    relationsSkipped: Type.Optional(
+      Type.Union([Type.String(), Type.Null()], {
+        description: "Reason a declared relation could not be loaded, when one was skipped"
+      })
+    )
+  },
+  {
+    title: "TriggerEvaluationExtraData",
+    description: "extra_data of a `trigger_evaluation` row — how a trigger resolved, never the entity data it resolved against",
+    additionalProperties: false
+  }
+);
+const triggerErrorExtraDataSchema = Type.Object(
+  { error: Type.String({ description: "String representation of the exception the trigger evaluation threw" }) },
+  { title: "TriggerErrorExtraData", description: "extra_data of a `trigger_error` row", additionalProperties: false }
+);
+const triggerActionExtraDataSchema = Type.Object(
+  {
+    actionId: Type.Number({ description: "id of the action row that ran" }),
+    triggerId: Type.Number({ description: "id of the trigger that ran this action" }),
+    // Needed because the engine is shared: `triggerId` alone is ambiguous, since automatic and
+    // manual triggers are different tables (`automatic_trigger`, `manual_trigger`) with overlapping
+    // id ranges. Paired with `triggerId` this is what a consumer needs to resolve the trigger row.
+    triggerModel: Type.String({ description: "Table the trigger belongs to (automatic_trigger or manual_trigger)" }),
+    executionOrder: Type.Number({ description: "Order of this action within the trigger" }),
+    type: Type.String({ description: "Type of the action (e.g. ApiAction)" }),
+    validation: Type.Unknown({ description: "Result of validating the action context before running it" }),
+    // `ok`/`output` describe an action that ran; `aborted`/`reason` an action that never did,
+    // because validating its context failed (`resolveActionOutcome`). The two pairs are mutually
+    // exclusive in practice but declared as four optionals rather than a union: `additionalProperties:
+    // false` is what makes this schema worth having, and a row whose outcome keys are undeclared is
+    // one the debugging popup cannot show a reason for — which is exactly the aborted case.
+    ok: Type.Optional(Type.Union([Type.Boolean(), Type.Null()], { description: "Whether the action call succeeded" })),
+    output: Type.Optional(
+      Type.Union([Type.String(), Type.Null()], { description: "Failure output, when the action ran and failed" })
+    ),
+    aborted: Type.Optional(Type.Boolean({ description: "True when the action never ran" })),
+    reason: Type.Optional(Type.String({ description: "Why the action was aborted, e.g. context_validation" }))
+  },
+  { title: "TriggerActionExtraData", description: "extra_data of a `trigger_action` row", additionalProperties: false }
+);
+const processLogTriggerEngineExtraDataSchema = Type.Union(
+  [
+    Type.Object({
+      code: Type.Literal(ProcessLogCode.TRIGGER_EVALUATION),
+      extra_data: triggerEvaluationExtraDataSchema
+    }),
+    Type.Object({ code: Type.Literal(ProcessLogCode.TRIGGER_ERROR), extra_data: triggerErrorExtraDataSchema }),
+    Type.Object({ code: Type.Literal(ProcessLogCode.TRIGGER_ACTION), extra_data: triggerActionExtraDataSchema })
+  ],
+  {
+    title: "ProcessLogTriggerEngineExtraData",
+    description: "Ties each trigger-engine `code` to the shape its `extra_data` takes"
+  }
+);
+const processLogSchema = Type.Object(
+  {
+    id: Type.Number({ description: "Unique identifier of the row" }),
+    project_id: Type.Optional(
+      Type.Union([Type.Number(), Type.Null()], { description: "Project this row belongs to, when scoped to one" })
+    ),
+    created_user: Type.Optional(
+      Type.Union([Type.Number(), Type.Null()], {
+        description: "User who caused the row to be written, when a user did"
+      })
+    ),
+    related_model: Type.Optional(
+      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], { description: "Table/entity kind the row is about" })
+    ),
+    related_id: Type.Optional(
+      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], {
+        description: "Id of the related entity, as a string"
+      })
+    ),
+    code: Type.Optional(Type.Union([processLogCodeSchema, Type.Null()])),
+    log: Type.String({ description: "Short human-readable message" }),
+    long_log: Type.Optional(Type.Union([Type.String(), Type.Null()], { description: "Extended message, when needed" })),
+    extra_data: Type.Optional(
+      Type.Union([Type.Record(Type.String(), Type.Unknown()), Type.Null()], {
+        description: "Structured data specific to `code` — see the per-code schemas for the trigger-engine codes"
+      })
+    ),
+    type: processLogTypeSchema,
+    requires_attention: Type.Optional(Type.Boolean({ description: "Whether the row needs a human to review it" })),
+    reviewed: Type.Optional(Type.Boolean({ description: "Whether the row has been reviewed" })),
+    reviewed_date: Type.Optional(
+      Type.Union([Type.String(), Type.Null()], {
+        description: `When the row was reviewed. Null while unreviewed. ${EMITTED_DATETIME_NOTE}`
+      })
+    ),
+    // Correlation to a parent row (#348): a `trigger_action` row's parent is the `trigger_evaluation`
+    // (or `trigger_error`) row of the trigger that ran it, so an action's trace can always be walked
+    // back to the evaluation that triggered it. Optional/nullable because most rows (bulk upload,
+    // the trigger-evaluation row itself) have no parent, and because the column is applied out of
+    // band per ecosystem — see README.md — so it may be entirely absent from a given row's database.
+    parent_id: Type.Optional(
+      Type.Union([Type.Number(), Type.Null()], {
+        description: "Id of this row's parent process_log row, when it has one"
+      })
+    ),
+    // `subject_*` vs `related_*` (both #348, see README.md "`related_*` vs `subject_*`"):
+    // `related_model`/`related_id` above name the row's own subject — the trigger or the action the
+    // row is about. `subject_model`/`subject_id` name the domain entity that originated the
+    // execution (a patient, a form...), so "what triggers ran from this entity" can be answered by
+    // filtering on them. A `trigger_action` row inherits the same subject as the `trigger_evaluation`
+    // row of the trigger that ran it — it is the batch's subject, not the action's own. Optional/
+    // nullable for the same two reasons as `parent_id`: most rows have none (there may be no
+    // resolvable subject for a batch, or the row predates this column), and the column is applied
+    // out of band per ecosystem, so it may be entirely absent from a given row's database.
+    subject_model: Type.Optional(
+      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], {
+        description: "Domain entity kind that originated the execution (e.g. patient), when resolvable"
+      })
+    ),
+    subject_id: Type.Optional(
+      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], {
+        description: "Id of the domain entity that originated the execution, as a string, when resolvable"
+      })
+    ),
+    expires_at: Type.Optional(
+      Type.Union([Type.String(), Type.Null()], {
+        description: `Retention deadline; the row is purged after it, and never expires when null. ${EMITTED_DATETIME_NOTE}`,
+        examples: [API_DATETIME_EXAMPLE]
+      })
+    ),
+    created_at: Type.Optional(
+      Type.String({
+        description: `When the row was created. ${EMITTED_DATETIME_NOTE}`,
+        examples: [API_DATETIME_EXAMPLE]
+      })
+    ),
+    mod_time: Type.Optional(
+      Type.String({
+        description: `When the row was last modified. ${EMITTED_DATETIME_NOTE}`,
+        examples: [API_DATETIME_EXAMPLE]
+      })
+    )
+  },
+  { title: "ProcessLog", description: "A process_log row" }
+);
+const listProcessLogQuerySchema = Type.Object(
+  {
+    code: Type.Optional(processLogCodeSchema),
+    type: Type.Optional(processLogTypeSchema),
+    related_model: Type.Optional(Type.String({ description: "Filter by the related entity kind" })),
+    related_id: Type.Optional(Type.String({ description: "Filter by the id of the related entity" })),
+    parent_id: Type.Optional(Type.Number({ description: "Filter by the id of the parent process_log row" })),
+    subject_model: Type.Optional(
+      Type.String({ description: "Filter by the domain entity kind that originated the execution" })
+    ),
+    subject_id: Type.Optional(
+      Type.String({ description: "Filter by the id of the domain entity that originated the execution" })
+    ),
+    requires_attention: Type.Optional(Type.Boolean({ description: "Filter by whether the row needs review" })),
+    reviewed: Type.Optional(Type.Boolean({ description: "Filter by whether the row has been reviewed" })),
+    // `apiDateTime`, not a bare string: it carries `format: 'date-time'`, so a malformed value is
+    // rejected by the validator as a 400. A plain `Type.String` accepts anything and hands it to
+    // `getMySQLDateTime(value, true)`, which throws a `PublicApiError` with no `statusCode` — a 500
+    // for what is a bad request. Same type `alert.schema.ts` uses for its datetime fields.
+    created_from: Type.Optional(
+      Type.Union([apiDateTime], {
+        description: `Only rows created at or after this instant. ${API_DATETIME_ACCEPTED_NOTE}. ${EMITTED_DATETIME_NOTE}`,
+        examples: [API_DATETIME_EXAMPLE]
+      })
+    ),
+    created_to: Type.Optional(
+      Type.Union([apiDateTime], {
+        description: `Only rows created at or before this instant. ${API_DATETIME_ACCEPTED_NOTE}. ${EMITTED_DATETIME_NOTE}`,
+        examples: [API_DATETIME_EXAMPLE]
+      })
+    )
+  },
+  { title: "ListProcessLogQuery", description: "Filters available on the process_log list" }
+);
+export {
+  ProcessLogCode,
+  ProcessLogType,
+  listProcessLogQuerySchema,
+  processLogCodeSchema,
+  processLogSchema,
+  processLogTriggerEngineExtraDataSchema,
+  processLogTypeSchema,
+  triggerActionExtraDataSchema,
+  triggerErrorExtraDataSchema,
+  triggerEvaluationExtraDataSchema
+};
+//# sourceMappingURL=ecosystem-process-log.mjs.map

package/dist/ecosystem-process-log.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"ecosystem-process-log.mjs","sources":["../../src/v2/modules/ecosystem/process-log/process-log.schema.ts"],"sourcesContent":["import { Type, Static, StaticDecode } from 'typebox'\n// From the schema file, not the module barrel (`@/modules/global/dates`) that every other consumer\n// imports — the one place where `no-restricted-imports` has to give way, hence the disable.\n//\n// This module has a `lib.ts`, so this file is an entry point of the published `@persei/perseed-api`\n// bundle, which is browser code. The barrel re-exports `dates.middleware`, a `fastify-plugin` that\n// pulls in `@v1/log/debug` and, transitively, the server dependencies behind it; bundling that\n// fails, and it fails naming a transitive JSON file (`ent/reversed.json: Could not parse JSON\n// file`) rather than the import that dragged it in, so the message points nowhere near the cause.\n//\n// `global/dates`'s own `lib.ts` sidesteps the same barrel for the same reason. The alternative —\n// inlining the two description constants — would duplicate the wording the whole API documents its\n// datetimes with, and let this module's copy drift from it silently.\n// eslint-disable-next-line no-restricted-imports\nimport {\n  EMITTED_DATETIME_NOTE,\n  API_DATETIME_EXAMPLE,\n  API_DATETIME_ACCEPTED_NOTE,\n  apiDateTime,\n} from '@/modules/global/dates/dates.schema'\n\n// `process_log` is the ecosystem-wide execution log (see README.md): rows written by the trigger\n// engine, the actions it runs and the v1 bulk upload. This module owns the schema for the whole\n// table, not only the trigger-engine rows — `code` is what tells them apart.\n\n// ── ProcessLogType (severity, NOT layout) ───────────────────────────────\n// Mirrors the v1 enum (`src/schemas/process_log/types.ts`) verbatim: it already ships on the wire\n// (`type` column) and changing its numeric values would be a breaking change for every existing row\n// and consumer. Restated here as a TypeBox schema — not imported from v1 — because `lib.ts` may\n// only export pure TypeBox (see below); v1 has no schema module of its own to import from.\nexport const ProcessLogType = {\n  LOG: 0,\n  RESULT: 1,\n  WARNING: -1,\n  ERROR: -2,\n} as const\nexport const processLogTypeSchema = Type.Enum(Object.values(ProcessLogType), {\n  title: 'ProcessLogType',\n  description: 'Severity of the log row (not a layout/kind marker): LOG, RESULT, WARNING or ERROR',\n})\nexport type ProcessLogType = Static<typeof processLogTypeSchema>\n\n// ── ProcessLogCode ───────────────────────────────────────────────────────\n//\n// Canonical enum now lives HERE (v2), not in `src/schemas/process_log/types.ts` (v1).\n//\n// Why: this module (`process-log`) is the one being extended with the trigger-engine codes as part\n// of #348, it already owns the model/service half of `process_log`, and every v2 consumer that needs\n// a *typed* extra_data contract (this schema file) has to sit next to the code enum it is keyed by.\n// The two v1 importers (`BulkUploadController.ts` and `IntrospectionController.ts`) import it from\n// here rather than from `@v1/schemas`, which keeps one enum instead of two that could drift. v1's\n// `types.ts` deliberately does NOT re-export the value: doing so closes the cycle `@v1/schemas` →\n// this module's barrel → `process-log.model.ts` → `@v1/schemas`, under which the enum resolves to\n// `undefined` at runtime. It keeps an `import type` only, which is erased at compile time.\nexport const ProcessLogCode = {\n  BULK_UPLOAD_BATCH: 'bulk_upload_batch',\n  BULK_UPLOAD_SUCCESS: 'bulk_upload_success',\n  BULK_UPLOAD_ERROR: 'bulk_upload_error',\n  // Trigger engine (#348). Written by `TriggerEngineService` (`action-system` module): one\n  // `TRIGGER_EVALUATION` row per trigger evaluated, one `TRIGGER_ACTION` row per action it ran, and a\n  // `TRIGGER_ERROR` row when a trigger's evaluation throws.\n  TRIGGER_EVALUATION: 'trigger_evaluation',\n  TRIGGER_ERROR: 'trigger_error',\n  TRIGGER_ACTION: 'trigger_action',\n} as const\nexport const processLogCodeSchema = Type.Enum(Object.values(ProcessLogCode), {\n  title: 'ProcessLogCode',\n  description: 'What kind of event a process_log row records, and what shape its extra_data takes',\n})\nexport type ProcessLogCode = Static<typeof processLogCodeSchema>\n\n// ── extra_data shapes, one per trigger-engine code ───────────────────────\n// Bulk upload codes carry no typed extra_data today (nothing writes them yet outside the\n// filter-by-code reads in `BulkUploadController.ts`), so they are left out of the discriminated\n// union below rather than given a placeholder shape that no writer populates.\n\nexport const triggerEvaluationExtraDataSchema = Type.Object(\n  {\n    source: Type.String({ description: 'What fired the event: a model row or a displayer/form save' }),\n    target: Type.Optional(\n      Type.Union([Type.String(), Type.Null()], { description: 'Model/displayer name the trigger is bound to' }),\n    ),\n    operation: Type.Optional(\n      Type.Union([Type.String(), Type.Null()], { description: 'create/update/delete that fired the event' }),\n    ),\n    matched: Type.Boolean({ description: 'Whether the trigger conditions matched' }),\n    conditions: Type.Optional(\n      Type.Union([Type.Unknown(), Type.Null()], {\n        description: 'jsonLogic conditions the trigger was configured with',\n      }),\n    ),\n    relations: Type.Optional(\n      Type.Union([Type.Unknown(), Type.Null()], {\n        description: 'Relations the trigger declared to load onto `current`',\n      }),\n    ),\n    relationsSkipped: Type.Optional(\n      Type.Union([Type.String(), Type.Null()], {\n        description: 'Reason a declared relation could not be loaded, when one was skipped',\n      }),\n    ),\n  },\n  {\n    title: 'TriggerEvaluationExtraData',\n    description:\n      'extra_data of a `trigger_evaluation` row — how a trigger resolved, never the entity data it resolved against',\n    additionalProperties: false,\n  },\n)\nexport type TriggerEvaluationExtraData = Static<typeof triggerEvaluationExtraDataSchema>\n\nexport const triggerErrorExtraDataSchema = Type.Object(\n  { error: Type.String({ description: 'String representation of the exception the trigger evaluation threw' }) },\n  { title: 'TriggerErrorExtraData', description: 'extra_data of a `trigger_error` row', additionalProperties: false },\n)\nexport type TriggerErrorExtraData = Static<typeof triggerErrorExtraDataSchema>\n\nexport const triggerActionExtraDataSchema = Type.Object(\n  {\n    actionId: Type.Number({ description: 'id of the action row that ran' }),\n    triggerId: Type.Number({ description: 'id of the trigger that ran this action' }),\n    // Needed because the engine is shared: `triggerId` alone is ambiguous, since automatic and\n    // manual triggers are different tables (`automatic_trigger`, `manual_trigger`) with overlapping\n    // id ranges. Paired with `triggerId` this is what a consumer needs to resolve the trigger row.\n    triggerModel: Type.String({ description: 'Table the trigger belongs to (automatic_trigger or manual_trigger)' }),\n    executionOrder: Type.Number({ description: 'Order of this action within the trigger' }),\n    type: Type.String({ description: 'Type of the action (e.g. ApiAction)' }),\n    validation: Type.Unknown({ description: 'Result of validating the action context before running it' }),\n    // `ok`/`output` describe an action that ran; `aborted`/`reason` an action that never did,\n    // because validating its context failed (`resolveActionOutcome`). The two pairs are mutually\n    // exclusive in practice but declared as four optionals rather than a union: `additionalProperties:\n    // false` is what makes this schema worth having, and a row whose outcome keys are undeclared is\n    // one the debugging popup cannot show a reason for — which is exactly the aborted case.\n    ok: Type.Optional(Type.Union([Type.Boolean(), Type.Null()], { description: 'Whether the action call succeeded' })),\n    output: Type.Optional(\n      Type.Union([Type.String(), Type.Null()], { description: 'Failure output, when the action ran and failed' }),\n    ),\n    aborted: Type.Optional(Type.Boolean({ description: 'True when the action never ran' })),\n    reason: Type.Optional(Type.String({ description: 'Why the action was aborted, e.g. context_validation' })),\n  },\n  { title: 'TriggerActionExtraData', description: 'extra_data of a `trigger_action` row', additionalProperties: false },\n)\nexport type TriggerActionExtraData = Static<typeof triggerActionExtraDataSchema>\n\n// Discriminated (by `code`) union tying each trigger-engine code to its extra_data shape. Usable\n// both to validate a row being created and to type one being read. Bulk upload codes are\n// deliberately absent (see comment above the individual schemas).\nexport const processLogTriggerEngineExtraDataSchema = Type.Union(\n  [\n    Type.Object({\n      code: Type.Literal(ProcessLogCode.TRIGGER_EVALUATION),\n      extra_data: triggerEvaluationExtraDataSchema,\n    }),\n    Type.Object({ code: Type.Literal(ProcessLogCode.TRIGGER_ERROR), extra_data: triggerErrorExtraDataSchema }),\n    Type.Object({ code: Type.Literal(ProcessLogCode.TRIGGER_ACTION), extra_data: triggerActionExtraDataSchema }),\n  ],\n  {\n    title: 'ProcessLogTriggerEngineExtraData',\n    description: 'Ties each trigger-engine `code` to the shape its `extra_data` takes',\n  },\n)\nexport type ProcessLogTriggerEngineExtraData = Static<typeof processLogTriggerEngineExtraDataSchema>\n\n// ── process_log entity ────────────────────────────────────────────────────\n// Full row shape, for the read side of the (still to be implemented) list endpoint. `extra_data` is\n// left as a free record here — a response schema describes what every row of the table can hold,\n// including the untyped bulk_upload rows, unlike `processLogTriggerEngineExtraDataSchema` above\n// which narrows by `code` for a writer/reader that already knows it is on the trigger-engine path.\nexport const processLogSchema = Type.Object(\n  {\n    id: Type.Number({ description: 'Unique identifier of the row' }),\n    project_id: Type.Optional(\n      Type.Union([Type.Number(), Type.Null()], { description: 'Project this row belongs to, when scoped to one' }),\n    ),\n    created_user: Type.Optional(\n      Type.Union([Type.Number(), Type.Null()], {\n        description: 'User who caused the row to be written, when a user did',\n      }),\n    ),\n    related_model: Type.Optional(\n      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], { description: 'Table/entity kind the row is about' }),\n    ),\n    related_id: Type.Optional(\n      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], {\n        description: 'Id of the related entity, as a string',\n      }),\n    ),\n    code: Type.Optional(Type.Union([processLogCodeSchema, Type.Null()])),\n    log: Type.String({ description: 'Short human-readable message' }),\n    long_log: Type.Optional(Type.Union([Type.String(), Type.Null()], { description: 'Extended message, when needed' })),\n    extra_data: Type.Optional(\n      Type.Union([Type.Record(Type.String(), Type.Unknown()), Type.Null()], {\n        description: 'Structured data specific to `code` — see the per-code schemas for the trigger-engine codes',\n      }),\n    ),\n    type: processLogTypeSchema,\n    requires_attention: Type.Optional(Type.Boolean({ description: 'Whether the row needs a human to review it' })),\n    reviewed: Type.Optional(Type.Boolean({ description: 'Whether the row has been reviewed' })),\n    reviewed_date: Type.Optional(\n      Type.Union([Type.String(), Type.Null()], {\n        description: `When the row was reviewed. Null while unreviewed. ${EMITTED_DATETIME_NOTE}`,\n      }),\n    ),\n    // Correlation to a parent row (#348): a `trigger_action` row's parent is the `trigger_evaluation`\n    // (or `trigger_error`) row of the trigger that ran it, so an action's trace can always be walked\n    // back to the evaluation that triggered it. Optional/nullable because most rows (bulk upload,\n    // the trigger-evaluation row itself) have no parent, and because the column is applied out of\n    // band per ecosystem — see README.md — so it may be entirely absent from a given row's database.\n    parent_id: Type.Optional(\n      Type.Union([Type.Number(), Type.Null()], {\n        description: \"Id of this row's parent process_log row, when it has one\",\n      }),\n    ),\n    // `subject_*` vs `related_*` (both #348, see README.md \"`related_*` vs `subject_*`\"):\n    // `related_model`/`related_id` above name the row's own subject — the trigger or the action the\n    // row is about. `subject_model`/`subject_id` name the domain entity that originated the\n    // execution (a patient, a form...), so \"what triggers ran from this entity\" can be answered by\n    // filtering on them. A `trigger_action` row inherits the same subject as the `trigger_evaluation`\n    // row of the trigger that ran it — it is the batch's subject, not the action's own. Optional/\n    // nullable for the same two reasons as `parent_id`: most rows have none (there may be no\n    // resolvable subject for a batch, or the row predates this column), and the column is applied\n    // out of band per ecosystem, so it may be entirely absent from a given row's database.\n    subject_model: Type.Optional(\n      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], {\n        description: 'Domain entity kind that originated the execution (e.g. patient), when resolvable',\n      }),\n    ),\n    subject_id: Type.Optional(\n      Type.Union([Type.String({ maxLength: 255 }), Type.Null()], {\n        description: 'Id of the domain entity that originated the execution, as a string, when resolvable',\n      }),\n    ),\n    expires_at: Type.Optional(\n      Type.Union([Type.String(), Type.Null()], {\n        description: `Retention deadline; the row is purged after it, and never expires when null. ${EMITTED_DATETIME_NOTE}`,\n        examples: [API_DATETIME_EXAMPLE],\n      }),\n    ),\n    created_at: Type.Optional(\n      Type.String({\n        description: `When the row was created. ${EMITTED_DATETIME_NOTE}`,\n        examples: [API_DATETIME_EXAMPLE],\n      }),\n    ),\n    mod_time: Type.Optional(\n      Type.String({\n        description: `When the row was last modified. ${EMITTED_DATETIME_NOTE}`,\n        examples: [API_DATETIME_EXAMPLE],\n      }),\n    ),\n  },\n  { title: 'ProcessLog', description: 'A process_log row' },\n)\nexport type ProcessLogData = Static<typeof processLogSchema>\n\n// ── list query filters ────────────────────────────────────────────────────\n// Filters of the (upcoming) list endpoint, on top of the pagination query — see `alert.schema.ts`\n// `listAlertQuerySchema` for the sibling precedent. Everything is optional: with none of them the\n// endpoint lists everything in scope. Exported for the endpoint (implemented separately) to consume.\nexport const listProcessLogQuerySchema = Type.Object(\n  {\n    code: Type.Optional(processLogCodeSchema),\n    type: Type.Optional(processLogTypeSchema),\n    related_model: Type.Optional(Type.String({ description: 'Filter by the related entity kind' })),\n    related_id: Type.Optional(Type.String({ description: 'Filter by the id of the related entity' })),\n    parent_id: Type.Optional(Type.Number({ description: 'Filter by the id of the parent process_log row' })),\n    subject_model: Type.Optional(\n      Type.String({ description: 'Filter by the domain entity kind that originated the execution' }),\n    ),\n    subject_id: Type.Optional(\n      Type.String({ description: 'Filter by the id of the domain entity that originated the execution' }),\n    ),\n    requires_attention: Type.Optional(Type.Boolean({ description: 'Filter by whether the row needs review' })),\n    reviewed: Type.Optional(Type.Boolean({ description: 'Filter by whether the row has been reviewed' })),\n    // `apiDateTime`, not a bare string: it carries `format: 'date-time'`, so a malformed value is\n    // rejected by the validator as a 400. A plain `Type.String` accepts anything and hands it to\n    // `getMySQLDateTime(value, true)`, which throws a `PublicApiError` with no `statusCode` — a 500\n    // for what is a bad request. Same type `alert.schema.ts` uses for its datetime fields.\n    created_from: Type.Optional(\n      Type.Union([apiDateTime], {\n        description: `Only rows created at or after this instant. ${API_DATETIME_ACCEPTED_NOTE}. ${EMITTED_DATETIME_NOTE}`,\n        examples: [API_DATETIME_EXAMPLE],\n      }),\n    ),\n    created_to: Type.Optional(\n      Type.Union([apiDateTime], {\n        description: `Only rows created at or before this instant. ${API_DATETIME_ACCEPTED_NOTE}. ${EMITTED_DATETIME_NOTE}`,\n        examples: [API_DATETIME_EXAMPLE],\n      }),\n    ),\n  },\n  { title: 'ListProcessLogQuery', description: 'Filters available on the process_log list' },\n)\n// `StaticDecode`, not `Static`: this type describes what the *handler receives*, and the two date\n// bounds carry `apiDateTime`, so they arrive decoded to a `Date`. `Static` would type them as the\n// strings the client sent and the service would format something it never gets.\nexport type ListProcessLogQuery = StaticDecode<typeof listProcessLogQuerySchema>\n"],"names":[],"mappings":";;AA8BO,MAAM,iBAAiB;AAAA,EAC5B,KAAK;AAAA,EACL,QAAQ;AAAA,EACR,SAAS;AAAA,EACT,OAAO;AACT;AACO,MAAM,uBAAuB,KAAK,KAAK,OAAO,OAAO,cAAc,GAAG;AAAA,EAC3E,OAAO;AAAA,EACP,aAAa;AACf,CAAC;AAeM,MAAM,iBAAiB;AAAA,EAC5B,mBAAmB;AAAA,EACnB,qBAAqB;AAAA,EACrB,mBAAmB;AAAA;AAAA;AAAA;AAAA,EAInB,oBAAoB;AAAA,EACpB,eAAe;AAAA,EACf,gBAAgB;AAClB;AACO,MAAM,uBAAuB,KAAK,KAAK,OAAO,OAAO,cAAc,GAAG;AAAA,EAC3E,OAAO;AAAA,EACP,aAAa;AACf,CAAC;AAQM,MAAM,mCAAmC,KAAK;AAAA,EACnD;AAAA,IACE,QAAQ,KAAK,OAAO,EAAE,aAAa,8DAA8D;AAAA,IACjG,QAAQ,KAAK;AAAA,MACX,KAAK,MAAM,CAAC,KAAK,OAAA,GAAU,KAAK,MAAM,GAAG,EAAE,aAAa,gDAAgD;AAAA,IAAA;AAAA,IAE1G,WAAW,KAAK;AAAA,MACd,KAAK,MAAM,CAAC,KAAK,OAAA,GAAU,KAAK,MAAM,GAAG,EAAE,aAAa,6CAA6C;AAAA,IAAA;AAAA,IAEvG,SAAS,KAAK,QAAQ,EAAE,aAAa,0CAA0C;AAAA,IAC/E,YAAY,KAAK;AAAA,MACf,KAAK,MAAM,CAAC,KAAK,WAAW,KAAK,KAAA,CAAM,GAAG;AAAA,QACxC,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,IAEH,WAAW,KAAK;AAAA,MACd,KAAK,MAAM,CAAC,KAAK,WAAW,KAAK,KAAA,CAAM,GAAG;AAAA,QACxC,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,IAEH,kBAAkB,KAAK;AAAA,MACrB,KAAK,MAAM,CAAC,KAAK,UAAU,KAAK,KAAA,CAAM,GAAG;AAAA,QACvC,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,EACH;AAAA,EAEF;AAAA,IACE,OAAO;AAAA,IACP,aACE;AAAA,IACF,sBAAsB;AAAA,EAAA;AAE1B;AAGO,MAAM,8BAA8B,KAAK;AAAA,EAC9C,EAAE,OAAO,KAAK,OAAO,EAAE,aAAa,sEAAA,CAAuE,EAAA;AAAA,EAC3G,EAAE,OAAO,yBAAyB,aAAa,uCAAuC,sBAAsB,MAAA;AAC9G;AAGO,MAAM,+BAA+B,KAAK;AAAA,EAC/C;AAAA,IACE,UAAU,KAAK,OAAO,EAAE,aAAa,iCAAiC;AAAA,IACtE,WAAW,KAAK,OAAO,EAAE,aAAa,0CAA0C;AAAA;AAAA;AAAA;AAAA,IAIhF,cAAc,KAAK,OAAO,EAAE,aAAa,sEAAsE;AAAA,IAC/G,gBAAgB,KAAK,OAAO,EAAE,aAAa,2CAA2C;AAAA,IACtF,MAAM,KAAK,OAAO,EAAE,aAAa,uCAAuC;AAAA,IACxE,YAAY,KAAK,QAAQ,EAAE,aAAa,6DAA6D;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAMrG,IAAI,KAAK,SAAS,KAAK,MAAM,CAAC,KAAK,QAAA,GAAW,KAAK,MAAM,GAAG,EAAE,aAAa,oCAAA,CAAqC,CAAC;AAAA,IACjH,QAAQ,KAAK;AAAA,MACX,KAAK,MAAM,CAAC,KAAK,OAAA,GAAU,KAAK,MAAM,GAAG,EAAE,aAAa,kDAAkD;AAAA,IAAA;AAAA,IAE5G,SAAS,KAAK,SAAS,KAAK,QAAQ,EAAE,aAAa,iCAAA,CAAkC,CAAC;AAAA,IACtF,QAAQ,KAAK,SAAS,KAAK,OAAO,EAAE,aAAa,uDAAuD,CAAC;AAAA,EAAA;AAAA,EAE3G,EAAE,OAAO,0BAA0B,aAAa,wCAAwC,sBAAsB,MAAA;AAChH;AAMO,MAAM,yCAAyC,KAAK;AAAA,EACzD;AAAA,IACE,KAAK,OAAO;AAAA,MACV,MAAM,KAAK,QAAQ,eAAe,kBAAkB;AAAA,MACpD,YAAY;AAAA,IAAA,CACb;AAAA,IACD,KAAK,OAAO,EAAE,MAAM,KAAK,QAAQ,eAAe,aAAa,GAAG,YAAY,6BAA6B;AAAA,IACzG,KAAK,OAAO,EAAE,MAAM,KAAK,QAAQ,eAAe,cAAc,GAAG,YAAY,6BAAA,CAA8B;AAAA,EAAA;AAAA,EAE7G;AAAA,IACE,OAAO;AAAA,IACP,aAAa;AAAA,EAAA;AAEjB;AAQO,MAAM,mBAAmB,KAAK;AAAA,EACnC;AAAA,IACE,IAAI,KAAK,OAAO,EAAE,aAAa,gCAAgC;AAAA,IAC/D,YAAY,KAAK;AAAA,MACf,KAAK,MAAM,CAAC,KAAK,OAAA,GAAU,KAAK,MAAM,GAAG,EAAE,aAAa,mDAAmD;AAAA,IAAA;AAAA,IAE7G,cAAc,KAAK;AAAA,MACjB,KAAK,MAAM,CAAC,KAAK,UAAU,KAAK,KAAA,CAAM,GAAG;AAAA,QACvC,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,IAEH,eAAe,KAAK;AAAA,MAClB,KAAK,MAAM,CAAC,KAAK,OAAO,EAAE,WAAW,KAAK,GAAG,KAAK,KAAA,CAAM,GAAG,EAAE,aAAa,sCAAsC;AAAA,IAAA;AAAA,IAElH,YAAY,KAAK;AAAA,MACf,KAAK,MAAM,CAAC,KAAK,OAAO,EAAE,WAAW,KAAK,GAAG,KAAK,KAAA,CAAM,GAAG;AAAA,QACzD,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,IAEH,MAAM,KAAK,SAAS,KAAK,MAAM,CAAC,sBAAsB,KAAK,KAAA,CAAM,CAAC,CAAC;AAAA,IACnE,KAAK,KAAK,OAAO,EAAE,aAAa,gCAAgC;AAAA,IAChE,UAAU,KAAK,SAAS,KAAK,MAAM,CAAC,KAAK,OAAA,GAAU,KAAK,MAAM,GAAG,EAAE,aAAa,gCAAA,CAAiC,CAAC;AAAA,IAClH,YAAY,KAAK;AAAA,MACf,KAAK,MAAM,CAAC,KAAK,OAAO,KAAK,UAAU,KAAK,SAAS,GAAG,KAAK,KAAA,CAAM,GAAG;AAAA,QACpE,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,IAEH,MAAM;AAAA,IACN,oBAAoB,KAAK,SAAS,KAAK,QAAQ,EAAE,aAAa,6CAAA,CAA8C,CAAC;AAAA,IAC7G,UAAU,KAAK,SAAS,KAAK,QAAQ,EAAE,aAAa,oCAAA,CAAqC,CAAC;AAAA,IAC1F,eAAe,KAAK;AAAA,MAClB,KAAK,MAAM,CAAC,KAAK,UAAU,KAAK,KAAA,CAAM,GAAG;AAAA,QACvC,aAAa,qDAAqD,qBAAqB;AAAA,MAAA,CACxF;AAAA,IAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAOH,WAAW,KAAK;AAAA,MACd,KAAK,MAAM,CAAC,KAAK,UAAU,KAAK,KAAA,CAAM,GAAG;AAAA,QACvC,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAWH,eAAe,KAAK;AAAA,MAClB,KAAK,MAAM,CAAC,KAAK,OAAO,EAAE,WAAW,KAAK,GAAG,KAAK,KAAA,CAAM,GAAG;AAAA,QACzD,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,IAEH,YAAY,KAAK;AAAA,MACf,KAAK,MAAM,CAAC,KAAK,OAAO,EAAE,WAAW,KAAK,GAAG,KAAK,KAAA,CAAM,GAAG;AAAA,QACzD,aAAa;AAAA,MAAA,CACd;AAAA,IAAA;AAAA,IAEH,YAAY,KAAK;AAAA,MACf,KAAK,MAAM,CAAC,KAAK,UAAU,KAAK,KAAA,CAAM,GAAG;AAAA,QACvC,aAAa,gFAAgF,qBAAqB;AAAA,QAClH,UAAU,CAAC,oBAAoB;AAAA,MAAA,CAChC;AAAA,IAAA;AAAA,IAEH,YAAY,KAAK;AAAA,MACf,KAAK,OAAO;AAAA,QACV,aAAa,6BAA6B,qBAAqB;AAAA,QAC/D,UAAU,CAAC,oBAAoB;AAAA,MAAA,CAChC;AAAA,IAAA;AAAA,IAEH,UAAU,KAAK;AAAA,MACb,KAAK,OAAO;AAAA,QACV,aAAa,mCAAmC,qBAAqB;AAAA,QACrE,UAAU,CAAC,oBAAoB;AAAA,MAAA,CAChC;AAAA,IAAA;AAAA,EACH;AAAA,EAEF,EAAE,OAAO,cAAc,aAAa,oBAAA;AACtC;AAOO,MAAM,4BAA4B,KAAK;AAAA,EAC5C;AAAA,IACE,MAAM,KAAK,SAAS,oBAAoB;AAAA,IACxC,MAAM,KAAK,SAAS,oBAAoB;AAAA,IACxC,eAAe,KAAK,SAAS,KAAK,OAAO,EAAE,aAAa,oCAAA,CAAqC,CAAC;AAAA,IAC9F,YAAY,KAAK,SAAS,KAAK,OAAO,EAAE,aAAa,yCAAA,CAA0C,CAAC;AAAA,IAChG,WAAW,KAAK,SAAS,KAAK,OAAO,EAAE,aAAa,iDAAA,CAAkD,CAAC;AAAA,IACvG,eAAe,KAAK;AAAA,MAClB,KAAK,OAAO,EAAE,aAAa,kEAAkE;AAAA,IAAA;AAAA,IAE/F,YAAY,KAAK;AAAA,MACf,KAAK,OAAO,EAAE,aAAa,uEAAuE;AAAA,IAAA;AAAA,IAEpG,oBAAoB,KAAK,SAAS,KAAK,QAAQ,EAAE,aAAa,yCAAA,CAA0C,CAAC;AAAA,IACzG,UAAU,KAAK,SAAS,KAAK,QAAQ,EAAE,aAAa,8CAAA,CAA+C,CAAC;AAAA;AAAA;AAAA;AAAA;AAAA,IAKpG,cAAc,KAAK;AAAA,MACjB,KAAK,MAAM,CAAC,WAAW,GAAG;AAAA,QACxB,aAAa,+CAA+C,0BAA0B,KAAK,qBAAqB;AAAA,QAChH,UAAU,CAAC,oBAAoB;AAAA,MAAA,CAChC;AAAA,IAAA;AAAA,IAEH,YAAY,KAAK;AAAA,MACf,KAAK,MAAM,CAAC,WAAW,GAAG;AAAA,QACxB,aAAa,gDAAgD,0BAA0B,KAAK,qBAAqB;AAAA,QACjH,UAAU,CAAC,oBAAoB;AAAA,MAAA,CAChC;AAAA,IAAA;AAAA,EACH;AAAA,EAEF,EAAE,OAAO,uBAAuB,aAAa,4CAAA;AAC/C;"}

package/dist/global-dates.cjs

@@ -1,12 +1,11 @@
 "use strict";
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
+const dates_schema = require("./dates.schema-npKpToAJ.cjs");
 const dates_helper = require("./dates.helper-CDM5aEJG.cjs");
-const API_DATETIME_ACCEPTED_NOTE = "Only this spelling is accepted: `T` as the separator (a space is a 400) and an offset with minutes, either `Z` or `±HH:MM` (`+01` and `+0100` are a 400). A lowercase `t`/`z` and a fractional second are fine";
-const API_DATETIME_EXAMPLE = "2026-01-15T10:30:00Z";
-const EMITTED_DATETIME_NOTE = "Emitted as ISO-8601 in UTC";
+exports.API_DATETIME_ACCEPTED_NOTE = dates_schema.API_DATETIME_ACCEPTED_NOTE;
+exports.API_DATETIME_EXAMPLE = dates_schema.API_DATETIME_EXAMPLE;
+exports.EMITTED_DATETIME_NOTE = dates_schema.EMITTED_DATETIME_NOTE;
+exports.apiDateTime = dates_schema.apiDateTime;
 exports.getPeriodStart = dates_helper.getPeriodStart;
 exports.subtractPeriods = dates_helper.subtractPeriods;
-exports.API_DATETIME_ACCEPTED_NOTE = API_DATETIME_ACCEPTED_NOTE;
-exports.API_DATETIME_EXAMPLE = API_DATETIME_EXAMPLE;
-exports.EMITTED_DATETIME_NOTE = EMITTED_DATETIME_NOTE;
 //# sourceMappingURL=global-dates.cjs.map

package/dist/global-dates.cjs.map

@@ -1 +1 @@
-{"version":3,"file":"global-dates.cjs","sources":["../../src/v2/modules/global/dates/dates.schema.ts"],"sourcesContent":["/**\n * Generic calendar unit shared by the date primitives. Pure type — the calendar arithmetic that\n * consumes it lives in `dates.helper.ts`. Domain modules that need a narrower alias (e.g. the trend\n * widget's `TrendWindowUnit`) build it on top of this one, so the set of units is defined once here.\n */\nexport type PeriodUnit = 'hour' | 'day' | 'week' | 'month'\n\n/**\n * Datetimes a request carries are declared with `format: 'date-time'` (RFC 3339): a date and a time\n * separated by `T`, an optional fraction, and a mandatory offset (`Z` or `±HH:MM`). The offset names\n * the instant; the service converts it to UTC for the column.\n *\n * The format is TypeBox's, not `ajv-formats`': routes compile through `TypeBoxValidatorCompiler`\n * (`app.ts`), and `ajv-formats` only validates the v1/Objection layer. Which one runs matters,\n * because TypeBox's is the stricter of the two and the difference is visible from outside:\n *\n * - It splits the value on `/T/i` alone, so `T`/`t` is the only separator — a space is a 400.\n * - Its offset is `(?:Z|([+-])(\\d\\d):(\\d\\d))?`, so the minutes are not optional: `+01` is a 400,\n *   and so is `+0100` without the colon. That is what keeps `dayjs.utc()` from ever seeing an\n *   hour-only offset, which it cannot read — it would fall back to parsing the value as a bare wall\n *   clock and drop the offset, storing an instant an hour off with no error.\n * - It bounds the offset to `±23:59` (`tzH > 23 || tzM > 59`), so `+99:99` is a 400, and it checks\n *   the calendar (`IsDate`, leap years included), so `2026-02-31T00:00:00Z` is a 400 before any\n *   handler runs. The bound is RFC 3339's and not the tz database's, so it also takes offsets no\n *   zone uses (`-14:00`, `+23:59`) — each still names one unambiguous instant, so what gets stored\n *   is right.\n *\n * A `pattern` alongside the format would be dead weight: everything one could reasonably spell in it\n * is already a subset of what the format checks, and a stricter one drifts silently the day either\n * side changes. This was tried and removed (persei/tasks#294).\n *\n * This is that contract in one sentence, for the description of a request field: what the format\n * takes and, just as important, the two near-miss spellings a client is likely to try.\n */\nexport const API_DATETIME_ACCEPTED_NOTE =\n  'Only this spelling is accepted: `T` as the separator (a space is a 400) and an offset with minutes, either `Z` or `±HH:MM` (`+01` and `+0100` are a 400). A lowercase `t`/`z` and a fractional second are fine'\n\n/** An RFC 3339 datetime, for schema examples and API documentation. */\nexport const API_DATETIME_EXAMPLE = '2026-01-15T10:30:00Z'\n\n/**\n * What a datetime *coming out* of the API looks like, for the description of a response field.\n *\n * The outbound shape is narrower than the inbound one and no pattern states it: datetimes leave the\n * column as `Date` and are serialised by `fast-json-stringify` with `.toISOString()`, so the schema\n * never validates what is emitted. Saying it in the description is what puts it in the published\n * spec, which is where a client reads the contract from.\n */\nexport const EMITTED_DATETIME_NOTE = 'Emitted as ISO-8601 in UTC'\n"],"names":[],"mappings":";;;AAkCO,MAAM,6BACX;AAGK,MAAM,uBAAuB;AAU7B,MAAM,wBAAwB;;;;;;"}
+{"version":3,"file":"global-dates.cjs","sources":[],"sourcesContent":[],"names":[],"mappings":";;;;;;;;;;"}

package/dist/global-dates.mjs

@@ -1,11 +1,10 @@
+import { A, a, E, b } from "./dates.schema-BqkBcmM6.js";
 import { g, s } from "./dates.helper-XRCJ_UAQ.js";
-const API_DATETIME_ACCEPTED_NOTE = "Only this spelling is accepted: `T` as the separator (a space is a 400) and an offset with minutes, either `Z` or `±HH:MM` (`+01` and `+0100` are a 400). A lowercase `t`/`z` and a fractional second are fine";
-const API_DATETIME_EXAMPLE = "2026-01-15T10:30:00Z";
-const EMITTED_DATETIME_NOTE = "Emitted as ISO-8601 in UTC";
 export {
-  API_DATETIME_ACCEPTED_NOTE,
-  API_DATETIME_EXAMPLE,
-  EMITTED_DATETIME_NOTE,
+  A as API_DATETIME_ACCEPTED_NOTE,
+  a as API_DATETIME_EXAMPLE,
+  E as EMITTED_DATETIME_NOTE,
+  b as apiDateTime,
   g as getPeriodStart,
   s as subtractPeriods
 };

package/dist/global-dates.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"global-dates.mjs","sources":["../../src/v2/modules/global/dates/dates.schema.ts"],"sourcesContent":["/**\n * Generic calendar unit shared by the date primitives. Pure type — the calendar arithmetic that\n * consumes it lives in `dates.helper.ts`. Domain modules that need a narrower alias (e.g. the trend\n * widget's `TrendWindowUnit`) build it on top of this one, so the set of units is defined once here.\n */\nexport type PeriodUnit = 'hour' | 'day' | 'week' | 'month'\n\n/**\n * Datetimes a request carries are declared with `format: 'date-time'` (RFC 3339): a date and a time\n * separated by `T`, an optional fraction, and a mandatory offset (`Z` or `±HH:MM`). The offset names\n * the instant; the service converts it to UTC for the column.\n *\n * The format is TypeBox's, not `ajv-formats`': routes compile through `TypeBoxValidatorCompiler`\n * (`app.ts`), and `ajv-formats` only validates the v1/Objection layer. Which one runs matters,\n * because TypeBox's is the stricter of the two and the difference is visible from outside:\n *\n * - It splits the value on `/T/i` alone, so `T`/`t` is the only separator — a space is a 400.\n * - Its offset is `(?:Z|([+-])(\\d\\d):(\\d\\d))?`, so the minutes are not optional: `+01` is a 400,\n *   and so is `+0100` without the colon. That is what keeps `dayjs.utc()` from ever seeing an\n *   hour-only offset, which it cannot read — it would fall back to parsing the value as a bare wall\n *   clock and drop the offset, storing an instant an hour off with no error.\n * - It bounds the offset to `±23:59` (`tzH > 23 || tzM > 59`), so `+99:99` is a 400, and it checks\n *   the calendar (`IsDate`, leap years included), so `2026-02-31T00:00:00Z` is a 400 before any\n *   handler runs. The bound is RFC 3339's and not the tz database's, so it also takes offsets no\n *   zone uses (`-14:00`, `+23:59`) — each still names one unambiguous instant, so what gets stored\n *   is right.\n *\n * A `pattern` alongside the format would be dead weight: everything one could reasonably spell in it\n * is already a subset of what the format checks, and a stricter one drifts silently the day either\n * side changes. This was tried and removed (persei/tasks#294).\n *\n * This is that contract in one sentence, for the description of a request field: what the format\n * takes and, just as important, the two near-miss spellings a client is likely to try.\n */\nexport const API_DATETIME_ACCEPTED_NOTE =\n  'Only this spelling is accepted: `T` as the separator (a space is a 400) and an offset with minutes, either `Z` or `±HH:MM` (`+01` and `+0100` are a 400). A lowercase `t`/`z` and a fractional second are fine'\n\n/** An RFC 3339 datetime, for schema examples and API documentation. */\nexport const API_DATETIME_EXAMPLE = '2026-01-15T10:30:00Z'\n\n/**\n * What a datetime *coming out* of the API looks like, for the description of a response field.\n *\n * The outbound shape is narrower than the inbound one and no pattern states it: datetimes leave the\n * column as `Date` and are serialised by `fast-json-stringify` with `.toISOString()`, so the schema\n * never validates what is emitted. Saying it in the description is what puts it in the published\n * spec, which is where a client reads the contract from.\n */\nexport const EMITTED_DATETIME_NOTE = 'Emitted as ISO-8601 in UTC'\n"],"names":[],"mappings":";AAkCO,MAAM,6BACX;AAGK,MAAM,uBAAuB;AAU7B,MAAM,wBAAwB;"}
+{"version":3,"file":"global-dates.mjs","sources":[],"sourcesContent":[],"names":[],"mappings":";;"}

package/dist/lib/src/generated/client.d.ts

@@ -9497,6 +9497,249 @@ export type RunManualTrigger404AllOfThree = {
  * Error when the resource is not found
  */
 export type RunManualTrigger404 = RunManualTrigger404AllOf & RunManualTrigger404AllOfThree;
+export type ListProcessLogsParams = {
+    /**
+     * Page number starting from 0
+     */
+    page?: number;
+    /**
+     * The number of items per page
+     */
+    perPage?: number;
+    /**
+     * What kind of event a process_log row records, and what shape its extra_data takes
+     */
+    code?: ListProcessLogsCode;
+    /**
+     * Severity of the log row (not a layout/kind marker): LOG, RESULT, WARNING or ERROR
+     */
+    type?: ListProcessLogsType;
+    /**
+     * Filter by the related entity kind
+     */
+    related_model?: string;
+    /**
+     * Filter by the id of the related entity
+     */
+    related_id?: string;
+    /**
+     * Filter by the id of the parent process_log row
+     */
+    parent_id?: number;
+    /**
+     * Filter by the domain entity kind that originated the execution
+     */
+    subject_model?: string;
+    /**
+     * Filter by the id of the domain entity that originated the execution
+     */
+    subject_id?: string;
+    /**
+     * Filter by whether the row needs review
+     */
+    requires_attention?: boolean;
+    /**
+     * Filter by whether the row has been reviewed
+     */
+    reviewed?: boolean;
+    /**
+     * Only rows created at or after this instant. Only this spelling is accepted: `T` as the separator (a space is a 400) and an offset with minutes, either `Z` or `±HH:MM` (`+01` and `+0100` are a 400). A lowercase `t`/`z` and a fractional second are fine. Emitted as ISO-8601 in UTC
+     */
+    created_from?: string;
+    /**
+     * Only rows created at or before this instant. Only this spelling is accepted: `T` as the separator (a space is a 400) and an offset with minutes, either `Z` or `±HH:MM` (`+01` and `+0100` are a 400). A lowercase `t`/`z` and a fractional second are fine. Emitted as ISO-8601 in UTC
+     */
+    created_to?: string;
+};
+export type ListProcessLogsCode = (typeof ListProcessLogsCode)[keyof typeof ListProcessLogsCode];
+export declare const ListProcessLogsCode: {
+    readonly bulk_upload_batch: "bulk_upload_batch";
+    readonly bulk_upload_success: "bulk_upload_success";
+    readonly bulk_upload_error: "bulk_upload_error";
+    readonly trigger_evaluation: "trigger_evaluation";
+    readonly trigger_error: "trigger_error";
+    readonly trigger_action: "trigger_action";
+};
+export type ListProcessLogsType = (typeof ListProcessLogsType)[keyof typeof ListProcessLogsType];
+export declare const ListProcessLogsType: {
+    readonly NUMBER_0: 0;
+    readonly NUMBER_1: 1;
+    readonly NUMBER_MINUS_1: -1;
+    readonly NUMBER_MINUS_2: -2;
+};
+/**
+ * Project this row belongs to, when scoped to one
+ */
+export type ListProcessLogs200ResultsItemProjectId = number | null;
+/**
+ * User who caused the row to be written, when a user did
+ */
+export type ListProcessLogs200ResultsItemCreatedUser = number | null;
+/**
+ * Table/entity kind the row is about
+ */
+export type ListProcessLogs200ResultsItemRelatedModel = string | null;
+/**
+ * Id of the related entity, as a string
+ */
+export type ListProcessLogs200ResultsItemRelatedId = string | null;
+export type ListProcessLogs200ResultsItemCode = 'bulk_upload_batch' | 'bulk_upload_success' | 'bulk_upload_error' | 'trigger_evaluation' | 'trigger_error' | 'trigger_action' | null;
+/**
+ * Extended message, when needed
+ */
+export type ListProcessLogs200ResultsItemLongLog = string | null;
+export type ListProcessLogs200ResultsItemExtraDataAnyOf = {
+    [key: string]: unknown;
+};
+/**
+ * Structured data specific to `code` — see the per-code schemas for the trigger-engine codes
+ */
+export type ListProcessLogs200ResultsItemExtraData = ListProcessLogs200ResultsItemExtraDataAnyOf | null;
+/**
+ * Severity of the log row (not a layout/kind marker): LOG, RESULT, WARNING or ERROR
+ */
+export type ListProcessLogs200ResultsItemType = (typeof ListProcessLogs200ResultsItemType)[keyof typeof ListProcessLogs200ResultsItemType];
+export declare const ListProcessLogs200ResultsItemType: {
+    readonly NUMBER_0: 0;
+    readonly NUMBER_1: 1;
+    readonly NUMBER_MINUS_1: -1;
+    readonly NUMBER_MINUS_2: -2;
+};
+/**
+ * When the row was reviewed. Null while unreviewed. Emitted as ISO-8601 in UTC
+ */
+export type ListProcessLogs200ResultsItemReviewedDate = string | null;
+/**
+ * Id of this row's parent process_log row, when it has one
+ */
+export type ListProcessLogs200ResultsItemParentId = number | null;
+/**
+ * Domain entity kind that originated the execution (e.g. patient), when resolvable
+ */
+export type ListProcessLogs200ResultsItemSubjectModel = string | null;
+/**
+ * Id of the domain entity that originated the execution, as a string, when resolvable
+ */
+export type ListProcessLogs200ResultsItemSubjectId = string | null;
+/**
+ * Retention deadline; the row is purged after it, and never expires when null. Emitted as ISO-8601 in UTC
+ */
+export type ListProcessLogs200ResultsItemExpiresAt = string | null;
+/**
+ * A process_log row
+ */
+export type ListProcessLogs200ResultsItem = {
+    /** Unique identifier of the row */
+    id: number;
+    /** Project this row belongs to, when scoped to one */
+    project_id?: ListProcessLogs200ResultsItemProjectId;
+    /** User who caused the row to be written, when a user did */
+    created_user?: ListProcessLogs200ResultsItemCreatedUser;
+    /** Table/entity kind the row is about */
+    related_model?: ListProcessLogs200ResultsItemRelatedModel;
+    /** Id of the related entity, as a string */
+    related_id?: ListProcessLogs200ResultsItemRelatedId;
+    code?: ListProcessLogs200ResultsItemCode;
+    /** Short human-readable message */
+    log: string;
+    /** Extended message, when needed */
+    long_log?: ListProcessLogs200ResultsItemLongLog;
+    /** Structured data specific to `code` — see the per-code schemas for the trigger-engine codes */
+    extra_data?: ListProcessLogs200ResultsItemExtraData;
+    /** Severity of the log row (not a layout/kind marker): LOG, RESULT, WARNING or ERROR */
+    type: ListProcessLogs200ResultsItemType;
+    /** Whether the row needs a human to review it */
+    requires_attention?: boolean;
+    /** Whether the row has been reviewed */
+    reviewed?: boolean;
+    /** When the row was reviewed. Null while unreviewed. Emitted as ISO-8601 in UTC */
+    reviewed_date?: ListProcessLogs200ResultsItemReviewedDate;
+    /** Id of this row's parent process_log row, when it has one */
+    parent_id?: ListProcessLogs200ResultsItemParentId;
+    /** Domain entity kind that originated the execution (e.g. patient), when resolvable */
+    subject_model?: ListProcessLogs200ResultsItemSubjectModel;
+    /** Id of the domain entity that originated the execution, as a string, when resolvable */
+    subject_id?: ListProcessLogs200ResultsItemSubjectId;
+    /** Retention deadline; the row is purged after it, and never expires when null. Emitted as ISO-8601 in UTC */
+    expires_at?: ListProcessLogs200ResultsItemExpiresAt;
+    /** When the row was created. Emitted as ISO-8601 in UTC */
+    created_at?: string;
+    /** When the row was last modified. Emitted as ISO-8601 in UTC */
+    mod_time?: string;
+};
+/**
+ * Paginated response
+ */
+export type ListProcessLogs200 = {
+    /** Array of items of the current page */
+    results: ListProcessLogs200ResultsItem[];
+    /** Total number of items not in this page but in the whole query */
+    total: number;
+};
+/**
+ * Debug information of the error
+ */
+export type ListProcessLogs403AllOfDebug = {
+    [key: string]: unknown;
+};
+export type ListProcessLogs403AllOf = {
+    /** HTTP status code */
+    statusCode: number;
+    /** Error code */
+    error: string;
+    /** Localized error message */
+    message: string;
+    /** Debug information of the error */
+    debug?: ListProcessLogs403AllOfDebug;
+};
+export type ListProcessLogs403AllOfThreeStatusCode = (typeof ListProcessLogs403AllOfThreeStatusCode)[keyof typeof ListProcessLogs403AllOfThreeStatusCode];
+export declare const ListProcessLogs403AllOfThreeStatusCode: {
+    readonly NUMBER_403: 403;
+};
+export type ListProcessLogs403AllOfThreeError = (typeof ListProcessLogs403AllOfThreeError)[keyof typeof ListProcessLogs403AllOfThreeError];
+export declare const ListProcessLogs403AllOfThreeError: {
+    readonly 'forbidden-error': "forbidden-error";
+};
+export type ListProcessLogs403AllOfThree = {
+    statusCode: ListProcessLogs403AllOfThreeStatusCode;
+    error: ListProcessLogs403AllOfThreeError;
+};
+/**
+ * Error when the user is forbidden to access the resource
+ */
+export type ListProcessLogs403 = ListProcessLogs403AllOf & ListProcessLogs403AllOfThree;
+/**
+ * Debug information of the error
+ */
+export type ListProcessLogs404AllOfDebug = {
+    [key: string]: unknown;
+};
+export type ListProcessLogs404AllOf = {
+    /** HTTP status code */
+    statusCode: number;
+    /** Error code */
+    error: string;
+    /** Localized error message */
+    message: string;
+    /** Debug information of the error */
+    debug?: ListProcessLogs404AllOfDebug;
+};
+export type ListProcessLogs404AllOfThreeStatusCode = (typeof ListProcessLogs404AllOfThreeStatusCode)[keyof typeof ListProcessLogs404AllOfThreeStatusCode];
+export declare const ListProcessLogs404AllOfThreeStatusCode: {
+    readonly NUMBER_404: 404;
+};
+export type ListProcessLogs404AllOfThreeError = (typeof ListProcessLogs404AllOfThreeError)[keyof typeof ListProcessLogs404AllOfThreeError];
+export declare const ListProcessLogs404AllOfThreeError: {
+    readonly 'not-found': "not-found";
+};
+export type ListProcessLogs404AllOfThree = {
+    statusCode: ListProcessLogs404AllOfThreeStatusCode;
+    error: ListProcessLogs404AllOfThreeError;
+};
+/**
+ * Error when the resource is not found
+ */
+export type ListProcessLogs404 = ListProcessLogs404AllOf & ListProcessLogs404AllOfThree;
 /**
  * Thryve connection widget URL response
  */
@@ -10788,6 +11031,30 @@ export type runManualTriggerResponseError = (runManualTriggerResponse403 | runMa
 export type runManualTriggerResponse = runManualTriggerResponseSuccess | runManualTriggerResponseError;
 export declare const getRunManualTriggerUrl: (ecosystemName: string, projectName: string, id: number) => string;
 export declare const runManualTrigger: (ecosystemName: string, projectName: string, id: number, runManualTriggerBody: RunManualTriggerBody, options?: RequestInit) => Promise<runManualTriggerResponse>;
+/**
+ * Get a paginated list of process_log rows of the project, optionally filtered by code, type, related entity, parent, review status or creation date range
+ */
+export type listProcessLogsResponse200 = {
+    data: ListProcessLogs200;
+    status: 200;
+};
+export type listProcessLogsResponse403 = {
+    data: ListProcessLogs403;
+    status: 403;
+};
+export type listProcessLogsResponse404 = {
+    data: ListProcessLogs404;
+    status: 404;
+};
+export type listProcessLogsResponseSuccess = listProcessLogsResponse200 & {
+    headers: Headers;
+};
+export type listProcessLogsResponseError = (listProcessLogsResponse403 | listProcessLogsResponse404) & {
+    headers: Headers;
+};
+export type listProcessLogsResponse = listProcessLogsResponseSuccess | listProcessLogsResponseError;
+export declare const getListProcessLogsUrl: (ecosystemName: string, projectName: string, params?: ListProcessLogsParams) => string;
+export declare const listProcessLogs: (ecosystemName: string, projectName: string, params?: ListProcessLogsParams, options?: RequestInit) => Promise<listProcessLogsResponse>;
 /**
  * [DEPRECATED] Returns a short-lived URL to embed the Thryve connection widget in an iframe / WebView. The native app builds this URL itself now; kept only for older installed clients. Slated for removal once access logs drop to zero.
  * @deprecated