bc0dffa965
The v0.4.0 energy-report entry said the conformance build builds the reference meters on every platform. It builds two of them, wai_meter and wai_world_meter. wai-energy-receipts.yml builds those two, wai_video_meter and wai_quantum_meter on linux, linux-arm64 and macos. No workflow builds wai_prov, which needs codecs. The entry now says so, and the conformance workflow's comment no longer names a Windows leg its matrix does not have. The entry now records two compatibility changes. Every reference meter bin requires receipt_claims, and Cargo skips a bin whose required features are off without an error. POST /verify in wai-quantum-serve renders an unmetered receipt's joules_micro as null and adds a metered member, so the crate moves to 0.4.0 and the Wire paragraph names the change. jwp-receipts §2.4.9 rule 2 reads "A point that is present MUST NOT be empty", in the form of the other rules. quantum-sim names the meter's other unmetered paths: a rail that is not live in both brackets (energy-measurement §3.1), and a §4 ratio or §2.3 uncertainty that cannot support a figure. Co-Authored-By: Claude Opus 5.5 <[email protected]>
18 lines
631 B
TOML
18 lines
631 B
TOML
[package]
|
|
name = "wai-quantum-serve"
|
|
version = "0.4.0"
|
|
edition = "2021"
|
|
license = "Apache-2.0"
|
|
description = "The WAI quantum stack as a WASI-HTTP component — deterministic quantum computation as a serverless function. Runs on any wasi:http/proxy host (wasmtime serve, and other component-model runtimes); returns the same statevector hashes and the same signed receipt bytes as a native run."
|
|
|
|
[lib]
|
|
crate-type = ["cdylib"]
|
|
|
|
[dependencies]
|
|
wasi = "0.14"
|
|
ed25519-dalek = "2"
|
|
wai = { path = "../wai-rs", default-features = false, features = ["quantum_toolchain", "quantum_receipt"] }
|
|
|
|
[profile.release]
|
|
opt-level = "s"
|
|
lto = true
|