Turtle
e7def469e1
* feat(i18n): key translation pairing records by heading section Replace the whole-file blob hashes in *.i18n.yaml with one entry per heading section that still holds language-specific content, keyed by the English heading-slug path. Blocks identical across the pair (generated table rows, code blocks, shared regions) stay out of the hash, so edits to different sections and identical regenerations merge with Git's default text merge, including on GitHub. Remove the dsh-translation-pairing merge driver, its resolver command and installer wiring; gen-translation-brief recovers last-confirmed text from commit history. Migrate all active records, archive the superseded Agent Note, and record the replayed conflict reduction in the new one. * test(i18n): refresh translation prompt snapshot for the terminology note * feat(i18n): exclude only code blocks and generated regions from pairing records Replace byte-equality masking with an explicit rule: a record hash skips fenced code blocks and BEGIN/END GENERATED regions, the two kinds of content the pairing gate already requires to be identical on both sides. Move generated data into regions written into both pages: gen-config-catalog renders both languages and the record with per-package regions labelled by code identifiers; gen-module-graph keeps its table in a region; gen-doc-graphs splices the event matrix regions into the Chinese page. Add a generic region splice beside the region grammar.
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.