nucleus-core-ts 0.10.56 → 0.10.58

package/dist/.build-ok

@@ -1 +1 @@
-0.10.56
+0.10.58

package/dist/fe/components/VerificationFlowPage/components/PendingTab.js

@@ -3,7 +3,7 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 import { useEffect, useEffectEvent, useState } from 'react';
 import { DEFAULT_VERIFICATION_FLOW_LABELS } from '../labels';
 import { useVerificationFlowStore } from '../store';
-import { planDecision } from './decisionPlan';
+import { planDecision, signatureFileType } from './decisionPlan';
 import { getActiveTheme } from '../theme/store';
 export function PendingTab({ pendingAction, decideAction, uploadSignatureAction, onDecisionMade, labels }) {
     // Local, not in the store: only one card is in deciding mode at a time, and
@@ -54,13 +54,37 @@ export function PendingTab({ pendingAction, decideAction, uploadSignatureAction,
                     signature_id: signatureId
                 } : {}
             },
-            onAfterHandle: ()=>{
+            onAfterHandle: (res)=>{
+                /*
+           * This API answers a REFUSED decision with HTTP 200 and
+           * `success: false`, and `onAfterHandle` fires on the status code. So
+           * closing the card here unconditionally is how a refusal came to look
+           * exactly like an approval.
+           *
+           * Measured on a leaflet install: a reviewer who had also submitted the
+           * version pressed Approve, the engine answered "The person who
+           * submitted this for verification cannot decide it", the card closed,
+           * nothing was recorded, and the item sat back in the queue with no
+           * explanation. The same silence covered every other refusal the engine
+           * makes -- wrong role, already decided, account switched off.
+           *
+           * The engine's own sentence is shown instead of a generic failure: it
+           * already says exactly what is wrong, and a reviewer can act on
+           * "cannot decide it" in a way they cannot act on "something failed".
+           */ if (res && res.success === false) {
+                    setSignatureNote(res.message || say.decisionRefused);
+                    return;
+                }
                 store.setDecidingId(null);
                 store.setDecisionReason('');
                 setSignatureFile(null);
                 setSignatureNote(null);
                 onDecisionMade?.(item.entity_name, item.entity_id);
                 loadPending();
+            },
+            onErrorHandle: (err)=>{
+                const msg = err?.message;
+                setSignatureNote(msg || say.decisionRefused);
             }
         });
     });
@@ -100,7 +124,7 @@ export function PendingTab({ pendingAction, decideAction, uploadSignatureAction,
             size: signatureFile.size,
             mime_type: signatureFile.type || 'application/octet-stream',
             extension: signatureFile.name.split('.').pop() || '',
-            type: 'signature'
+            type: signatureFileType(signatureFile.type)
         }));
         setSignatureNote(say.signatureUploading);
         uploadSignatureAction.start({

package/dist/fe/components/VerificationFlowPage/components/decisionPlan.d.ts

@@ -25,3 +25,18 @@ export declare function planDecision(input: {
     hasUploadAction: boolean;
     hasFile: boolean;
 }): DecisionPlan;
+/**
+ * Which `files.type` a signature upload should declare.
+ *
+ * The column is an enum the HOST configures, and a generic component cannot
+ * invent a value for it. The first version of this sent `type: 'signature'`
+ * and the install answered, from its own list: "type must be one of: image,
+ * document, video, audio, profile_picture" — a 400 the reviewer saw only as
+ * "the signature could not be uploaded".
+ *
+ * So it is derived from the file itself and lands on one of the names every
+ * install carries. `document` is the fallback because a signature that is not
+ * an image is a signed document, and because it is the safest of the five to
+ * be wrong about.
+ */
+export declare function signatureFileType(mimeType: string | undefined): string;

package/dist/fe/components/VerificationFlowPage/components/decisionPlan.js

@@ -29,3 +29,23 @@
         kind: 'upload-then-send'
     };
 }
+/**
+ * Which `files.type` a signature upload should declare.
+ *
+ * The column is an enum the HOST configures, and a generic component cannot
+ * invent a value for it. The first version of this sent `type: 'signature'`
+ * and the install answered, from its own list: "type must be one of: image,
+ * document, video, audio, profile_picture" — a 400 the reviewer saw only as
+ * "the signature could not be uploaded".
+ *
+ * So it is derived from the file itself and lands on one of the names every
+ * install carries. `document` is the fallback because a signature that is not
+ * an image is a signed document, and because it is the safest of the five to
+ * be wrong about.
+ */ export function signatureFileType(mimeType) {
+    const mime = (mimeType || '').toLowerCase();
+    if (mime.startsWith('image/')) return 'image';
+    if (mime.startsWith('video/')) return 'video';
+    if (mime.startsWith('audio/')) return 'audio';
+    return 'document';
+}

package/dist/fe/components/VerificationFlowPage/labels.d.ts

@@ -97,6 +97,8 @@ export type VerificationFlowLabels = {
     signatureUploadFailed: string;
     /** Shown when the host wired no upload action at all. */
     signatureUnavailable: string;
+    /** Fallback when a decision is refused and the engine sent no sentence. */
+    decisionRefused: string;
     recipientAllVerifiers: string;
     recipientStepVerifier: string;
     recipientEntityCreator: string;

package/dist/fe/components/VerificationFlowPage/labels.js

@@ -77,6 +77,7 @@
     signatureUploading: 'Uploading signature…',
     signatureUploadFailed: 'The signature could not be uploaded. The decision was not sent.',
     signatureUnavailable: 'This step requires a signature, but signing is not available on this screen. Nobody can complete it here — remove the signature requirement from the step, or wire an upload action.',
+    decisionRefused: 'The decision was refused and nothing was recorded.',
     recipientAllVerifiers: 'All Verifiers',
     recipientStepVerifier: 'Step Verifier',
     recipientEntityCreator: 'Entity Creator',

package/package.json

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