kami
bfb57c3148
The prompt named seven intents but never said which one a clock or date question belongs to, so the model guessed: system->query x4 in every eval run. The rule now says the clock and the calendar date themselves are system, what is written in the calendar or in memory stays query, and a time named inside a request is just part of the request. That split follows what the daemon can answer. Only replySystem owns the clock and the date formatter, while the agenda is answered from CalendarEvents inside the query branch. Also adds one calendar-agenda fixture case so an over-broad system rule cannot pass unnoticed, and writes up the before/after numbers. The targeted confusion is gone; the headline accuracy did not move. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CGeSZxh1DCtRxmFVSYVGvJ