Add Dify compatibility contract checks#3
Open
awxxxxxx wants to merge 1 commit into
Open
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
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.
Summary
Adds repo-local contract tests and CI for the mem9 Dify plugin.
This PR covers the plugin-upgrade side. The main mem9 compatibility workflow can now checkout this repo with
plugin_refand run Dify contract checks as part of the cross-agent matrix.What changed
.github/workflows/compat-checks.yml.tests/test_contract.pywith a stubbed Dify runtime so tests do not need a live Dify server.What the tests cover
X-API-KeyandX-Mnemo-Agent-Id.memory_searchsends expected headers and params, includingsession_id,scanAll, and upstreamlimit * 3.memory_storesends smart ingest payload withmessages[],agent_id,mode=smart, andsession_id.How this relates to mem9 main
The main
mem9repo PR adds:Dify does not currently have a real headless host smoke lane in the same way as OpenClaw/Hermes/Claude/OpenCode/Codex, so the blocking gate is the plugin contract suite. The main workflow still includes Dify in
agent=allplugin/full matrices.GitHub Action usage from mem9 main
Dify plugin upgrade check:
Full matrix check:
Verified locally
Result:
5 passed.