FabledScribe

`current_settings` read a surface's history with one query and `limit(2)`, then
keyed the rows by dial. That is only the same thing while both dials have moved
equally often — and they do not. Floors get walked; budgets rarely move. Three
floor changes and one budget change returns two floor rows, and the budget
change vanishes.

Under #4102 that cost a missing reason. Since #4104 it is worse: the dial then
reports `source: "shipped"` — still on the value Scribe shipped — for a number
somebody deliberately tuned. A wrong calibration answer, in the direction a
reader has no cause to double-check.

One query per dial, `limit(1)` each.

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

2026-09-17 12:49:15 -04:00

mcp

feat(retrieval): a tuned number carries the space it was measured in (#4104 )

2026-09-17 12:45:48 -04:00

models

feat(retrieval): a tuned number carries the space it was measured in (#4104 )

2026-09-17 12:45:48 -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(retrieval): the newest two rows are not the newest row of each dial (#4104 )