Issue-resolution ledger · verified · snapshot 2026-09-16 21:35 UTC
Implement Step 3 of the Pi Operator extension roadmap from owners-manual/pbc/appendix-pi-operator-extension.pbc.md: add /op:supervisor-review only. It must wrap the existing claim-scoped review-delegate semantics safely: one named claim, explicit reviewer, verify_cmd must exist or be supplied, unavailable/clear failure under broker enrollment, no raw arbitrary operator execution, no self-verificat
Step 3 of the Pi Operator extension exists as /op:supervisor-review on .pi/extensions/operator/, preserving /op:doctor, /op:status, /op:tasks, /op:use, /op:claim, /op:evidence, and /op:handoff. /op:delegate and /pbc:* are not registered, an
The extension selftest passes 328/328 with 0 failed and 0 skipped: tier A pins step-1 argv builders; tier A2 pins claim/evidence/handoff builders; tier A3 pins review-delegate builders including required reviewer/verify-cmd, uid-isolated --
Focused pytest for the extension is green: python3 -m pytest tests/test_pi_operator_extension.py -q reports 5 passed. tests/test_pi_operator_extension.py is clean under ruff, black, and isort.
The extension holds the Operator authority boundary at step 3: /op:supervisor-review wraps review-delegate for one named claim with explicit --reviewer (never from the session or review_harness), a recorded or supplied verify-cmd, and fail-
run_log for claim-0128
test_output for claim-0129
test_output for claim-0130
test_output for claim-0131
test_output for claim-0131
Current Pi session (review_harness pi-01a05bf2) should call for supervisor review of claim-0131 (and optionally 0128-0130). Use /op:supervisor-review with an explicit reviewer distinct from grok, a recorded verify-cmd, and the trusted uid-i
advisory-agent review of claim-0131 as n/a
test_output for claim-0131
paper_section for claim-0131
Run /op:supervisor-review on claim-0131 in uid-isolated mode with an explicit reviewer other than grok and --review-user for operator-verifier or uid-971. Authorize the sudo -u script as that user. Attach status-setting evidence as the regi
run_log for claim-0131
Recommended: accept verified claim-0131 as sufficient for Step 3 and move to Step 4 /op:delegate design/implementation, unless owner wants live TUI dogfood first.