Enhance conversation actions, indexing, and self-help features

ts/docs/architecture/agents/agentServerConversations.md

@@ -270,7 +270,7 @@ See `packages/vscode-shell/src/agentServerBridge.ts` (`handleManageConversation`
 
 The browser extension (`packages/agents/browserExtension/src/extension`) is a Chrome MV3 extension that runs in **connected mode only** — its service worker maintains a WebSocket to the agentServer. The chat panel surfaces the same `@conversation` slash commands and NL phrases as the Shell and CLI.
 
-The chat panel forwards the dispatcher's `manage-conversation` `takeAction` payload to the service worker via a `chatPanelManageConversation` invoke RPC. The service worker (`extension/serviceWorker/dispatcherConnection.ts`) delegates to the shared `manageConversation` helper from `@typeagent/agent-server-client/conversation` (which implements all eight subcommands) via a thin `AgentServerConnection` adapter over the extension's RPC channel, and returns a rendered HTML message plus a `switched` flag.
+The chat panel forwards the dispatcher's `manage-conversation` `takeAction` payload to the service worker via a `chatPanelManageConversation` invoke RPC. The service worker (`extension/serviceWorker/dispatcherConnection.ts`) delegates to the shared `manageConversation` helper from `@typeagent/agent-server-client/conversation` (which implements every subcommand) via a thin `AgentServerConnection` adapter over the extension's RPC channel, and returns a rendered HTML message plus a `switched` flag.
 
 When `switched` is set, the chat panel clears its DOM and re-runs `loadSessionHistory()` (mirroring the Shell's `replayDisplayHistory` on `conversationChanged`), then renders the confirmation message so it lands after the replayed history. Live display events arriving during the replay are queued via a `runOrDefer` gate and flushed in order on completion.
 
@@ -286,11 +286,11 @@ All four clients (CLI, Electron Shell, VS Code, browser extension) drive their c
 
 Modules:
 
-| Module         | Surface                                                                                                                                                                                                                                                                |
-| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `naming.ts`    | `normalizeConversationName`, `findConversationByName`, `findUniqueConversationByName`, `formatAutoConversationName`, `sortConversationsByCreatedDesc`                                                                                                                  |
-| `lifecycle.ts` | `findOrCreateNamedConversation`, `joinNamedOrFallback`, `switchConversationSafe`, `createEphemeralConversation`, `deleteEphemeralConversation`, `validateConversationNameUnique`, `isConversationNotFoundError`                                                        |
-| `manage.ts`    | `manageConversation` (top-level dispatcher) + per-subcommand entries (`manageNew`, `manageList`, `manageInfo`, `manageSwitch`, `manageCycle`, `manageRename`, `manageDelete`). All return a discriminated `ConversationActionResult` the caller renders to its own UI. |
+| Module         | Surface                                                                                                                                                                                                                                                                                              |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `naming.ts`    | `normalizeConversationName`, `findConversationByName`, `findUniqueConversationByName`, `formatAutoConversationName`, `sortConversationsByCreatedDesc`                                                                                                                                                |
+| `lifecycle.ts` | `findOrCreateNamedConversation`, `joinNamedOrFallback`, `switchConversationSafe`, `createEphemeralConversation`, `deleteEphemeralConversation`, `validateConversationNameUnique`, `isConversationNotFoundError`                                                                                      |
+| `manage.ts`    | `manageConversation` (top-level dispatcher) + per-subcommand entries (`manageNew`, `manageList`, `manageFind`, `manageSearch`, `manageInfo`, `manageSwitch`, `manageCycle`, `manageRename`, `manageDelete`). All return a discriminated `ConversationActionResult` the caller renders to its own UI. |
 
 ### Switch protocol
 
@@ -345,6 +345,8 @@ where `payload` has the shape:
 { subcommand: "help" }
 { subcommand: "new"; name?: string }
 { subcommand: "list" }
+{ subcommand: "find"; query: string }
+{ subcommand: "search"; query: string }
 { subcommand: "info" }
 { subcommand: "switch"; name: string }
 { subcommand: "prev" }
@@ -353,7 +355,7 @@ where `payload` has the shape:
 { subcommand: "rename"; name?: string; newName: string }
 ```
 
-`help` is dispatched when `@conversation` / `/conversation` is invoked with no subcommand (via the dispatcher's `defaultSubCommand: "help"`); there is intentionally no natural-language form for it. NL drops `help` from its `ConversationActionPayload` union and only emits `new`, `list`, `info`, `switch`, `prev`, `next`, `rename`, `delete`. See `packages/dispatcher/dispatcher/src/context/system/manageConversationPayload.ts` for the authoritative type.
+`help` is dispatched when `@conversation` / `/conversation` is invoked with no subcommand (via the dispatcher's `defaultSubCommand: "help"`), and also has a natural-language form (e.g. "conversation help", "help with conversations"). `find` matches conversations by **name** (lexical + embedding); `search` matches conversation **content** via the knowPro unified message index. The full natural-language set the `system.conversation` sub-agent emits is `new`, `list`, `find`, `search`, `info`, `switch`, `prev`, `next`, `rename`, `delete`, and `help`. See `packages/dispatcher/dispatcher/src/context/system/manageConversationPayload.ts` for the authoritative type.
 
 Each client handles `"manage-conversation"` using its own conversation management API:
 

ts/docs/architecture/core/dispatcher.md

@@ -730,14 +730,17 @@ subcommands, and help text.
 
 The system agent also has sub-agents with LLM-translated action schemas:
 
-- **`system.describe`** — Natural language capability discovery ("what can the spotify agent do",
-  "describe the play action"). `executeDescribeAction` forwards to the equivalent `@describe`
-  command (same convention as `system.config`/`system.history`), which resolves the agent/action
-  against `getAgentSchemas()` (agentSchemaInfo.ts) and renders a deterministic markdown summary,
-  optionally polished by a fast structured-output LLM call when one is configured — the model
-  returns a schema-validated JSON object (summary / explanation + example) that is rendered to
-  markdown deterministically, falling back to the deterministic text on a missing/failed model
-  (see `describeCore.ts`).
+- **`system.help`** — Natural language questions about TypeAgent itself. One schema owns three
+  actions: `answerTypeAgentQuestion` (find the command/action for a task) and `explainTypeAgent`
+  (conceptual/setup questions), both grounded via the `@typeagent/selfhelp` library, plus
+  `describeAgent`/`describeAction` capability discovery ("what can the spotify agent do", "describe
+  the play action"). The describe actions forward to the same `describeCore` engine as the
+  `@describe` command, which resolves the agent/action against `getAgentSchemas()`
+  (agentSchemaInfo.ts) and renders a deterministic markdown summary, optionally polished by a fast
+  structured-output LLM call when one is configured, falling back to the deterministic text on a
+  missing/failed model (see `describeCore.ts`). When `describeAgent` names something that is not an
+  installed agent (a concept like "translation"), the handler falls back to `explainTypeAgent`
+  rather than dead-ending.
 - **`system.config`** — Natural language configuration changes.
 - **`system.conversation`** — Natural language management of **agentServer client-connection
   conversations** (the named, GUID-keyed sessions described in