Skip to content

follow-up: MCP / Telegram / briefings should pass framework + lens to writeTurnSummary #4

@fru-dev3

Description

@fru-dev3

`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:

  1. src/mcp-server.ts — MCP-initiated turns
  2. src/telegram.ts — Telegram bot turns
  3. src/briefings.ts — scheduled daily briefings

Each should:

  1. Read `resolveResponseFramework(domainKey)` and `resolveResponseLens(domainKey)` before firing the turn
  2. Convert ids to display labels via `getFramework(id)?.label` / `getLens(id)?.label`
  3. 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".

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfollow-upKnown follow-ups from commits that should become real work items

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions