Refresh agent compatibility and align Eve setup - #75
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New Eve setup now generates the same canonical MDevolved connection shown in the dashboard and documentation. Existing legacy connections remain supported. Refresh the reviewed Eve/Connect dependencies and Hermes, OpenClaw, Gemini CLI, and Copilot compatibility records; update the README with available setup paths and links to dated evidence.
The compatibility review found no required transport or archive-layout changes. Copilot evidence is release/documentation based; no live vendor certification is claimed. Eve 0.66.2 remains deferred, and larger framework/sync upgrades are outside this release.
Validation on the candidate: full repository checks, migration tests, unit/Worker/package tests, desktop and narrow browser tests, production build, Community and marketing deployment dry-runs, dependency audit, and public-source/history scan. The earlier independent review found the Eve naming mismatch; this candidate repairs it and covers the generated module and displayed path in tests.
No new migrations, resources, or npm publication. The existing alpha Worker was deployed using its legacy configuration after merge
79abfc3; rollback remains the preceding Worker version. Post-deploy health passed, the public frontend bundle matched the tested local build byte-for-byte, and canonical Eve setup was present. The marketing website was reachable and required no content deployment. Production resource identifiers remain outside this public receipt.Full local gate passed, including 23 migration tests, 565 core tests, package suites, and all 80 browser tests. PR and post-merge main CI and macOS/Linux/Windows checks all passed. The merged tree exactly matched candidate
c9b6a55.