Skip to content

Activate shared SpanOp journaling and resumable routing - #184

Merged
Stephen Belanger (Qard) merged 3 commits into
mainfrom
pipeline/05-journal-boundary
Oct 19, 2026
Merged

Stephen Belanger (Qard) merged 3 commits into
mainfrom
pipeline/05-journal-boundary

Conversation

@Qard

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

Copy link
Copy Markdown
Collaborator

Routing consumes persisted, route-neutral SpanOps through an independent durable head for each destination. One source/session actor owns translation and atomically commits bounded output with its consumed event position; routing resume reads those values without replaying translation. Released event checkpoints seed new route heads, and ordered checkpoint/finalize/retirement controls preserve restart and late-response behavior.

This activates the adapter from #177. Native correlation observations remain independent of retirement exports and sink progress. Deferred roots retain their unresolved prefix until checked delivery, while shutdown waits every route through shared retirement output. Canonical profile-ID heads recognize legacy named routes. Event and transcript reconstruction inputs are protected from existing age-only collection; completed-partition collection and typed recovery conditions follow in later layers.

Birth provenance is journaled for every owned span before routing, including tool and LLM spans. Ordered controls retain the latest native capture versions for newly discovered work. The delivery ledger reuses journaled snapshots while preserving main's append-only format, cross-process locking, legacy migration, and first-persisted snapshot precedence. Plugins cannot replace protected provenance. Stage bookkeeping uses non-poisoning mutexes and explicit error handling under the production panic bans.

Based on main at b2d8c59, including merged #177.

Pipeline layer 5; base: main (includes #177). Recovery transitions and lifecycle consolidation remain separate PRs.

Validation at 1903cb1: all 523 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 efa2119: all three commits retain identical patches (git range-diff); diff checks pass. Tests are left to fresh CI as requested.

@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-13T18:14:17.847180Z 00080d4 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: 00080d483d

ℹ️ 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/server/maintenance.rs
Comment thread bt-daemon/src/server/recovery.rs
Comment thread bt-daemon/src/server/maintenance.rs Outdated
Base automatically changed from pipeline/04-durable-channel to main October 19, 2026 18:32
@Qard
Stephen Belanger (Qard) merged commit f7b7683 into main Oct 19, 2026
22 checks passed
@Qard
Stephen Belanger (Qard) deleted the pipeline/05-journal-boundary branch October 19, 2026 18:44
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