You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.
ui(panel): surface session Web-UI deep link in /acp panel and acp-cache
ui(web): session title cells become real hash anchors — Ctrl/Cmd+click or middle-click opens the session in a new tab; plain clicks navigate in-page as before
ui(web): render expanded compression-block summaries as markdown
ui(web): fit tables without horizontal scroll; universal copy-flash without label swap; per-client launcher notes as hover tooltips
ui(web): miss-split annotations back to % not pp; upstream reachable wording for HTTP >= 400; single raw config-file editor replaces route/compress JSON boxes; plugin mode marked recommended with full 9-agent list; copy feedback on chip buttons
feat(web): add Logs page (live tail of bili.log with session-id filter, download, copy path); detail identity links to a session's log lines
ui(web): unify percentage-point units on hit-rate annotations, hide empty stub sessions (count shown), make wide tables scrollable
ui(web): add ? help icon (click-to-open popover) on annotated stats
ui(web): annotate the cache hit-rate stat with TTL/comp/new cost split in-card; drop the long footnote (full text moved to hover tooltip)
ui(web): make session usage miss-split line (new/comp/TTL with hit-rate cost) visibly readable
feat(web): show hit-rate miss decomposition (new/comp/TTL, in pp) on every session row, the global hit card and session usage; folds table becomes one scroll panel
feat(web): decompose missed tokens into new/compression/TTL-expiry globally and per protocol; add cache hit rate to session usage card
fix(web): per-session saved column now derives from cache ledger (stats.tokensSaved is no longer written); add client / cum. input / compression-count columns; per-block copy buttons + blocks copy-markdown action + title copy & hover-full-title
feat(web): mark compression blocks active vs archived; add download-blocks(.md) action
fix(web): handoff doc readability - role divider headers, tool args kept verbatim in pre, line breaks preserved; chart legend swatches get real colors (TTL now purple)
fix(web): trajectory polish - merge burst-fold markers (no ghosting), draw system-prompt baseline, show client origin; fold table capped at 30; untitled blocks titled from summary lead
Release audit — v0.1.161 (branch 2026-09-27_release-v0.1.161, head ef965c31)
Release diff: exactly one commit over master — release v0.1.161, touching only package.json + package-lock.json (version 0.1.160 → 0.1.161). Complies with the one-version-one-commit discipline; no content bundled into the release commit.
Version-window regression audit (v0.1.160..HEAD, 35 non-merge commits): ~25 commits are the Web UI rewrite (#1426) — read-only management plane under /__bili/. The pipeline-relevant changes are five, all deliberate and disclosed in this PR's changelog:
Chain checkpoint step 3 enforcement ([design] chain checkpoint step 3: carrier stamp shape on role-alternation-strict wires (anthropic/google) #1421) — old: shadow mode, log-only, zero forwarding decision → new: first-processor-wins is enforced. Requests carrying a verifiable <bili-chain> checkpoint forward verbatim (pipeline skipped); stale unmatched carriers are stripped and processed normally; invalid tags are never trusted. Every processed outbound request is now stamped with a content-level <bili-chain> tag in the per-wire trailing control slot (anthropic: extra trailing text part of the last user message; google: merged into last content parts; openai: standalone trailing user message; responses: before any trailing compaction_trigger). Consequence: model providers now see this ~≤200-char tag on every processed request (small per-request token overhead, visible to the model) — owner-documented design decision from 2026-09-26, gated by the pre-existing chainContentDetection !== false config. Wire invariants held: compaction_trigger stays last input item; role-alternation-strict wires use merged (not appended) forms; digest covers the exact forwarded bytes; stamp failure is best-effort (forward unstamped, never breaks the forward).
Cache ledger unbounded (缓存账本在 SAMPLE_CAP 处丢弃最早的逐请求采样——轨迹图无法覆盖会话完整时间跨度 #1489) — old: trimmed to 512 lines / 256 folds (oldest spliced out) → new: full history retained; only the acp_cache detail:"full" text rendering caps at the newest 512 lines with an explicit linesOmitted count. Memory growth bounded (~one small line per request).
Web UI rewrite + Logs page (feat(web): full UI rewrite — read-only overview / sessions / config / connect (#1420) #1426) — read-only; new /__bili/overview|sessions|logs|sessions/<id>/detail endpoints follow the existing loopback-only protection incl. tunnel-marker rejection. Panel/acp-cache output gains a Web UI: deep link inserted BEFORE the panel footer deliberately (after-footer would break the LLM-context stripper's anchor match and leak the panel into model context); acp-cache MCP results gain one extra link line (harmless, intended).
High-risk pattern checks: no fail-fast→swallow regressions (stamp failure logged best-effort by design; nameless drop logs warn loudly); no default/threshold drift beyond the feature itself; no persistence-format or message-ref/id changes; src/update.ts, acp-kernel pin, zod pin, MITM/CA/security paths untouched. Behavior changes are pinned by dedicated tests (chain-checkpoint-step3, loop-strict-echo-responses, cache-ledger, reasoning-echo*, openai-toolcall-finish-reason, WC-009 gate) — assertions with teeth, not tautologies.
CI on head sha ef965c31: 13/13 green — unit tests (ubuntu+windows, node 22+24), real codex/pi/dsh/opencode lanes vs deterministic fake upstream, hermetic registry e2e, build-artifact, version-guard. PR state: open, mergeable clean, base master.
Verdict:本版本引入回归:无(0 处)。Five behavior changes above are intentional and disclosed (old→new stated); release diff clean; CI fully green on the rebased head. 可合并 — ready for human merge (merging publishes via release.yml; agent will not merge).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.
Changes since v0.1.160