AstrBot-Desktop/CHANGELOG.md
YokiiroBW 9b2ec64502
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
fix(pet): read stored preferences and stop the pet from stealing focus
An audit of the destroy→hide change across four lenses raised 17
findings; 14 survived adversarial verification. Two of them were
regressions that change introduced, and both had the same shape: code
that only worked because the pet window used to not exist.

  show_pet_context_menu picked the pet window and fell back to main.
  While the pet rendered inside the app its window had been destroyed at
  startup, so the fallback happened to select the visible main window.
  Now that the window merely hides, the menu was being anchored to a
  hidden HWND, which Win32 cannot bring to the foreground. The
  visibility test is explicit now rather than incidental.

  DesktopPetView read the connection state in a mount effect and nothing
  emitted connection events, so destroy-and-rebuild was what re-read it.
  Without a remount the floating pet showed whatever was true at startup
  for the rest of the session. reveal_pet_window now emits
  pet-window-revealed and the view re-reads on it.

The rest were already there. Every pet setting was decorative: the
preferences were applied and then dropped, so reveal_pet_window had to
invent an answer and hard-coded the first monitor, the safe edge and
always-on-top — reverting the user's choices on every show. The pet view
re-sent a fully hard-coded payload whenever game mode toggled, and the
settings page initialised its controls from literals, so returning to
the page and changing one thing pushed three stale defaults back onto
the window. There is a session-scoped store now, a command to read it,
and both frontends read before they write. Persisting it across restarts
is F-75.

Always-on-top is off by default, which is what the Q6 acceptance
criterion asked for (F-35), and the window no longer takes focus when
shown — it was activating on show and swallowing keystrokes meant for
the main window. focusable is left alone on purpose: clearing it adds
WS_EX_NOACTIVATE, which would re-break the context menu now anchored to
that window. That is F-79.

The pet also painted a solid dark rectangle before its assets arrived.
The transparency rule is gated on a class that an effect inside the
5.2 MB lazy chunk added, so until that chunk ran the app's opaque
background won. This is why the earlier hunt for "the rule that beats
!important" found nothing: the class was not applied yet, so specificity
was never the question. The pet now has its own entry document carrying
the class statically. An inline script would not do — tauri-utils only
nonces script[src^='http'], so it would pass in dev and be blocked by
script-src 'self' in a release build.

Rust tests 92 → 97, frontend 30 → 35. All 11 mutations of the new
assertions were confirmed to fail.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 05:25:27 +08:00

147 行
11 KiB
Markdown

# Changelog
All notable changes to this project will be documented in this file.
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow Semantic Versioning.
## [Unreleased]
### Added
- Debug-level tracing of AstrBot SSE frame shapes: frame type, which identity fields are present, and the key names inside `data`. No payload text is recorded. Enable with `RUST_LOG`.
- Q10-Q15 chat experience increment: lightweight Markdown rendering, message actions, generation controls, session actions, connection controls, and responsive chat layout.
- AstrBot OpenAPI adapter foundation: SSE mapper, dual-slot runtime skeleton, credential enrollment IPC, transport-aware profiles (ADR-0005).
- Authoritative architecture, implementation, and repository workflow documents.
- Repository rules, ignore rules, implementation plan, progress tracking, and decision log.
- Tauri 2, React, TypeScript, Vite, and Rust workspace skeleton with tray and single-instance lifecycle.
- Independent companion and operations REST/SSE clients with local profile binding, cancellation, reconnect, Last-Event-ID, and per-slot deduplication.
- Windows Credential Manager, bounded UI Automation, selected-window in-memory capture, Event Log, process, port, foreground-window, authorized log-tail, configuration parsing, and redaction Spikes.
- Recoverable plan/dry-run/copy/verify/commit file transactions with no-overwrite conflict policies and source preservation.
- Composite-key SQLite isolation for profile, server, conversation, message, cursor, proposal, and transaction data.
- Provisional desktop-v1alpha1 Rust types, TypeScript exports, ten JSON Schemas, drift checks, and two loopback-only Mock Gateway instances.
- Frontend, browser, Rust, integration, Windows provider, soak, and Forgejo CI test entry points.
- P00 dependency review and durable Spike result records.
- Persistent SQLite application-data initialization with transactional `user_version` migration and future-version rejection.
- Strict Zod validation for the Rust bootstrap IPC payload, including the active database schema version.
- Redacting tracing output writer with structured-field, bearer-token, URL-credential, private-key, and known-secret coverage.
- P01 migration, logging, IPC validation, real Tauri startup, and production-build verification.
- SQLite schema v2 for persistent non-sensitive ConnectionProfile metadata.
- Bounded Rust-owned Profile list/create/update/delete IPC with generated UUIDs and timestamps.
- Strict frontend ConnectionProfile Schemas and a basic Profile management UI.
- Migration, five-Profile CRUD, persistent reopen, secret-field rejection, and browser fallback tests.
- Persistent dual companion/operations slot assignment with SQLite schema v3 and bounded list/assign/clear IPC.
- Auto-connect configuration validation for at most two Profiles with distinct slots.
- Runtime operations switch guard that blocks operations slot changes while an operations task is active.
- Duplicate `server_instance_id` warnings without silently merging Profiles.
### Changed
- Adding a connection now asks for four things — server address, adapter id, API key, and slot —
with the rest behind a collapsed advanced section. The SSE URL and certificate fingerprint fields
were removed because nothing reads them, and the role field was removed because it follows the
chosen slot. The display name is derived from the identity and host unless set explicitly, and the
insecure-HTTP approval appears only for an `http://` address, where it is required.
- Choosing a slot in the connection form now assigns the slot and points startup auto-connect at it,
replacing a separate slot card interaction and a separate dropdown that could disagree.
- The API key is enrolled as part of saving a new connection instead of as a second step.
- Synchronized the 13-item roadmap status with the actual P02 implementation state.
- Documented external prerequisites for HTTPS certificate pinning, signed updates, and dual-server soak testing.
### Fixed
- Message action buttons render as borderless icons again. Their labels were being laid out inside
a 32px button, which wrapped them into vertical strips of single characters.
- The avatar sits beside its message bubble again instead of below it.
- Message actions can now be reached with the keyboard. They were hidden with `visibility`, which
removed them from the tab order, so the focus rule that reveals them could never fire.
- A failure to open the desktop pet's context menu is now reported instead of silently doing
nothing.
- The desktop pet appears when its display mode is set to floating. Switching modes closed the pet
by destroying its window, which forced every later open through a rebuild path that failed
outright; the pet window is now hidden and re-shown instead.
- The desktop pet no longer sits inside an opaque dark card when rendered inside the application.
- The desktop pet no longer appears as a solid dark rectangle before its assets finish loading. It
now has its own entry document, so the transparency rule applies before anything paints instead of
waiting on a lazily-imported chunk.
- The desktop pet no longer takes focus from the main window when it is shown, so keystrokes are no
longer delivered to a window with nothing to type into.
- The desktop pet is no longer pinned above every other window by default, and turning that off is
no longer undone the next time the pet is shown.
- The pet's monitor, position mode and always-on-top choices survive the pet being hidden and shown,
and the pet settings page now reflects what the window is actually doing rather than a fixed set
of defaults. They are not yet remembered across restarts.
- The desktop pet's animation now follows the connection again after the first time it is shown.
- The pet's context menu is anchored to a visible window again.
- One unreachable connection no longer freezes the whole application. The reachability probe now
runs outside the runtime lock, so a slot that is connecting cannot block status, sending,
cancelling or disconnecting on the other slot, and the attempt itself can be interrupted.
- An activation rejected during validation no longer tears down a working connection or leaves the
slot stuck in "connecting" with nothing to explain it.
- Switching a session while the slot is being reconnected no longer writes the old session id onto
the new connection, and no longer copies it into that profile's sticky session.
- One connection profile can no longer be activated into both slots at once, which previously let
the two slots overwrite each other's sticky session.
- Disconnecting or re-pointing the operations slot is now refused while an operations task is
active, matching the existing rule for slot assignment.
- A rejected chat send no longer leaves the question in local history without a failure marker, and
retrying no longer appends a second copy of it. A send that fails after AstrBot accepted it keeps
its question, since the remote conversation already has it.
- Streaming replies are no longer doubled in development. Event listeners that resolved after their
component had unmounted were never unregistered, so a leaked listener applied every delta twice.
- The composer draft, pending attachments, and the error banner are now per slot. An attachment
uploaded on the companion slot no longer follows the user to the operations slot, and an error
from one slot no longer appears on the other.
- An error from sending or uploading is no longer erased half a second later by the connection
status poll.
- Scoped AstrBot stream event ids per chat request so the second and later messages on a
connection are no longer discarded by the client-side event deduplicator.
- Accepted Rust `null` values in the runtime-event, remote-session, and model-option
frontend contracts, restoring streaming events, remote session lists, and file upload.
- Serialized AstrBot model options in camelCase to match the frontend contract.
- Allowed `blob:` images in the production Content Security Policy so chat attachments
render in release builds.
- Granted the desktop pet window a Tauri capability so its IPC and event listeners work.
- Corrected the pet pack manifest image pattern, which previously rejected every valid pack.
- Restricted rendered markdown links to http, https, and mailto and added `rel="noopener"`.
- Replaced `[object Object]` IPC error text with the message returned by Rust.
- Restored corrupted user-facing strings and an accessibility label in the pet view and shell.
- Long-lived event streams are no longer killed by a total request timeout. Streaming endpoints now
use a separate HTTP client with idle-based `read_timeout` detection, so a desktop-v1 connection
survives past 30 seconds and an AstrBot reply may take longer than two minutes.
- Chinese and other multi-byte text no longer turns into replacement characters when a character
straddles two network chunks; the SSE stream is now split into lines at the byte level.
- A chat message is no longer resent after AstrBot has started answering it, which previously
duplicated both the question and the answer in the remote conversation. A stream that breaks
mid-reply now reports a distinct error so it can be retried manually.
- A long reply no longer makes the rest of its slot report "not connected" while it streams, so
attachments, session lists, and capability lookups keep working during generation.
- Stopping generation, or losing the stream mid-reply, now finalizes the message. It could
previously stay marked as generating, including after a restart.
- Stopping generation no longer flickers the connection status to disconnected and back.
- Corrected a session-timestamp type and moved a link-safety helper out of a component module, both
of which broke the type and lint gates for the previous batch.
- Duplicate optimistic chat messages when switching sessions repeatedly.
### Security
- Kept credentials and native capabilities in Rust; the React capability set remains `core:default` only.
- Added secret redaction and repository scans; no arbitrary PowerShell, CMD, shell, input-injection, registry-write, or unrestricted filesystem API is exposed.
- Kept real UNC writes, signing keys, updater keys, and release secrets outside P00.
- Rejected Token, password, API Key, URL credential, query-string credential, and unknown fields at the Profile IPC boundary.
- Required explicit approval for insecure HTTP and kept slots, connections, and credential enrollment outside P01.
## [0.1.0-alpha.2] - 2026-07-20
### Added
- Q6-Q8 companion state, multi-monitor safe placement, read-only diagnostics, proactive-message handling, quiet hours, and Web Speech MVP.
- Q9 local session recovery marker and release validation checklist.
### Fixed
- Streaming chat history isolation and completed-message persistence across both slots.
- Tray exit, hidden-window cleanup, and release build packaging regressions.
### Notes
- This is an unsigned local Windows build. Automatic updates and code signing are not configured.