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

package/CHANGELOG.md

@@ -2,6 +2,80 @@
 
 ## Unreleased
 
+- Reword the final-reply guidance so the outcome leads and structure follows what the answer needs. The
+  reporting guidance is part of every request's stable prefix, so this changes the cached prefix.
+- Keep the provider cache working after a compaction (ADR-0067). The compaction checkpoint now arms only
+  for a compaction during the running reply, is built once, and sits right after the summary instead
+  of being rebuilt at the end of every request. A request after a compaction is again the previous
+  request plus new items, so Codex WebSocket continuation and prefix caching apply. Before, every later
+  turn of a compacted session resent its whole context: one measured session fell from 94–99% to
+  18–24% cache hits after its first compaction.
+- Flag a low prompt-cache hit rate in the terminal's composer status bar. `R<percentage>%` now covers the
+  last 10 model responses instead of the whole session (`recentCacheUsage`, `CACHE_HIT_WINDOW`), and
+  gets a yellow `⚠` below 70 percent and a red one below 40 percent. Each drop to a worse level posts
+  one transcript notice. A window of one response, or one with no cache reads or writes, is not judged
+  (`cacheHitLevel`, `CACHE_HIT_WARNING_PERCENT`, `CACHE_HIT_CRITICAL_PERCENT`).
+
+- Refine a variant from the terminal and keep checkpoints of it (PROP-0052, ADR-0065, ADR-0066).
+  `/refine [what to look at]` replays the latest request typed in this chat from a snapshot of the
+  folder as that turn found it, in throwaway shared clones, after a confirmation that shows the run
+  count and models; it runs in the background, and `/refine review` shows every candidate's changes
+  and output and adopts any of them. Guidance reaches improvers and composers only, never the blind
+  selector. Task runs default to this chat's model; `--model` sets the improver's, and an adopted
+  version records the model it was tuned on. `/variant` switches this conversation to another
+  version at the next turn (resuming the same conversation), restores, compares, tags, and takes
+  single components back from an earlier version. New methods: `refine.fromRun`,
+  `refine.candidateDiff`, `refine.candidateOutput`, `variants.tag|untag|tags|resolve|revert`. Run
+  records gain `workspaceSnapshot`, version records `tunedFor`, and scopes `tags.json`.
+
+- Start a conversation this account cannot use on the account's newest selection. A resumed
+  conversation keeps its model while the account offers it and holds its provider's credentials;
+  otherwise the terminal starts it on the mode's choice, then normal's, then the newest selection in
+  any mode, with that selection's effort, writes the model change into the conversation, and says in
+  one notice which model it replaced. A fallback is never saved as the person's choice, and with no
+  usable saved model Pi's own fallback message stands (ADR-0064).
+
+- Make unfinished-work handoffs actionable: the stable reporting guidance now names the person’s
+  concrete decision or the next action and its owner for each material blocker, without imposing a
+  fixed heading (PROP-0051, ADR-0063).
+
+- Share the account sign-in between `npm run dev` and the installed `xagent`. A standalone launch
+  can now take its account identity from another state directory with `--account-state <dir>`
+  (`HarnessOptions.accountsDir` plus that state's `secrets.json`), and `npm run dev` passes the
+  installed one, so one provider sign-in serves both while development keeps its own data,
+  approvals and plugin trust (ADR-0062).
+
+- Require owner-prefixed plugin commands on terminal and structured sessions. Plugin-owned prompt
+  templates join extension commands under `/<owner-prefix>:<name>`, with no bare plugin aliases.
+  A package can select a root template with `harness.defaultPrompt`; owner and route collisions fail
+  closed. Standalone templates, `/skill:<name>` and core commands remain (ADR-0061).
+
+- Make an approval a control, never a typed permission. The compiled guidance now tells the model to
+  call the tool, the Harness pauses that exact call (`waiting_for_approval`), and Allow resumes it in
+  the same turn; a denial returns a tool result on the still-running turn and says so, instead of
+  inviting another prose request. Nothing outside the workspace changes before the click, and Full
+  Permission remains the standing bypass (INV-GATE-9, ADR-0060).
+
+- Record structured tool refusals and run stop codes, and expose them in trajectory search and the
+  terminal trajectory page. Compaction events include available token measurements; older run
+  records remain readable without these fields.
+
+- Keep a refused question answer in the terminal. A choice, note or typed answer that the Harness
+would reject now stays in the dock with an inline reason, instead of closing the form and losing the
+draft; the reason names the question and the field (selection, typed answer or note), and the answer
+is checked against the server rule before it is sent. The terminal was previously reopening an empty
+question after any rejection, so a second Continue skipped everything.
+
+- Scroll a `/btw` answer taller than its block. PageUp/PageDown now reach the side-question dock
+while it is open, and the mouse wheel over the block browses it too; before this the transcript
+consumed those keys, so the block's `PgUp/PgDn/wheel browse` hint did nothing. When the answer fits, the
+keys scroll the transcript as before.
+
+- Drop the context-use reading from the terminal's composer status line, so it no longer ends the
+token group with a figure such as `6.6%/?`. The line keeps the project and branch, account, model
+and effort, and input/cache hit rate/output tokens; the share of the window stays on the `/context`
+page. Both the OpenTUI status bar and the exported `tui/status` band lose the reading.
+
 - 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.

package/README.md

@@ -294,11 +294,13 @@ npm run dev
 
 `npm run dev` rebuilds the CLI and opens the Harness terminal in the current working directory.
 It uses separate development directories by default: `~/.xingular-harness-dev/data` and
-`~/.xingular-harness-dev/state`. This keeps development harness data and device settings—including
-accounts, Pi settings, approvals, and connections—separate from the installed command. Press
-`/quit`, Ctrl+C or Ctrl+D to close it. Override either directory with `--data <dir>` or
-`--state <dir>`; for example: `npm run dev -- --data <dir> --state <dir>`. An omitted option keeps
-its development specific default.
+`~/.xingular-harness-dev/state`, so development harness data, approvals, plugin trust and
+connections stay separate from the installed command. It signs in as the installed command's
+accounts, though: one provider sign-in serves both launches. Press `/quit`, Ctrl+C or Ctrl+D to
+close it. Override either directory with `--data <dir>` or `--state <dir>`; choose the accounts a
+launch signs in as with `--account-state <dir>`, for example
+`npm run dev -- --account-state ~/.xingular-harness-dev/state` for a fully separate identity. An
+omitted option keeps its development specific default.
 
 The OpenTUI/Solid frontend is the only terminal. Install Bun 1.3.14 or newer and run
 `npm run build:tui` (or `npm run build`); without Bun the build fails rather than producing a
@@ -404,10 +406,13 @@ still be removed; that session then asks for another account the next time it st
 The installed standalone command defaults to `~/.xingular-harness/data` and
 `~/.xingular-harness/state`; `npm run dev` instead defaults to the separate
 `~/.xingular-harness-dev/data` and `~/.xingular-harness-dev/state`. Override either with
-`--data <dir>` and `--state <dir>`. Session history is stored per working directory and can be
-reopened with the terminal's `/resume` command. The explicit `terminal` command is an alias for
-the default launch. Use `--help` to see the commands; `serve` remains the host-facing RPC service
-for integrations such as Xingular Agent/App.
+`--data <dir>` and `--state <dir>`. A launch signs in as the accounts kept in the state directory
+it uses; `--account-state <dir>` takes them from another state directory instead (its `accounts`
+folder and its `secrets.json`), which is how `npm run dev` reaches the installed command's sign-in.
+Session history is stored per working directory and can be reopened with the terminal's `/resume`
+command. The explicit `terminal` command is an alias for the default launch. Use `--help` to see
+the commands; `serve` remains the host-facing RPC service for integrations such as Xingular
+Agent/App.
 
 ## Storage