Repository navigation
fix: preserve managed prompt dispatch and enforce coding ownership - #648
Merged
Merged
Conversation
Session: ses_f1279a464ffepDzWuP5fWg8S5x
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #647.
Verification
The original filter failed the native final-HTTP-payload probe; the candidate passes fresh and resumed requests. The real tool hook refuses a forbidden command before a harmless sentinel executable runs. Deliberate late reinjection produces an actionable diagnostic and zero provider requests.
Passed:
node tests/kimaki-dispatch-contract.mjsbash tests/kimaki-managed-plugin-rig.sh(includes native OpenCode dispatch proof)bash tests/kimaki-system-message-patch.shbash tests/kimaki-agent-fallback.shnode tests/effective-prompt/run.mjsTests use an isolated temporary project and a loopback model fixture, with no production model account or bot restart. The native probe covers the OpenAI-compatible HTTP path; instruction-option contracts are additionally covered without claiming a paid live OAuth evaluation. The command guard is operational ownership enforcement, not an arbitrary-code sandbox.
AI assistance
OpenAI
gpt-6.1-solthrough OpenCode directly investigated, implemented, and verified the repair. Chris identified the leaked orchestration route, requested the fix, and authorized landing this PR.