Repository navigation
feat: establish shared file ownership foundation - #8609
mzxchandra wants to merge 12 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Add canonical entity ownership while preserving legacy workspace writers. Make storage accounting, lifecycle cleanup, search, document artifacts, and realtime transport tolerate project-owned data before feature activation. Keep Project file user/API/tool entry points in the stacked feature change.
9a1af75 to
6f8882e
Compare
|
@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. |
|
@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 191 files
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Turn on auto-fix | Re-trigger cubic
|
@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 191 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
workspace_idandorganization_idand gain a nullableproject_idFK; a database check permits at most one owner. Existing personal/chat attachments may have none, with their access and lifecycle unchanged.entityType/entityIdinterface above storage. Native FKs enforce parent existence and concurrent deletion; shared directory locks and domain guards cover folders, history, creator attribution, billing and cleanup. Search/share owner pairs derive from canonical FK columns.db:pushalso installs the file-integrity functions and triggers. Project file endpoints and UI arrive in feat: add shared Project files #8610.Stacked on #8590; #8580 has merged. Project Files #8610 targets this branch and pairs with Mothership #594.
Rollout and rollback
Deploy the foundation and verify retirement of incompatible app/realtime tasks and worker jobs before enabling Project files. Traffic cutover alone is insufficient. The feature remains disabled by default in the follow-up. Earlier draft migrations ran only on disposable databases and were replaced before release.
This foundation is the compatible rollback target once Project files exist: Project UI access is unavailable, while accounting and lifecycle consumers continue handling those rows.
Type of Change
Testing
Checklist