Issue-resolution ledger · verified · snapshot 2026-09-16 21:35 UTC
Implement Step 4 of the Pi Operator extension roadmap from owners-manual/pbc/appendix-pi-operator-extension.pbc.md: add /op:delegate only. It must use a chooser-first surface and preserve the verified Step 1-3 boundaries. /op:delegate sends bounded implementation work to another agent while the current Pi agent remains in the loop. It must not offer unroutable targets silently: if target is alread
The extension holds the Operator authority boundary at step 4: /op:delegate is chooser-first over configured targets that distinguish ledger harness id, carrier/adapter id, model, isolation, and brief format. A parent-routed assigned_harnes
Step 4 /op:delegate files exist: .pi/extensions/operator/index.ts registers op:delegate; core.ts exports classifyDelegateTarget, taskCreateArgv, sessionStartArgv, and adapterInvokeArgv; targets.json lists harness_id plus carrier_id without
test_output for claim-0132
test_output for claim-0132
manifest for claim-0133
manifest for claim-0133
Supervisor reviewer (review_harness pi-01a05bf2, then a distinct verifier UID) should rerun the selftest and focused pytest, inspect that parent routing is not mutated and dual-role targets are refused, and only then attach status-setting e
advisory-agent review of claim-0132 as n/a
test_output for claim-0132
paper_section for claim-0132
Run /op:supervisor-review on claim-0132 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-0132
Recommended: run Step 5 dogfood using the extension itself in Pi TUI, including at least one /op:delegate or /op:supervisor-review loop plus /op:handoff, then decide whether PBC commands are next.
go
Implement /op:handoff generated-draft/minimal-closeout fix, then rerun live TUI dogfood.
/op:handoff now supports generated closeout semantics for live dogfood: the template is prefilled with deterministic task-context sections, typing 'go' as the whole editor content or as /op:handoff go accepts the generated draft rather than
test_output for claim-0134
manifest for claim-0134
Reload Pi and run /op:handoff go on pi-operator-extension-step4; confirm it creates a non-empty generated handoff, not next_action: go.
Reload Pi and run /op:handoff go on pi-operator-extension-step4; confirm it creates a non-empty generated handoff, not next_action: go.
Reload Pi and run /op:handoff go on pi-operator-extension-step4; confirm it creates a non-empty generated handoff, not next_action: go.