@xingular/harness 1.3.1-unstable.2 → 1.3.1-unstable.4

package/CHANGELOG.md

@@ -2,6 +2,88 @@
 
 ## Unreleased
 
+- Render the `/btw` side answer as Markdown instead of plain text. Headings, emphasis, lists,
+  quotes, links, tables and fenced code use the theme's markdown colours, and a streaming answer
+  re-renders in place. Terminal control sequences in model output are still removed.
+
+- Add `/remote-control` (alias `/rc`): continue a terminal session from a phone or iPad, as Claude
+  Code's `/rc` does, without a cloud relay. The harness serves a small phone page on the computer's
+  Tailscale address, or its private Wi-Fi address, and the terminal shows a QR code for a one-device
+  pairing link. The person at the terminal allows each device; a paired phone then sends messages,
+  watches the reply stream, stops it, and answers approvals and questions through the same paths
+  the terminal uses. Every body is sealed with a key that reaches the phone only in the QR code's
+  fragment, keys live in memory, and remote control ends with the session. `xagent --remote-control`
+  turns it on at start; `/rc off` stops it. Terminal runs now also record streamed `message.delta`
+  events. New dependencies: `tweetnacl`, `uqr` (ADR-0056, page 15).
+
+- Recover a plan run whose reply loses its plan block. An attended top-level plan run now makes one
+  hidden format-repair turn in the same run, asking the model to re-send its own plan in one complete
+  block; a failed repair leaves the run completed and the terminal shows a warning instead of a plan
+  choice. The plan-research children, commands, probes, improvers, reflections and other unattended
+  runs are unchanged (ADR-0055).
+
+- A live terminal reply now reports a heartbeat every 30 seconds, and one that produces nothing but
+  heartbeats for 15 minutes is ended as `interrupted` with reason `stalled` instead of showing a run
+  that never settles. A running tool gets 30 minutes and an unanswered approval or question is never
+  cut short. Before this, a terminal reply reported no heartbeat at all, so the run sweep waited the
+  full 30-minute silence window and recorded `owner_gone` while the process was alive (ADR-0054).
+
+- Stop refusing repeated work. A reply is no longer refused, or ended, for calling the same tool
+  with the same arguments three times, for a Bash check that keeps failing, or for editing one path
+  more than four times: those calls are ordinary work, and the reply budget is the single bound. The
+  320-call/60-minute budget, its checkpoint handoff, slice continuation and the three-compaction
+  thrash rule are unchanged, and the `stuck` checkpoint reason stays readable in existing runs
+  (ADR-0053).
+
+- Make a skill named in a message required for that request. `$name` is a skill invocation at any
+  word start, not only as the first token: `Launch.requiredSkills` carries it and the compiler
+  renders a built-in dynamic `required-skills` section (order 52, 12,000 characters) from the pinned
+  variant's `SKILL.md`, naming an unavailable skill honestly and falling back to the shipped
+  `plugin-authoring` skill. It changes no tool or permission, and it belongs to the request, so an
+  identical one is delivered again; structured sessions deliver it through `sessionLaunch` and the
+  terminal appends the same text as a hidden `xingular-required-skills` message
+  (`requiredSkillsText`). The terminal no longer rewrites a leading `$name` to `/skill:name`, and its
+  `$` palette opens at the caret and inserts there, keeping the rest of the draft (ADR-0048).
+
+- Bound delegation per run and per profile. `spawn_subagent` and `wait_subagents` still exist, but a
+  run now starts at most four distinct child conversations: two `worker`, three `explorer`, one of
+  any other named profile and one with no profile. The parent's `subagents` option overrides them
+  (`maxChildren`, `maxByProfile`, `maxOther`, `maxUnprofiled`, clamped to 0–50), so a host and the
+  terminal receive the same defaults; `Subagents.spawn` refuses a child past a limit with an
+  `invalid_request` that tells the model to do the work itself, and starts no run. The count covers
+  the runs the parent was continued from, continuing a stopped child costs no slot, and a concurrent
+  spawn reserves its slot before it launches (ADR-0052).
+
+- Record where a request's characters went. `renderSized` returns the prompt and each section's
+  size, `Delivery.sizes` stores them on the recorded pack, and `Source.chars` attributes a variant's
+  tool guidance inside the tools section, so `context.attribution` (`terminal.context` in the
+  terminal) can return one row per contributor with its estimated tokens and share of the window,
+  reconciled to the provider's measured total, plus one row's text. `context.snapshot` also records
+  the compaction headroom the run was held to (`compaction: { enabled, reserveTokens }`) from Pi's
+  own settings.
+
+- Define an opt-in approved-window screenshot contract. `computer_screenshot` in
+  `src/computer/screenshot.ts` takes a host backend that captures exactly one currently approved
+  window, excludes the desktop, other windows and overlapping overlays, and refuses with
+  `COMPUTER_SCREENSHOT_UNAVAILABLE` instead of falling back to a display capture. It goes through
+  the ordinary tool gate and is not plan-mode safe; the standalone terminal has no backend, and the
+  existing macOS host capture has not adopted the contract (ADR-0050).
+
+- Watch approvals and questions through `terminal.pending.wait`: a control-key-protected revision
+  snapshot that returns as soon as the pending set changes and otherwise waits at most 20 seconds,
+  waking on additions, removals and disposal. `terminal.pending` stays available, the client
+  resynchronizes after errors, and no persisted state or public protocol changes (ADR-0051).
+
+- Swap the OpenTUI send keys back. `Return` sends, or queues a follow-up behind a running reply, and
+  `Cmd+Return`, `Ctrl+Return` or `Alt+Return` steers that reply. The `app.message.followUp` action is
+  `app.message.steer` again, so a `keybindings.json` entry under the newer name needs renaming.
+
+- Keep a stray mouse report out of input. When the terminal delivers a mouse report in two pieces
+  across the input parser's timeout, its `<button;column;row>` tail is dropped instead of being
+  typed into the composer or a single-line field, so a scroll can never become a run's prompt or a
+  filter. Text typed at human speed is never touched, pastes are never rewritten, and the Trajectory
+  page no longer prints a recorded mouse report.
+
 - Give top-level sessions a name and a current-state prompt. An unnamed session derives a
   provisional six-word name from its first substantive request; greetings and short replies stay
   unnamed, and the model can revise the name. Each top-level run also receives a request-scoped

package/README.md

@@ -37,7 +37,7 @@ index](docs/README.md) links the architecture and other project records.
 
 ### Session options for applications
 
-- Interactive sessions offer `spawn_subagent` and `wait_subagents` by default. `subagents: null` disables them; `{ maxDepth }` configures native nesting (default one, maximum three), independently of the host caller depth. Unattended sessions remain disabled unless the host explicitly supplies subagent options. A frozen capability set can narrow these tools further.
+- Interactive sessions offer `spawn_subagent` and `wait_subagents` by default. `subagents: null` disables them; `{ maxDepth }` configures native nesting (default one, maximum three), independently of the host caller depth. `{ maxChildren, maxByProfile, maxOther, maxUnprofiled }` bounds breadth: by default a run starts at most four distinct child conversations, two `worker`, three `explorer`, one of any other named profile and one with no profile. Unattended sessions remain disabled unless the host explicitly supplies subagent options. A frozen capability set can narrow these tools further.
 - `harness.subagents.spawn({ parentRunId, brief, agent?, tools?, wait? })` opens a fresh child of the same caller with no wider capabilities. `agent` names an agent profile (below). It returns `{ runId, nativeSessionId, agent?, unavailableTools? }` once open; `wait: true` also waits for settlement. `harness.subagents.wait({ parentRunId, runIds? })` joins selected direct children, or the current children when omitted, and returns their outcomes. `results` reads the same bounded outcome records without waiting. RPC exposes `subagents.spawn`, `subagents.wait`, and `subagents.results`; `sessions.spawnSubagent` remains a compatibility alias.
 - **Agent profiles** (PROP-0029) are what a subagent starts from: the built-in `worker` (reads, edits, writes, runs commands) and `explorer` (reads only), a person's own `<data root>/agents/<name>.md`, a repository's `<project>/.xingular/agents/<name>.md`, and the variant's c5 subagents, later ones winning. A profile is Markdown with frontmatter (`description`, `color`, `tools`, `plugins`, `variant`, `model`, `effort`) and its body is the role. It only narrows the parent's tools and plugins. `listProfiles`, `resolveProfile`, `createProfile` and `removeProfile` (RPC `agents.list|get|create|remove`) read and write them, and the child's `RunRecord.profile` names the one it used.
 - The model's `spawn_subagent` returns immediately by default; `wait: true` returns an inline result. `wait_subagents` joins selected children. The SDK and standalone terminal share this execution service. Terminal calls use its private control channel, including when connected apps are disabled.