Update config defaults based on 61 CI sessions of live validation #2101
Description
Summary
8 runtime settings are currently disabled by default but have been validated through 37-61 live CI sessions without issues. Enabling them by default improves the out-of-box experience.
Config Changes
| Setting | Current Default | New Default | Sessions Validated |
|---|---|---|---|
memory.semantic.temporal_decay_enabled |
false |
true (half_life=30d) |
CI-13 to CI-61 (48) |
memory.semantic.mmr_enabled |
false |
true (lambda=0.7) |
CI-13 to CI-61 (48) |
memory.semantic.importance_enabled |
false |
true (weight=0.15) |
CI-24 to CI-61 (37) |
tools.anomaly.enabled |
false |
true |
CI-18 to CI-61 (43) |
tools.audit.enabled |
false |
true (stdout) |
CI-18 to CI-61 (43) |
cost.enabled |
false |
true (max_daily=0/unlimited) |
CI-18 to CI-61 (43) |
autosave_assistant |
false |
true (min_length=20) |
CI-1 to CI-61 (61) |
vector_backend |
"qdrant" (implied) |
"sqlite" |
CI-1 to CI-61 (61) |
Rationale per Setting
- temporal_decay: prevents stale memories from drowning recent ones; 30-day half-life is conservative
- MMR: diversifies recall results; re-ranking only, no data loss
- importance_scoring: 15% weight is dominated by cosine similarity; subtle quality improvement
- anomaly_detection: advisory only (log + warning), never blocks tool execution
- audit_logging: security best practice; stdout default has zero file I/O overhead
- cost_tracking: visibility without cap (max_daily=0); users see what they spend
- autosave: enables cross-session recall; min_length=20 filters trivial noise
- vector_backend=sqlite: zero-dependency out-of-box; Qdrant users set explicit config
Changes
- Update
config/default.tomlwith new defaults - Update
--initwizard defaults to match - Add
--migrate-configmigration step for existing configs - Update documentation with new defaults
- Document all changes in CHANGELOG.md as behavioral change
Risk
- LOW for most settings (advisory, non-blocking, conservative thresholds)
- MEDIUM for
vector_backend = "sqlite": existing Qdrant users need explicit config after update
Analysis
Full details: .local/reports/feature-stabilization-analysis.md, Section 3