pi-operator-extension-cross-project-delegate
newDo not recreate the FUT slices from this task. Remaining work is owner publishing/commit and any new UX issues (POE-ISS-011..013), not another backlog stub.
Simple Operator board · snapshot 2026-09-16 23:19 UTC · not Graphify, not a knowledge graph
Do not recreate the FUT slices from this task. Remaining work is owner publishing/commit and any new UX issues (POE-ISS-011..013), not another backlog stub.
Cross-project install helper and disposable consumer smoke are verified; publishing and live non-temp consumer trust remain out of scope.
/op:next-steps implementation is verified; no further implementation or verification action is pending on this task.
Implementation claims 0156 and 0161 are verified. Remaining on this task is claim-0155 (Route C compatibility-route record, not proposed-rule ratification) and any later owner-authorized publish/profile work.
Do not start Step 1 from this review task. Use the existing step/FUT task IDs. claim-0119 remains historical on this task.
/op:project dashboard implementation is verified; no further implementation or verification action is pending on this task.
STALE · Owner decision: proceed to Step 2 (/op:claim, /op:evidence, /op:handoff) or request additional verification of claims 0120-0122 before continuing.
STALE · Proceed to Step 3 decision: implement /op:supervisor-review, or first capture the verifier-only draft-evidence limitation in the PBC backlog.
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.
Do not resume this child loop. Parent step4 is verified; later dogfood is on step5 (currently quarantined for source drift).
STALE · Reload Pi and run /op:handoff go on pi-operator-extension-step4; confirm it creates a non-empty generated handoff, not next_action: go.
Do not restore trust on pi-operator-extension-step5-dogfood until an independent uid-966 verifier reruns against a coherent tree; current dirty test file is not that target.
Use the separately scoped Project Phoenix task; do not resume this accidental child task.
Leave for publish hardening; continue cross-project trials or commit PBC backlog updates.
Workflow-guidance tokens on /op:next-steps are verified; no /op:mode command and no further verification action pending on this task.