Skip to content

Refuse native NEAR tool fields before sending or dispatching - #74

Draft
amiller wants to merge 3 commits into
mainfrom
work/near-tool-confidentiality
Draft

amiller wants to merge 3 commits into
mainfrom
work/near-tool-confidentiality

Conversation

@amiller

@amiller amiller commented Oct 14, 2026 •

Copy link
Copy Markdown
Owner

Native tool fields can bypass this integration’s content-only encryption: legacy function-call history was sent unchanged, and the ordinary reply decoder forwarded structured tool calls to Pi. Reject modern and legacy tool history before admission, strip both schema formats, and refuse unsupported tool responses before dispatch. Keep local tools inside encrypted message text.

Move the ordinary stream decoder into a directly exercised module. Normalize SSE data framing before checking it so zero/extra spaces and CRLF cannot bypass the guard. Share tool-field refusal with the coupon adapter, preserve static coupon errors, and retain gift accounting/signature ordering and encrypted reasoning behavior. Regenerate the admitted manifest. Native encrypted-tool support remains disabled.

Validation at b4d092c on zed with freshly built locked dependencies and Node 24.21.0: 41 focused tests pass (NEAR decoder, coupon adapter, chat signatures and in-content parser); documentation checks pass (171 local links/fragments); whitespace/import checks pass. The full offline gate was attempted: 46 suites pass, 9 fail. Failures include an overly long rehearsal Unix socket path, a missing legacy bin/abalone-mcp entry point, browser startup and UI checks. No passing full-gate or baseline-comparison claim is made. Detailed logs are retained locally; installed dependencies and generated build outputs were removed.

Independent review and a passing applicable integration gate remain outstanding. No merge/deployment, paid calls or protocol switch. Relates to #73 and #56, amiller/awesome-private-inference#23, and the proposed DevProof supplement amiller/devproof-audits-guide#5.

@amiller amiller changed the title Document and test the current NEAR encrypted tool boundary Refuse native NEAR tool fields before sending or dispatching Oct 14, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant