Tauri Knowledge Patch

Apply the patch

Inspect tauri.conf.json, Cargo.toml, capability files, plugin permissions, and the frontend API imports before changing code.
Identify whether the work concerns migration, configuration, windows/webviews, IPC, security, plugin development, a core plugin, or the experimental runtime.
Read every matching reference from the index; cross-cutting work commonly needs both the configuration and security references.
Keep platform branches explicit. Many window, filesystem, installer, and mobile APIs are target-specific.
Validate capability grants and scope enforcement separately: permission to invoke a command does not make its scoped arguments safe.

For an application migration, read the migration, configuration, windows/webviews, and capabilities references together.
For a new command, read the IPC and capabilities references; add the plugin reference when the command is plugin-owned.
For mobile-native work, read the plugin reference plus the relevant configuration, filesystem, or window section.
For release packaging, read configuration/distribution and the updater section of the core-plugin reference.
For runtime replacement, read the Verso boundary before assuming ordinary Wry behavior is available.