Skip to content

Release Ambush Streams 0.2.0 for Codex - #1

Draft
ecejas wants to merge 1 commit into
mainfrom
codex/event-driven-workflows-v0.2.0
Draft

Release Ambush Streams 0.2.0 for Codex#1
ecejas wants to merge 1 commit into
mainfrom
codex/event-driven-workflows-v0.2.0

Conversation

@ecejas

@ecejas ecejas commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Why

The public Codex marketplace package is still version 0.1.0 and 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.0 release.

What changed

  • Bumps the Ambush Streams Codex plugin from 0.1.0 to 0.2.0.
  • Adds event-time post_processing, list_channels, route_feed_channel, and update_feed_channel_route workflows to the bundled skill.
  • Routes “every event” requests through Ambush instead of scheduled polling.
  • Documents credential-safe channel discovery: webhook paths and internal metadata are not model-visible.
  • Warns that muting a route permanently cancels pending deliveries and attempts; unmuting only enables future work.
  • Updates plugin descriptions, default prompts, keywords, homepage, READMEs, listing copy, and release notes.
  • Expands reviewer materials from six to nine tools with corrected safety justifications.
  • Adds a deterministic end-to-end review case for transforming and routing every future event to a connected Slack destination.

The package keeps its existing ambush-streams installation coordinate and user-facing stream terminology. The MCP API’s legacy *_feed identifiers 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, sanitized list_channels output, and destructiveHint: true on update_feed_channel_route.

Verification

  • Skill Creator quick_validate.py plugins/ambush-streams/skills/manage-ambush-streams — passed.
  • Plugin Creator validate_plugin.py plugins/ambush-streams — passed.
  • Manifest version audit and JSON parsing — passed.
  • The bundled skill is byte-for-byte identical to the standalone and Claude copies.
  • git diff --check — passed.

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