nucleus-core-ts 0.10.39 → 0.10.41

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

@@ -28,6 +28,14 @@ export declare class VerificationService {
         success: boolean;
         flow_id: string;
     }>;
+    /**
+     * Step nodes in this flow that no verifier node points at.
+     *
+     * Mirrors materializeRequirementsForStep's own lookup exactly — verifiers are
+     * the SOURCES of edges whose TARGET is the step — so publish refuses on the
+     * same rule the runtime would silently obey.
+     */
+    private findStepsWithoutVerifiers;
     publishFlow(flowId: string): Promise<{
         success: boolean;
         message: string;

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

@@ -2,6 +2,20 @@ export interface VerificationConfig {
     enabled?: boolean;
     autoResetOnRejection?: boolean;
     requireSignatureByDefault?: boolean;
+    /**
+     * Whether the person who started a verification may also decide it.
+     *
+     * Defaults to FALSE, because that is what an approval chain is for. The
+     * engine records `started_by` on the instance and `created_by` on the row
+     * being reviewed, and until this existed it compared neither: on a
+     * pharmaceutical-leaflet install one account created the leaflet version,
+     * started the chain and approved its own submission in three calls, and the
+     * audit trail shows an approval with that person's name on both ends.
+     *
+     * Set it true only for a flow where self-approval is genuinely intended --
+     * an acknowledgement step, or a single-person shop.
+     */
+    allowSelfApproval?: boolean;
     diffTrackingEnabled?: boolean;
     endpoints?: {
         enabled?: boolean;

package/package.json

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