Report WP-0024 approvals by task

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa

docs/wp0024-owner-review-interface.md

@@ -27,6 +27,15 @@ resource metadata, but they never read Secret data or OpenBao lease payloads.
 They cannot revoke a lease, restart a workload, create a snapshot, or reboot a
 node. A successful review is still not a live execution window.
 
+The task-to-owner interface is explicit in the contract:
+
+- T02 requires `audit-core` and `rapp-postgres`.
+- T03 requires `audit-core`, `rapp-postgres`, `railiance-cluster`, and
+  `railiance-infra`.
+
+One owner receipt may approve both tasks when that owner is responsible for
+both; its receipt is bound to all artifacts and checks in that owner's review.
+
 To request changes instead:
 
 ```bash
@@ -46,9 +55,10 @@ Anyone can collect current receipts without interpreting owner messages:
 python3 scripts/wp0024-owner-review.py status
 ```
 
-The result reports `approve`, `request-changes`, or `missing` per owner and an
-`all_approved` aggregate. Receipts for an older contract digest or different
-artifact hashes are counted as stale and cannot satisfy the aggregate.
+The result reports `approve`, `request-changes`, or `missing` per owner, then
+computes `all_approved` separately for T02 and T03 as well as for the whole
+interface. Receipts for an older contract digest or different artifact hashes
+are counted as stale and cannot satisfy an aggregate.
 
 The interface uses `STATE_HUB_URL` when set and otherwise connects to
 `http://127.0.0.1:8000`. The same value can be supplied explicitly with the