Attachment reads and ZIP export previously inferred ownership from common field names on arbitrary events. Opaque ignorable plugin payloads could therefore cause storage reads, while declared compaction content was missed. Select attachment-bearing fields by current built-in event type in both readers. Read direct image and file blocks, including flat V4 tool results and developer messages, without interpreting extra block fields. Leave unknown payloads and malformed inbox entries opaque. The archive preserves the complete logical log even when its payload does not authorize a read. V4 validates title requests as one text block, so do not treat them as an attachment carrier. Compaction keeps its declared ContentBlock fields for valid custom producers; the basic producer's text-only output is documented. Historical wrappers remain the adjacent converters' responsibility rather than a second compatibility path in attachment readers. Adapt the original policy change to master after V4 landed, retaining its author credit and scope. Cover tool-result export explicitly, keep Team fixtures free of invented message roles, and verify that denied carriers never read storage. The 889 owning tests pass with 100% statement, branch, function, and line coverage for both changed runtime files. Co-authored-by: Tianyi Cui <[email protected]>
description, kind
| description | kind |
|---|---|
| Package map for the session retrieval capability family: searching, tracing, and reading live and durable session history, plus the Web session-log export. | package-group |
session-query/ — session retrieval capability family
English | 中文
Summary
The session-query/ group provides retrieval over live and durable session history, independent of compaction: programmatic callers query one unified service for exact logs, filtered lists, relationship traces, and full-text search; a SQLite backend powers the search; the model gets five workspace-authorized tools; and the Web UI gets an /export command that downloads a session ZIP. Search results agree with the conversation history the model sees. This page maps the group; each package README owns its per-package contract.
Table of Contents
Packages
Each package README describes what you can do with its part of the family.
| Package | Role | ctx key |
|---|---|---|
session-query/ |
Unified session-history query service: exact reads, relationship traces, and filters | ctx.sessionQuery |
session-query-sqlite/ |
Full-text search across session history backed by a SQLite FTS5 index | registers on ctx.sessionQuery |
session-log-export/ |
Web /export command and browser download of a session ZIP |
ctx.sessionLogDownload (browser) |
tool-session-query/ |
Model-facing tools to search, trace, and read session history | registers on ctx.tools |
Related documentation
Start with the subsystem reference for the shared query vocabulary, then the design records behind tracing and search.
- Session Query subsystem reference — logical records, filters, search pages, lineage, bounded reads, and event relationships.
- Session query relationship tracing — trace semantics and the validation boundary.
- SQLite FTS5 session search — search semantics, reconciliation, and the tokenizer decision.
Dev Note
None.