[ctfbruce]

Behaviour

• POST /payment/quote takes the body of PUT /payment/intent, under the same authentication and request quota, and prices it with the single pricing function the intent uses. It writes nothing: no transaction, order, auth key, run or retry row, and no capacity is reserved. A batch the intent would refuse is still answered 200 with every problem on the order it concerns (field errors in the existing shape) and no total; a malformed body, an unsupported method, a chain method while blockchain payments are disabled and a missing credential keep the intent's status.
• The intent response gains quote, the stored prices in the same shape, so a client can compare an earlier quote with what was charged; both carry the pricing rule's name (bw-s-ceil-ms-v1).
• GET /me gains economics: the payment methods admitted now, whether chain payments are enabled and whether usage allowances are offered (not yet).
• GET /me/orders pages the caller's own intents, newest first, with their orders, settlement (pending, credited, refunded, as run details report it) and the admitted run; another account's intents are never listed, and a foreign cursor yields an empty page.
• API contract 1.15; the Go client gains Quote and Orders, and Whoami returns the new field. Scoped credentials: measurements:read quotes, account:read reads the history.

Proof

• Real-SQLite tests: a quote writes nothing (row counts of five tables unchanged in the serving connection and in the reopened file; no transaction id or auth key in the body); the intent's quote equals the earlier quote and the stored prices; every problem of a six-order batch is reported on its order while the intent stops at the first; the kept refusals; /me economics; history paging with ownership and a foreign cursor; the client's body, version requirement and decoding; the access matrix and the contract-exercise test extended; the generated bindings match the pinned generator.

Limits

• No console code; allowances are reported as unavailable until the allowance change; an intent recovered through an explicit retry does not repeat its quote.
• Based on Record each order's settlement once and deliver it after a failed credit #373's head (the pricing rule column it adds is read by the history); no dispatcher schema change of its own.

GitHub issues #214 and #215.

Candidate CI

Run 37284748943 on c0b3876: 16 of 16 lanes and required succeeded. Run 37289538171 on 7717bca (the branch with #373's corrected head merged forward): 16 of 16 lanes and required succeeded. Correction 97b85f4: a quote and an intent now report an out-of-range start_time and a policy the executor cannot currently serve (for example require_icmp without ICMP) as per-order field errors, through the same checks the submission applies, so a clean quote no longer promises admission for a request already known to be invalid; the quote still reserves nothing and the submission still validates again; the Go client's Quote description no longer refers to a price the high-level submission does not return. Run 37302452972 on 97b85f4: 16 of 16 lanes and required succeeded. The branch then took the receipts branch (be51d25, run 37307041399 green) and the payout branch with the corrected adapter (55daed3), so that the composed tree builds its tests against the payment handler constructor that reports a configuration error; Run 37308476427 on 55daed3: 16 of 16 lanes and required succeeded.