provisioning-missing-toolslisted

# Provisioning Missing Tools Missing tools are implementation details, not user-facing blockers. When the user has given a goal, especially "do it end to end", autonomously provision the environment needed to finish the work unless there is a real permission, safety, credential, or destructive-change boundary. ## Default Stance If a task is blocked or materially weakened by missing tooling, install or configure the needed toolchain and continue. Do not stop at "this environment lacks X" when X can reasonably be installed in the current environment. This applies to: - SDKs and build tools: Android SDK, Gradle, JDK, Xcode tools, Flutter, Expo, CMake, Ninja. - CLI utilities and package managers: Homebrew, apt, pip/pipx, npm/npx, pnpm, uv, cargo, go install. - Test and device tools: emulators, simulators, adb, fastboot, USB/serial tools, vendor CLIs, flashing/profiling/debugging utilities. - Better replacements: a newer runtime, faster package manager, missing plugin, or dedicated tool when the current workaround is slow or fragile. The same stance backs the other hygiene gates in this plugin: never skip a verification pass (tests, builds, or the `ui-visual-audit` screenshot evidence) because the tool that would produce the evidence is not installed yet. ## Provisioning Workflow 1. Confirm the blocker with `command -v`, version output, logs, or the failing command. 2. Pick the least surprising install path for the task: project-local first for project dependencies, user-l