Skip to content

Isolate routing behind a bounded actor port - #175

Merged
Stephen Belanger (Qard) merged 3 commits into
mainfrom
pipeline/02-routing-actor
Oct 19, 2026
Merged

Stephen Belanger (Qard) merged 3 commits into
mainfrom
pipeline/02-routing-actor

Conversation

@Qard

@Qard Stephen Belanger (Qard) commented Oct 13, 2026 •

Copy link
Copy Markdown
Collaborator

Routing owns plugin execution, sink configuration, and delivery state behind a bounded typed actor port. The existing session handle and event replay remain intact. Completion-preserving envelopes forward typed requests; replies carry sink outcomes and pending-delivery status.

Partial plugin failures preserve counts for successfully emitted rows and report cached failures only once. Routing bookkeeping uses the same non-poisoning mutex as dispatch, and completion failures return an error rather than panic. Channel-port contracts now have production consumers, removing the preceding layer's temporary allowance.

Based on main at 2fc47d5, including merged #174 and the landed Rust SDK pin f2216fa0. Later pipeline layers remain separate.

Validation at d2216c2: all 515 tests pass in the locked all-feature Rust suite without exclusions or environment overrides; five live-agent tests remain normally ignored. Strict all-target/all-feature Clippy, formatting, and diff checks pass.

Rebased at cb30038: all three commits retain identical patches (git range-diff); diff checks pass. Tests are left to fresh CI as requested.

@Qard
Stephen Belanger (Qard) force-pushed the pipeline/02-routing-actor branch 2 times, most recently from 3d5a83b to 94b44aa Compare October 13, 2026 16:03
@Qard
Stephen Belanger (Qard) force-pushed the pipeline/02-routing-actor branch 4 times, most recently from 68dc53a to 48ee623 Compare October 13, 2026 16:48
@Qard
Stephen Belanger (Qard) marked this pull request as ready for review October 13, 2026 17:01
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-13T17:05:06.829794Z 48ee623 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 48ee623cd5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "Codex (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

Comment thread bt-daemon/src/pipeline/routing.rs Outdated
Comment thread bt-daemon/src/pipeline/routing.rs
@Qard
Stephen Belanger (Qard) force-pushed the pipeline/01-stage-contracts branch 2 times, most recently from 026a97f to 45ca37f Compare October 16, 2026 14:19
@Qard
Stephen Belanger (Qard) force-pushed the pipeline/02-routing-actor branch 2 times, most recently from 40cfa8c to d2216c2 Compare October 16, 2026 16:11
Base automatically changed from pipeline/01-stage-contracts to main October 19, 2026 17:58
@Qard
Stephen Belanger (Qard) merged commit 977101b into main Oct 19, 2026
22 checks passed
@Qard
Stephen Belanger (Qard) deleted the pipeline/02-routing-actor branch October 19, 2026 18:08
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.

2 participants