You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wire RuleTracker write-path for self-evolving rule effectiveness (#1444):
- Extend RuleStats with generatedRule / baselineFailureRate / currentFailureRate
- Add markRuleAsGenerated(name) and recordFailureRate(name, rate, kind) APIs
- Existing trackRuleUsage preserves the generatedRule flag across updates
- Drop cast hack in RuleInsightsService now that fields are first-class
- 7 new rule-tracker tests cover tagging, failure rate recording, and persistence
Sync auto-generated plugin README with manual surface additions (#1218):
- scripts/build.ts feature table now includes Staged planning, Clarification
gate, Permission forecast, and Council scene rows
- Footnote matches post-v5.4.0 wording ("features that read agent definitions")
- Regenerated README.md bumps version 5.4.0 → 5.4.1 (aligning with package.json)
Also closes already-implemented sub-issues found by the verification pass:
#1442 (pipeline wiring), #1443 (suggest_rules handler), #1445 (prompt
suggestions), #1446 (onboarding tour integration), #1447 (PreToolUse rule
checker), #1448 (violation renderer).
> ¹ Standalone specialist prompts require a local \`.ai-rules/\` directory. Run \`npx codingbuddy-rules init\` to scaffold it. See [#1216](https://github.com/JeremyDev87/codingbuddy/issues/1216) for the standalone enhancement roadmap.
133
+
> ¹ Standalone features that read agent definitions require a local \`.ai-rules/\` directory. Run \`npx codingbuddy-rules init\` to scaffold it. See [#1216](https://github.com/JeremyDev87/codingbuddy/issues/1216) for the standalone enhancement roadmap.
0 commit comments