Repository navigation
fix: retain captures during worker restarts - #10
Merged
Merged
Conversation
davidrobertson
deleted the
fix/preserve-capture-during-worker-restarts
branch
October 10, 2026 16:53
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.
Capture hooks could lose observations during a daemon restart: the engine's HTTP listener stayed up while the worker route returned 404, and clients treated that as a permanent rejection. Hooks now spool those observations, and CLI drains retain existing records until the route returns. Validation and authentication rejections keep their existing behavior.
This follow-up publishes fork version
0.9.30-codex.2with matching plugin manifests and export compatibility.Validation: both new regressions failed before the fix. Final suite: 2,683 passed, zero failures, four opt-in skips. All ten packed-artifact scenarios passed. A real iii 0.22.1 engine without a worker returns404, the hook spools, the CLI keeps the record, and worker startup recovers it into searchable memory. Independent review and QA reports are bound to the final source SHA before handoff.