CI Fix Commit Cleanup

[hazre]

Destination

A clean set of decisions showing exactly what to revert vs what to keep from the CI fix commits that followed the mise PR (#1202). Each decision is precise enough that 7w1 can use the spec to craft a clean-up PR.

Notes

• Domain: GitHub Actions CI/CD workflow cleanup for a Svelte/Tauri/Matrix chat app
• Skills: wayfinder -- this session only charts; it hands off for execution
• Standing preferences: Revert to mise-managed Rust for iOS; restore file task discovery; no mise-action in workflows that already use the setup composite action
• References: mise-action#215 (cache breaks Rust components), mise docs for file tasks

Decisions so far

Not yet specified

• mise-action cache bug in rust-quality.yml: mise-action#215 shows cache: true breaks Rust component installation (rustfmt, clippy won't be installed). Our rust-quality.yml uses cache: true. Scope: investigate and decide whether to disable cache, pin versions, or change approach.
• mise trust step necessity: The "Trust project mise configuration" step was added to setup/action.yml during the fix cycle. Was this actually needed for CI to work, or was it flailing? Needs correlation with the CI logs.
• Non-mise workflows' mise access: prepare-release.yml and release.yml have standalone jdx/mise-action steps (added during fix cycle). Original mise PR had none. These workflows need mise on PATH -- either keep the standalone action or upgrade to use the .github/actions/setup composite action.
• Dependabot cargo grouping corruption: The cargo ecosystem's tauri-family grouping was replaced with docker: * (line 69 of dependabot.yml). Needs investigation of when/how this happened and whether to revert.

Out of scope