zc2 0.0.51

P2P compute broker with yen-denominated billing, WAL, and broker mesh support
# Rollout: hub-validated user keys (zc#384)

What changes: with a hub URL configured, the broker asks the hub who a Bearer key belongs to (`GET /api/auth/me/api-key`) and bills that user. A key the hub rejects, or whose `zk_<uid>_` prefix disagrees with the hub's `zakuro_user_id`, is refused with 401. A hub that is unreachable, times out (5 s), or answers 5xx gives 503.

No hub change is needed: the endpoint already exists (it backs `zc me` and the broker's startup handshake). This can ship on its own.

Operational notes:
- The broker makes at most one hub call per distinct key per 5 minutes (valid) or 30 seconds (invalid). Verdicts are cached by SHA-256 of the key; the key itself is never stored.
- A revoked key may keep working for up to 5 minutes.
- Hub outages now surface as 503 on `/execute`, `/execute/batch` and other key-authenticated routes for keys not already cached. Brokers rolled out together with a healthy hub see no change.
- Local mode (no hub configured) and `ZAKURO_MASTER_KEY` admin access are unchanged.
- Emergency opt-out: `ZAKURO_TRUST_KEY_SHAPE=1` restores shape-only auth and logs a warning at startup. Emergency use only: anyone who knows a user id can spend that user's balance while it is set. Unset it as soon as the hub is healthy.
- Rollback: deploy the previous broker version, or set the opt-out env as a stopgap.
- Mesh peers re-validate forwarded batch shares against their own hub, so every broker in a mesh needs a reachable hub.

## User-key proof on settlements (zc#404, pairs with mkt#418)

Additive; hubs that ignore the header keep working unchanged.

Header contract for the hub (`POST /api/broker/transaction`):
- `X-Zakuro-User-Key-Sha256: <64 lowercase hex chars>` = `sha256(Bearer key, utf-8)`. It is the same digest as `users.api_key_hash` / `device_keys.key_hash`, so the hub matches it without seeing the key. The raw key is never sent, logged or persisted by the broker.
- The digest is of a key that authenticated `zakuro_user_id` on this broker (validated against the hub, or shape-only under `ZAKURO_TRUST_KEY_SHAPE=1`). The hub should check that it belongs to the `zakuro_user_id` in the body.
- Absent when there is no user key: local mode, `ZAKURO_MASTER_KEY` admin calls, and settlements after a broker restart (WAL replays) until that user next authenticates. mkt#418 must therefore treat a missing header as "legacy/unproven", gated by its own enforcement flag, not as an error by default.
- The broker holds the digest in memory only, per user (the most recent key that authenticated them). A revoked key can still be sent on a settlement for up to its last use; the hub should decide whether that fails.
- `/api/broker/reserve`: the broker reserves locally and makes no hub call, so there is nothing to attach there today.
- `/api/broker/batch-sync` (buffered rows) does not carry the header yet: the buffer is a durable record, and adding a digest means a format change (ZC-0009 frozen wire). Follow-up.