grounder 0.3.0 → 0.5.0

package/templates/agents/claude/commands/grounder-plan.md

@@ -1,4 +1,4 @@
-Write a named, updatable plan document to the Obsidian vault for this project.
+Write a named, updatable plan document to the markdown vault for this project.
 
 Distill the instruction after `/grounder-plan` into a structured plan — not a chat transcript.
 Do not dump tool traces, full conversation, or false starts.
@@ -22,31 +22,35 @@ Build a markdown body with these sections:
 …
 ```
 
-Update vs create — never guess a `--title` for an update:
+**Special case: the instruction asks to view existing plans, not name a new topic** (`list`, `list 3 oldest`, `show plans`, etc.) → run `{{GROUNDER_CLI}} plan list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no plan write, no title. Relay the CLI stdout as-is (it already includes the count header; title lines are clickable `[relativePath](fileUri)` links).
 
-**1. Path known** (attached/open in chat, or printed by an earlier `grounder plan` this conversation): update that exact file.
+Otherwise, resolve the target, then **state it plainly before writing** — `Updating plan at <path>.` or `Creating new plan titled <title>.` This is a visible record, not a blocking confirmation — updates overwrite with no `--force`, so get the match right.
+
+**1. Known path** (attached/open in chat, or printed by an earlier `grounder plan` this conversation) → update it directly.
+
+**2. No path, but update intent** (e.g. "update/continue/revise the plan", or a name that sounds like an existing one) → look it up first:
 
 ```bash
-{{GROUNDER_CLI}} plan "$(cat <<'EOF'
-# Plan: …
-…
-EOF
-)" --path <path-to-existing-plan.md>
+{{GROUNDER_CLI}} plan list --limit 5 --markdown
 ```
 
-`--path` must resolve under this project's `plans/` dir; it always overwrites (no `--force`).
+CLI output starts with a count header, then each result as a numbered two-line block — `N. ` + `[relativePath](fileUri)` on the first line, the absolute path indented beneath it (use that absolute path for `--path`).
 
-**2. Path unknown** (e.g. "update the plan" with nothing attached and no prior path this conversation): look it up, then update as in (1).
+A match counts only if the filename stem / relative path actually corresponds to what the user named — not just "it's the only plan in the project." No name given and exactly one plan exists → that counts too. If the user refers to a plan by the number shown in *this* listing (e.g. "update plan 2"), that counts as a match too — resolve it to the indented absolute path from this same output, don't reuse a number from an earlier listing in the conversation (it's positional, not a stable id, and can shift if plans changed since). Otherwise (no match, several matches, or a name/number that doesn't correspond to any existing plan) → ask; never guess.
+
+Cases 1 and 2 (update) — run:
 
 ```bash
-{{GROUNDER_CLI}} plan list --limit 5
+{{GROUNDER_CLI}} plan "$(cat <<'EOF'
+# Plan: …
+…
+EOF
+)" --path <path>
 ```
 
-Pick the path matching the user's intent; ask if none or several match.
+`--path` must resolve under this project's `plans/` dir; it always overwrites (no `--force`).
 
-**3. Genuinely new plan** (not an update): derive a `--title`.
-- If the instruction names one explicitly (e.g. `save as "implementation-phase-1"` or `…phase-1.md`), use it (strip a trailing `.md`).
-- Otherwise derive a short kebab-case name from the plan's title/goal and confirm it with the user before writing.
+**3. No path, no update intent → genuinely new plan.** Derive a `--title` (the user's explicit name, else a short kebab-case slug from the plan's title/goal) and write immediately — don't ask about the name itself.
 
 ```bash
 {{GROUNDER_CLI}} plan "$(cat <<'EOF'
@@ -56,10 +60,12 @@ EOF
 )" --title <name>
 ```
 
-If the CLI refuses because that name already exists (non-zero exit; stderr names the conflict), tell the user and ask whether to overwrite (`--force`) or pick a different name. `--force` only resolves this title collision — it is never how you update a plan you already meant to target (use `--path` for that). **Never** silently pass `--force`.
+If `--title` collides with an existing plan (non-zero exit; stderr names the conflict), ask: overwrite (`--force`) or a different name. `--force` only resolves that collision — **never** use it to update a plan you meant to target with `--path`.
+
+Always include `--topics` with 3-5 comma-separated lowercase keywords that capture the plan's core concepts (e.g. `--topics "caching,redis,performance,api"`). Pick terms a future search would use — concrete nouns and technical terms, not verbs or filler.
 
 Run from the linked project folder or any subdirectory beneath it.
 The vault is outside the workspace — grant shell permissions if Claude Code prompts you.
 
 Do not compute vault paths or write files yourself — the CLI handles it.
-Report the CLI output path from stdout to the user.
+Report the exact path the CLI prints on stdout — it confirms the real outcome, not just the intent.

package/templates/agents/claude/commands/grounder-search.md

@@ -0,0 +1,144 @@
+Search this project's vault content for relevant context.
+
+**Silence:** write **no assistant text** until step 3. Rounds 1–2 are tool calls with an empty/absent text part — not “I’ll search…”, not “I’ll read…”, not “**Analyzing…**”, not query/terms narration.
+
+Use this when the user asks to find prior project-vault context by topic, keyword, concept, or phrase.
+
+Scope is this linked project only — the CLI resolves and searches under the linked project vault root. Do not search outside it.
+
+## Turn budget (speed)
+
+**Rounds 1–2: tool calls only — no text part in those messages.** Not even one sentence.
+
+Exactly **two** assistant turns with tools, then the answer. Allowed tools, nothing else:
+
+1. Round 1 — Shell only: one `search … --json` (optional second search in the *same* round only per the broaden rule below). Message = that tool call, nothing else.
+2. Round 2 — Read only: **one** parallel batch of full-file reads (hits 1–4). Message = those Read calls, nothing else.
+3. Final answer to the user (first and only chat text).
+
+**Do not** Glob, Grep, extra Shell, or status/UI tools (`UpdateCurrentStep`, `TodoWrite`, and similar). Do not add a third tool turn. Do not explore the repo.
+
+## Output contract (default — hybrid)
+
+- Do not echo commands or shell output.
+- **Never paste CLI JSON, snippets, or raw stdout into chat** — parse `--json` internally only.
+- One final synthesized response only.
+
+**Path links (mandatory for every listed file):**
+- Visible title = `hits[].relativePath` from JSON **exactly** (project-vault-relative; the folder that contains `notes/`, `logs/`, and `plans/`). Example: `plans/archive/0.2.0 and older/doc.md`.
+- **Do not** derive the title from `hits[].file`, path segments, or parent-vault prefixes.
+- **Wrong titles:** `10-Projects/grounder/plans/…`, `%20` in the visible title, or any path above the project vault root.
+- Link href = `hits[].fileUri` from JSON (spaces already percent-encoded).
+- Markdown form: `[hits[i].relativePath](hits[i].fileUri)`
+
+**Numbering (mandatory):**
+- Number every listed file, continuing across sections (`1…` in **Read these**, then `5…` in **Also matched`).
+- Do not restart at 1 in **Also matched**. Do not use bullet-only lists without numbers.
+
+Structure:
+
+1. **Opening** — one sentence of what the vault says (not a search recap). Never start with “I have searched…”, “I found…”, or similar.
+2. **Read these** — hits 1–4 only; numbered linked paths + optional role + short bullets under each. You may list a design/archive authority first *among those four*.
+3. **Also matched** — leftover top-10 **in CLI order** (do not reshuffle); numbered linked paths + one short phrase each (`hits[].alsoMatchedHint` or `matches[].term`). Every line must end with ` — phrase`; bare links are invalid. Omit if empty.
+
+Example shape (`##` headings required — not bold-only, not `###`):
+
+```markdown
+Vault notes discuss …
+
+## Read these
+1. [plans/archive/0.3.0/schema_….md](file:///…/schema_….md) — design authority
+   - …
+2. [plans/…](file:///…) — …
+## Also matched
+3. [plans/archive/0.2.0 and older/doc.md](file:///…/0.2.0%20and%20older/doc.md) — one phrase
+4. [plans/…](file:///…) — one phrase
+```
+
+**Lookup mode:** explicit lookup wording (`exact phrase`, `this line`, `the wording`) **or** the entire input after stripping retrieval wrappers is a bare `"quoted span"` → relay CLI `--markdown` as-is (one search, no `--terms`, no full reads).
+
+## Steps
+
+1. **Query and terms (private)** — classify, then build argv. Classification is silent (no chat text). The CLI always line-scans `query` plus `--terms`. Multi-word queries only match lines that contain that phrase verbatim. Rank is dominated by how many distinct terms hit the **same** file — complementary vault words beat extra English synonyms and source module names.
+
+   **Classify** after stripping retrieval wrappers (`find`, `search for`, `documents discussing`, `notes about`, `look up`). Then pick one:
+
+   - **Lookup** — explicit lookup wording (`exact phrase`, `this line`, `the wording`), **or** leftover is a bare `"quoted span"`. `query` = the quoted text, unmodified. Relay CLI `--markdown` as-is; no `--terms`, no full reads.
+   - **Request** — leftover still has request syntax (any of): `that mention` / `that discuss` / `that talk about`; leftover starts with `plans that` / `notes that` / `docs that` / `documents that`; trailing scope `both in` / `either in` / `in CLI and`. Do **not** pass that leftover as `query`. `query` = one primary noun or named command from the topic (tight phrase; do not prefix a product name). Extra nouns go in `--terms`.
+   - **Topic leftover** — leftover is already a topic noun-phrase. `query` = leftover, same words, same order. Do not paraphrase, shorten, or coin a new phrase.
+
+   Strip only retrieval wrappers. Do not pass the whole utterance. Do not recycle the query as a `--terms` item.
+
+   Examples below are a **fictional** domain. Copy the shape; invent tokens for *this* topic. Do not reuse these strings as `--terms`.
+
+   Example — lookup. User: `find "retry of expired jobs"`
+   - class: lookup
+   - argv: {{GROUNDER_CLI}} search "retry of expired jobs" --markdown
+
+   Example — topic leftover. User: `find documents discussing retry of expired jobs`
+   - class: topic leftover
+   - query: `retry of expired jobs` (leftover after stripping the wrapper)
+   - wrong query: `expired job retries` (rewritten)
+   - wrong class: request (`documents discussing` is a wrapper)
+
+   Example — request. User: `find plans that mention updating the charge or refund command, both in worker and API`
+   - class: request (`plans that mention` / `both in` stay leftover — not the topic)
+   - query: `charge` (one named command from leftover; not `billing charge`)
+   - terms: `refund,settlement,invoices.json,RefundPolicy`
+     - from leftover: `refund` (the other named command)
+     - invented: `settlement` (domain), `invoices.json` (file), `RefundPolicy` (schema) — guess this project's equivalents
+   - wrong query: `plans that mention updating the charge or refund command, both in worker and API`
+   - wrong query: `charge refund command` (joined nouns)
+   - not as terms: `plan`, `command`, `api`
+
+   **Terms** — invent 3–5 complementary vault tokens for *this* topic, then stop. They need not appear in the utterance:
+   1. Domain noun/phrase from the topic (skip if it would duplicate the query)
+   2. Named command or product verb if the topic has one — never a lone generic verb (`migrate`, `install`)
+   3. One on-disk identifier (filename, config key, schema field) guessed for this project
+   4–5. Only another vault/product token. No paraphrase of the query.
+
+   **Never as terms** (unless the user asked about code layout): repo paths, `packages/…`, source module / file stems. Lone high-df words (`plan`, `command`, `cli`) flatten rank. Prefer words that appear in vault notes (named commands, config files, domain identifiers).
+
+   Example — user: `look up why the retry queue must skip expired jobs`
+   - class: topic leftover
+   - query: `why the retry queue must skip expired jobs`
+   - terms: `retry queue,dead letter,jobs.json,RetryPolicy,ttl` (`retry queue` from leftover; others invented)
+   - not: `queue-worker`, `process-jobs`, `skip`, `look up`
+
+2. **Search (tool round 1):**
+
+```bash
+{{GROUNDER_CLI}} search "<query>" --terms "<csv>" --context 2 --json
+```
+
+**Always quote `--terms`.** Unquoted CSV with spaces corrupts argv.
+
+Parse JSON privately. Take hits in CLI order (`hits[0]` …). For links use `relativePath` + `fileUri`; for Also matched gloss use `alsoMatchedHint` or `matches[].term` — do not quote snippets.
+
+**Broaden once (silent)** only if: `totalFileCount` is 0; or ≤2 and every hit is meta (`discussions/search/`, or snippet only quotes the query); or any term in `termHitCounts` has a count of 0 (that term produced no files — it was a bad guess and must be replaced). Otherwise do not re-search.
+
+   Broaden call (use `--context 3` — weaker matches need more context):
+
+```bash
+{{GROUNDER_CLI}} search "<query>" --terms "<csv-with-replacement>" --context 3 --json
+```
+
+   **Broaden strategy (deterministic):** check `termHitCounts` first — if any term has count 0, replace **that term** (not slot-3) with a different product/vault token. If no zero-hit term, drop slot-3 (the on-disk identifier). Keep slots 1–2 (product noun/verb) unchanged. Do not invent new terms or rewrite existing ones.
+
+3. **Read (tool round 2)** — mandatory unless lookup:
+   - Full-read CLI hits **1–4** in rank order, **all in one parallel batch**.
+   - Read path = `hits[i].file` (absolute). Link title/href = `hits[i].relativePath` + `hits[i].fileUri`.
+   - **No skips, no substitutions, no “maybe also hit 5.”** Trust CLI order; judge relevance only when writing the answer.
+   - Grant read permissions for vault paths outside the workspace when needed.
+
+4. **Answer** — synthesize immediately after reads:
+   - Claims only from files you full-read. Unread hits must not grow new facts.
+   - **Read these:** useful full-reads (those 1–4 only). Thin/off-topic reads get one blunt numbered line there or move to **Also matched**.
+   - **Also matched:** remaining top-10 you did not deep-summarize, **in CLI leftover order**. Copy `alsoMatchedHint` or phrase from `matches[].term`; every line ends with ` — phrase`.
+   - Every file line: `[relativePath](fileUri)` from JSON; continue numbering across sections.
+   - Prefer design/archive docs when they are the authority among the files you read.
+
+Run from the linked project folder or any subdirectory beneath it.
+The vault is outside the workspace — grant shell permissions if Claude Code prompts you.
+Do not write to vault files during search.
+Do not grep the vault yourself — the CLI ranks; you read and synthesize.

package/templates/agents/claude/commands/grounder-task-handoff.md

@@ -1,4 +1,4 @@
-Write a session handoff checkpoint to the Obsidian vault for this project.
+Write a session handoff checkpoint to the markdown vault for this project.
 
 Summarize the session into a structured handoff — not a chat transcript.
 Do not dump tool traces, full conversation, or false starts.
@@ -38,6 +38,10 @@ Optional short title slug (filename + frontmatter):
 
   {{GROUNDER_CLI}} handoff --title <slug> "<body>"
 
+Always include `--topics` with 3-5 comma-separated lowercase keywords that capture the session's core concepts (e.g. `--topics "auth,middleware,jwt,session"`). Pick terms a future search would use — concrete nouns and technical terms, not verbs or filler:
+
+  {{GROUNDER_CLI}} handoff --topics "keyword1,keyword2,keyword3" "<body>"
+
 For multi-line bodies, prefer a shell heredoc so quoting does not break:
 
 ```bash

package/templates/agents/claude/commands/grounder-task.md

@@ -2,7 +2,9 @@ Hydrate this session from the latest vault handoff and repo truth.
 
 Read-only — do not write to the vault. Do not invent vault paths.
 
-From the linked project folder or any subdirectory beneath it:
+**Special case: the instruction asks to view existing handoffs, not hydrate** (`list`, `list 3 oldest`, `show handoffs`, etc.) → run `{{GROUNDER_CLI}} handoff list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no hydrate, no `AGENTS.md`, no “start work.” Relay the CLI stdout as-is (it already includes the count header; title lines are clickable `[relativePath](fileUri)` links).
+
+Otherwise, from the linked project folder or any subdirectory beneath it:
 
 1. Get the current handoff (skips empty/unreadable files, same pick as the session-start teaser):
 
@@ -10,7 +12,7 @@ From the linked project folder or any subdirectory beneath it:
 
 2. If empty: tell the user there are no handoffs yet, then read repo `AGENTS.md` only and proceed.
 
-3. Otherwise, read that file. If the user names a specific session instead, run `{{GROUNDER_CLI}} handoff list --limit 5` and read the path they mean.
+3. Otherwise, read that file. If the user names a specific session instead: `{{GROUNDER_CLI}} handoff list --limit 5 --markdown` → match name/index to the indented absolute path in *this* listing (positional, not a stable id). Miss → once with `--limit 50 --markdown` (*that* listing only). Still miss → tell the user and stop — no guessed hydrate.
 
 4. Read repo `AGENTS.md` (project conventions and constraints).
 

package/templates/agents/cursor/commands/grounder-note.md

@@ -1,11 +1,37 @@
-Save a note to the Obsidian vault for this project.
+Save a note to the markdown vault for this project.
 
-Run from the linked project folder or any subdirectory beneath it:
+Distill the instruction after `/grounder-note` into a clean note body — not a chat transcript.
+Do not dump tool traces, full conversation, or false starts.
 
-  {{GROUNDER_CLI}} note "<user text>"
+**Special case: the instruction asks to view existing notes, not write one** (`list`, `list 3 oldest`, `show notes`, etc.) → run `{{GROUNDER_CLI}} note list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no note write. Relay the CLI stdout as-is (it already includes the count header; title lines are clickable `[relativePath](fileUri)` links).
 
-The vault is outside the workspace — approve shell permissions if Cursor prompts you.
+Rules:
+- Default → distill the args into a clean note body
+- Exact wording marked to keep (quoted, "save exactly:"/"verbatim:", or a fenced block) → use that verbatim instead, unmodified
+- Empty args → distill the central point of the current thread instead
+
+Then run from the linked project folder or any subdirectory beneath it:
+
+  {{GROUNDER_CLI}} note "<body>"
+
+Optional short title slug (filename):
+
+  {{GROUNDER_CLI}} note --title <slug> "<body>"
+
+Always include `--topics` with 3-5 comma-separated lowercase keywords that capture the note's core concepts (e.g. `--topics "schema,migration,postgres"`). Pick terms a future search would use — concrete nouns and technical terms, not verbs or filler:
+
+  {{GROUNDER_CLI}} note --topics "keyword1,keyword2,keyword3" "<body>"
+
+For multi-line bodies, prefer a shell heredoc so quoting does not break:
+
+```bash
+{{GROUNDER_CLI}} note "$(cat <<'EOF'
+…
+EOF
+)"
+```
+
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
 
-Use the text after `/grounder-note` as the note body.
 Do not compute vault paths or write files yourself — the CLI handles it.
 Report the CLI output path from stdout to the user.

package/templates/agents/cursor/commands/grounder-plan.md

@@ -1,4 +1,4 @@
-Write a named, updatable plan document to the Obsidian vault for this project.
+Write a named, updatable plan document to the markdown vault for this project.
 
 Distill the instruction after `/grounder-plan` into a structured plan — not a chat transcript.
 Do not dump tool traces, full conversation, or false starts.
@@ -22,31 +22,35 @@ Build a markdown body with these sections:
 …
 ```
 
-Update vs create — never guess a `--title` for an update:
+**Special case: the instruction asks to view existing plans, not name a new topic** (`list`, `list 3 oldest`, `show plans`, etc.) → run `{{GROUNDER_CLI}} plan list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no plan write, no title. Relay the CLI stdout as-is (it already includes the count header; title lines are clickable `[relativePath](fileUri)` links).
 
-**1. Path known** (attached/open in chat, or printed by an earlier `grounder plan` this conversation): update that exact file.
+Otherwise, resolve the target, then **state it plainly before writing** — `Updating plan at <path>.` or `Creating new plan titled <title>.` This is a visible record, not a blocking confirmation — updates overwrite with no `--force`, so get the match right.
+
+**1. Known path** (attached/open in chat, or printed by an earlier `grounder plan` this conversation) → update it directly.
+
+**2. No path, but update intent** (e.g. "update/continue/revise the plan", or a name that sounds like an existing one) → look it up first:
 
 ```bash
-{{GROUNDER_CLI}} plan "$(cat <<'EOF'
-# Plan: …
-…
-EOF
-)" --path <path-to-existing-plan.md>
+{{GROUNDER_CLI}} plan list --limit 5 --markdown
 ```
 
-`--path` must resolve under this project's `plans/` dir; it always overwrites (no `--force`).
+CLI output starts with a count header, then each result as a numbered two-line block — `N. ` + `[relativePath](fileUri)` on the first line, the absolute path indented beneath it (use that absolute path for `--path`).
 
-**2. Path unknown** (e.g. "update the plan" with nothing attached and no prior path this conversation): look it up, then update as in (1).
+A match counts only if the filename stem / relative path actually corresponds to what the user named — not just "it's the only plan in the project." No name given and exactly one plan exists → that counts too. If the user refers to a plan by the number shown in *this* listing (e.g. "update plan 2"), that counts as a match too — resolve it to the indented absolute path from this same output, don't reuse a number from an earlier listing in the conversation (it's positional, not a stable id, and can shift if plans changed since). Otherwise (no match, several matches, or a name/number that doesn't correspond to any existing plan) → ask; never guess.
+
+Cases 1 and 2 (update) — run:
 
 ```bash
-{{GROUNDER_CLI}} plan list --limit 5
+{{GROUNDER_CLI}} plan "$(cat <<'EOF'
+# Plan: …
+…
+EOF
+)" --path <path>
 ```
 
-Pick the path matching the user's intent; ask if none or several match.
+`--path` must resolve under this project's `plans/` dir; it always overwrites (no `--force`).
 
-**3. Genuinely new plan** (not an update): derive a `--title`.
-- If the instruction names one explicitly (e.g. `save as "implementation-phase-1"` or `…phase-1.md`), use it (strip a trailing `.md`).
-- Otherwise derive a short kebab-case name from the plan's title/goal and confirm it with the user before writing.
+**3. No path, no update intent → genuinely new plan.** Derive a `--title` (the user's explicit name, else a short kebab-case slug from the plan's title/goal) and write immediately — don't ask about the name itself.
 
 ```bash
 {{GROUNDER_CLI}} plan "$(cat <<'EOF'
@@ -56,10 +60,12 @@ EOF
 )" --title <name>
 ```
 
-If the CLI refuses because that name already exists (non-zero exit; stderr names the conflict), tell the user and ask whether to overwrite (`--force`) or pick a different name. `--force` only resolves this title collision — it is never how you update a plan you already meant to target (use `--path` for that). **Never** silently pass `--force`.
+If `--title` collides with an existing plan (non-zero exit; stderr names the conflict), ask: overwrite (`--force`) or a different name. `--force` only resolves that collision — **never** use it to update a plan you meant to target with `--path`.
+
+Always include `--topics` with 3-5 comma-separated lowercase keywords that capture the plan's core concepts (e.g. `--topics "caching,redis,performance,api"`). Pick terms a future search would use — concrete nouns and technical terms, not verbs or filler.
 
 Run from the linked project folder or any subdirectory beneath it.
-The vault is outside the workspace — approve shell permissions if Cursor prompts you.
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
 
 Do not compute vault paths or write files yourself — the CLI handles it.
-Report the CLI output path from stdout to the user.
+Report the exact path the CLI prints on stdout — it confirms the real outcome, not just the intent.

package/templates/agents/cursor/commands/grounder-search.md

@@ -0,0 +1,144 @@
+Search this project's vault content for relevant context.
+
+**Silence:** write **no assistant text** until step 3. Rounds 1–2 are tool calls with an empty/absent text part — not “I’ll search…”, not “I’ll read…”, not “**Analyzing…**”, not query/terms narration.
+
+Use this when the user asks to find prior project-vault context by topic, keyword, concept, or phrase.
+
+Scope is this linked project only — the CLI resolves and searches under the linked project vault root. Do not search outside it.
+
+## Turn budget (speed)
+
+**Rounds 1–2: tool calls only — no text part in those messages.** Not even one sentence.
+
+Exactly **two** assistant turns with tools, then the answer. Allowed tools, nothing else:
+
+1. Round 1 — Shell only: one `search … --json` (optional second search in the *same* round only per the broaden rule below). Message = that tool call, nothing else.
+2. Round 2 — Read only: **one** parallel batch of full-file reads (hits 1–4). Message = those Read calls, nothing else.
+3. Final answer to the user (first and only chat text).
+
+**Do not** Glob, Grep, extra Shell, or status/UI tools (`UpdateCurrentStep`, `TodoWrite`, and similar). Do not add a third tool turn. Do not explore the repo.
+
+## Output contract (default — hybrid)
+
+- Do not echo commands or shell output.
+- **Never paste CLI JSON, snippets, or raw stdout into chat** — parse `--json` internally only.
+- One final synthesized response only.
+
+**Path links (mandatory for every listed file):**
+- Visible title = `hits[].relativePath` from JSON **exactly** (project-vault-relative; the folder that contains `notes/`, `logs/`, and `plans/`). Example: `plans/archive/0.2.0 and older/doc.md`.
+- **Do not** derive the title from `hits[].file`, path segments, or parent-vault prefixes.
+- **Wrong titles:** `10-Projects/grounder/plans/…`, `%20` in the visible title, or any path above the project vault root.
+- Link href = `hits[].fileUri` from JSON (spaces already percent-encoded).
+- Markdown form: `[hits[i].relativePath](hits[i].fileUri)`
+
+**Numbering (mandatory):**
+- Number every listed file, continuing across sections (`1…` in **Read these**, then `5…` in **Also matched`).
+- Do not restart at 1 in **Also matched**. Do not use bullet-only lists without numbers.
+
+Structure:
+
+1. **Opening** — one sentence of what the vault says (not a search recap). Never start with “I have searched…”, “I found…”, or similar.
+2. **Read these** — hits 1–4 only; numbered linked paths + optional role + short bullets under each. You may list a design/archive authority first *among those four*.
+3. **Also matched** — leftover top-10 **in CLI order** (do not reshuffle); numbered linked paths + one short phrase each (`hits[].alsoMatchedHint` or `matches[].term`). Every line must end with ` — phrase`; bare links are invalid. Omit if empty.
+
+Example shape (`##` headings required — not bold-only, not `###`):
+
+```markdown
+Vault notes discuss …
+
+## Read these
+1. [plans/archive/0.3.0/schema_….md](file:///…/schema_….md) — design authority
+   - …
+2. [plans/…](file:///…) — …
+## Also matched
+3. [plans/archive/0.2.0 and older/doc.md](file:///…/0.2.0%20and%20older/doc.md) — one phrase
+4. [plans/…](file:///…) — one phrase
+```
+
+**Lookup mode:** explicit lookup wording (`exact phrase`, `this line`, `the wording`) **or** the entire input after stripping retrieval wrappers is a bare `"quoted span"` → relay CLI `--markdown` as-is (one search, no `--terms`, no full reads).
+
+## Steps
+
+1. **Query and terms (private)** — classify, then build argv. Classification is silent (no chat text). The CLI always line-scans `query` plus `--terms`. Multi-word queries only match lines that contain that phrase verbatim. Rank is dominated by how many distinct terms hit the **same** file — complementary vault words beat extra English synonyms and source module names.
+
+   **Classify** after stripping retrieval wrappers (`find`, `search for`, `documents discussing`, `notes about`, `look up`). Then pick one:
+
+   - **Lookup** — explicit lookup wording (`exact phrase`, `this line`, `the wording`), **or** leftover is a bare `"quoted span"`. `query` = the quoted text, unmodified. Relay CLI `--markdown` as-is; no `--terms`, no full reads.
+   - **Request** — leftover still has request syntax (any of): `that mention` / `that discuss` / `that talk about`; leftover starts with `plans that` / `notes that` / `docs that` / `documents that`; trailing scope `both in` / `either in` / `in CLI and`. Do **not** pass that leftover as `query`. `query` = one primary noun or named command from the topic (tight phrase; do not prefix a product name). Extra nouns go in `--terms`.
+   - **Topic leftover** — leftover is already a topic noun-phrase. `query` = leftover, same words, same order. Do not paraphrase, shorten, or coin a new phrase.
+
+   Strip only retrieval wrappers. Do not pass the whole utterance. Do not recycle the query as a `--terms` item.
+
+   Examples below are a **fictional** domain. Copy the shape; invent tokens for *this* topic. Do not reuse these strings as `--terms`.
+
+   Example — lookup. User: `find "retry of expired jobs"`
+   - class: lookup
+   - argv: {{GROUNDER_CLI}} search "retry of expired jobs" --markdown
+
+   Example — topic leftover. User: `find documents discussing retry of expired jobs`
+   - class: topic leftover
+   - query: `retry of expired jobs` (leftover after stripping the wrapper)
+   - wrong query: `expired job retries` (rewritten)
+   - wrong class: request (`documents discussing` is a wrapper)
+
+   Example — request. User: `find plans that mention updating the charge or refund command, both in worker and API`
+   - class: request (`plans that mention` / `both in` stay leftover — not the topic)
+   - query: `charge` (one named command from leftover; not `billing charge`)
+   - terms: `refund,settlement,invoices.json,RefundPolicy`
+     - from leftover: `refund` (the other named command)
+     - invented: `settlement` (domain), `invoices.json` (file), `RefundPolicy` (schema) — guess this project's equivalents
+   - wrong query: `plans that mention updating the charge or refund command, both in worker and API`
+   - wrong query: `charge refund command` (joined nouns)
+   - not as terms: `plan`, `command`, `api`
+
+   **Terms** — invent 3–5 complementary vault tokens for *this* topic, then stop. They need not appear in the utterance:
+   1. Domain noun/phrase from the topic (skip if it would duplicate the query)
+   2. Named command or product verb if the topic has one — never a lone generic verb (`migrate`, `install`)
+   3. One on-disk identifier (filename, config key, schema field) guessed for this project
+   4–5. Only another vault/product token. No paraphrase of the query.
+
+   **Never as terms** (unless the user asked about code layout): repo paths, `packages/…`, source module / file stems. Lone high-df words (`plan`, `command`, `cli`) flatten rank. Prefer words that appear in vault notes (named commands, config files, domain identifiers).
+
+   Example — user: `look up why the retry queue must skip expired jobs`
+   - class: topic leftover
+   - query: `why the retry queue must skip expired jobs`
+   - terms: `retry queue,dead letter,jobs.json,RetryPolicy,ttl` (`retry queue` from leftover; others invented)
+   - not: `queue-worker`, `process-jobs`, `skip`, `look up`
+
+2. **Search (tool round 1):**
+
+```bash
+{{GROUNDER_CLI}} search "<query>" --terms "<csv>" --context 2 --json
+```
+
+**Always quote `--terms`.** Unquoted CSV with spaces corrupts argv.
+
+Parse JSON privately. Take hits in CLI order (`hits[0]` …). For links use `relativePath` + `fileUri`; for Also matched gloss use `alsoMatchedHint` or `matches[].term` — do not quote snippets.
+
+**Broaden once (silent)** only if: `totalFileCount` is 0; or ≤2 and every hit is meta (`discussions/search/`, or snippet only quotes the query); or any term in `termHitCounts` has a count of 0 (that term produced no files — it was a bad guess and must be replaced). Otherwise do not re-search.
+
+   Broaden call (use `--context 3` — weaker matches need more context):
+
+```bash
+{{GROUNDER_CLI}} search "<query>" --terms "<csv-with-replacement>" --context 3 --json
+```
+
+   **Broaden strategy (deterministic):** check `termHitCounts` first — if any term has count 0, replace **that term** (not slot-3) with a different product/vault token. If no zero-hit term, drop slot-3 (the on-disk identifier). Keep slots 1–2 (product noun/verb) unchanged. Do not invent new terms or rewrite existing ones.
+
+3. **Read (tool round 2)** — mandatory unless lookup:
+   - Full-read CLI hits **1–4** in rank order, **all in one parallel batch**.
+   - Read path = `hits[i].file` (absolute). Link title/href = `hits[i].relativePath` + `hits[i].fileUri`.
+   - **No skips, no substitutions, no “maybe also hit 5.”** Trust CLI order; judge relevance only when writing the answer.
+   - Request vault read permissions as needed.
+
+4. **Answer** — synthesize immediately after reads:
+   - Claims only from files you full-read. Unread hits must not grow new facts.
+   - **Read these:** useful full-reads (those 1–4 only). Thin/off-topic reads get one blunt numbered line there or move to **Also matched**.
+   - **Also matched:** remaining top-10 you did not deep-summarize, **in CLI leftover order**. Copy `alsoMatchedHint` or phrase from `matches[].term`; every line ends with ` — phrase`.
+   - Every file line: `[relativePath](fileUri)` from JSON; continue numbering across sections.
+   - Prefer design/archive docs when they are the authority among the files you read.
+
+Run from the linked project folder or any subdirectory beneath it.
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
+Do not write to vault files during search.
+Do not grep the vault yourself — the CLI ranks; you read and synthesize.

package/templates/agents/cursor/commands/grounder-task-handoff.md

@@ -1,4 +1,4 @@
-Write a session handoff checkpoint to the Obsidian vault for this project.
+Write a session handoff checkpoint to the markdown vault for this project.
 
 Summarize the session into a structured handoff — not a chat transcript.
 Do not dump tool traces, full conversation, or false starts.
@@ -38,6 +38,10 @@ Optional short title slug (filename + frontmatter):
 
   {{GROUNDER_CLI}} handoff --title <slug> "<body>"
 
+Always include `--topics` with 3-5 comma-separated lowercase keywords that capture the session's core concepts (e.g. `--topics "auth,middleware,jwt,session"`). Pick terms a future search would use — concrete nouns and technical terms, not verbs or filler:
+
+  {{GROUNDER_CLI}} handoff --topics "keyword1,keyword2,keyword3" "<body>"
+
 For multi-line bodies, prefer a shell heredoc so quoting does not break:
 
 ```bash
@@ -48,7 +52,7 @@ EOF
 )"
 ```
 
-The vault is outside the workspace — approve shell permissions if Cursor prompts you.
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
 
 Do not compute vault paths or write files yourself — the CLI handles it.
 Report the CLI output path from stdout to the user.

package/templates/agents/cursor/commands/grounder-task.md

@@ -2,7 +2,9 @@ Hydrate this session from the latest vault handoff and repo truth.
 
 Read-only — do not write to the vault. Do not invent vault paths.
 
-From the linked project folder or any subdirectory beneath it:
+**Special case: the instruction asks to view existing handoffs, not hydrate** (`list`, `list 3 oldest`, `show handoffs`, etc.) → run `{{GROUNDER_CLI}} handoff list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no hydrate, no `AGENTS.md`, no “start work.” Relay the CLI stdout as-is (it already includes the count header; title lines are clickable `[relativePath](fileUri)` links).
+
+Otherwise, from the linked project folder or any subdirectory beneath it:
 
 1. Get the current handoff (skips empty/unreadable files, same pick as the session-start teaser):
 
@@ -10,11 +12,11 @@ From the linked project folder or any subdirectory beneath it:
 
 2. If empty: tell the user there are no handoffs yet, then read repo `AGENTS.md` only and proceed.
 
-3. Otherwise, read that file. If the user names a specific session instead, run `{{GROUNDER_CLI}} handoff list --limit 5` and read the path they mean.
+3. Otherwise, read that file. If the user names a specific session instead: `{{GROUNDER_CLI}} handoff list --limit 5 --markdown` → match name/index to the indented absolute path in *this* listing (positional, not a stable id). Miss → once with `--limit 50 --markdown` (*that* listing only). Still miss → tell the user and stop — no guessed hydrate.
 
 4. Read repo `AGENTS.md` (project conventions and constraints).
 
 5. Summarize briefly what is next (from the handoff `## Next` section when present), then start work.
 
-The vault is outside the workspace — approve shell permissions if Cursor prompts you.
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
 Use free-text after `/grounder-task` as optional focus (session name, index, or task hint).

package/dist/commands/repo/init.d.ts

@@ -1,11 +0,0 @@
-export interface RepoInitOptions {
-    cwd?: string;
-    yes?: boolean;
-    force?: boolean;
-    id?: string;
-    vault?: string;
-    homeDir?: string;
-}
-export declare function runRepoInit(argv: string[]): Promise<number>;
-export declare function runRepoInitWithOptions(options?: RepoInitOptions): Promise<number>;
-//# sourceMappingURL=init.d.ts.map

package/dist/commands/repo/init.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"init.d.ts","sourceRoot":"","sources":["../../../src/commands/repo/init.ts"],"names":[],"mappings":"AAiBA,MAAM,WAAW,eAAe;IAC9B,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,GAAG,CAAC,EAAE,OAAO,CAAC;IACd,KAAK,CAAC,EAAE,OAAO,CAAC;IAChB,EAAE,CAAC,EAAE,MAAM,CAAC;IACZ,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB;AAED,wBAAsB,WAAW,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,CAAC,CAajE;AAED,wBAAsB,sBAAsB,CAAC,OAAO,GAAE,eAAoB,GAAG,OAAO,CAAC,MAAM,CAAC,CA4E3F"}

package/dist/commands/repo/init.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"init.js","sourceRoot":"","sources":["../../../src/commands/repo/init.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,EAAE,MAAM,kBAAkB,CAAC;AACzC,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,WAAW,EAAE,MAAM,wBAAwB,CAAC;AACrD,OAAO,EAAE,cAAc,EAAE,WAAW,EAAE,MAAM,yBAAyB,CAAC;AACtE,OAAO,EAAE,eAAe,EAAE,qBAAqB,EAAE,MAAM,+BAA+B,CAAC;AACvF,OAAO,EAAE,cAAc,EAAE,cAAc,EAAE,eAAe,EAAE,MAAM,yBAAyB,CAAC;AAC1F,OAAO,EACL,cAAc,EACd,eAAe,EACf,eAAe,EACf,gBAAgB,GACjB,MAAM,0BAA0B,CAAC;AAClC,OAAO,EAAE,YAAY,EAAE,MAAM,eAAe,CAAC;AAC7C,OAAO,EAAE,QAAQ,EAAE,UAAU,EAAE,SAAS,EAAE,MAAM,0BAA0B,CAAC;AAC3E,OAAO,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AACrD,OAAO,EAAE,OAAO,EAAE,MAAM,sBAAsB,CAAC;AAW/C,MAAM,CAAC,KAAK,UAAU,WAAW,CAAC,IAAc;IAC9C,MAAM,QAAQ,GAAG,YAAY,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC;IAC5C,IAAI,QAAQ,KAAK,IAAI,EAAE,CAAC;QACtB,OAAO,QAAQ,CAAC;IAClB,CAAC;IAED,MAAM,EAAE,KAAK,EAAE,GAAG,SAAS,CAAC,IAAI,CAAC,CAAC;IAClC,OAAO,sBAAsB,CAAC;QAC5B,GAAG,EAAE,QAAQ,CAAC,KAAK,EAAE,KAAK,EAAE,GAAG,CAAC;QAChC,KAAK,EAAE,QAAQ,CAAC,KAAK,EAAE,OAAO,EAAE,GAAG,CAAC;QACpC,EAAE,EAAE,UAAU,CAAC,KAAK,EAAE,IAAI,CAAC;QAC3B,KAAK,EAAE,UAAU,CAAC,KAAK,EAAE,OAAO,CAAC;KAClC,CAAC,CAAC;AACL,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,sBAAsB,CAAC,UAA2B,EAAE;IACxE,OAAO,WAAW,CAAC,OAAO,CAAC,OAAO,EAAE,KAAK,IAAI,EAAE;QAC7C,MAAM,GAAG,GAAG,IAAI,CAAC,OAAO,CAAC,OAAO,CAAC,GAAG,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC,CAAC;QACvD,MAAM,GAAG,GAAG,OAAO,CAAC,GAAG,IAAI,KAAK,CAAC;QACjC,MAAM,KAAK,GAAG,OAAO,CAAC,KAAK,IAAI,KAAK,CAAC;QACrC,MAAM,OAAO,GAAG,MAAM,WAAW,CAAC,GAAG,CAAC,CAAC;QAEvC,IAAI,IAAI,GAAG,MAAM,cAAc,EAAE,CAAC;QAClC,IAAI,CAAC,IAAI,EAAE,CAAC;YACV,IAAI,CAAC,OAAO,CAAC,KAAK,EAAE,CAAC;gBACnB,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,wDAAwD,CAAC,CAAC;gBAC/E,OAAO,CAAC,CAAC;YACX,CAAC;YACD,IAAI,GAAG,EAAE,SAAS,EAAE,eAAe,CAAC,OAAO,CAAC,KAAK,CAAC,EAAE,CAAC;QACvD,CAAC;QAED,MAAM,SAAS,GAAG,gBAAgB,CAAC,IAAI,EAAE,OAAO,CAAC,KAAK,CAAC,CAAC;QACxD,MAAM,QAAQ,GAAG,MAAM,eAAe,CAAC,GAAG,EAAE,OAAO,CAAC,EAAE,EAAE,OAAO,CAAC,CAAC;QACjE,MAAM,YAAY,GAAG,MAAM,cAAc,CAAC,GAAG,CAAC,CAAC;QAC/C,MAAM,aAAa,GAAG,EAAE,OAAO,EAAE,CAAU,EAAE,SAAS,EAAE,QAAQ,CAAC,EAAE,EAAE,CAAC;QACtE,MAAM,QAAQ,GAAG,eAAe,CAAC,IAAI,EAAE,aAAa,EAAE,OAAO,CAAC,KAAK,CAAC,CAAC;QACrE,MAAM,OAAO,GAAG,cAAc,CAAC,IAAI,EAAE,aAAa,EAAE,OAAO,CAAC,KAAK,CAAC,CAAC;QACnE,MAAM,QAAQ,GAAG,eAAe,CAAC,IAAI,EAAE,aAAa,EAAE,OAAO,CAAC,KAAK,CAAC,CAAC;QAErE,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,eAAe,GAAG,IAAI,CAAC,CAAC;QAC7C,IAAI,OAAO,EAAE,CAAC;YACZ,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,eAAe,OAAO,IAAI,CAAC,CAAC;QACnD,CAAC;QACD,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,eAAe,SAAS,IAAI,CAAC,CAAC;QACnD,OAAO,CAAC,MAAM,CAAC,KAAK,CAClB,eAAe,QAAQ,CAAC,EAAE,KAAK,qBAAqB,CAAC,QAAQ,CAAC,MAAM,CAAC,OAAO,CAC7E,CAAC;QACF,MAAM,gBAAgB,GAAG,IAAI,CAAC,QAAQ,CAAC,SAAS,EAAE,QAAQ,CAAC,CAAC;QAC5D,MAAM,eAAe,GAAG,IAAI,CAAC,QAAQ,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;QAC1D,MAAM,gBAAgB,GAAG,IAAI,CAAC,QAAQ,CAAC,SAAS,EAAE,QAAQ,CAAC,CAAC;QAE5D,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,gBAAgB,CAAC,CAAC;QACvC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,YAAY,cAAc,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAC1D,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,YAAY,gBAAgB,KAAK,CAAC,CAAC;QACxD,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,YAAY,eAAe,KAAK,CAAC,CAAC;QACvD,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,YAAY,gBAAgB,KAAK,CAAC,CAAC;QAExD,IAAI,CAAC,GAAG,EAAE,CAAC;YACT,MAAM,OAAO,GAAG,MAAM,OAAO,CAAC,UAAU,CAAC,CAAC;YAC1C,IAAI,CAAC,OAAO,EAAE,CAAC;gBACb,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,YAAY,CAAC,CAAC;gBACnC,OAAO,CAAC,CAAC;YACX,CAAC;QACH,CAAC;QAED,IAAI,YAAY,IAAI,CAAC,KAAK,EAAE,CAAC;YAC3B,IAAI,YAAY,CAAC,SAAS,KAAK,QAAQ,CAAC,EAAE,EAAE,CAAC;gBAC3C,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,8BAA8B,CAAC,CAAC;gBACrD,MAAM,KAAK,CAAC,QAAQ,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;gBAC3C,MAAM,KAAK,CAAC,OAAO,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;gBAC1C,MAAM,KAAK,CAAC,QAAQ,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;gBAC3C,OAAO,CAAC,CAAC;YACX,CAAC;YAED,OAAO,CAAC,MAAM,CAAC,KAAK,CAClB,4BAA4B,YAAY,CAAC,SAAS,+BAA+B,CAClF,CAAC;YACF,OAAO,CAAC,CAAC;QACX,CAAC;QAED,MAAM,eAAe,CAAC,GAAG,EAAE,EAAE,OAAO,EAAE,CAAC,EAAE,SAAS,EAAE,QAAQ,CAAC,EAAE,EAAE,CAAC,CAAC;QACnE,MAAM,KAAK,CAAC,QAAQ,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAC3C,MAAM,KAAK,CAAC,OAAO,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAC1C,MAAM,KAAK,CAAC,QAAQ,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAE3C,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,0BAA0B,CAAC,CAAC;QACjD,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,2BAA2B,QAAQ,IAAI,CAAC,CAAC;QAC9D,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,0BAA0B,OAAO,IAAI,CAAC,CAAC;QAC5D,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,2BAA2B,QAAQ,IAAI,CAAC,CAAC;QAC9D,OAAO,CAAC,CAAC;IACX,CAAC,CAAC,CAAC;AACL,CAAC"}

package/dist/commands/vault/init.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"init.d.ts","sourceRoot":"","sources":["../../../src/commands/vault/init.ts"],"names":[],"mappings":"AAgBA,MAAM,WAAW,gBAAgB;IAC/B,SAAS,EAAE,MAAM,CAAC;IAClB,GAAG,CAAC,EAAE,OAAO,CAAC;IACd,KAAK,CAAC,EAAE,OAAO,CAAC;IAChB,8EAA8E;IAC9E,KAAK,CAAC,EAAE,OAAO,CAAC;IAChB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,6EAA6E;IAC7E,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC;CACnB;AAED,wBAAsB,YAAY,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,CAAC,CAyBlE;AAED,wBAAsB,uBAAuB,CAAC,OAAO,EAAE,gBAAgB,GAAG,OAAO,CAAC,MAAM,CAAC,CAiExF"}