engrim 1.2.0 — the log records the work, not just the talk

The transcript log kept prose only, which left it too chat-focused. Measured on one real session: 14 KB of visible text against 315 KB of tool traffic — so the record of what was actually done, files changed and releases cut, existed nowhere searchable.

Action lines

Each state-changing tool call now folds into the log as one line:

[changed] src/engrim/cli.py
[ran] Cut the release — gh release create v1.2.0 …

A snippet of value, not the payload: 93 KB of tool calls became ~10 KB of readable spine. Deliberately state-changing only — greps and reads are how you find things, not what you did, and including them buried the signal 4:1.

recall --log

Extraction without reachability is nearly pointless, so recall can now search the transcript alongside curated memory:

engrim recall -q "release.yml" --log

Opt-in, so the two-tier split holds: the log still never auto-loads into context, it's just no longer unreachable when you ask. Plain scan, no FTS table — 21 ms over 44k rows doesn't justify an index or a migration.

Existing history isn't left behind

engrim log --reindex re-derives searchable text from the raw turns already on disk. On the author's store that recovered 2,619 turns across eight projects, in under a second each.

Action lines never trip the ✎ to capture nudge — they're a record of work, not a decision to curate. 86 tests.