feat(config): promote scheduler and guardrail features to default#2106
Merged
feat(config): promote scheduler and guardrail features to default#2106
Conversation
github-actions
bot
added
documentation
bug-ops
force-pushed
the
feat-issue-2099-promote-scheduler-guardrail
branch
from
359a261 to
63006f9
Compare
Add scheduler and guardrail to the default feature set. Both features have been extensively live-verified (scheduler: CI-30/32/54/58; guardrail: CI-42/45). No behavioral change: scheduler.enabled is already true in default.toml; guardrail is runtime-disabled by default. Remove scheduler from desktop and server bundles (now redundant with default). Add scheduler explicitly to full bundle to preserve --no-default-features --features full behavior. Closes #2099
bug-ops
force-pushed
the
feat-issue-2099-promote-scheduler-guardrail
branch
from
63006f9 to
3fd532f
Compare
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
1 participant
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.
Summary
schedulerandguardrailtodefaultfeatures in rootCargo.tomlschedulerfromdesktopandserverbundles (now redundant with default)schedulerexplicitly tofullbundle (preserves--no-default-features --features fullbehavior)default.tomlcopiesMotivation
Both features have demonstrated strong stability through extensive live testing:
scheduler.enabled = true.[security.guardrail] enabled = falseby default).Risk
LOW. Adding features to default is additive. Users with
default-features = falseare unaffected. No behavioral change at runtime.Pre-commit checks
cargo +nightly fmt --check— cleancargo clippy --workspace --features full -- -D warnings— 0 warningscargo nextest run --config-file .github/nextest.toml --workspace --features full --lib --bins— 6363 tests passedcargo check(default features) — compiles cleanlycargo check --no-default-features— compiles cleanlyCloses #2099