@misterhuydo/cairn-mcp 1.36.1 → 1.37.0

package/README.md

@@ -520,6 +520,38 @@ them to `[object Object]`, so the most substantial notes were the ones that arri
 noise. When a feature demands expensive judgement from the agent, test the whole return
 path, not just the write.
 
+**v1.37.0 gives the handoff somewhere permanent to live, and stops previews cutting
+mid-word.** `session.json` holds exactly *one* `would_be_lost`, and every manual
+checkpoint overwrites the last, so a project's history of what each session would have
+lost was destroyed one checkpoint at a time — and the rotation at 100KB scattered
+whatever survived across `session.N.json` files nobody reads. The most expensive field
+cairn ever asks an agent to produce had the shortest life of anything cairn stores.
+
+Every answered handoff is now appended to **`.cairn/handoff.md`**: full text, never
+clipped, newlines intact, plain Markdown you can read or grep without cairn. Newest
+first — unlike `roadmap_completed.md`, which appends at the end because it is a shipping
+record read in order. This is a lookup, so it is ordered for the lookup. The every-turn
+heartbeat is not logged; only a real answer is, or a handful of genuine judgements would
+be buried under thousands of identical copies. It is an addition rather than a migration:
+`session.json` keeps the field unchanged as the hooks' fast path, so nothing that reads
+it needs to know the file exists.
+
+Previews no longer end mid-word. A cut like `…the re-injection clipped would…` is worse
+than a shorter clean one: the reader cannot tell whether the truncated token was `would`,
+`would_be_lost` or `wouldn't`, so the last thing they are shown is the one thing they
+must not trust. `clip()` backs up to the last space and drops trailing punctuation. The
+exception is deliberate — an unbroken run longer than the cap (a stack trace, a base64
+blob, a Windows path) has no boundary to back up to, so below a 0.6 floor it takes the
+hard cut rather than returning almost nothing. The cap itself went 220 → 400, because at
+220 the budget line reliably died inside the first sentence of point (1): enough to prove
+a handoff existed, not enough to say what it was about.
+
+One test had to change, and it is worth saying which. The v1.36.1 guard asserted the
+every-prompt line stayed under 300 characters — a magic number tied to the old cap, so it
+failed on a change that was entirely intended. It now asserts a *ratio*: the preview must
+stay under half the payload. The invariant was never a particular length, it was that one
+channel stays a preview while the other carries everything.
+
 It needs no rate limit: it self-extinguishes. The moment the handoff is written the
 demand returns null, and it speaks again only if later commits make that answer stale.
 Crossing is remembered in `.cairn/.handoff-gate` and forgotten when usage drops back