v0.3.1

Fixed

• pitree did nothing when installed. The CLI guarded its entry point with an
  argv[1].endsWith("cli.js") check, but npm links the bin as a symlink at
  node_modules/.bin/pitree, so argv[1] ends with pitree and main() never ran — a silent
  exit 0 for every installed user since the package was first published. Now guarded with
  import.meta.main, which is symlink-proof. (The usual pathToFileURL(argv[1]) idiom would also
  have failed here: import.meta.url is the realpath, argv[1] is not.)
• Context size was estimated far too low. The gauge and panel summed chars/4 over session
  entries, which cannot see the system prompt or the tool schemas — charged every turn, present in
  no entry. Measured against pi's own count across local sessions the estimate ran 0.01x-0.7x of
  reality (mean 0.24x), a floor of ~2k tokens even on a small toolset. Context size now anchors on
  the last assistant turn's real message.usage and estimates only what follows, as pi does
  (compaction.js:131); the same sessions now read 1.00x. This mattered more after 0.3.0 moved the
  bands to absolute tokens (8k/32k/64k), where a 2k undercount can hold the gauge a whole band low.
  Affected the standalone pitree ui (always estimating), the panel right after load or
  compaction, and the ambient gauge before the first turn.
• The anchor refuses usage recorded before the latest compaction. Compaction keeps a tail of
  older messages, so a kept assistant turn carries usage describing the context compaction just
  discarded — anchoring on it read 150,100 tokens for a context of ~200, and it would have done so
  at exactly the moment the fallback path is used. Eligible turns are the compaction entry's
  descendants, matching pi's own refusal (agent-session.js getContextUsage returns
  tokens: null when nothing has answered since the boundary).

Changed

• @pi-context-tree/core adds contextTokens(tree, leafId) for "how big is this context";
  estimateContextTokens(slice) keeps its pure chars/4 meaning and is now only used for entry and
  branch weights, where the per-session baseline must not be counted.

v0.3.0

Added

• /gauge bar|border (F5.6) — the context gauge can render into pi's input box border instead of
  a widget pinned above the prompt, buying back a line of vertical space:

  ─ 46k / 200k · 23.2% filling ▲ +24% (chrome.snapshot) ──────··········
  

  Both modes render the same gaugeLabel() — tokens, percent, band word, est marker, compaction
  notice — plus the trend, so switching loses nothing. Narrow terminals drop the label and keep the
  bar; pi's ─── ↓ N more scroll indicator is preserved; RPC/headless falls back to the bar. The
  choice persists in ~/.pi/agent/pi-context-tree.json.

Changed

• The context gauge bands on absolute tokens instead of share-of-window. <8k low · 8k–32k
  healthy · 32k–64k filling · ≥64k red. Share-of-window was a poor proxy for what it claimed to
  measure: 10% of a 1M window is 100k tokens (deep into degradation) while 10% of a 32k window is
  3.2k (fine) — the same reading meaning opposite things. Percent is still printed as a label; it no
  longer decides anything.
• Thresholds are read off LOCA-bench (Feb 2026), which measures
  agent success against growing context rather than needle retrieval: 8k is where every model is
  still at peak, 32k is where the between-model spread opens, and 64k is the last point before the
  sharp 64k–96k drop. The previous NoLiMa-derived figures are 2025 retrieval numbers and markedly
  stricter than what 2026 agentic models actually do; spec Part 0 keeps NoLiMa for direction.
• Gauge ticks now sit where the band color actually changes for the current window.

Added

• Compaction guard (F5.5) — an independent warning when context enters pi's auto-compaction
  reserve (contextWindow - reserveTokens, default 16384). This is the container failure, not the
  quality one, and the two are deliberately separate signals: a 32k-window session can hit it while
  still healthy, and a 1M-window session can sit red for hours without approaching it. The gauge bar
  shows · pi compacts soon.

Fixed

• The red-band nudge re-armed on every dip out of red, so hovering the boundary during normal work
  re-fired what F5.3 specifies as a one-time nudge. It now re-arms only after context drops a full
  band clear of red, and resets between sessions.
• The nudge reported a fixed 40% threshold; it now reports the measured size.

v0.2.0

Added

• /branch names can contain Chinese characters (CJK Unified Ideographs) — contributed by
  @chaosorder010, ported from their fork with authorship.
• Panel: PageUp/PageDown paging in every view; x clears all marks in the current crop mode;
  the tree footer now documents g/G.

Fixed

• Panel: Ctrl+Q from a view-only pi context now opens the panel read-only up front (with a
  "run /panel to act" denial) instead of letting crop marks silently vanish when the action fails
  after close.
• Panel: applying a crop in one mode while the other mode (results vs whole-turns) still has marks
  now warns once — ⏎ again confirms — instead of silently dropping the other mode's marks.
• Panel: the overlay no longer shifts by one row when entering/leaving the inspect view.
• Panel: a (auto-select) reports only newly marked entries, and says so when nothing new matched
  instead of inviting an empty apply.
• Panel: first-line previews truncate by code points — emoji/CJK can no longer be split into
  mojibake at the cut.
• pitree: the gauge shows ~N est · window unknown instead of a permanent
  "estimating… (awaiting next turn)" when the token estimate is known but no context window is.
• /decisions --export takes the token after the flag as the output path (not the first token)
  and expands a leading ~.

Changed

• /merge squash/tournament review (#33 flow 1): the decision record now confirms in a
  full-screen overlay preview — Enter accept · e edit in editor · r re-draft · Esc cancel —
  with the blast radius (entries closed, ~tokens, drafting model) in the header. The editor is one
  keypress away, and saving there still confirms; closing it without saving returns to the preview
  instead of aborting the merge. Headless/RPC hosts keep the original editor gate unchanged. Nothing
  lands without explicit confirmation either way (F2.2).
• Pinned pi bumped 0.79.1 → @earendil-works/*@0.84.3; golden files re-recorded for pi's
  additive session-format fields (usage.reasoning, rawStopReason) — no behavior change in
  what this extension writes.
• Toolchain: TypeScript 6, Vitest 4, Biome 2 (config migrated; the static docs mockup is excluded
  from lint, matching Biome 1.x's scope), @types/node 25, @xterm/headless 6, postcss 8.5.25,
  and GitHub Actions checkout/setup-node v7.
• The release workflow can also be run manually (workflow_dispatch): it gates and cuts the
  release for the version on main, creating the tag server-side — for maintainers working from
  environments that can't push tags.

Security

• undici 8.5.0 → 8.9.0 (via the pi bump): fixes GHSA-4cwx-7wf7-3272 (high) and four
  medium-severity cache/cookie/header advisories.
• Transitive dev-dependency fixes: nanoid 3.3.18 (GHSA-2v37-7h3g-55p8, high) and protobufjs
  7.6.5 (GHSA-j3f2-48v5-ccww, moderate); the vulnerable esbuild left the dependency tree
  entirely with Vitest 4. npm audit: 0 vulnerabilities.

v0.1.1

Fixed

• Gallery preview media (image / video) now served via jsDelivr instead of raw.githubusercontent.com — which returned the demo MP4 as application/octet-stream, so pi.dev's gallery couldn't render it. jsDelivr serves the correct video/mp4 and image/gif with CDN + CORS. (Packaging only; no behavior change.)

v0.1.0

First public release — a git-style branch/merge/crop workflow plus a full-screen context panel for pi sessions. Append-only and recoverable; pinned to @earendil-works/*@0.79.1.

Commands

• /branch <name> [model] — label the current point (mirrored into pi's native labels) and fork off, optionally onto a cheaper branch model; the trunk model is recorded and restored on merge. Tab-completes model ids.
• /merge [--pick | --no-llm | --discard | --tournament] [note] — bare /merge squashes the branch into a human-confirmed ◆ decision record (mandatory editor gate — nothing lands until you save). --pick opens the mode selector; --no-llm writes the record by hand; --discard rejects; --tournament keeps the winner's record + drafted epitaphs for the sibling branches. Always navigates summarize:false so pi's own summary never double-writes.
• /crop [--top] [--auto] [--apply] [--dry-run] [--min-tokens N] [--older-than N] [--keep glob] — surgically stub fat tool/MCP results (result mode) or drop a whole Q&A turn (turn mode), append-only. --top crops the single biggest unprotected result with one inline confirm; --auto/--apply/--dry-run for rule-based and headless crops; latest-per-tool protection. Originals always recoverable.
• /undo — one-key, append-only revert of the last mutation: re-open a squashed/discarded branch, restore a crop, or undo a /branch. Nothing is deleted.
• /panel (Ctrl+Q) — full-screen context panel: tree with per-node token costs, branch status colors, top consumers, decision cards, and an entry inspector.
• /decisions [--export path] — review decision records; --export writes them to portable markdown (PR / ADR / Slack).
• pitree — standalone, read-only forest CLI across all pi projects (--dangling, --json) plus pitree ui.

Ambient UI

• Context-health gauge bar pinned above the prompt (green→red, band ticks at 5/15/40%) with a ▲ trend and jump attribution (ctx 38% ▲ +24% (chrome.snapshot)); stays honest while pi is still calibrating (band word + ~est, never a fake-precise percent). Plus a footer status, a color-hashed terminal title, a one-time >40% nudge, and a /compact philosophy warning.

Foundations

• Append-only data model (ctree/* markers) — session JSONL is never edited or deleted; every change is recoverable.
• Layered, pi-light core — core has zero pi deps; tui builds on pi-tui; extension is the only pi-facing surface; pitree is standalone.

Project & tooling

• MIT license, CONTRIBUTING.md, issue/PR templates, an SVG banner, a demo GIF, and discovery metadata on the package manifest.
• Tests — core units + committed fixtures + a 50MB perf test; tui xterm-headless harness; extension fake-pi units, real-pi RPC goldens (squash/discard/tournament/crop) and a v0.2 e2e (bare-merge, /undo, /crop --top, /decisions --export), plus a real-TUI PTY walk; pitree zero-write assertion.
• CI — lint/types/unit per push, integration against the pinned pi (keyless), and a non-blocking pi@latest drift lane.
• Release — pushing a vX.Y.Z tag runs the gate and cuts a GitHub Release from this changelog.