feat(recursive_lean_prover): 0.2.0

[futrime]

What this adds

recursive_lean_prover 0.2.0 (release, humanfia/recursive-lean-prover-flow#5, #6 and #7): recursively plan, prove, compare, review and catalogue Lean theorems.

What changed from 0.1.2: the flow passes the env to Agent.run(prompt, session=, env=), not to spawn() and fork(), as hmz takes it since humanfia/humanize#229, and the humanize1 range is now >=0.2.0,<0.3.0: humanize1 0.1.x still passes the env to spawn() and fork(), and 0.2.0 (#58) is the first that does not. Its contract test runs against humanize1-flow v0.2.0.

Because dependencies changes, this is not a pure version bump and automerge should decline it; a maintainer merges it.

Checklist

• This pull request adds exactly one version of one flow: flows/recursive_lean_prover/0.2.0/flow.yaml (a humanfia flow, listed by name alone).
• I wrote the flow or maintain it, or its author agreed to it being listed.
• The repository is public, and the version's tag is pushed.
• commit is the full commit the tag points at.
• I ran the flow with hmz at that commit, and its tests pass.
• The repository has a license, and license names it.
• uv run .github/scripts/validate.py --base origin/main --network passes.
• I read the code of conduct.

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

Not merged automatically; a maintainer will review it, as

• recursive_lean_prover 0.2.0 changes dependencies from 0.1.2

Only a pull request that adds new versions of flows already listed, each newer than every version listed and the same as the newest but for version, ref and commit, is merged without review once every job of validate passes: see Review and merge.