@xingular/harness 1.6.0-unstable → 2.0.1-unstable

package/docs/parity.md

@@ -36,7 +36,7 @@ implemented is not a parity claim; acceptance is tracked per command.
 | Agent profiles | `agents/profiles.ts` | `spawn_subagent { agent }`, `agents.list/get/create/remove`; terminal `terminal.agents.*`; package profiles through `Loading.profilePaths` | `/agents` page: browse, create, edit in `$EDITOR`, copy, delete; package profiles listed under "From a plugin" and switched on `/plugins` | Solo `/agents` lists profiles; profile details and management are not wired | partial | PAR-010 |
 | Run todo list | `tools/todo.ts` | `todo_write`, `runs.todo` (`runs.checklist` deprecated); terminal `todo` telemetry | registered in terminal sessions and their subagents; each write shows as a todo block in the transcript; `/todo` shows the current list; a subagent row shows its `n of m tasks` | `/todo` shows the current list on demand; each write is not rendered inline | terminal done; App shows it on demand | PAR-001 |
 | Continuation of a stopped run | `sessions/continuation.ts` | `continueFrom`, `runs.continuation` | not offered (`/resume` reopens history only) | not offered | planned | PAR-003 |
-| Bounded replies and checkpoints (PROP-0041) | `sessions/workSlice.ts`, `tools/checkpoint.ts`, `sessions/runner.ts`, `terminal/stallWatch.ts` | `checkpoint_write`, `workSlice`, `runs.continuation.checkpoint`, `checkpoint`/`heartbeat` events | guard on every terminal reply with the shared tool; every live reply heartbeats and a reply with no progress for fifteen minutes ends as `stalled`, a reply waiting on subagents is judged by each child's own clock, and the working row names what it waits on; the handoff is recorded on the run; no checkpoint card or slice control yet | not wired | implemented; terminal card, App presentation and `/slices` open | PAR-004 |
+| Bounded replies and checkpoints (PROP-0041) | `sessions/workSlice.ts`, `tools/checkpoint.ts`, `sessions/runner.ts`, `sessions/stallWatch.ts` | `checkpoint_write`, `workSlice`, `runs.continuation.checkpoint`, `checkpoint`/`heartbeat` events | guard on every terminal reply with the shared tool; every harness run and terminal reply heartbeats and a reply with no progress for fifteen minutes ends as `stalled` (a stalled live session is closed), a reply waiting on subagents is judged by each child's own clock, and the working row names what it waits on; the handoff is recorded on the run; no checkpoint card or slice control yet | not wired | implemented; terminal card, App presentation and `/slices` open | PAR-004 |
 | Accounts | `accounts/` | `accounts.*` | `/accounts` | Accounts | parity | — |
 | Models and effort | `accounts/choices.ts` | — | `/model`, `/effort` | composer pickers | parity | — |
 | Skills | `plugins/`, `tools/dispatch.ts`, `prompt/compile.ts` | `skill_load`; `Launch.requiredSkills` | `$name` at any word start (required for that request), `/skill:name`, browser Skills tab | composer `$` chip with `requiredSkills`; Capability | implemented; install routes taught in the release-owned skill, foreign manifest skills load as package skills; acceptance not recertified | — |
@@ -136,7 +136,8 @@ or live-model sketch quality.
 
 | ID | Gap | Planned change |
 |---|---|---|
-| PAR-018 | Remote control from the App | `/remote-control` drives an `xagent` terminal session from a phone (page 15). App sessions are structured runs, not terminal sessions; the App would need the same pairing over its own session controls, or to present a terminal session's remote control. |
+| PAR-019 | Client terminal (ADR-0083) | The default terminal runs on harness live sessions; `--daemon` and `xagent attach` let a reply outlive its window. The full production PTY run passes at 40x20, 80x24, 100x30 and 120x40, with the focused suites as recorded in ADR-0083; the suites that still fail fail the same way on the previous release's in-process runtime (Known drift D-30, D-31). Plugin custom TUI components, key handlers, renderers, shortcuts and themes need `XINGULAR_TERMINAL_RUNTIME=inprocess` (INV-TUI-8). Provider limits are captured by the harness's own model runtime; `/goal` runs as a harness goal. |
+| PAR-018 | Remote control from the App | `/remote-control` drives an `xagent` terminal session from a phone (page 15). App sessions are structured runs, not terminal sessions; the App would need the same pairing over its own session controls, or to present a terminal session's remote control. ADR-0083: App chat turns now run on live sessions (`live: true`), the same path a client terminal uses, so remote control can move to live sessions; not built yet. |
 | PAR-017 | Plugin proposal review surfaces | The terminal provides hash-bound review in `/plugins`; the App has no proposal review UI yet. |
 | PAR-001 | Todo list not rendered inline in the App | Both surfaces can show the current list: the terminal renders each write as a todo block and `/todo` shows a snapshot; the App's `/todo` shows a read-only list. The App still does not draw an inline block for each write. |
 | PAR-002 | Acceptance of terminal-model History/Wiki/skill tools | Source gap resolved: `Terminals.ownTools` registers History/trajectory, Wiki-read and skill tools over the session socket; `xagent-wiki` is a user-facing shell utility, not the model's only route. Acceptance has not been recertified in this documentation pass. |
@@ -145,7 +146,7 @@ or live-model sketch quality.
 | PAR-005 | Wiki browsing only in the App | A `/wiki` page over `wiki.*`. |
 | PAR-006 | Acceptance of terminal first-party hooks | Source gap resolved: enabled hooks are returned by protected `firstParty.list` and loaded by `terminal/piExtension.ts`. Acceptance has not been recertified in this documentation pass. |
 | PAR-007 | Host tools without a complete Harness surface | The opt-in screenshot contract and unregistered interaction adapter exist, but terminal availability reporting, per-action authorization and a conforming backend are not wired. The current macOS host captures a display, not an isolated approved window, and uses global input. Terminal socket execution and native input delivery require a verified authorization boundary before control tools can be exposed. The remaining computer controls are host-owned; the files vault becomes a Harness capability or is dropped. |
-| PAR-008 | Separate session catalogs | Proposal approved; shared catalog is not implemented. Terminal `/session` selects native Pi history in the current folder. App `/session` reads Solo `agent.threads`, maps threads through Solo project groups, and filters to the current effective account and folder; `/session all` broadens only within that App catalog. It cannot open an arbitrary native session path. No cross-surface catalog or visibility guarantee exists. |
+| PAR-008 | Separate session catalogs | Proposal approved; shared catalog is not implemented. Terminal `/session` selects native Pi history in the current folder. App `/session` reads Solo `agent.threads`, maps threads through Solo project groups, and filters to the current effective account and folder; `/session all` broadens only within that App catalog. It cannot open an arbitrary native session path. No cross-surface catalog or visibility guarantee exists. ADR-0083: `sessions.live` lists the live sessions of one harness, and the long-lived harness lists detached terminal replies (`terminal.detached`); neither is a catalog of saved sessions. |
 | PAR-009 | Shared folder/recent-project choice | Terminal starts from its launch `cwd` and can switch through its worktree surface. App Solo uses Project › Session and starts new sessions in the selected project's folder; it has no folder/worktree level or shared recent-folder picker. |
 | PAR-010 | Agent profile management in Solo | App Solo `/agents` can list profiles. Although the renderer allowlist includes `agents.get`, Solo does not wrap it; `agents.create/remove` are not exposed there. Profile details and management actions are unavailable, unlike terminal `/agents`. |
 | PAR-011 | Web annotations | Harness, terminal and App source done (PROP-0017, PROP-0018, 2026-10-24): the App calls `annotations.*`, imports its old notes once, uses the `page_notes_*` tools, and has the Annotate panel. Open: acceptance of the inspector and selection gestures in the running App's WKWebView. PROP-0038 (2026-10-25): both front ends share the page helper, so open shadow roots work in the terminal's capture browser and the App's tabs alike; composed text capture, save, resolve and reveal were exercised in an isolated App WKWebView, inspector clicks were not. PROP-0048 (2026-10-27): Harness and terminal moved to pending/sent with two popover actions, send-all with an optional request, clear, read-only page-note tools, and DevTools app discovery and launch; the App's Annotate panel still uses the removed queue methods and must follow. |

package/docs/releases/2.0.1-unstable.md

@@ -0,0 +1,63 @@
+# Xingular Harness 2.0.1-unstable
+
+Unstable preview of the current Harness work. Install with `npm install @xingular/harness@unstable`.
+2.0.0-unstable was tagged but never published; this is its first release.
+This is a 2.0 line because the terminal's runtime changes: `xagent` is now a client of the harness
+(ADR-0083), which adds methods and a socket transport and changes who owns execution in the
+terminal. The package API and the stored data layout are otherwise unchanged.
+
+- **One session runtime (ADR-0083): the terminal is now a client of the harness.** `xagent` runs no
+  agent loop in its window any more. Each turn is a harness run with the same gate, run records,
+  plan mode, goals and subagents as a host's, and the harness keeps the conversation's Pi session
+  open across turns (`sessions.run { live: true }`), so steering, queued follow-ups and plugin
+  state carry from one turn to the next. New methods `sessions.live`, `sessions.close`,
+  `sessions.followUp` and `sessions.followUp.clear`. `XINGULAR_TERMINAL_RUNTIME=inprocess` runs the
+  previous in-process runtime.
+- **A long-lived harness (opt-in).** `xagent daemon start|stop|status` runs one harness per state
+  folder on an owner-only socket; `xagent --daemon` windows use it, so a reply keeps running when
+  its window closes, and `xagent attach [session]` reconnects. Plain `xagent` is unchanged: its
+  window runs its own private harness.
+- **Every harness run now ends when it stops making progress.** A reply that produces nothing for
+  fifteen minutes (thirty with a tool running; a pending approval or a wait for subagents does not
+  count) is interrupted with reason `stalled`, whatever front end started it, and its live session
+  is closed rather than reused. Every run now sends the 30-second `heartbeat`, not only runs with a
+  work slice, so a long quiet tool is no longer settled as `owner_gone`.
+- **Switching accounts starts on the new account's model.** A conversation resumed on another
+  account that names a model this account cannot use starts on this account's own latest choice,
+  with a notice, instead of showing and sending the old account's model. Plan and normal mode keep
+  their own model and effort in the new terminal: a mode that never chose an effort starts on the
+  default rather than the other mode's, a mode switch during a reply waits for it to settle, and a
+  one-shot `/plan` runs on the plan mode's choice.
+- **The new terminal offers every effort level the model supports.** It stopped at `high`; it now
+  lists `xhigh` and `max` where the model maps them, and runs a model at the nearest level it
+  supports when asked for one it does not.
+- **Fenced code in labeled panels.** Code blocks appear in a bordered panel labeled with the fence
+  language, with tree-sitter highlighting where a grammar is bundled and lightweight Python, shell
+  and JSON highlighting otherwise. The final-answer prompt asks for language-labeled fences and
+  `bash` fences for commands the person must run.
+- **A reply whose provider request timed out and was retried successfully is now recorded as
+  completed**, not failed. A terminal window whose terminal closed no longer leaves its process
+  running.
+- Terminal runs now record Pi's session id as `nativeSessionId`, as host runs do (in-process runs
+  keep recording their history file). `/session` takes a saved conversation's session id as well
+  as its file. Plugin dialogs reach the window as questions.
+
+Two prompt lines change (the language-labeled fences), so the stable prefix misses the provider
+cache once per existing session after the upgrade.
+
+Behaviour changes to know about: in the default terminal, plugins get the host's interface
+(dialogs, notices, status lines and text widgets); custom terminal components, key handlers,
+renderers, shortcuts and themes need `XINGULAR_TERMINAL_RUNTIME=inprocess`.
+
+Known gaps: a list item's wrapped lines are not aligned beneath its text (the renderer that did
+that cost the blank rows between paragraphs, so lists wrap as in the previous release; Known drift
+D-32). Remote control (`/remote-control`) still belongs to a terminal session, so a phone cannot
+reach an App chat, and a reply that outlives its window under `--daemon` loses its phone
+(PAR-018). The stall guard was tested with a fake Pi session and fake timers; no live model
+request exercised it.
+
+The release workflow builds the tarball from the `v2.0.1-unstable` tag, reruns CI on Ubuntu and
+macOS, smoke-tests that exact tarball on both, and attaches it with `SHA256SUMS` to the GitHub
+release before publishing it to npm's `unstable` dist-tag with provenance. The published SHA-256 and
+npm integrity are the ones in that attached file, which `scripts/release-verify.mjs` checks against
+the registry.

package/docs/terminal-tui.md

@@ -203,9 +203,10 @@ An empty conversation shows a centered welcome. The default `Xingular Agent` ide
 an orange block `X` and blue letter-spaced `A G E N T`, followed by `Welcome.`, the tagline
 `One run, done well.`, and a blue `/help` hint. Explicit host product names use the same generic mark and
 subline formatting. The current model and thinking level remain available in dim text. Once a message
-exists, a scrollable transcript fills the space above the composer. Single-line notices can appear
-with the welcome, while multiline notices such as `/help` switch to the transcript layout so their
-output cannot overlap it. The composer is a single top and bottom rule, with the right-aligned `plan mode` label followed by one divider character in the top rule,
+exists, a scrollable transcript fills the space above the composer. Assistant replies, plan bodies,
+and other transcript Markdown use one renderer. Single-line notices
+can appear with the welcome, while multiline notices such as `/help` switch to the transcript layout
+so their output cannot overlap it. The composer is a single top and bottom rule, with the right-aligned `plan mode` label followed by one divider character in the top rule,
 and the textarea in the middle.
 The working status row shows the active verb with a soft, warm glint that feathers across it and
 fades past its edges, followed by run duration and the latest completed assistant response's output
@@ -310,8 +311,12 @@ bundle, an installer, a launchable script or an executable file is refused with
 being run. The launcher receives the address as one argument without a shell. OSC 8 metadata is
 emitted where available, but link activation does not depend on terminal OSC 8 support; a terminal
 that opens OSC 8 links itself acts on its own modifier, so the Harness keeps the primary click.
-Inline and fenced code use a subtle panel fill with syntax colors. Emphasis, quotes, list markers,
-tables, dividers and task-list markers use the existing titanium palette. Images display their alt
+Inline code uses a subtle panel fill. Fenced code appears in a bordered panel labeled with the
+opening fence's language; JavaScript, TypeScript/TSX, Zig and other bundled grammars use tree-sitter,
+while Python, shell and JSON receive lightweight token highlighting. Unknown or unlabeled languages
+remain readable in the same panel, with `CODE` shown when no language is given. The code itself
+stays selectable and copyable, and the panel updates while a reply streams. Emphasis, quotes, list
+markers, tables, dividers and task-list markers use the existing titanium palette. Images display their alt
 text and are not fetched or rendered as image files.
 
 ## Todo block

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xingular/harness",
-  "version": "1.6.0-unstable",
+  "version": "2.0.1-unstable",
   "type": "module",
   "description": "Xingular Harness — a Pi agent harness built on recursive harnessing (Harness²): versioned eight-component variants, refinement from evidence, multi-account sessions, a compiled prompt, project notes, tools, and MCP",
   "repository": {