v0.7.3

Patch release: removes a hardcoded maintainer-specific Python path from two shipped scripts and replaces it with environment-derived conda discovery.

Fixed

• scripts/_python and skills/implement-review/scripts/health-check.ps1 no longer hardcode a miniforge3/envs/py312 interpreter path (#10). They ship in the package and tripped the release leak sweep. They now discover a conda/Miniforge interpreter from the environment (CONDA_PREFIX, then CONDA_ROOT, a resolvable conda/mamba launcher, and a $HOME conda-meta signature scan), with no hardcoded env name or install dir, before falling through to py -3 / python3 / python on PATH (WindowsApps shims skipped).

Changed

• _python interpreter preference is now environment-derived, not pinned to a py312 env. A hook or tool that relied on _python resolving a specific conda env (for example, one carrying an editable package) should set ANYWHERE_AGENTS_PYTHON to that env's interpreter; it is _python's explicit override, honored before any discovery.

Full changelog: v0.7.2...v0.7.3