Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. For privacy information, see our Privacy Notice. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA behalf on myself, e-mail: example@example.com

or

I have read the CLA Document and I hereby sign the CLA behalf of my company, e-mail: example@example.com

Signature is valid for 6 months.

0 out of 2 committers have signed the CLA.
❌ @nandanadileep
❌ @cursoragent
nandanadileep seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{This bot will be retriggered when the Contributor License Agreement comment has been provided. Posted by the CLA Assistant Lite bot.}

AI-assisted source review of 92ddb3d; I have not executed these paths.

The newly wired facade appears to break the fallback contract for four existing hooks: remove_communities, node_get_by_names, saga_get_previous_episode_uuid, and saga_get_episode_contents. They are absent from _METHOD_MAP, so __getattr__ raises AttributeError, whereas their callers catch only NotImplementedError.

The effects are specific:

• remove_communities cannot reach its existing graph_ops fallback, so Graphiti.build_communities fails during its initial clearing step.
• The two saga hooks raise instead of running the previous-episode query or returning None to let summarization use its query fallback.
• EntityNode.get_by_names raises instead of reaching its query fallback. Its ingestion caller catches that error and falls back to semantic search, losing the exact-name candidates.

Could unsupported hooks preserve the NotImplementedError contract, or receive explicit delegation? Facade-backed caller regressions should assert the fallback delegate/query is actually reached and its results are preserved, including the saga None sentinel and the subsequent summarization query. That would exercise more than facade construction and the one episodic routing call currently added.

Please also select the existing tests/driver/test_falkordb_ops_routing.py module in CI: unit_tests.yml excludes tests/driver/ from the no-database job, while the database job names only test_falkordb_driver.py from that directory. Neither selection includes the two appended regressions.

AI-assisted source re-review of 7ad3fb7; I have not run tests.

The async NotImplementedError hooks, facade-backed caller regressions, and updated no-database test selection address the four fallback paths and CI-selection gap raised in my earlier comment. The tests now exercise the community delegate, exact-name query, previous-episode result, and saga None sentinel followed by the summarization query.

Runtime validation is still pending: the Tests run for this head remains action_required.

@galshubeli this FalkorDB-related PR currently has no review/comments from the FalkorDB team. Please take a look when possible.