172 行
13 KiB
Markdown
172 行
13 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
|
|
|
|
- Separate companion navigation for text chat, voice chat, and game companion. The game surface remains explicitly unavailable until Windows.Graphics.Capture has validated real DirectX/Vulkan frames.
|
|
- Screen-awareness implementation framework for scoped display consent, WGC capture, local privacy/quality gates, multimodal AstrBot validation, and low-interruption response control.
|
|
- WGC S0.1 target-binding preflight for authorized windows and attached displays. It returns metadata only; no capture session, pixels, disk write, or upload is performed.
|
|
- Bounded WGC S0.2 diagnostic readback for an already authorized window: one in-memory D3D11 frame, local blank-frame classification, and discarded PNG conversion metadata only.
|
|
- Per-session manual WGC acceptance action that displays only local frame-quality metadata and is structurally unable to upload or send an image.
|
|
- 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.
|
|
|
|
- Voice input records the microphone and sends the audio for AstrBot to transcribe. The previous
|
|
implementation called the browser speech API, which WebView2 does not provide, so it could never
|
|
have worked. Refused permission, a missing microphone, and a microphone held by another program are
|
|
now reported as three different things.
|
|
- Voice, file, and video attachments in a reply are now carried through and played or shown, instead
|
|
of being dropped without a marker, an event, or an error. A SILK-encoded voice message says that no
|
|
browser can play it rather than showing a player that does nothing.
|
|
- The companion can be shown one window the user authorizes: its text or its picture. Authorization is
|
|
per window, rate limited, revocable, and off until switched on; a banner shows while it is live.
|
|
|
|
### 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.
|
|
- Attachments now reach AstrBot. They were sent under a top-level `attachments` key that the server's
|
|
chat request does not declare, and unknown keys are ignored rather than rejected, so every
|
|
attachment was discarded in silence while the send reported success. They travel inside `message` as
|
|
segments now.
|
|
- A reply that arrives in several blocks keeps every block. The blocks were appended into one message
|
|
and then replaced wholesale by the final frame, so only whichever block that frame restated was
|
|
ever shown. A block that merely restates text already streamed is no longer shown twice.
|
|
- Streaming replies no longer break into one message per fragment when the server sends no message id
|
|
on the opening frames.
|
|
- An attachment download is now bounded while it runs rather than measured after being read in full.
|
|
- 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.
|