`writeTurnSummary` accepts framework + lens display labels (added in v0.8.0) and emits a `> meta:` blockquote with the full cockpit-state snapshot (extended in v0.8.1 to include model, web, serendipity, council mode).
But three callsites currently pass no framework/lens, so turns initiated from them produce _log entries WITHOUT the shaping metadata:
- src/mcp-server.ts — MCP-initiated turns
- src/telegram.ts — Telegram bot turns
- src/briefings.ts — scheduled daily briefings
Each should:
- Read `resolveResponseFramework(domainKey)` and `resolveResponseLens(domainKey)` before firing the turn
- Convert ids to display labels via `getFramework(id)?.label` / `getLens(id)?.label`
- Pass them to the writeTurnSummary call
Same for webAccess / serendipity / councilOn — the v0.8.1 expansion of the meta line. Without this, turns from these surfaces are second-class in the audit log.
Filed in: commit 3224ef6 "fix+feat: NBSP chip spacing · _journal/ rename · full config snapshot in _log".
`writeTurnSummary` accepts framework + lens display labels (added in v0.8.0) and emits a `> meta:` blockquote with the full cockpit-state snapshot (extended in v0.8.1 to include model, web, serendipity, council mode).
But three callsites currently pass no framework/lens, so turns initiated from them produce _log entries WITHOUT the shaping metadata:
Each should:
Same for webAccess / serendipity / councilOn — the v0.8.1 expansion of the meta line. Without this, turns from these surfaces are second-class in the audit log.
Filed in: commit 3224ef6 "fix+feat: NBSP chip spacing · _journal/ rename · full config snapshot in _log".