FabledGrimoire

Both said the repeated read-and-clamp was "canon #2860 across 295 of 372
siblings". Wrong on both halves, and checked rather than assumed:
#2860 is "Scribe service function — the async_session unit", the
service-layer canon, and its instance count is that canon's dominance in
src/scribe/services — nothing to do with a threshold helper. The
divergence hook flagged the new module against it because the new module
is a service, which is the hook working correctly and me misreading it.

The duplication itself was real and is what the registry consolidated:
`plugin_context` read and clamped the pair twice over, three rule arms
did it again, and `reply_preferences._threshold` once more. The comments
now say that, and claim nothing about a ledger count.

`rule_usage.py:122` cites #2860 correctly as the service canon and is
untouched.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01821k5B3Ysecp9fNYs92Kuy

2026-09-17 11:41:30 -04:00

mcp

docs(retrieval): stop asking the operator to diagnose retrieval (#4102 )

2026-09-17 11:38:16 -04:00

models

fix(tests): two readers moved, and the settings guard now checks the registry (#4102 )

2026-09-17 11:20:47 -04:00

routes

feat(retrieval): the operator can see what was tuned, and every write is recorded (#4102 )

2026-09-17 11:36:22 -04:00

services

fix(docs): two comments cited the wrong snippet for the duplication (#4102 )