fix(panel): drop window-relative percentages, lead with sent-to-LLM tokens

[ranxianglei]

Why

An end-user misread the panel headline Context (session accounting): 65% (645k / 1.0M) as the live context size and reported "context blew up to 600k" (billion-context#12). The actual sent context was 98k (10%). Two problems:

1. Window-relative % is unstable across models — the same 645k is 65% of a 1M window and 322% of a 200k window; the number communicates nothing on its own.
2. The cumulative ledger sat in the headline slot, above the number compression actually controls.

What changed

• Removed both window-relative percentages (session-accounting headline %, X% of limit on the sent line).
• Reordered: Sent to LLM (est.) first — the current actual context — with the absolute window as reference (98k / 1.0M), then Session-only, then the cumulative line, relabeled Cumulative (session accounting, host footer scale) with an inline note that the host footer % is this number ÷ window.
• Sent-view composition percentages (Tool 40% etc.) are untouched — they are shares of the sent view, independent of the window.

Before / After

- Context (session accounting, host footer scale): 65% (645k / 1.0M) — never shrinks; includes compressed originals
+ Sent to LLM (after compression, est.): 98k / 1.0M
+ Session-only (compressed originals, est.): 109k — pruned from every request; the footer/nudge still count them
+ Cumulative (session accounting, host footer scale): 645k — never shrinks; includes compressed originals (the host footer % is this number ÷ window)

Verification

• typecheck clean; full suite 534 pass (panel tests updated: assert no % of limit, no NN% ( window-pct pattern, new line formats).
• Rendered the panel with the reported session's real numbers to eyeball ordering.

[github-actions]

📦 Built Package Artifact

Branch: 2026-08-25_panel-drop-window-pct (d22de3b)

Option A — Install from npm PR tag (recommended)

In your adapter project:

npm install acp-kernel@pr-161

Each push to this PR publishes a new version under the pr-161 npm tag.

Option B — Download artifact

1. Download the artifact from the Actions run
2. Extract the tarball and install:

tar xzf acp-kernel-pr161.tgz
npm install ./package

---

This comment is automatically updated on each push.