nucleus-core-ts 0.10.47 → 0.10.49

package/dist/src/Nucleus/routes/entity/activeVerification.d.ts

@@ -0,0 +1,18 @@
+import type { NodePgDatabase } from 'drizzle-orm/node-postgres';
+/**
+ * Is this row currently going through an approval chain?
+ *
+ * The verification tables address their subject polymorphically — `entity_name`
+ * plus `entity_id`, no foreign key — so the database cannot refuse a delete the
+ * way `pages.product_id` can. Nothing stopped a row from being removed out from
+ * under a running instance, and nothing noticed afterwards: measured on a
+ * pharmaceutical-leaflet install, deleting a page version that was awaiting
+ * review answered 200, the row went, and the instance stayed `active` with a
+ * pending requirement pointing at an id that no longer resolves. The reviewer
+ * keeps seeing work they can never finish, for a document that is gone.
+ *
+ * So the check lives where the delete is. It is deliberately narrow — only an
+ * `active` instance blocks; a completed or rejected one is history and must not
+ * make a row undeletable forever.
+ */
+export declare function activeVerificationExists(db: NodePgDatabase, schemaTables: Record<string, unknown>, entityName: string, entityId: string): Promise<boolean>;

package/dist/src/Services/Verification/index.d.ts

@@ -42,6 +42,11 @@ export declare class VerificationService {
      * engine's `current_step + 1` walk can actually traverse.
      */
     private findStepOrderProblem;
+    /**
+     * Describes the first notification rule whose `trigger` is not one the engine
+     * ever fires, or null when they all are.
+     */
+    private findUnknownNotificationTrigger;
     publishFlow(flowId: string): Promise<{
         success: boolean;
         message: string;

package/dist/src/Services/Verification/types.d.ts

@@ -28,7 +28,17 @@ export interface VerificationConfig {
 }
 export declare const DEFAULT_VERIFICATION_CONFIG: Required<VerificationConfig>;
 export type VerificationDecision = 'approved' | 'rejected' | 'pending';
-export type VerificationTrigger = 'on_flow_started' | 'on_step_reached' | 'on_approved' | 'on_rejected' | 'on_flow_completed';
+/**
+ * Every moment the engine actually fires a notification rule at.
+ *
+ * A runtime list rather than a bare union, because publishFlow has to CHECK a
+ * stored trigger against it: the save body types the graph as `t.Array(t.Any())`,
+ * so a name outside this set used to be stored and published happily and then
+ * never match anything. The type is derived from the list so the two cannot
+ * drift apart.
+ */
+export declare const VERIFICATION_TRIGGERS: readonly ["on_flow_started", "on_step_reached", "on_approved", "on_rejected", "on_flow_completed"];
+export type VerificationTrigger = (typeof VERIFICATION_TRIGGERS)[number];
 export type FlowTriggerOn = 'create' | 'update' | 'delete' | 'manual';
 export type NodeType = 'step' | 'verifier' | 'notification';
 export type EdgeType = 'default' | 'conditional' | 'success' | 'failure';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nucleus-core-ts",
-  "version": "0.10.47",
+  "version": "0.10.49",
   "description": "Production-ready, enterprise-grade TypeScript framework for building multi-tenant APIs",
   "author": "Hidayet Can Özcan <hidayetcan@gmail.com>",
   "license": "SEE LICENSE IN LICENSE",