Prepare 1.7.9 with managed Jev, workspace routing, and graph fixes - #243
Conversation
…plans with included Jev System 1
…ting via engraphis_decide
…h offline evidence
… into codex/managed-jev-benefits-20260928
Coding-Dev-Tools
changed the title
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
1 similar comment
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Coding-Dev-Tools
changed the title
2 participants
This consolidates the reviewed Engraphis changes from PRs #238 through #243 into the 1.7.9 client candidate. It adds the consent-controlled managed Jev client and local decision safeguards, explicit project workspace routing and governed memory moves, graph cache and renderer fixes, provider compatibility, and Pi dependency repairs. Package, plugin, commercial manifest, and changelog versions are synchronized at 1.7.9.
The six original heads form one ancestry chain. The final head is
156150b09393e2e18b632096ec07fe331930d044; all 58 review threads are resolved. Its CI run 36833198797 passed all 26 jobs, including the offline suite, lint, typecheck, encryption, package installation, six installed journeys, browser accessibility, and Docker smoke. Both CodeQL analyses and every required main-branch context passed. The v128 source hash registry and skill checksums match the candidate.Main requires linear history, so this PR is the squash integration boundary for the complete stack. The parent PRs will be closed as superseded only after the resulting main tree is verified against the reviewed head. Publication remains subject to the protected release workflow and a current qualification for the selected source and distribution bytes; the older release-specific waivers do not cover 1.7.9.