Issue-resolution ledger · verified · snapshot 2026-09-16 21:35 UTC
Implement Step 1 of the Pi Operator extension roadmap from owners-manual/pbc/appendix-pi-operator-extension.pbc.md: add a project-local Pi extension for read-only orientation commands only. Required commands: /op:doctor runs ./operator doctor and displays concise success/failure; /op:status shows current task orientation plus recent ledger state without modifying authority records; /op:tasks wraps
Step 1 of the Pi Operator extension exists as a project-local pi extension at .pi/extensions/operator/ (index.ts, core.ts, render.ts, selftest.ts, README.md), discoverable by pi's .pi/extensions/*/index.ts rule.
The extension selftest passes 87/87 with 0 failed and 0 skipped: tier A pins core.ts argv builders and output parsers against a throwaway ledger built by the real ./operator; tier B loads index.ts through pi's own extension loader with no l
Adding the extension leaves the repo suite green: python3 -m pytest tests/ -q reports 542 passed, 10 skipped, including the 5 new tests in tests/test_pi_operator_extension.py. The new test file is clean under ruff, black and isort.
The extension holds the Operator authority boundary at step 1: it registers exactly op:doctor, op:status, op:tasks and op:use and zero model-callable tools; core.ts assertSafeArgv refuses any subcommand outside {doctor, task-list, task-show
run_log for claim-0121
test_output for claim-0122
run_log for claim-0123
external_doc for claim-0120
Reviewer pi-01a05bf2 (or another identity whose OS uid differs from 1000) should load the repo in pi, trust the project, run /op:doctor, /op:status, /op:tasks and /op:use interactively to confirm the TUI dialogs and the report renderer beha
Read /home/blueaz/operator-control-plane/.operator/delegations/pi-operator-extension-step1/claude-opus-implement/delegate-pi-operator-extension-step1-claude-20260901T151151.log, then evaluate the brief's acceptance checklist against the del
advisory-agent review of claim-0123 as n/a
Read /home/blueaz/operator-control-plane/.operator/delegations/pi-operator-extension-step1/grok-supervisor-review/delegate-pi-operator-extension-step1-grok-20260901T154607.log, then evaluate the brief's acceptance checklist against the deli
run_log for claim-0123
external_doc for claim-0123
Re-run the same verify_cmd as a registered verifier UID distinct from 1000 (971 luna-review-ffsi001-rowa or 966 operator-verifier) and, if it still passes, attach --status verified --verified-by <that registry name>. Do not treat this same-
Use the provided temporary auth to rerun the claim-0123 verify command under a registered verifier UID and attach verified status if it passes; then record the UID/auth wrinkle as a PBC/dogfood issue for supervisor-review.
Use an interactive auth path to run the claim-0123 verification under operator-verifier or luna-review-ffsi001-rowa; after that, attach verified status if it passes.
run_log for claim-0123
Owner decision: proceed to Step 2 (/op:claim, /op:evidence, /op:handoff) or request additional verification of claims 0120-0122 before continuing.