On a machine where rustup has no default toolchain, tauri-cli calls
`cargo metadata` without specifying one and panics in its metadata thread
with no useful error — just an abort. The file lives at the project root
(not src-tauri/) because tauri-cli invokes cargo from there; rustup walks
up from the CWD, so the root copy is the one that gets picked up.
Also notes this in FORK.md so a future forker knows what they would hit
and why the file must exist.
The useful thing to hand someone is not what the code does - the README
and the spec cover that - but the constraints that cost time to find:
native view layering, why an inactive webview must not be hidden, why a
background page must not be told it is hidden, and the several APIs that
deadlock or silently return a fallback when called from the wrong thread.
Vincent Rozenberg
Vincent