helm-asclisted

# `helm-asc` Use `helm-asc` instead of ad-hoc App Store Connect scripting whenever the requested workflow already exists in the CLI. ## Setup Resolve the CLI once before the first command: 1. Prefer `command -v helm-asc`. 2. If that fails, try common symlink locations: `/opt/homebrew/bin/helm-asc` and `/usr/local/bin/helm-asc`. 3. If those fail, try the bundled app helper: `/Applications/Helm.app/Contents/Helpers/helm-asc` and `~/Applications/Helm.app/Contents/Helpers/helm-asc`. 4. If any candidate exists and is executable, use that path for all Helm CLI commands in this session. The agent shell may have a different `PATH` than the user's Terminal. 5. Only after all candidates fail, stop and point the user to **Helm Preferences -> Helm CLI** to install or repair the command line tool. In examples below, `helm-asc` means the resolved CLI command. If setup resolved an absolute path, substitute that absolute path anywhere an example starts with `helm-asc`. ## Start here - If the workflow is obvious, run the direct command immediately with `--agent`. - If the command branch is unclear, inspect only the nearest help path, such as `helm-asc apps --help`, `helm-asc version --help`, `helm-asc build --help`, `helm-asc review --help`, `helm-asc submission --help`, `helm-asc localization --help`, `helm-asc inAppPurchase --help`, `helm-asc subscription --help`, `helm-asc testFlightGroup --help`, or `helm-asc apps <app-id> testFlightGroupAliases --help`. - Keep each shell command s