@buildaharness/aielia 0.3.4 → 0.3.6

package/README.md

@@ -7,6 +7,30 @@ what it may do, what it may believe, and what a job may cost — light enough fo
 "what's the weather", and it stages anything that can't be undone (`write_file`,
 `run_shell_command`, `send_email`) for your approval. Website: https://myaielia.com.
 
+## Install
+
+```bash
+# macOS / Linux — standalone binary, installed to ~/.local/bin (override with AIELIA_INSTALL_DIR)
+curl -fsSL https://myaielia.com/install.sh | sh
+curl -fsSL https://myaielia.com/install.sh | sh -s -- --force   # replace a non-aielia file at the target path
+
+# Windows (PowerShell) — installs to %LOCALAPPDATA%\Aielia\aielia.exe and adds it to your user PATH
+irm https://myaielia.com/install.ps1 | iex                       # set $env:AIELIA_FORCE = '1' first to force
+
+# or from npm
+npm install -g @buildaharness/aielia
+```
+
+Both installers read the manifest at `https://myaielia.com/aielia-latest.json`, download
+the binary for your platform over HTTPS only, verify its SHA-256 against the manifest and
+install it; re-running upgrades in place, or says it is already up to date. They refuse
+to overwrite an unrelated file (or a symlink, such as an npm-linked `aielia`) without
+`--force`. `aielia update` does the same upgrade later (see "Updates and the update check"
+below). On the first interactive launch with nothing configured, the CLI asks which
+provider to use and for its API key (live-checked with a free read-only call) and saves
+the choice to the persisted config; piped/scripted stdin skips this and keeps the
+`proxy` default.
+
 ## Design
 
 The harness here is a governance and reliability control plane, not just a
@@ -142,7 +166,7 @@ contradiction detection considers it:
 
 | Tier | Answers | Allowed `FactSource` | Retention | Contradiction-checked | Where it lives |
 |---|---|---|---|---|---|
-| **Episodic** | "What was said or mused, unconfirmed?" | any | session | no | `facts:<sessionId>` — also every `model_inferred`/`observed` `UserFact` lands here regardless of its `durable` bit; an unconfirmed model guess is never Knowledge |
+| **Episodic** | "What was said or mused, unconfirmed?" | any | session | no | `facts:<sessionId>`, plus `episodic:<sessionId>` session digests when `AUDIT_EPISODIC_DIGEST` is on (see below) — also every `model_inferred`/`observed` `UserFact` lands here regardless of its `durable` bit; an unconfirmed model guess is never Knowledge |
 | **Semantic** | "What's currently stated as true?" | `user_asserted`, `externally_verified` | durable (by tier policy) | yes | `facts:<sessionId>` or `facts:durable`, depending on the existing promotion policy (`durable` bit) — the tier a fact belongs to and whether it's actually promoted are tracked separately today |
 | **Identity** | "Who is this?" (name, "call me X") | `user_asserted` | durable | yes | `facts:durable` |
 | **Preference** | "What does the user want?" (stated preference) | `user_asserted` | durable | yes | `facts:durable`; a *configured* preference (backend, model, `enableShell`) is separately `AssistantConfig` (`config.ts`), not a `UserFact` at all |
@@ -158,6 +182,40 @@ the other half is that `isKnowledgeTier()` only returns true for `semantic`,
 `identity`, and `preference` — episodic entries, procedural weights, and
 commitments never enter contradiction detection as if they were beliefs.
 
+**Episodic memory now has a store and a writer, behind a flag.** With
+`AUDIT_EPISODIC_DIGEST` on (off by default; the cross-session scenario improved on 2 of 2 seeds, one scenario only), the assistant
+writes one short handoff digest per session (objective, what was done,
+decisions, open items, next step) at the session edge (`/new`, exit), never
+inside a turn, to `episodic:<sessionId>`. A second use of the same writer runs
+just before transcript compaction drops old messages, so facts in those
+messages are queued for confirmation instead of being lost. Digests are kept
+apart from durable facts and are never injected into the prompt: they reach the
+model only through the read-only `recall_memory` tool (`AUDIT_RECALL_TOOL`, off
+by default), which returns an index of recent digests and then one digest by id,
+wrapped as untrusted context. The model picks which digest to open; there is no
+keyword search. Digest text passes the same secret judgement as any other
+memory write, and a digest can never populate a Knowledge tier (the extended
+INV-16: a non-user origin is episodic only). Digests are kept for a retention
+window (default 90 days, `AUDIT_EPISODIC_RETENTION_DAYS`) and are covered by
+`/memory forget` and `/memory export`. This changes what `/new` keeps: durable
+facts as before, plus digests when the flag is on. Evidence is one scenario and two seeds; it also adds one model call per session edge.
+
+Related write-path controls: `AUDIT_MEMORY_BUDGETED_RENDER` is **on by default**
+(character-budgeted, priority-ordered facts block with keyed supersession, so a
+corrected fact replaces the old one; `=0` restores the old 20-fact slice; budget
+`memoryBudgetChars`, default 4000). In a six-week corrections scenario it fixed a
+stale-fact failure on 3 of 3 seeds. Off by default: `AUDIT_MEMORY_WRITE_GATE`
+(semantic secret redaction and instruction-shaped-text flagging before a fact is
+promoted; a missing judgement means the fact is not promoted; no outcome
+difference was seen because the base model already resisted the planted secret),
+`AUDIT_MEMORY_AUDIT_LOG` (`/memory history`, `/memory undo <seq>`),
+`AUDIT_MEMORY_REVIEWER` (post-turn reviewer; its writes are staged for
+`/memory confirm` unless `memoryWriteMode` is `auto`) and
+`AUDIT_MEMORY_CONSOLIDATION` (staged merge and archive proposals; not measured as
+an outcome). Known gaps: the model sometimes keys the same attribute two ways, so
+a correction can miss the old fact, and a natural-language "forget that" request
+is staged for approval rather than applied.
+
 The conversation transcript itself (`transcript:<sessionId>`, "what was
 said" verbatim) and a single turn's `AnswerClaim` (evidence vs. claim for one
 reply, see below) sit outside this tier system — they're the raw material a
@@ -273,8 +331,9 @@ await assistant.turn('Summarize this into notes.md', { approved: true, pendingAc
 
 Declining (`{ approved: false, pendingActionId }`) discards the staged record
 without writing. A pending action left over from a crashed/abandoned turn sits
-in `.pending-actions/` indefinitely — harmless (never applied without an explicit
-`approved: true` with the matching ID) but not currently auto-swept. This same
+in `.pending-actions/` — harmless (never applied without an explicit
+`approved: true` with the matching ID), and swept on the next startup unless a
+session still has a resumable checkpoint (`sweepAbandonedPendingActionsOnStartup`). This same
 staging record shape (a `kind` discriminator) is shared with `run_shell_command`
 (see "Shell access via tools" below) and `send_email`.
 
@@ -314,7 +373,7 @@ Both backends enforce the same "never write inline" rule, by different
 mechanisms:
 
 - **Proxy/Anthropic backend** (`LLMClient`): `PersonalAssistant`'s tool loop
-  (capped at 5 iterations) calls `callChatStructured` directly, executes
+  (bounded by `maxSteps`, default 15, minus a few steps held back for recovery) calls `callChatStructured` directly, executes
   non-mutating tool calls for real, and intercepts `write_file` itself before
   it ever reaches `file-tools.ts`'s staging code.
 - **Claude CLI backend** (`ClaudeCliLLMClient`): Claude Code's own agentic loop
@@ -331,8 +390,10 @@ mechanisms:
 
 v1 is deliberately read/list/write only — no delete/move tool (higher
 consequence than a write, no "undo" via re-approval). One workspace root per
-assistant instance; no multi-root or per-request override. chat-ui doesn't have
-a write-approval UI yet — file tools are CLI/desktop-only for now.
+assistant instance; no multi-root or per-request override. File tools need a
+real workspace directory, so they are CLI/desktop-only; chat-ui's approval card
+(with the exact change shown) is what resolves a staged write or shell command
+on the desktop build.
 
 ## Clarifying questions
 
@@ -370,8 +431,8 @@ follow-up `needs_clarification` batch if it's still unresolved once the first ba
 folded in, resolved through this exact same path.
 
 Two kinds of sites can raise a `questions` batch: the Trajectory Supervisor's `ASK_USER` directive
-(see ADR-005 — currently inert by default, since
-`HARNESS_TRAJECTORY_SUPERVISOR` stays off) and a handful of deterministic sites with a genuinely
+(see ADR-005 — the supervisor is on by default in Aielia;
+`HARNESS_TRAJECTORY_SUPERVISOR=0` turns it off) and a handful of deterministic sites with a genuinely
 enumerable option set, e.g. a batch-research budget running out ("continue with N more steps" /
 "stop and summarize" / "let me clarify the goal"). A site with no discrete option set keeps
 today's plain `missing_info` halt unchanged — this mechanism never forces a multiple-choice
@@ -448,6 +509,9 @@ without ever exposing the filesystem or shell.
 
 ## Batch research budget
 
+> The list detector below is a lexical check (the `batch-list` family), **off by default**: set
+> `ASSISTANT_LEXICAL_ON=batch-list` (or `ASSISTANT_LEXICAL_MODE=enabled`) to use batch research.
+
 The flat `maxSteps` cap that governs an ordinary chat turn (see below) doesn't
 know the difference between a one-question turn and a turn asking for the same
 lookup across many items — a 7-item batch and a 1-item question get the same
@@ -705,18 +769,9 @@ non-functional `web_search`. The active state is shown in the startup banner
 running session with `/config set` instead of an env var — see
 "Configuration" below.
 
-Set `ASSISTANT_LLM_BACKEND=claude-cli` to skip the proxy entirely and run turns
-through a local `claude -p` subprocess instead, using your already-authenticated
-Claude Code CLI session rather than an API key (`CLAUDE_PATH` overrides the
-`claude` binary path if it's not on `PATH`):
-
-```bash
-ASSISTANT_LLM_BACKEND=claude-cli npm run cli --workspace=packages/aielia
-```
-
-Or skip both the proxy and claude-cli and call a provider directly with your
-own API key — `ASSISTANT_LLM_BACKEND=anthropic|openai|openrouter` plus
-`ASSISTANT_API_KEY`:
+`ASSISTANT_LLM_BACKEND` also accepts `claude-cli` (shells out to the `claude` CLI already on
+your PATH, no API key needed; CLI and desktop only). Skip the proxy and call a provider directly with your own API
+key — `ASSISTANT_LLM_BACKEND=anthropic|openai|openrouter` plus `ASSISTANT_API_KEY`:
 
 ```bash
 ASSISTANT_LLM_BACKEND=anthropic ASSISTANT_API_KEY=sk-ant-... \
@@ -734,7 +789,8 @@ These three go straight from this process to the provider's own API
 — no proxy deployment needed, but unlike `authToken` (a self-hosted proxy's
 own bearer token), `ASSISTANT_API_KEY`/`apiKey` is a *real* provider key.
 It's stored the same way as every other secret field here — plaintext in
-`config.json`, not an OS keychain — so treat that file accordingly. When
+`config.json` (written with mode `0600`, in a `0700` directory), not an OS
+keychain — so treat that file accordingly. When
 `ASSISTANT_MODEL`/`/config set model` isn't set, each backend falls back to the
 current-generation default id exported from `@buildaharness/runtime`'s
 `model-defaults.ts` (`openai` → `gpt-5-mini`, `openrouter` →
@@ -767,9 +823,13 @@ you> /config
   model          (not set)
   enableWeb      false
   braveApiKey    (not set)
+  webBackend     direct
   enableShell    false
   shellTimeoutMs (not set)
+  shellNetworkAllowlist (not set)
   workspaceRoot  (not set)
+  enableEmail    false
+  ...            (one line per key; the full list is `CONFIG_KEYS` in config.ts)
   dangerouslySkipPermissions false
 
 you> /config set enableWeb true
@@ -785,7 +845,9 @@ you> /config reset enableWeb
 ✓ Reset enableWeb to default
 ```
 
-- `/config` lists every field's current (resolved) value. A field currently
+- `/config` lists every field's current (resolved) value; secret fields
+  (`authToken`, `apiKey`, `braveApiKey`, `resendApiKey`, `smtpPass`) print as
+  `********`, and credentials or query strings inside `proxyUrl` are masked. A field currently
   pinned by an env var shows `(env-pinned: VAR_NAME)` and cannot be changed
   with `/config set` — unset the env var first.
 - `/config set <key> <value>` validates the change (e.g. `enableWeb true`
@@ -798,15 +860,67 @@ you> /config reset enableWeb
 
 **Precedence**: env var > persisted config > built-in default, evaluated
 independently per field. Settings persist as plain JSON at
-`~/.buildaharness/personal-assistant/config.json` — like the rest of this
-package's persistence, it's a real file, not encrypted, so `authToken` and
-`braveApiKey` are stored in plaintext there. This is the same trust boundary
+`~/.buildaharness/personal-assistant/config.json` (created `0600` inside a
+`0700` directory) — like the rest of this
+package's persistence, it's a real file, not encrypted, so `authToken`,
+`apiKey`, `braveApiKey` and the email credentials are stored in plaintext there. This is the same trust boundary
 the repo's root `.env` already has, not a new one.
 
+Settings beyond those above (each has an env var, a `/config set` key, and a built-in default;
+mode flags take `enabled`/`disabled`):
+
+| Key (env var) | Default | What it does |
+|---|---|---|
+| `webBackend` | `direct` | Browser build only (see chat-ui README); the CLI always calls Brave directly |
+| `shellNetworkAllowlist` (`ASSISTANT_SHELL_NETWORK_ALLOWLIST`) | none (deny all) | Hosts an approved shell command may reach |
+| `enableEmail`, `emailProvider` (`resend`/`smtp`), `emailFrom`, `resendApiKey`, `smtpHost`/`smtpPort`/`smtpUser`/`smtpPass` (`ASSISTANT_ENABLE_EMAIL`, `ASSISTANT_EMAIL_*`, `ASSISTANT_RESEND_API_KEY`, `ASSISTANT_SMTP_*`) | off | Registers the staged `send_email` tool; `enableEmail` needs `emailFrom` and the provider's credentials |
+| `sessionCostLimitUsd`, `sessionCallLimit` (`ASSISTANT_SESSION_COST_LIMIT_USD`, `ASSISTANT_SESSION_CALL_LIMIT`) | unbounded | Refuses a new turn once the cross-session estimated spend or completed-turn count reaches the ceiling; shown in `/status` and `/cost` |
+| `memoryBudgetChars` (`ASSISTANT_MEMORY_BUDGET_CHARS`) | 4000 | Character budget for the facts block in the prompt |
+| `memoryWriteMode` (`ASSISTANT_MEMORY_WRITE_MODE`) | `staged` | `auto`, `staged` or `user_only`; see "Memory tiers" |
+| `oneLoopMode` (`ASSISTANT_ONE_LOOP`) | `enabled` | See "Design" |
+| `askMode` (`ASSISTANT_ASK_MODE`) | `disabled` | See "Clarifying questions" |
+| `planMode` (`ASSISTANT_PLAN_MODE`) | `legacy` | `gated` or `legacy` plan rollout |
+| `ambiguityGuardMode` (`ASSISTANT_AMBIGUITY_GUARD`) | `disabled` | Ambiguity guard |
+| `tuiMode` (`ASSISTANT_TUI`) | `disabled` | Full-screen terminal UI (Ink); only on a real TTY |
+| `updateCheck` (`ASSISTANT_UPDATE_CHECK`) | `enabled` | Passive update check |
+| `activeProject` (`ASSISTANT_ACTIVE_PROJECT`) | none | Project new project-scoped facts are tagged with (`/project`) |
+| `goalGraphMode`, `goalGraphSuggestMode` (`ASSISTANT_GOAL_GRAPH`, `ASSISTANT_GOAL_GRAPH_SUGGEST`) | `enabled` in the CLI | Goal tree, steering and next-step options |
+| `planGraphMode` (`ASSISTANT_PLAN_GRAPH`) | `disabled` | `/plan graph` |
+| `layerPolicyMode` (`ASSISTANT_LAYER_POLICY`) | `static` | `static`, `shadow` or `adaptive` |
+| `layers` | `{}` | Per-layer on/off, edited with `/layers`, not `/config set` |
+
+`ASSISTANT_ACTIVITY_LOG=1` additionally appends a debug activity log to
+`activity-log.jsonl` in the data directory (created `0600`). All CLI output has
+terminal escape sequences stripped, so text echoed from a fetched page or file
+cannot rewrite what an approval prompt shows.
+
+### Lexical checks (off by default)
+
+Every lexical pass in this package (regex / keyword / phrase-list checks over natural-language text) sits
+behind one switch, `lexicalMode`, and **every one is off by default** in the CLI, the browser tab and the
+desktop app — the LLM-based checks do the work instead. The ten families (`fact-markers`, `coding-fact`,
+`injection`, `enumeration`, `risk`, `task-cancel`, `plan-mode`, `batch-list`, `tool-yield`,
+`template-keywords`) and what "off" means for each are listed in `src/lexical/lexical-mode.ts`.
+
+- `ASSISTANT_LEXICAL_MODE=enabled` turns every family back on (the pre-2026-09-28 behaviour).
+- `ASSISTANT_LEXICAL_ON=batch-list,task-cancel` turns only those families back on (`all` for every one).
+- `ASSISTANT_LEXICAL_OFF=<families>` turns families off even under `enabled`; it wins over ON.
+
+The mode is handed to `@buildaharness/harness`'s own lexical switch at the start of every run, so
+`enabled` turns the harness's checks back on too (see that package's README).
+
+Some families have no LLM replacement, so with them off the feature they drive does not run: batch
+research (`batch-list`), matching "skip that step" to one step of an active plan (`task-cancel`), leaving
+plan drafting by phrase (`plan-mode`; `/plan` still works), and the batch sub-loop's lexical dead-end
+detection (`tool-yield`; the web tool's own "No results found." still counts). With `risk` off, a durable
+plan step saved without its own risk level is treated as HIGH.
+
 ## REPL commands
 
-Type `/help` inside a running CLI session for this list. All of them read or
-change local session/config state — none of them make an LLM call themselves.
+Type `/help` inside a running CLI session for this list. Almost all of them read or
+change local session/config state without an LLM call; the exceptions are `/plan sketch`
+and `/memory consolidate`, each of which makes one. `/exit` (also `/quit`, `exit`, `quit`)
+ends the session.
 
 | Command | What it does |
 |---|---|
@@ -815,15 +929,28 @@ change local session/config state — none of them make an LLM call themselves.
 | `/status` | Show the resolved config (model, backend, workspace, enabled capabilities — same as the startup banner) plus this session's transcript length and whether a plan is active |
 | `/export [file]` | Save this session's transcript to a markdown file (default: `assistant-transcript-<timestamp>.md` in the current directory) |
 | `/undo` | Remove the last exchange from conversation history — a completed turn drops both the user message and the reply; a turn still awaiting approval drops just the pending message. Only affects what the model remembers: a real `write_file`/`run_shell_command` effect from that turn is **not** reversed |
-| `/memory` | Show facts learned about you, reminders created so far, and the learning-layer `ExperienceStore`'s real content — every strategy weight, plus the 20 most recently learned decompositions/recovery sequences (newest first), not just counts |
+| `/undo-action [id]` | List the real filesystem effects of approved actions that can still be reverted (see `/status`'s undo-log line), or stage a revert of one for your approval |
+| `/memory` | Show facts learned about you, pending-confirmation guesses, reminders created so far, and the learning-layer `ExperienceStore`'s real content — every strategy weight, plus the 20 most recently learned decompositions/recovery sequences (newest first), not just counts |
+| `/memory confirm <n\|category>` / `/memory reject <n\|category>` | Promote a pending-confirmation guess (or a whole category) to durable memory, or discard it |
+| `/memory forget <n> [erase]` | Remove a learned fact by its number in "Facts I know". It stays restorable through the audit log (`/memory undo`) unless you add `erase`, which scrubs its text from the log too. `/memory forget digest [id]` erases one stored session digest, or all of them |
+| `/memory history` / `/memory undo <seq>` | Show recent memory changes with their sequence numbers, and restore one change's pre-image (needs `AUDIT_MEMORY_AUDIT_LOG`) |
+| `/memory status` | Store size vs budget, pending count, write mode, last consolidation |
+| `/memory archive [restore <n> \| forget <n>]` | List facts set aside or replaced by a newer statement; restore one, or erase one for good |
+| `/memory consolidate [accept\|dismiss <n>]` | Propose merging or retiring overlapping facts; nothing changes until you accept (needs `AUDIT_MEMORY_CONSOLIDATION`) |
+| `/memory off` / `/memory on` | Stop or resume all memory writes for this install; existing facts stay readable and removable |
 | `/memory export [file]` | Write the full, unbounded `ExperienceStore` contents (every strategy weight/decomposition/recovery sequence, not the 20-entry preview `/memory` prints) plus facts/reminders to a JSON file (default: `assistant-memory-<timestamp>.json`). Read-only: there's no matching import path, so exported data can't be hand-edited and loaded back in |
 | `/search <query>` | Ranked search over past messages, across every session in this install — a hit is the one message that matched, not the whole session transcript around it. Read-only: never an LLM call or network request. Scoring is tokenized/graduated, not exact-substring-only (see "Conversation history" above), and a query matching nothing returns an explicit "no results" line |
+| `/project [name]` | Show or switch the project new project-scoped facts are tagged with; `/project clear` reverts to the workspace default |
 | `/model [name]` | Show the active model, or switch it — a thin alias over `/config set model <name>` (see "Configuration" above); rejected the same way if `model` is pinned by `ASSISTANT_MODEL` |
 | `/cost` | Show token usage for the last turn and the running session total |
 | `/doctor` | Check proxy reachability (proxy backend) or the `claude` binary (claude-cli backend), plus workspace root and data dir health — no dedicated check yet for the anthropic/openai/openrouter backends, only the backend-agnostic checks run for those |
 | `/why` | Explain the harness path the last turn took (verification confidence + node sequence) |
+| `/layers` | Show all 11 harness layers: fired or skipped, and why, for the last turn. `/layers settings` lists the reasoning layers with their cost/evidence; `/layers on\|off\|reset <id>` changes a layer's persisted on/off choice (an operator-set `AUDIT_*` env flag wins and shows as pinned) |
 | `/sources` | List files/URLs the last turn actually consulted |
 | `/plan` | Show the active structured plan's task status |
+| `/plan sketch <request>` | One-shot, advisory plan sketch: no plan record, nothing staged, cannot execute |
+| `/goals` | Review every known goal thread this session: status, tasks and visibility (freshly computed, carried over, done, suggested) |
+| `/plan graph [thread-id]` | Draw the active plan as a read-only dependency graph (needs `planGraphMode` enabled; full-screen pane in the terminal UI with arrows/Tab/Enter/q, one static render in the plain REPL). Glyphs, mapping and keys: `docs/plan-visualization.md` |
 | `/checkpoint [clear]` | Inspect a stuck in-progress harness checkpoint (step, node, failed-resume count so far), or `/checkpoint clear` to discard it — see "Recovering a stuck checkpoint" above. Scoped to just the checkpoint: unlike `/clear`, transcript/facts/plan are untouched |
 
 ### `/cost` and real vs. estimated dollar figures
@@ -831,13 +958,7 @@ change local session/config state — none of them make an LLM call themselves.
 Token counts are always real, on every backend. The dollar figure attached to
 them is not always the same kind of number:
 
-- **claude-cli backend**: `costUsd` comes straight from `claude
-  --output-format json`'s own `total_cost_usd` field — real Anthropic
-  accounting. It may read `$0` if the underlying `claude` session is
-  authenticated against a Pro/Max subscription rather than API billing, in
-  which case `$0` does *not* mean "this turn was free" — `/cost`'s output
-  says so explicitly.
-- **every other backend** (`proxy`, `anthropic`, `openai`, `openrouter`):
+- **every backend** (`proxy`, `anthropic`, `openai`, `openrouter`):
   none of these compute a dollar cost themselves — only the raw token counts
   each provider's response already includes (`@buildaharness/proxy` is a thin
   pass-through, see `packages/proxy/src/forward.ts`; the three direct clients

package/dist/PlanGraphPane.d.ts

@@ -0,0 +1,19 @@
+import { VizNode } from './plan-viz/types.js';
+/** Width at which the detail drawer docks to the right instead of being toggled. */
+export declare const DRAWER_DOCK_COLUMNS = 120;
+export interface PlanGraphPaneProps {
+    nodes: readonly VizNode[];
+    columns: number;
+    rows: number;
+    /** False while an approval prompt owns the keyboard: the pane stays drawn but ignores keys. */
+    active?: boolean;
+    color?: boolean;
+    ascii?: boolean;
+    onClose: () => void;
+}
+/**
+ * Read-only plan graph pane (plans/plan_visualization_plan.html, R2). Keys: arrows (or [ ]) move along edges and ranks, j/k and PgUp/PgDn scroll the detail drawer,
+ * Tab/Shift+Tab walk task order, Enter or d toggles the detail drawer below 120 columns, q or Esc closes.
+ * No key edits anything: the plan changes only through the approval gate.
+ */
+export declare function PlanGraphPane({ nodes, columns, rows, active, color, ascii, onClose }: PlanGraphPaneProps): React.JSX.Element;