refactor(maintenance): extract store kernels and tick policy from root - #1177
Conversation
…plan-reopened' into grok/w2-maintenance-kernels
|
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: f27db40b33
ℹ️ 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".
0b5ccfd
into
codex/tracedecay-total-redesign-plan-reopened
Performance Comparison
|
Move maintenance kernels into their owning crates while keeping one canonical enrollment identity implementation. Retention, lifecycle, and selected-memory callers now use the same policy. Degraded maintenance outcomes retain warning-level visibility under the default log filter.
The corrected head preserves existing cancellation and durability behavior. Validation: two enrollment regressions, three selected-memory authorization/isolation journeys, and one real WARN/INFO subscriber test pass (cc-12932/12935/12933). Strict runtime-core, maintenance, and root library/test Clippy passes without warnings (cc-12934).