Skip to content

feat(files): Project file browser and Mothership integration - #9034

Draft
mzxchandra wants to merge 2 commits into
stagingfrom
codex/project-files-product-v2
Draft

mzxchandra wants to merge 2 commits into
stagingfrom
codex/project-files-product-v2

Conversation

@mzxchandra

Copy link
Copy Markdown
Contributor

Summary

Companion: simstudioai/mothership#594

Keep both companions draft pending paired validation and coordinated rollout. No deployment or activation is included.

Type of Change

  • New feature

Testing

  • 34 focused disposable PostgreSQL integration checks passed after integration with staging: Project access, copy callbacks, immutable selections, native reads, secret handling, and workbench writes.
  • 16 focused browser tests and 75 CLI/transport/resource tests passed; scoped production TypeScript and API validation passed.
  • Full repository validation runs in hosted CI. Physical E2B/Daytona acceptance remains separate and is not established by these local tests.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Focused tests added/updated and passing
  • Hosted CI completed
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercel Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Oct 15, 2026 4:43am UTC

Request Review

@mzxchandra
mzxchandra force-pushed the codex/project-files-product-v2 branch from dc1b9e6 to d66d69d Compare October 15, 2026 04:23
@github-actions github-actions Bot added the requires-mothership-merge Has a companion PR on the mothership/copilot side — merge in lockstep label Oct 15, 2026
@github-actions

Copy link
Copy Markdown

⚠️ Cross-repo companion check

One or more companion PRs aren't merged into staging yet. Merging this without them will leave copilot and sim out of sync — merge them in lockstep.

  • ❌ simstudioai/mothership#594 — OPEN, not merged (targets staging) — Support explicit file owners and Project files in the worker

- Keep prepareProjectsForAccountDeletion returning the Project IDs to delete.
  The object return added an unused storageCleanupEventIds field; the
  durable cleanup outbox already processes those events, so restore the
  staging contract and its stronger integration assertions.
- Exempt lib/mothership/generated from the relative-import convention.
  contracts:sync copies those wire contracts verbatim and byte-checks them,
  so their sibling imports must stay relative; drop their baseline rows.
- Re-record the files page module-count baseline for the Project browser.
- Type the test fixtures that regressed, including a queue-recovery
  fixture that persisted the invalid completion status 'success'.

This branch was successfully deployed

1 active deployment
Preview — ecffcbbe Deployed Oct 15, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

requires-mothership-merge Has a companion PR on the mothership/copilot side — merge in lockstep

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant