Release Ambush Streams 0.2.0 for Codex - #1
Draft
ecejas wants to merge 1 commit into
Draft
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.
Why
The public Codex marketplace package is still version
0.1.0and describes only the original six Ambush stream lifecycle tools. It does not teach Codex how to configure per-event processing, discover safe destination metadata, or route future events through Ambush’s native delivery pipeline.psychobot-team/reflex#4724 adds that MCP surface and hardens it against webhook credential exposure while correcting the destructive annotation for route muting. This PR prepares the public Codex package as the corresponding
0.2.0release.What changed
0.1.0to0.2.0.post_processing,list_channels,route_feed_channel, andupdate_feed_channel_routeworkflows to the bundled skill.The package keeps its existing
ambush-streamsinstallation coordinate and user-facing stream terminology. The MCP API’s legacy*_feedidentifiers remain unchanged.User impact
After the API release, Codex users can configure a stream’s future-event transformation and delivery route conversationally without sharing endpoint credentials or creating a polling task. Existing lifecycle workflows remain compatible.
Rollout dependency
Keep this PR in draft until psychobot-team/reflex#4724 is merged and deployed. Before merging or publishing
0.2.0, run a production tool scan and confirm all nine tools, sanitizedlist_channelsoutput, anddestructiveHint: trueonupdate_feed_channel_route.Verification
quick_validate.py plugins/ambush-streams/skills/manage-ambush-streams— passed.validate_plugin.py plugins/ambush-streams— passed.git diff --check— passed.