Repository navigation
feat(agent-kiro-kit): run a pinned agent with policy hooks (Story 8.1) - #37
Merged
botanarede merged 3 commits intoNov 17, 2026
Merged
Conversation
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.
Story 8.1 (Epic 8). The Kiro adapter always passes --agent and --agent-engine v3 (D-28), keeps --trust-all-tools with a deny-by-default hook (D-30), installs the Delivery agent through an operator command (D-29), removes the curl auto-install, and returns hook counts in AgentResult.events.
Gates on the head commit: agent-kiro-kit 81 passed; profile-dev-kit 922 passed, 1 skipped; mypy clean; ruff and format findings identical to base or fewer; schema validator 46 kits passed; diff 63840 bytes.