Repository navigation
Conversation
This branch has not been deployed
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
Continues #89 after merged #90. Runs pinned Cognee
690c0ec023719a2a277dc893cdecfec1ca8012ccwith authentication and backend access control enabled, local default storage, and HTTP ingestion disabled.This slice deliberately does not overclaim
COMPLEMENT_PASS: it executes Cognee's pinned publictest_multi_tenant_access_control_e2e.pyas a bounded baseline and records onlyBASELINE_PASSwhen that real authenticated multi-tenant/dataset-isolation contract succeeds.Why this intermediate executable
During implementation I rejected an initially assumed upstream test path because it does not exist in the pin. The pin does contain a dedicated multi-tenant access-control E2E suite, so this PR uses that actual contract instead of inventing evidence.
A green result establishes that the candidate's real auth + backend ACL stack is executable in our bounded profile. It does not yet establish the normalized live A→B grant→revoke sequence or restart persistence.
Next slice after green
Build the Yukh-owned normalized public-API test on top of this working profile:
A owns M → B denied → grant B/read → fresh B reads → revoke B/read while A/B/M stay alive → fresh B denied → restart same storage → B remains denied and A remains allowed.
Related: #63, #77, #87, #88, #89, #90.