Describe uses inside definitions: mock 45, kind: with ref:, content: or struct: finds each line inside the definitions it keeps; a name and a file's text are searched apart
Keep short names only for file:, author:, symbol:, language: and message: (f:, a:, sym:, lang:, msg:); the old letters and path: offer the full name
Describe searching from your code: mock 50, the selection, Find Definitions and Find Uses, and the setting
kind: a word next to kind: or symbol: matches the definition's name Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Definitions and code shape: struct: examples end with code The examples a == :[b] and if :[x] == :[x] end with a hole, which a template can't: a hole takes as little as it can, so at the end it would always take nothing. They now end with code, and the page says why. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Split the query reference into one page per operator family Each operator gets one card (short name, what it takes, what it searches, an example) on the page for its family, with the screens that show it beside it. Query Language becomes the one-screen summary, linking every operator to its card. Operators in Action and Core Query Modes are dissolved into these pages. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>