Files
openclaw/docs/.generated
Ayaan Zaidi 7c47e4ad0e fix(channels): collapse cumulative commentary snapshots onto one progress-draft line
Providers stream commentary as cumulative snapshots, and the draft line id was derived from the commentary text, so each snapshot minted a new id and stacked another line instead of replacing the open one. Id-less commentary now remembers its open line and reuses that id when the next snapshot continues it; a snapshot sanitized to nothing no longer clears the line, since only an explicit item id retracts.

Also fixes activation: the commentary gate guessed "partial" when streaming.mode was unset, which made progress.commentary a silent no-op on channels whose own default is progress (Telegram, Discord). It now takes the caller's resolved mode, matching resolveChannelStreamingPreviewToolProgress. Proven live on Telegram: three overlapping commentary lines collapse to one.
2026-07-30 16:36:16 +09:00
..

Generated Docs Artifacts

SHA-256 files are tracked drift-detection artifacts. Full generated snapshots remain local inspection artifacts.

Tracked (committed to git):

  • config-baseline.sha256 — hashes of config baseline JSON artifacts.
  • config-baseline.counts.json — maximum entry counts for each config baseline kind.
  • plugin-sdk-api-baseline.sha256 — one hash per Plugin SDK entrypoint.
  • sqlite-session-transcript-schema-baseline.sha256 — hash of the sessions/transcripts SQLite schema baseline.

Local only (gitignored):

  • config-baseline.json, config-baseline.core.json, config-baseline.channel.json, config-baseline.plugin.json
  • plugin-sdk-api-baseline.json, plugin-sdk-api-baseline.jsonl
  • .artifacts/sqlite-session-transcript-schema-baseline.sql

Do not edit any of these files by hand.

  • Regenerate config baseline: pnpm config:docs:gen
  • Validate config baseline: pnpm config:docs:check
  • Regenerate Plugin SDK API baseline: pnpm plugin-sdk:api:gen
  • Validate Plugin SDK API contract manifest: pnpm plugin-sdk:api:check

The Plugin SDK manifest hashes each entrypoint independently. PRs changing separate public modules therefore update separate records instead of racing to overwrite one whole-surface checksum. Concurrent changes to the same entrypoint remain a real merge conflict and require regeneration against combined source.

  • Regenerate SQLite sessions/transcripts schema baseline: pnpm sqlite:sessions-schema:gen
  • Validate SQLite sessions/transcripts schema baseline: pnpm sqlite:sessions-schema:check