bzst_id evidence field, SDK v0.2.0, reliability improvements
A third immutable evidence reference on §18e qualified confirmations, plus reliability improvements across the registry chain.
- Retries on transient upstream blips. VIES, HMRC, BFS, Brønnøysund,
and BZSt calls now retry brief upstream failures automatically before
falling back to cache. Customers see
source_status: livemore often;/statusnumbers reflect genuine downtime instead of every momentary hiccup. - Audit log durability. Audit-trail writes (the §18e evidence record) now retry transient failures instead of silently dropping the record. No added latency.
bzst_idfield onPOST /v1/confirm(meta.bzst_id) andGET /v1/confirmations/{id}. BZSt returns its own request identifier in every qualified-confirmation response — now surfaced as a third immutable evidence reference alongsiderequest_idandconfirmation_id. Customers can prove "BZSt acknowledged this specific request" with a stable, queryable identifier independent of our own internal IDs. Strengthens the §18e evidence chain.@vatverify/nodev0.2.0 ships withclient.confirm(),client.confirmations.get(id),bzst_idonConfirmResponse.metaandConfirmationRecord, and three new typed error classes (BzstError,BzstInvalidRequesterError,BzstQualifiedFieldsMissingError).