feat(directory): show verified delivery during DACS-5 finalisation

[randomblocker]

What changed

• Parse the gateway's published preview procurement field with a fail-closed client contract, without requiring unpublished finalisation metadata.
• Show a verified Oracle, due-diligence, or security delivery as soon as payment evidence and the seller delivery have been verified.
• Keep DACS-5 visibly active and label the preview as nonterminal; Settled & accepted remains unavailable until the completed two-copy bundle reconciles.
• Preserve a verified delivery for operator recovery if later DACS-5 work fails, without offering unsafe repurchase guidance.
• Render preview anchors, findings/values, failure state, and raw verified delivery evidence.
• Treat a terminal producer's omitted or null preview as cleared, and reject a completed response that still carries a nonterminal preview.
• Add contract and browser regressions for preview-to-completion, post-payment failure, and malformed preview states.

Why

The gateway can return a useful verified delivery before DACS-5 anchoring finishes. The Directory previously discarded that state and appeared frozen until the terminal job response arrived. This change exposes real progress and results without weakening DACS acceptance semantics.

User impact

Users see their verified result earlier, can inspect its evidence while final bundles reconcile, and can distinguish clearly between delivery verified, DACS-5 needs recovery, and the later settled and accepted terminal state.

Contract alignment

The UI consumes the gateway's actual preview-only shape (preview.kind, preview.status, verified delivery.report, and anchors). It does not invent attempt counts, timestamps, or a separate finalisation object that the gateway does not publish.

Validation

• npm run typecheck
• npm test - 186/186 passed
• CI=1 npm run test:e2e -- --workers=1 - 14/14 passed
• npm run check:deploy-config
• npm run build
• Branch merged with current Community main

No paid live procurement was dispatched by these UI tests.