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
{{ message }}
Repository navigation
Commit 3c4e46a
Browse filesBrowse the repository at this point in the historyBrowse files
fix(pet): load user pet spritesheets through the host and keep the pet above the app window
Pet spritesheets never resolved (#3370). The webview read them with the
filesystem plugin, whose scope requires a literal leading dot on unix while
every XDG directory starts with one, so the read always failed with
`forbidden path`. The host now serves the bytes through
`load_agent_companion_pet_spritesheet`, confined to the managed companion
directory: the request is canonicalized, must stay under that root (symlink
escapes are rejected), must be a regular file, and is capped at 16 MiB. The
filesystem-plugin scope keeps its dot-literal default instead of being widened
to every hidden path under the home directory.
The desktop pet disappeared behind the app's own page. Wayland compositors drop
GTK's keep-above request, so the only stacking relationship the platform still
guarantees is "above its parent": the pet window is now a GTK transient of the
main window on Linux, and both show paths re-assert always-on-top so X11 keeps
floating it above other applications too.
Remote scenarios exercised: none. Both changes stay controller-local
(`load_agent_companion_pet_spritesheet` is registered as LocalOnly /
ControllerLocal / REFUSED).
Docs, website, search, and agents see only features, settings, and documented sub-capabilities. Every sub-capability must reference a registered Tauri command or a resolvable source marker; evidence is stripped from public projections. The **692** Tauri commands remain implementation-audit evidence only. Product UI interaction sources are scanned and validated during generation and checks, but are not stored as a versioned snapshot that churns with ordinary UI changes.
32
+
Docs, website, search, and agents see only features, settings, and documented sub-capabilities. Every sub-capability must reference a registered Tauri command or a resolvable source marker; evidence is stripped from public projections. The **693** Tauri commands remain implementation-audit evidence only. Product UI interaction sources are scanned and validated during generation and checks, but are not stored as a versioned snapshot that churns with ordinary UI changes.
0 commit comments