Repository navigation
greenproof 0.4.1
Install: uvx greenproof@0.4.1 --version or pipx install greenproof==0.4.1 (PyPI).
Fixed
initno longer writes hooks that point at an ephemeral environment. Run as
uvx greenproof init(orpipx run, or from a project venv that is only active in the
current shell), it found its own copy ofgreenproofon PATH and wrote the bare command into
the hook files; the agent's PATH does not have that copy, so the hook failed open. The
scripts directory of a virtual environment the running interpreter is in is now skipped when
looking for an installedgreenproof; apipx installoruv tool installsymlink in
~/.local/binstill counts. When none is found the hooks useuvx greenproof@Xas before,
and the summary says so and how to install it.- The AGENTS.md section named the command to run as bare
greenproof checkwhenever
--hook-commandwas not given, even when the hooks useduvx greenproof@X. It now names the
command the hooks use. - The workflow written by
init --ci githubinstalled nothing for a plain-pip Python project
(a pyproject,setup.pyorsetup.cfgwithoutrequirements.txt) or for npm without a
lockfile, sopython -m pytestran without pytest or the package, andnpm testwithout
node_modules. When the policy has nosetupcommand it now adds apython -m pip install
step (the package with itstest,tests,testingordevextra, the requirements files
for development and test, and the pytest, ruff, mypy or pyright the policy runs) and an
npm installstep. The step is in the workflow only:setupalso runs in--isolate
worktrees, wherepip install -e .would point your own environment at a temporary directory.
For a project with asrc/directory the run step also setsPYTHONPATH: src, so the revert
check's base worktree imports its ownsrc/and not the editable install of the checkout.
Changed
- Documentation only, no behaviour beyond the fixes above. README and SPEC describe the new hook
command rule, the AGENTS.md command and the CI install step,PYTHONPATH: srcincluded, and
thatinitadds an@AGENTS.mdimport to an existingCLAUDE.md. They also correct the
smoke key rule (some keys but not all is a policy error, exit 4), the OpenCode timeouts
(3600 s for the check, 120 s for session start), the claim that a Pythonparametrizefold
is blocked when its body ignores the row values (it warns), wheresetupruns (ci mode,
--isolateand revert worktrees), and theopencodechoices of--agentsand--hook.
The README quick-start output is re-run on 0.4.1. - README notes that a uv
exclude-newersetting keepsuvx greenproof@Xfrom resolving for
new releases, souvxhooks fail open until the release ages past the window. - SPEC marks each item of "Known limits (0.3.0)" as closed, narrowed or still open in 0.4.0.
MEASUREMENTS labels the 0.2.0 real-history section and marks the false blocks 0.4.0 no
longer blocks.
Full changelog: v0.4.0...v0.4.1