Clarify StateLease verifier installation - #7
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a280b9f7e5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| python -m pip install . | ||
| recurquant verify-statelease-stage-a evidence/experiment012-statelease-stage-a-666.json |
There was a problem hiding this comment.
These commands do not isolate or connect the installation and executable: on systems where python is not Python 3.11+, global pip is disabled, or an older recurquant is already earlier on PATH, the sequence either fails during installation or invokes the v0.2.0a1 executable that lacks this subcommand. Create a venv with the supported interpreter and invoke its platform-specific recurquant path, as the Quickstart does, so the newly installed verifier is guaranteed to run.
Useful? React with 👍 / 👎.
1 participant
The public README installed the v0.2.0a1 tag, then later suggested a verifier that was added after that release. This separates the two paths and gives an explicit main-branch checkout for the StateLease artifact verifier.\n\nVerified locally: README asset verifier, local links, 22 focused tests, Ruff, and git diff --check.