Write the 0.2.92 changelog and release notes

Second sweep over the OpenTUI cutover plus the rebuilt model
surface. Several entries are behaviour that had been fixed once and
lost when the renderer was replaced, so the notes say what changed
for the operator rather than which branch restored it.

Author: TheGreatAxios

CHANGELOG.md

@@ -19,6 +19,98 @@ Format loosely follows [Keep a Changelog](https://keepachangelog.com/). Versions
 - Live OTEL collector verify (Phoenix or equivalent) against the merged sink.
 - Dogfood session migrate: new session under `~/.corbits/projects`, one legacy `.agent-state` migrate, write under state root still asks.
 
+## [0.2.92] - 2026-08-07
+
+A second sweep over the OpenTUI cutover, plus a rebuilt model surface. Two of
+these faults could end a session outright, and several were behaviour that had
+been fixed once already and lost when the renderer was replaced.
+
+### Model selection
+
+The picker lists providers first and descends into models on select, with
+Escape returning to the provider level. Recents and favourites stay flat at the
+top, and each account appears as its own row.
+
+- **Model tiers are gone.** `settings.tiers`, `profile.tier`, and the
+  `task(tier=)` argument no longer exist, and `/fast`, `/standard`, and
+  `/clever` are retired rather than remapped — a tier was a per-name fallback
+  chain, which neither a favourite nor a pinned model expresses. Per-agent
+  selection continues through `profile.inference`. A settings file containing
+  `tiers` still loads; the key is dropped on save. (CL-5591)
+- **The context meter was wrong by nearly four times** for any provider with a
+  custom name. An account-qualified identity did not match the registry, so a
+  500k window read as the 128k default. Resolution now tries the identity as
+  given, the bare model id, and the canonical provider/model form, and marks a
+  figure as estimated only when it genuinely falls back. (CL-5587)
+- The current model is read from the live session rather than inferred from the
+  most recent pick, which mislabelled any session that never opened the picker.
+  (CL-5597)
+
+### Sessions could be killed outright
+
+- **Switching models poisoned the conversation permanently.** A reasoning
+  signature issued by one provider was replayed to another that could not
+  decrypt it, and every subsequent turn failed with HTTP 400. Signatures now
+  carry the provider that issued them, so two backends sharing a model name
+  cannot replay each other's. Switching accounts on the same provider still
+  preserves reasoning continuity. (CL-5592, CL-5594)
+- **A model that fell into a loop ran unbounded.** Repetition is detected by
+  character period within a streaming cycle, and by comparing cycle
+  fingerprints across tool calls, so a loop that emits a tool call each pass is
+  still caught. Ordinary narration repeated before successive tool calls is
+  not. (CL-5577)
+
+### The screen
+
+- Plugin diagnostics wrote raw to stderr and corrupted the frame. They now go
+  through the log sink, and the warnings that used to vanish with them are
+  surfaced where the operator can see them. (CL-5411)
+- The provider setup screen garbled its own text on short terminals — rows were
+  compressed into one another instead of clipping. (CL-5363)
+- The command palette matches the prompt box width, drops its marker column,
+  kind column, and title rule, and marks the selected row by colour rather than
+  a grey band. (CL-5581, CL-5582, CL-5583, CL-5584)
+- An open overlay reserves its own border, title, and content rows before any
+  other chrome is allowed to starve it. (CL-5584)
+- **`/resume` was offering sessions that did not exist.** Demo fixture data was
+  shipping in the production bundle and rendering whenever a dependency was
+  missing. A missing dependency now produces an honest empty state. (CL-5596)
+- Dialog choices read as plain English rather than internal names. (CL-5586)
+
+### Context and state
+
+- Compaction stopped hollowing out the turns it had just decided to keep. A file
+  edit inside the recent window keeps its content. (CL-5595)
+- `run.json` is finalized when the process crashes, without reading from disk on
+  the crash path. (CL-5574)
+- An `@`-mentioned file outside the workspace is inlined once rather than
+  blocked, gated by the sensitive-path list and a total byte cap. That list now
+  covers shell histories, system credential files, keychains, browser cookie and
+  login stores, and cloud credentials. (CL-5479)
+
+### Agents and the machine
+
+- **An agent could rewrite your global git configuration to push**, altering
+  every repository on the machine. That now requires operator approval, and a
+  scoped push path applies credentials per invocation with nothing written to
+  any config file. (CL-4762)
+- `present`, `manage_goal`, `manage_tasks`, and `lsp` are advertised only when
+  they apply. (CL-5588)
+- Live progress appears on a dispatched sub-agent's transcript row. (CL-5576)
+- The most recently queued message can be cancelled. (CL-5572)
+
+### Development
+
+- **The test suite only passed in one order.** Bun mutates the namespace object
+  returned by `await import()` when a module is later mocked, so the usual
+  capture-then-restore idiom silently reinstalled the mock process-wide. Under
+  randomized order the suite produced over a hundred failures; it now passes
+  across every seed tried, and CI runs a fixed seed on each change plus a
+  rotating seed nightly. (CL-5579)
+- `docs/TUI.md` states how the terminal UI is meant to look and behave —
+  overlays, selectors, the palette, the prompt box, scrolling, and key macros.
+  Nine documents describing the finished migration are retired.
+
 ## [0.2.91] - 2026-08-07
 
 A bug-fix release on the OpenTUI cutover. Most of these faults had no visible

docs/release-notes-0.2.92.md

@@ -0,0 +1,95 @@
+## A rebuilt model surface, and two bugs that could end a session
+
+This is the second sweep over the OpenTUI cutover. Several of these were
+behaviour that had been fixed once already and lost when the renderer was
+replaced — the fix lived in a file the cutover deleted, so the bug came back
+without anyone changing it.
+
+### Picking a model
+
+The picker now lists providers, and you descend into one to choose a model.
+Escape steps back out to the provider level rather than closing. Recents and
+favourites stay flat at the top so a model you already use is one keystroke
+away, and each account gets its own row instead of being flattened into a
+single combined list.
+
+**Model tiers are gone.** `/fast`, `/standard`, and `/clever` are retired
+rather than remapped, because a tier was a fallback chain of providers rather
+than a single model — neither a favourite nor a pinned model says the same
+thing. Per-agent selection still works through the agent's own inference
+setting. A settings file that still contains tiers loads fine; the key is
+dropped the next time settings are saved.
+
+**The context meter was reading nearly four times low** for anyone on a
+custom-named provider. A 500k window showed as the 128k default, so the meter
+looked comfortable while the real context filled. It now recognises
+account-qualified model names, and only marks a figure as estimated when it is
+genuinely guessing.
+
+The model marked as current is the one the session is actually running. It used
+to be inferred from the most recent pick, which meant any session that never
+opened the picker showed the wrong one.
+
+### Two ways a session could die
+
+**Switching models used to poison the conversation permanently.** Reasoning
+state issued by one provider was replayed to another that could not read it,
+and every turn after that failed. Reasoning state now travels with the provider
+that produced it. Switching between accounts on the same provider still keeps
+reasoning continuity.
+
+**A model that fell into a loop ran until you stopped it.** Repetition is now
+detected inside a single streaming stretch, and by comparing successive
+stretches across tool calls — so a model that loops while calling a tool each
+pass is still caught. Ordinary narration repeated before successive tool calls
+is left alone.
+
+### The screen
+
+- Plugin diagnostics were writing straight to the terminal and corrupting the
+  display. They go to the log now, and the warnings that used to disappear
+  along with them are surfaced where you can see them.
+- The provider setup screen garbled its own text on a short terminal, with rows
+  compressed into one another instead of clipping.
+- The command palette matches the prompt box width, loses its marker column,
+  kind column and title rule, and marks the selected row by colour instead of a
+  grey band.
+- An overlay reserves room for its own frame before anything else is allowed to
+  squeeze it.
+- **`/resume` was offering sessions that did not exist.** Demo placeholder data
+  was shipping in the product and appeared whenever something failed to load.
+  A missing dependency now shows an honest empty state.
+- Dialogs describe their choices in plain English.
+
+### Context and files
+
+- Compaction stopped hollowing out the turns it had just decided to keep, so a
+  file you edited two turns ago is still there when you ask about it.
+- A crash finalizes the session record instead of leaving it marked running.
+- Mentioning a file outside your workspace inlines it once rather than refusing.
+  Sensitive files stay blocked, and that list now covers shell history, system
+  credentials, keychains, browser cookie and password stores, and cloud
+  credentials.
+
+### Your machine
+
+**An agent could rewrite your global git configuration in order to push**,
+which changes every repository on the machine and outlives the session. That
+now asks you first, and there is a scoped push path that applies credentials
+for a single command without writing to any config file.
+
+Tools that only apply sometimes — `present`, goal and task management, and LSP —
+are only offered when they apply. A dispatched sub-agent shows live progress on
+its own row. The most recently queued message can be cancelled.
+
+### Underneath
+
+The test suite only passed in one order. Under a randomized order it produced
+over a hundred failures, because a mocking idiom used throughout was silently
+leaving mocks installed for every file that ran afterwards. It now passes in any
+order, and CI checks a fixed order on every change plus a random one nightly.
+
+There is also now a written specification for how the terminal UI is meant to
+look and behave, covering overlays, selectors, the palette, the prompt box,
+scrolling and key macros. Nine documents describing the finished migration have
+been retired.