v1.4.1 — one injection, counted once

A measurement that decides what gets built has to be right before the thing gets built. This one was not, and it was pointing at a working channel.

The bug

The usefulness scan charged twice for every push delivered on the per-turn seam. On that seam the host echoes a hook's output back into the attachment's content field, so the transcript records the same injected block in two places — while the model is shown it once. The scan summed both.

The tool-call seams carry the block once and were never affected, so the entire error fell on a single channel.

Why it mattered

The error was invisible for the reason such errors usually are: it was consistent. The per-turn channel simply looked expensive — expensive enough that trimming it was the obvious next piece of work.

Corrected, it costs about half what it appeared to. That puts it mid-pack among the push channels rather than worst, and the channel it would have been trimmed in favour of is now the dearest of them.

What changes for you

• Measured push cost falls by roughly a seventh on a lived-in store, so fornixdb value is that much less pessimistic about what memory costs.
• The per-channel cost-per-reference figures introduced in 1.3.0 are now correct for every channel.
• No behavior changed — only the accounting of what was already happening. Nothing pushes differently, and no stored data is affected.

If you acted on a per-channel cost figure from 1.3.0 or 1.4.0, re-run fornixdb value --transcripts <dir> before acting further.

1101 tests + 1 skip.

Install: pip install "git+https://github.com/itdtllc/fornixdb@v1.4.1"