You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Establish the final harness-admission names/contracts, remove superseded receipt and Pi-specific compatibility paths, pin the actual fork contract, and add real multi-turn provider fixtures before broader hooks are added.
The current system admits user messages and tool results, then re-admits the newest entry at send time. This phase is naming/contract hygiene only; later phases add origins and whole-context binding.
Initial heads: Research c7b757d, Pi 61500e60, OpenShell 8332c459.
Scope
In scope, Research: rename hooks to user_message/tool_result; --require-agent-attestation; registry-based binding resolution; openshell.pi-message.v1 with required origin=user; PiMessageV1Adapter; remove ReceiptClaimsV1, one-use receipt APIs/state, extension-v1, and obsolete receipt reason names; correct middleware manifest proto source/hash/note; add multi-turn Chat Completions, Responses, and Qwen fixtures and strict-schema decisions; mark the managed-harness ledger plan superseded.
In scope, OpenShell: remove LEGACY_PI_BRIDGE_URL_ENV and provider-env insertion.
In scope, workspace: archive the uncommitted /home/ubuntu/workspaces/2/pi-egress-fork design to explore/prepare-context-hook in the Pi fork with a clear note, verify the remote branch, then remove only that archived checkout.
Strictly rejected fields have an explicit fixture/test decision.
The alternate prototype is recoverably archived before its checkout is removed.
Required Validation
Research: cd projects/egress-gate && make check && make check-py311
OpenShell: mise run pre-commit, focused cargo test -p openshell-sandbox, then mise run test/mise run ci before review.
Acceptance grep for pi-input.v1|extension-v1|require_pi_attestation|OPENSHELL_PI_CONVERSATION_URL across current code.
PR Expectations
Keep changes grouped into phase-specific commits. Reviewer notes must call out fixture provenance and every deleted compatibility path. No generated protobuf diff is expected.
Objective
Establish the final harness-admission names/contracts, remove superseded receipt and Pi-specific compatibility paths, pin the actual fork contract, and add real multi-turn provider fixtures before broader hooks are added.
Context
c7b757d, Pi61500e60, OpenShell8332c459.Scope
user_message/tool_result;--require-agent-attestation; registry-based binding resolution;openshell.pi-message.v1with requiredorigin=user;PiMessageV1Adapter; removeReceiptClaimsV1, one-use receipt APIs/state,extension-v1, and obsolete receipt reason names; correct middleware manifest proto source/hash/note; add multi-turn Chat Completions, Responses, and Qwen fixtures and strict-schema decisions; mark the managed-harness ledger plan superseded.LEGACY_PI_BRIDGE_URL_ENVand provider-env insertion./home/ubuntu/workspaces/2/pi-egress-forkdesign toexplore/prepare-context-hookin the Pi fork with a clear note, verify the remote branch, then remove only that archived checkout.Implementation Notes
harness=pias registry data, never a servicer literal check.reserved_header_present.Acceptance Criteria
Required Validation
cd projects/egress-gate && make check && make check-py311mise run pre-commit, focusedcargo test -p openshell-sandbox, thenmise run test/mise run cibefore review.pi-input.v1|extension-v1|require_pi_attestation|OPENSHELL_PI_CONVERSATION_URLacross current code.PR Expectations
Keep changes grouped into phase-specific commits. Reviewer notes must call out fixture provenance and every deleted compatibility path. No generated protobuf diff is expected.