feat(daemon): isolate provider startup recovery - #119
Conversation
ae914b9 to
722a512
Compare
e153394 to
206e948
Compare
PR SummaryHigh Risk Overview Provider I/O is fenced by connection generation: Cached reads stay honest during outages: The supervisor races reactor, recovery, and disconnect per generation, wraps registry recovery in shared-core errors, and Reviewed by Cursor Bugbot for commit f969fb2. Configure here. |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_dfc26489-8fae-4d9f-be23-88bcfebed260) |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour 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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 722a51278c
ℹ️ 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 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 address that feedback".
722a512 to
cf65364
Compare
206e948 to
2e1b5ca
Compare
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_61eee65f-2b49-4a1c-afc4-4fda7aa2c907) |
2e1b5ca to
bedb1a6
Compare
cf65364 to
2101434
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. Bravo. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
2101434 to
65a7a3c
Compare
bedb1a6 to
53d321f
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
65a7a3c to
bdb5218
Compare
53d321f to
68f04b0
Compare
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_bd3056c1-22fe-4efb-8a12-cd514a0f438e) |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bdb5218a90
ℹ️ 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 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 address that feedback".
bdb5218 to
67fd6b8
Compare
68f04b0 to
d90c934
Compare
67fd6b8 to
b0609f4
Compare
d90c934 to
64ca4a2
Compare
b0609f4 to
f969fb2
Compare
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_693cd3e0-475d-44f1-b926-6dd139fadeeb) |

Context
The registry and control plane must remain readable while one provider is starting, recovering, or unavailable. Provider lifecycle failures should remain local, while shared registry or control failures stay visible as daemon failures.
What changed
Verification
7e5d6bais clean at 5/5 with zero P0–P3 findings; adversarial supervisor coverage exercised all 27 immediate and 12 delayed recovery/closure outcome combinations.Risks and boundaries
Provider actions remain unavailable or in startup state until a current generation is ready; preview paths do not start a Hermes runtime. The stack remains ready for review and unmerged.
Closes: DIS-83