Repository navigation
1.0.2
Vastu scan calls (save, retrieve, list, delete, timelapse) no longer send an Idempotency-Key: the API identifies a scan retry by scanId or the body's requestId and rejected every scan call carrying one with 422 IDEMPOTENCY_CONTRACT_UNSUPPORTED. Passing a key to a scan call now fails before sending, and scan calls are still retried on transient errors. Response types now include notAssessed (spaces with no placement rule, never graded) and the other new Vastu response fields; the offline runtime carries the heading-provider fixes. No breaking changes except that an explicit idempotency key on a scan call is now refused.