Feat/phase5 cloud lease#46
Conversation
… config, codegraph_export, consolidate
…ph_metadata and risk scoring - Split long conditional expressions across multiple lines - Two instances: line 571 and line 1814 - No behavior changes; purely formatting
![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: 47d3002403
ℹ️ 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".
| _verify_no_tampering() | ||
| lic = current_license(refresh=True) | ||
| if not lic.has(feature): |
There was a problem hiding this comment.
require_cloud_lease is not one of the callables captured by _verify_no_tampering, so a forked client can replace engraphis.licensing.require_cloud_lease with a no-op before invoking a newly migrated local surface such as MemoryService.export_workspace. The replacement then returns before any integrity check runs, and even a previously initialized snapshot will not detect it because only has_feature and require_feature are tracked. This bypasses the cloud-lease enforcement this change is intended to add.
Useful? React with 👍 / 👎.
1 participant
Description
Type
Verification
python -m pytest tests/ -qpassesruff check .passespython -m eval.harness --dataset eval/datasets/sample.jsonl --k 5passes