fix: CI release failures — commit Cargo.lock + add permissions

[proofofprints]

Summary

Fixes both issues that caused all 4 release builds to fail on the v1.0.0 tag push.

Issue 1: Cargo.lock was gitignored (macOS + Linux + Windows build failures)

Error: windows-future 0.2.1 failed to compile with cannot find type IMarshal in module windows_core::imp

Root cause: Cargo.lock was in .gitignore, so CI resolved fresh dependency versions from scratch every build. The latest resolved combination of windows-future, windows-core, and windows-sys had a breaking incompatibility. Your local build worked because your local Cargo.lock pinned compatible versions.

Fix: Remove Cargo.lock from .gitignore and commit the working lockfile (6893 lines pinning all transitive deps). This is the recommended practice for binary crates — only library crates should gitignore their lockfile.

Issue 2: Missing permissions (Windows build failure)

Error: Resource not accessible by integration - https://docs.github.com/rest/releases/releases#create-a-release

Root cause: The tauri-apps/tauri-action step needs to create a GitHub release via the REST API, but the workflow's GITHUB_TOKEN defaulted to read-only permissions.

Fix: Add top-level permissions: contents: write to release.yml.

After merge

Delete the failed v1.0.0 tag and re-tag:

git tag -d v1.0.0
git push origin :refs/tags/v1.0.0
git checkout main && git pull
git tag v1.0.0
git push --tags

This will trigger a fresh release build with the lockfile and correct permissions.

Files changed

.gitignore                     | -1 (removed Cargo.lock line)
.github/workflows/release.yml | +3 (added permissions block)
src-tauri/Cargo.lock           | +6893 (NEW — committed from local working state)