Repository navigation
feat(memory): authorize scoped note access and durable cleanup - #9096
Conversation
Rename the scoped-note control kind from memory_access to memory_notes_access so it is distinct from graph memory_scope. The HTTP path, delegation audience sim:memory-access, and semantic operation id are unchanged.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
|
@cubic review |
@mzxchandra I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
All reported issues were addressed across 18 files
Reply with feedback, questions, or to request a fix.
Turn on auto-fix | Re-trigger cubic
[Critical impact] The PR appears safe to merge, with no new actionable issues in the latest changes. SummaryAdds live access checks for personal, workspace, and Project notes, removes memory payloads from chat exports, and queues cleanup during account deletion.
|
…port rule contracts:sync copies these files byte for byte from the worker, whose sibling imports are relative, so they cannot use the app's aliases. Exempt only files in lib/mothership/generated that carry the sync header, and drop their baseline entries.
|
@cubic-dev-ai review this PR |
@mzxchandra I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
All reported issues were addressed across 21 files
Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.
Turn on auto-fix | Re-trigger cubic
…skip keyless cleanup Project note checks took the Project lock exclusively while already holding it shared, so overlapping workspace checks could deadlock; they now read under the shared Project lock and the permission-group read lock, as Project Files does. Exports also redact remember calls stored in the legacy top-level toolCalls list. A Sim without COPILOT_API_KEY never reached a worker, so it queues no memory cleanup it could not deliver.
|
@cubic-dev-ai review this PR |
@mzxchandra I have started the AI code review. It will take a few minutes to complete. |
|
@cubic-dev-ai review this PR |
@mzxchandra I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 22 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
You've manually re-run cubic several times on this PR. Each manual re-review checks the full PR again and counts toward your usage quota. To preserve your usage limits, we recommend letting cubic automatically review new commits.
Turn on auto-fix | Re-trigger cubic
Summary
POST /api/mothership/memories/access) and checkpoint transport (memory_notes_accesscontrol).currentProject: null.rememberpayloads from chat exports and queue durable cleanup when an account, workspace, or Project is physically deleted.memory_scopecontract and eligibility; both operations share the existing owned-chat and authorized-use-case infrastructure.Rollout
projectsflag; there is no memory-specific flag.Type of Change
Testing
resolve-access.integration.ts,cleanup.integration.ts): both transports, Projects on/off/on, read-only private writes, Project Files capability on shared writes, cross-organization denial, detach, cleanup rollback and retry.memory_scoperegression tests.git diff --check.check:contract-syncpasses against this branch (canonicalmemory-notes-access.tsandsim-transport.tsbyte-identical).Checklist
Companion PRs