docs: batch fix filler Note/page openers and one TUI auth Warning

- gateway/authentication: tighten model-provider Note opener
- help/debugging: drop 'this page covers' filler
- reference/session-management-compaction: rephrase end-to-end intro
- reference/transcript-hygiene: drop 'this document describes' filler
- web/index: collapse 'this page focuses' filler
- web/tui: convert prose --url Note to Warning component
This commit is contained in:
Vincent Koc
2026-04-26 22:11:54 -07:00
parent 9df7fe3986
commit 5bba899a70
6 changed files with 10 additions and 16 deletions

View File

@@ -7,15 +7,15 @@ read_when:
title: "Session management deep dive"
---
This page explains how OpenClaw manages sessions end-to-end:
OpenClaw manages sessions end-to-end across these areas:
- **Session routing** (how inbound messages map to a `sessionKey`)
- **Session store** (`sessions.json`) and what it tracks
- **Transcript persistence** (`*.jsonl`) and its structure
- **Transcript hygiene** (provider-specific fixups before runs)
- **Context limits** (context window vs tracked tokens)
- **Compaction** (manual + auto-compaction) and where to hook pre-compaction work
- **Silent housekeeping** (e.g. memory writes that shouldnt produce user-visible output)
- **Compaction** (manual and auto-compaction) and where to hook pre-compaction work
- **Silent housekeeping** (memory writes that should not produce user-visible output)
If you want a higher-level overview first, start with:

View File

@@ -7,11 +7,7 @@ read_when:
title: "Transcript hygiene"
---
This document describes **provider-specific fixes** applied to transcripts before a run
(building model context). Most of these are **in-memory** adjustments used to satisfy
strict provider requirements. A separate session-file repair pass may also rewrite
stored JSONL before the session is loaded, either by dropping malformed JSONL lines or
by repairing persisted turns that are syntactically valid but known to be rejected by a
OpenClaw applies **provider-specific fixes** to transcripts before a run (building model context). Most of these are **in-memory** adjustments used to satisfy strict provider requirements. A separate session-file repair pass may also rewrite stored JSONL before the session is loaded, either by dropping malformed JSONL lines or by repairing persisted turns that are syntactically valid but known to be rejected by a
provider during replay. When a repair occurs, the original file is backed up alongside
the session file.