@flop-labs/contracts 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.1.2] - 2026-11-08
11
+
12
+ ### Added
13
+
14
+ - Generated exact-ID credential receipt, request ID and lookup error contracts,
15
+ preserving unknown values and exact terminal allocations in raw FLOP units.
16
+
10
17
  ## [0.1.1] - 2026-10-26
11
18
 
12
19
  ### Added
package/README.md CHANGED
@@ -3,6 +3,7 @@
3
3
  Structural types, JSON Schema exports, and assertion validators for the FLOP
4
4
  public HTTP API. Version 0.1.0 covers `listModels`, `getModel`, and JSON
5
5
  `createChatCompletion` payloads and streaming frames from `services/rest-gateway/openapi.yaml`.
6
+ The unreleased surface also includes exact-ID credential receipt lookup.
6
7
 
7
8
  ```sh
8
9
  npm install @flop-labs/contracts
@@ -23,6 +24,15 @@ Exports: `Model`, `ModelList` (also `ModelListResponse`), `ModelResponse`,
23
24
  and `*Schema` objects. Invalid data throws `ContractValidationError`; its message
24
25
  contains the contract name, never the submitted values.
25
26
 
27
+ `CredentialReceipt`, `CredentialReceiptError` and `CredentialReceiptRequestId` also
28
+ export `assert*` functions and `*Schema` objects, generated from
29
+ `GET /keys/me/receipts/{request_id}`. A receipt is a current scoped ledger observation;
30
+ it does not rewrite the original completion checkpoint. Exact terminal allocations
31
+ use `settled_spend_raw` decimal strings in raw FLOP units (10^18 raw = 1 FLOP).
32
+ Unavailable values remain null. A pooled channel event is not a separate payment
33
+ or burn transaction for each request. See the client's recovery example for authority,
34
+ state, retention and manual replay rules.
35
+
26
36
  Validation checks structure without coercion, default insertion, or removal of
27
37
  fields. Responses allow extensions, including receipt evidence, exactly as the
28
38
  source schemas allow. Validating an envelope does not authenticate its evidence,