feat: ship twelve runnable framework helpers#17
Conversation
|
Strix is installed on this repository, but we couldn't run this PR security review because this workspace's trial has ended. Add a card to resume code reviews here. |
![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: ca7dd52d96
ℹ️ 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".
| trap 'rm -rf "$consumer_dir"' EXIT | ||
| python -m venv "$consumer_dir/venv" | ||
| "$consumer_dir/venv/bin/python" -m pip install --no-index --no-deps "$PWD/$wheel" | ||
| "$consumer_dir/venv/bin/python" -m helm_tool_wrapper.examples.framework_helpers |
There was a problem hiding this comment.
In the Python half of this package-assembly check, the venv invocation still runs from packages/python/helm_tool_wrapper, so Python puts the checkout on sys.path before the venv's site-packages. If the wheel is missing core files such as helm_tool_wrapper/boundary.py or otherwise contains stale installed code, python -m helm_tool_wrapper.examples.framework_helpers can pass by importing the source tree instead of the installed wheel; the JS half avoids this by changing into the temp consumer directory. Change to the temp consumer (or another directory outside the source tree) before running the module so this validates the wheel artifact.
Useful? React with 👍 / 👎.
1 participant
Summary
/api/v1/evaluaterequest contract through in-process transports and prove denied unknown-tool dispatch stays at zeronpm cifor repeatable dependency installsTruth boundary
These are deterministic simulated preflight/deny contract examples. They do not call a live Kernel or provider, dispatch an external effect, or create an EvidencePack; they do not close the CompanyArtifactGraph → GeneratedSpec → Kernel → EvidencePack objective.
Validation
make validatemake packageactionlint .github/workflows/helm-boundary-check.yml