2026-07-21 14:43:14 +08:00
|
|
|
{
|
|
|
|
|
"$schema": "https://schema.tauri.app/config/2",
|
|
|
|
|
"productName": "AstrBot Desktop",
|
|
|
|
|
"version": "0.1.0-alpha.2",
|
|
|
|
|
"identifier": "com.yokiirobw.astrbot-desktop",
|
|
|
|
|
"build": {
|
|
|
|
|
"beforeDevCommand": "npm run dev",
|
|
|
|
|
"devUrl": "http://127.0.0.1:1420",
|
|
|
|
|
"beforeBuildCommand": "npm run build",
|
|
|
|
|
"frontendDist": "../dist"
|
|
|
|
|
},
|
|
|
|
|
"app": {
|
|
|
|
|
"windows": [
|
|
|
|
|
{
|
|
|
|
|
"label": "main",
|
|
|
|
|
"title": "AstrBot Desktop",
|
|
|
|
|
"width": 1100,
|
|
|
|
|
"height": 760,
|
|
|
|
|
"minWidth": 720,
|
|
|
|
|
"minHeight": 520,
|
|
|
|
|
"center": true,
|
|
|
|
|
"resizable": true,
|
|
|
|
|
"decorations": false,
|
|
|
|
|
"shadow": false
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"label": "desktop-pet",
|
|
|
|
|
"title": "AstrBot Pet",
|
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
|
|
|
"url": "pet.html",
|
2026-07-21 14:43:14 +08:00
|
|
|
"width": 180,
|
|
|
|
|
"height": 220,
|
|
|
|
|
"resizable": false,
|
|
|
|
|
"decorations": false,
|
|
|
|
|
"shadow": false,
|
|
|
|
|
"transparent": true,
|
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
|
|
|
"alwaysOnTop": false,
|
|
|
|
|
"focus": false,
|
2026-07-21 14:43:14 +08:00
|
|
|
"skipTaskbar": true,
|
|
|
|
|
"visible": false,
|
|
|
|
|
"x": 120,
|
|
|
|
|
"y": 120,
|
|
|
|
|
"create": true
|
|
|
|
|
}
|
|
|
|
|
],
|
|
|
|
|
"security": {
|
2026-07-26 22:28:35 +08:00
|
|
|
"csp": "default-src \u0027self\u0027; connect-src ipc: http://ipc.localhost http://127.0.0.1:*; img-src \u0027self\u0027 asset: http://asset.localhost data: blob:; style-src \u0027self\u0027 \u0027unsafe-inline\u0027; script-src \u0027self\u0027"
|
2026-07-21 14:43:14 +08:00
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"bundle": {
|
|
|
|
|
"active": true,
|
|
|
|
|
"targets": ["nsis"],
|
|
|
|
|
"icon": [
|
|
|
|
|
"icons/32x32.png",
|
|
|
|
|
"icons/128x128.png",
|
|
|
|
|
"icons/128x128@2x.png",
|
|
|
|
|
"icons/icon.ico"
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
}
|