@ashx-j/lunr 0.2.11 → 0.2.13

package/docs/quickstart.md

@@ -1,91 +1,115 @@
 # Quickstart
 
-This page gets you from install to a useful first pi session.
+This page gets you from install to a useful first lunR session.
 
 ## Install
 
-Pi is distributed as an npm package:
+Requires **Node.js ≥ 22.19**. lunR is distributed as `@ashx-j/lunr`:
 
 ```bash
-npm install -g --ignore-scripts @earendil-works/pi-coding-agent
+npm i -g @ashx-j/lunr
 ```
 
-`--ignore-scripts` disables dependency lifecycle scripts during install. Pi does not require install scripts for normal npm installs.
+`--ignore-scripts` is optional; lunR does not require install scripts for a normal npm install. There is no pi.dev `install.sh`.
 
 ### Uninstall
 
-Use the package manager that installed pi. The curl installer uses npm globally, so curl and npm installs are removed with npm:
+Product uninstall vs package uninstall:
 
 ```bash
-# curl installer or npm install -g
-npm uninstall -g @earendil-works/pi-coding-agent
+# Remove this lunR install; keeps ~/.lunr/agent
+lunr uninstall
 
-# pnpm
-pnpm remove -g @earendil-works/pi-coding-agent
+# Also wipe ~/.lunr/agent (settings, credentials, sessions, packages)
+lunr uninstall --purge
 
-# Yarn
-yarn global remove @earendil-works/pi-coding-agent
+# Remove an extension package (alias for lunr remove)
+lunr uninstall npm:@foo/bar
+```
+
+You can also uninstall the npm package itself:
 
-# Bun
-bun uninstall -g @earendil-works/pi-coding-agent
+```bash
+npm uninstall -g @ashx-j/lunr
+pnpm remove -g @ashx-j/lunr
+yarn global remove @ashx-j/lunr
+bun uninstall -g @ashx-j/lunr
 ```
 
-Uninstalling pi leaves settings, credentials, sessions, and installed pi packages in `~/.pi/agent/`.
+`npm uninstall -g` leaves settings, credentials, sessions, and installed packages in `~/.lunr/agent/`. Use `lunr uninstall --purge` to wipe that directory.
 
-Then start pi in the project directory you want it to work on:
+Optional first-run features (Telegram/Discord gateway):
+
+```bash
+lunr setup
+lunr features list
+lunr features enable chat-platforms
+```
+
+Then start lunR in the project directory you want it to work on:
 
 ```bash
 cd /path/to/project
-pi
+lunr
 ```
 
+Config lives in `~/.lunr/agent` (global) and project `.lunr/`. Override with `PI_CODING_AGENT_DIR`. Never use `~/.pi/` as the lunR home.
+
 ## Authenticate
 
-Pi can use subscription providers through `/login`, or API-key providers through environment variables or the auth file.
+lunR can use subscription providers through `/login`, or API-key providers through environment variables or the auth file.
 
 ### Option 1: subscription login
 
-Start pi and run:
+Start lunR and run:
 
 ```text
 /login
 ```
 
-Then select a provider. Built-in subscription logins include Claude Pro/Max, ChatGPT Plus/Pro (Codex), and GitHub Copilot.
+Then select a provider. Built-in subscription logins include Claude Pro/Max, ChatGPT Plus/Pro (Codex), GitHub Copilot, and xAI SuperGrok.
+
+`/login xai` can import the Grok CLI session from `~/.grok/auth.json`. `/logout xai` does not delete that file.
+
+Local Ollama and LM Studio: `/login` and select the local provider (lunR probes localhost). OpenCode Zen: `/login opencode` then `/refresh`.
 
 ### Option 2: API key
 
-Set an API key before launching pi:
+Set an API key before launching lunR:
 
 ```bash
 export ANTHROPIC_API_KEY=sk-ant-...
-pi
+lunr
 ```
 
-You can also run `/login` and select an API-key provider to store the key in `~/.pi/agent/auth.json`.
+You can also run `/login` and select an API-key provider to store the key in `~/.lunr/agent/auth.json`.
 
 See [Providers](providers.md) for all supported providers, environment variables, and cloud-provider setup.
 
+`/model` lists **stored-credential** providers only. An environment variable such as `OPENROUTER_API_KEY` does not list that provider until you store a credential or pass `--api-key`. First paint is cache-only; run `/refresh` to pull newer catalogs.
+
 ## First session
 
-Once pi starts, type a request and press Enter:
+Once lunR starts, type a request and press Enter:
 
 ```text
 Summarize this repository and tell me how to run its checks.
 ```
 
-By default, pi gives the model four tools:
+By default, lunR gives the model four tools:
 
 - `read` - read files
 - `write` - create or overwrite files
 - `edit` - patch files
 - `bash` - run shell commands
 
-Additional built-in read-only tools (`grep`, `find`, `ls`) are available through tool options. Pi runs in your current working directory and can modify files there. Use git or another checkpointing workflow if you want easy rollback.
+Additional built-in read-only tools (`grep`, `find`, `ls`) exist but start off. lunR runs in your current working directory and can modify files there. Use git or `/rollback` if you want easy undo.
 
-## Give pi project instructions
+Permission modes are `manual | yolo | plan | auto`. Shift+Tab cycles that order. In plan mode the model uses `present_plan` for approval.
 
-Pi loads context files at startup. Add an `AGENTS.md` file to tell it how to work in a project:
+## Give lunR project instructions
+
+lunR loads context files at startup. Add an `AGENTS.md` file to tell it how to work in a project:
 
 ```markdown
 # Project Instructions
@@ -95,12 +119,12 @@ Pi loads context files at startup. Add an `AGENTS.md` file to tell it how to wor
 - Keep responses concise.
 ```
 
-Pi loads:
+lunR loads:
 
-- `~/.pi/agent/AGENTS.md` for global instructions
+- `~/.lunr/agent/AGENTS.md` for global instructions
 - `AGENTS.md` or `CLAUDE.md` from parent directories and the current directory
 
-Restart pi, or run `/reload`, after changing context files.
+Restart lunR, or run `/reload`, after changing context files.
 
 ## Common things to try
 
@@ -109,11 +133,11 @@ Restart pi, or run `/reload`, after changing context files.
 Type `@` in the editor to fuzzy-search files, or pass files on the command line:
 
 ```bash
-pi @README.md "Summarize this"
-pi @src/app.ts @src/app.test.ts "Review these together"
+lunr @README.md "Summarize this"
+lunr @src/app.ts @src/app.test.ts "Review these together"
 ```
 
-Images or text can be pasted with Ctrl+V (Alt+V on Windows); images can also be dragged into supported terminals.
+Paste images with Ctrl+V (Alt+V on Windows). The editor inserts `[image_1]`, `[image_2]`, … chips instead of a temp path. Dragging images into supported terminals also works.
 
 ### Run shell commands
 
@@ -123,43 +147,54 @@ In interactive mode:
 !npm run lint
 ```
 
-The command output is sent to the model. Use `!!command` to run a command without adding its output to the model context.
+The command output is sent to the model. Use `!!command` to run a command without adding its output to the model context. `/processes` lists background processes started this session.
 
 ### Switch models
 
-Use `/model` or Ctrl+L to choose a model. Use Shift+Tab to cycle permission mode (manual → yolo → plan → auto). Use `/thinking`, `/effort`, `/reasoning`, or `/settings` to change thinking level. Use Ctrl+P / Shift+Ctrl+P to cycle through scoped models.
+Use `/model` or Ctrl+L to choose a model. Use Shift+Tab to cycle permission mode (manual → yolo → plan → auto). Use `/thinking`, `/effort`, `/reasoning`, or `/settings` to change thinking level. `xhigh` and `max` are opt-in when the model supports them. Use Ctrl+P / Shift+Ctrl+P to cycle through scoped models. Catalog refresh is `/refresh`, not `lunr update`.
 
 ### Continue later
 
 Sessions are saved automatically:
 
 ```bash
-pi -c                  # Continue most recent session
-pi -r                  # Browse previous sessions
-pi --name "my task"    # Set session display name at startup
-pi --session <path|id> # Open a specific session
+lunr -c                  # Continue most recent session
+lunr -r                  # Browse previous sessions
+lunr --name "my task"    # Set session display name at startup
+lunr --session <path|id> # Open a specific session
+lunr --session-id <id>   # Exact project session ID (created if missing)
 ```
 
-Inside pi, use `/resume`, `/new`, `/tree`, `/fork`, and `/clone` to manage sessions.
+Inside lunR, use `/resume`, `/new`, `/tree`, `/fork`, and `/clone` to manage sessions. `/undo` rewinds the same session; `/edit` rewinds and pastes; `/rollback` forks and restores files.
 
 ### Non-interactive mode
 
 For one-shot prompts:
 
 ```bash
-pi -p "Summarize this codebase"
-cat README.md | pi -p "Summarize this text"
-pi -p @screenshot.png "What's in this image?"
+lunr -p "Summarize this codebase"
+cat README.md | lunr -p "Summarize this text"
+lunr -p @screenshot.png "What's in this image?"
+```
+
+Use `--mode json` for JSON event output or `--mode rpc` for process integration. `--offline` (or `PI_OFFLINE=1`) skips startup network operations.
+
+### Update
+
+```bash
+lunr update          # reinstall global @ashx-j/lunr from npm
+lunr update --self   # same
 ```
 
-Use `--mode json` for JSON event output or `--mode rpc` for process integration.
+Workspace `npx lunr` from this repo is not a published install and will not self-update. Catalog refresh is `/refresh`. Extra flags such as `--models`, `--all`, and `--force` are invalid.
 
 ## Next steps
 
-- [Using Pi](usage.md) - interactive mode, slash commands, sessions, context files, and CLI reference.
+- [Using lunR](usage.md) - interactive mode, slash commands, sessions, context files, and CLI reference.
+- [Built-in features](features.md) - gateway, cron, MCP, subagents, plan, todos, and more.
 - [Providers](providers.md) - authentication and model setup.
 - [Settings](settings.md) - global and project configuration.
 - [Keybindings](keybindings.md) - shortcuts and customization.
-- [Pi Packages](packages.md) - install shared extensions, skills, prompts, and themes.
+- [Packages](packages.md) - install shared extensions, skills, prompts, and themes.
 
 Platform notes: [Windows](windows.md), [Termux](termux.md), [tmux](tmux.md), [Terminal setup](terminal-setup.md), [Shell aliases](shell-aliases.md).

package/docs/rpc.md

@@ -2,12 +2,12 @@
 
 RPC mode enables headless operation of the coding agent via a JSON protocol over stdin/stdout. This is useful for embedding the agent in other applications, IDEs, or custom UIs.
 
-**Note for Node.js/TypeScript users**: If you're building a Node.js application, consider using `AgentSession` directly from `@earendil-works/pi-coding-agent` instead of spawning a subprocess. See [`src/core/agent-session.ts`](../src/core/agent-session.ts) for the API. For a subprocess-based TypeScript client, see [`src/modes/rpc/rpc-client.ts`](../src/modes/rpc/rpc-client.ts).
+**Note for Node.js/TypeScript users**: If you're building a Node.js application, consider using `AgentSession` directly from `@ashx-j/lunr` instead of spawning a subprocess. See the SDK (`docs/sdk.md`) and types in the published package (`node_modules/@ashx-j/lunr`). A subprocess TypeScript client ships in the repo as `packages/coding-agent/src/modes/rpc/rpc-client.ts`.
 
 ## Starting RPC Mode
 
 ```bash
-pi --mode rpc [options]
+lunr --mode rpc [options]
 ```
 
 Common options:
@@ -756,7 +756,7 @@ Response:
 }
 ```
 
-The current session name is available via `get_state` in the `sessionName` field. To set the initial name when starting RPC mode, pass `--name <name>` or `-n <name>` to the `pi --mode rpc` process.
+The current session name is available via `get_state` in the `sessionName` field. To set the initial name when starting RPC mode, pass `--name <name>` or `-n <name>` to the `lunr --mode rpc` process.
 
 ### Commands
 
@@ -792,7 +792,7 @@ Each command has:
   - `"prompt"`: Loaded from a prompt template `.md` file
   - `"skill"`: Loaded from a skill directory (name is prefixed with `skill:`)
 - `location`: Where it was loaded from (optional, not present for extensions):
-  - `"user"`: User-level (`~/.pi/agent/`)
+  - `"user"`: User-level (`~/.lunr/agent/`)
   - `"project"`: Project-level (`./.pi/agent/`)
   - `"path"`: Explicit path via CLI or settings
 - `path`: Absolute file path to the command source (optional)
@@ -847,7 +847,7 @@ Emitted when one low-level agent run completes. Contains all messages generated
 
 ### agent_settled
 
-Emitted after the full session-level run settles. At this point Pi will not continue automatically through retry, compaction retry, or queued follow-up messages.
+Emitted after the full session-level run settles. At this point lunR will not continue automatically through retry, compaction retry, or queued follow-up messages.
 
 ```json
 {"type": "agent_settled"}
@@ -1272,11 +1272,7 @@ Parse errors:
 
 ## Types
 
-Source files:
-- [`packages/ai/src/types.ts`](../../ai/src/types.ts) - `Model`, `UserMessage`, `AssistantMessage`, `ToolResultMessage`
-- [`packages/agent/src/types.ts`](../../agent/src/types.ts) - `AgentMessage`, `AgentEvent`
-- [`src/core/messages.ts`](../src/core/messages.ts) - `BashExecutionMessage`
-- [`src/modes/rpc/rpc-types.ts`](../src/modes/rpc/rpc-types.ts) - RPC command/response types, extension UI request/response types
+Types ship in the published package (`node_modules/@ashx-j/lunr`). In this repo they live under `packages/ai`, `packages/agent`, and `packages/coding-agent/src`.
 
 ### Model
 
@@ -1423,9 +1419,7 @@ for event in read_events():
 
 ## Example: Interactive Client (Node.js)
 
-See [`test/rpc-example.ts`](../test/rpc-example.ts) for a complete interactive example, or [`src/modes/rpc/rpc-client.ts`](../src/modes/rpc/rpc-client.ts) for a typed client implementation.
-
-For a complete example of handling the extension UI protocol, see [`examples/rpc-extension-ui.ts`](../examples/rpc-extension-ui.ts) which pairs with the [`examples/extensions/rpc-demo.ts`](../examples/extensions/rpc-demo.ts) extension.
+See [`examples/rpc-extension-ui.ts`](../examples/rpc-extension-ui.ts) for a complete example of handling the extension UI protocol; it pairs with [`examples/extensions/rpc-demo.ts`](../examples/extensions/rpc-demo.ts). After a global install, examples live under `node_modules/@ashx-j/lunr/examples` (or `npm root -g` then `@ashx-j/lunr/examples`). From this repo they are `packages/coding-agent/examples/`.
 
 ```javascript
 const { spawn } = require("child_process");

package/docs/sdk.md

@@ -1,8 +1,10 @@
-> pi can help you use the SDK. Ask it to build an integration for your use case.
+> lunR can help you use the SDK. Ask it to build an integration for your use case.
 
 # SDK
 
-The SDK provides programmatic access to pi's agent capabilities. Use it to embed pi in other applications, build custom interfaces, or integrate with automated workflows.
+The SDK provides programmatic access to lunR's agent capabilities. Use it to embed lunR in other applications, build custom interfaces, or integrate with automated workflows.
+
+Standalone consumers install and import `@ashx-j/lunr`. The jiti extension loader also aliases `@earendil-works/pi-coding-agent` (and the companion `@ashx-j/lunr-*` / `@earendil-works/pi-*` names). Default `agentDir` is `~/.lunr/agent`.
 
 **Example use cases:**
 - Build a custom UI (web, desktop, mobile)
@@ -16,7 +18,7 @@ See [examples/sdk/](../examples/sdk/) for working examples from minimal to full
 ## Quick Start
 
 ```typescript
-import { createAgentSession, ModelRuntime, SessionManager } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, ModelRuntime, SessionManager } from "@ashx-j/lunr";
 
 const modelRuntime = await ModelRuntime.create();
 const { session } = await createAgentSession({
@@ -36,7 +38,7 @@ await session.prompt("What files are in the current directory?");
 ## Installation
 
 ```bash
-npm install @earendil-works/pi-coding-agent
+npm install @ashx-j/lunr
 ```
 
 The SDK is included in the main package. No separate installation needed.
@@ -50,7 +52,7 @@ The main factory function for a single `AgentSession`.
 `createAgentSession()` uses a `ResourceLoader` to supply extensions, skills, prompt templates, themes, and context files. If you do not provide one, it uses `DefaultResourceLoader` with standard discovery.
 
 ```typescript
-import { createAgentSession, SessionManager } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, SessionManager } from "@ashx-j/lunr";
 
 // Minimal: defaults with DefaultResourceLoader
 const { session } = await createAgentSession();
@@ -128,7 +130,7 @@ import {
   createAgentSessionServices,
   getAgentDir,
   SessionManager,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const createRuntime: CreateAgentSessionRuntimeFactory = async ({ cwd, sessionManager, sessionStartEvent }) => {
   const services = await createAgentSessionServices({ cwd });
@@ -235,7 +237,7 @@ Both `steer()` and `followUp()` expand file-based prompt templates but error on
 
 ### Agent and AgentState
 
-The `Agent` class (from `@earendil-works/pi-agent-core`) handles the core LLM interaction. Access it via `session.agent`.
+The `Agent` class (from `@ashx-j/lunr-agent`) handles the core LLM interaction. Access it via `session.agent`.
 
 ```typescript
 // Access current state
@@ -334,23 +336,23 @@ const { session } = await createAgentSession({
   cwd: process.cwd(), // default
   
   // Global config directory
-  agentDir: "~/.pi/agent", // default (expands ~)
+  agentDir: "~/.lunr/agent", // default (expands ~)
 });
 ```
 
 `cwd` is used by `DefaultResourceLoader` for:
-- Project extensions (`.pi/extensions/`)
+- Project extensions (`.lunr/extensions/`)
 - Project skills:
-  - `.pi/skills/`
+  - `.lunr/skills/`
   - `.agents/skills/` in `cwd` and ancestor directories (up to git repo root, or filesystem root when not in a repo)
-- Project prompts (`.pi/prompts/`)
+- Project prompts (`.lunr/prompts/`)
 - Context files (`AGENTS.md` walking up from cwd)
 - Session directory naming
 
 `agentDir` is used by `DefaultResourceLoader` for:
 - Global extensions (`extensions/`)
 - Global skills:
-  - `skills/` under `agentDir` (for example `~/.pi/agent/skills/`)
+  - `skills/` under `agentDir` (for example `~/.lunr/agent/skills/`)
   - `~/.agents/skills/`
 - Global prompts (`prompts/`)
 - Global context file (`AGENTS.md`)
@@ -364,8 +366,8 @@ When you pass a custom `ResourceLoader`, `cwd` and `agentDir` no longer control
 ### Model
 
 ```typescript
-import { getModel } from "@earendil-works/pi-ai";
-import { ModelRuntime } from "@earendil-works/pi-coding-agent";
+import { getModel } from "@ashx-j/lunr-ai";
+import { ModelRuntime } from "@ashx-j/lunr";
 
 const modelRuntime = await ModelRuntime.create();
 
@@ -405,7 +407,7 @@ To match CLI model parsing, use the exported resolver helpers:
 import {
   resolveCliModel,
   resolveModelScopeWithDiagnostics,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const cliModel = resolveCliModel({
   cliModel: "anthropic/claude-opus-4-5:high",
@@ -436,10 +438,10 @@ Authentication resolution priority (handled by `ModelRuntime`):
 4. Fallback resolver (for custom provider keys from `models.json`)
 
 ```typescript
-import { InMemoryCredentialStore } from "@earendil-works/pi-ai";
-import { createAgentSession, ModelRuntime } from "@earendil-works/pi-coding-agent";
+import { InMemoryCredentialStore } from "@ashx-j/lunr-ai";
+import { createAgentSession, ModelRuntime } from "@ashx-j/lunr";
 
-// Default: uses ~/.pi/agent/auth.json and ~/.pi/agent/models.json
+// Default: uses ~/.lunr/agent/auth.json and ~/.lunr/agent/models.json
 const modelRuntime = await ModelRuntime.create();
 
 // Provider-owned auth methods and current status
@@ -473,7 +475,7 @@ const { session } = await createAgentSession({
 Use a `ResourceLoader` to override the system prompt:
 
 ```typescript
-import { createAgentSession, DefaultResourceLoader } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, DefaultResourceLoader } from "@ashx-j/lunr";
 
 const loader = new DefaultResourceLoader({
   systemPromptOverride: () => "You are a helpful assistant.",
@@ -495,10 +497,10 @@ Specify which built-in tools to enable:
 - `noTools: "builtin"` disables default built-ins while keeping extension and custom tools enabled
 - `excludeTools` disables specific built-in, extension, or custom tool names after any `tools` allowlist is applied
 
-The `edit` tool returns `details.diff` for Pi's TUI display and `details.patch` as a standard unified patch for SDK consumers.
+The `edit` tool returns `details.diff` for lunR's TUI display and `details.patch` as a standard unified patch for SDK consumers.
 
 ```typescript
-import { createAgentSession } from "@earendil-works/pi-coding-agent";
+import { createAgentSession } from "@ashx-j/lunr";
 
 // Read-only mode
 const { session } = await createAgentSession({
@@ -521,7 +523,7 @@ const { session } = await createAgentSession({
 When you pass a custom `cwd`, `createAgentSession()` builds selected built-in tools for that cwd.
 
 ```typescript
-import { createAgentSession, SessionManager } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, SessionManager } from "@ashx-j/lunr";
 
 const cwd = "/path/to/project";
 
@@ -545,7 +547,7 @@ const { session } = await createAgentSession({
 
 ```typescript
 import { Type } from "typebox";
-import { createAgentSession, defineTool } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, defineTool } from "@ashx-j/lunr";
 
 // Inline custom tool
 const myTool = defineTool({
@@ -577,10 +579,10 @@ If you pass `tools`, include each custom or extension tool name you want enabled
 
 ### Extensions
 
-Extensions are loaded by the `ResourceLoader`. `DefaultResourceLoader` discovers extensions from `~/.pi/agent/extensions/`, `.pi/extensions/`, and settings.json extension sources.
+Extensions are loaded by the `ResourceLoader`. `DefaultResourceLoader` discovers extensions from `~/.lunr/agent/extensions/`, `.lunr/extensions/`, and settings.json extension sources.
 
 ```typescript
-import { createAgentSession, DefaultResourceLoader } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, DefaultResourceLoader } from "@ashx-j/lunr";
 
 const loader = new DefaultResourceLoader({
   additionalExtensionPaths: ["/path/to/my-extension.ts"],
@@ -602,7 +604,7 @@ Extensions can register tools, subscribe to events, add commands, and more. See
 **Named inline extensions:** By default, inline factories display as `<inline:1>`, `<inline:2>`, etc. in the startup Extensions list. To show a descriptive name instead, wrap the factory:
 
 ```typescript
-import type { InlineExtension } from "@earendil-works/pi-coding-agent";
+import type { InlineExtension } from "@ashx-j/lunr";
 
 const myProvider: InlineExtension = {
   name: "my-provider",
@@ -623,7 +625,7 @@ This displays as `<inline:my-provider>` instead of `<inline:1>`. Bare factory fu
 **Event Bus:** Extensions can communicate via `pi.events`. Pass a shared `eventBus` to `DefaultResourceLoader` if you need to emit or listen from outside:
 
 ```typescript
-import { createEventBus, DefaultResourceLoader } from "@earendil-works/pi-coding-agent";
+import { createEventBus, DefaultResourceLoader } from "@ashx-j/lunr";
 
 const eventBus = createEventBus();
 const loader = new DefaultResourceLoader({
@@ -643,7 +645,7 @@ import {
   createAgentSession,
   DefaultResourceLoader,
   type Skill,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const customSkill: Skill = {
   name: "my-skill",
@@ -669,7 +671,7 @@ const { session } = await createAgentSession({ resourceLoader: loader });
 ### Context Files
 
 ```typescript
-import { createAgentSession, DefaultResourceLoader } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, DefaultResourceLoader } from "@ashx-j/lunr";
 
 const loader = new DefaultResourceLoader({
   agentsFilesOverride: (current) => ({
@@ -693,7 +695,7 @@ import {
   createAgentSession,
   DefaultResourceLoader,
   type PromptTemplate,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const customCommand: PromptTemplate = {
   name: "deploy",
@@ -728,7 +730,7 @@ import {
   createAgentSessionServices,
   getAgentDir,
   SessionManager,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 // In-memory (no persistence)
 const { session } = await createAgentSession({
@@ -822,7 +824,7 @@ sm.createBranchedSession(leafId);       // Extract path to new file
 ### Settings Management
 
 ```typescript
-import { createAgentSession, SettingsManager, SessionManager } from "@earendil-works/pi-coding-agent";
+import { createAgentSession, SettingsManager, SessionManager } from "@ashx-j/lunr";
 
 // Default: loads from files (global + project merged)
 const { session } = await createAgentSession({
@@ -856,8 +858,8 @@ const { session } = await createAgentSession({
 **Project-specific settings:**
 
 Settings load from two locations and merge:
-1. Global: `~/.pi/agent/settings.json`
-2. Project: `<cwd>/.pi/settings.json`
+1. Global: `~/.lunr/agent/settings.json`
+2. Project: `<cwd>/.lunr/settings.json`
 
 Project overrides global. Nested objects merge keys. Setters modify global settings by default.
 
@@ -878,7 +880,7 @@ Use `DefaultResourceLoader` to discover extensions, skills, prompts, themes, and
 import {
   DefaultResourceLoader,
   getAgentDir,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const loader = new DefaultResourceLoader({
   cwd,
@@ -919,7 +921,7 @@ interface LoadExtensionsResult {
 ## Complete Example
 
 ```typescript
-import { getModel } from "@earendil-works/pi-ai";
+import { getModel } from "@ashx-j/lunr-ai";
 import { Type } from "typebox";
 import {
   createAgentSession,
@@ -928,7 +930,7 @@ import {
   ModelRuntime,
   SessionManager,
   SettingsManager,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const modelRuntime = await ModelRuntime.create({
   authPath: "/custom/agent/auth.json",
@@ -1009,7 +1011,7 @@ import {
   getAgentDir,
   InteractiveMode,
   SessionManager,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const createRuntime: CreateAgentSessionRuntimeFactory = async ({ cwd, sessionManager, sessionStartEvent }) => {
   const services = await createAgentSessionServices({ cwd });
@@ -1049,7 +1051,7 @@ import {
   getAgentDir,
   runPrintMode,
   SessionManager,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const createRuntime: CreateAgentSessionRuntimeFactory = async ({ cwd, sessionManager, sessionStartEvent }) => {
   const services = await createAgentSessionServices({ cwd });
@@ -1086,7 +1088,7 @@ import {
   getAgentDir,
   runRpcMode,
   SessionManager,
-} from "@earendil-works/pi-coding-agent";
+} from "@ashx-j/lunr";
 
 const createRuntime: CreateAgentSessionRuntimeFactory = async ({ cwd, sessionManager, sessionStartEvent }) => {
   const services = await createAgentSessionServices({ cwd });
@@ -1112,7 +1114,7 @@ See [RPC documentation](rpc.md) for the JSON protocol.
 For subprocess-based integration without building with the SDK, use the CLI directly:
 
 ```bash
-pi --mode rpc --no-session
+lunr --mode rpc --no-session
 ```
 
 See [RPC documentation](rpc.md) for the JSON protocol.