Add cloud storage ids for projects

[iterion]

If we upload the KCL, we want to keep track of that so we can easily update the project again in the future.

What is getting added?

To account for our internal usage of multiple environments, we track cloud project id per environment:

[cloud."zoo.dev"]
project_id = "<uuid>"

[cloud."dev.zoo.dev"]
project_id = "<uuid>"

Most folks will only ever interact with one environment, but for us, that's a pretty common use case. Because of this, we want to make sure that our way of working is not impacted, insofar as we can upload/download from any environment.

Why not reuse meta.id?

meta.id is a locally generated id and it serves as a good artifact of that local or shared lineage. None of our APIs currently accept customer generated ids, and we do that so the API remains the source of truth. Because these are IDs in our database it should be in charge of issuing valid values.

For now, we accept that this could lead to some drift between environments.

Not in scope for this PR

• automatic reconciliation between environments
• automatic merge behavior when the same local meta.id appears in multiple places
• sample upload to projects

Expected workflow from ZDS/CLI

flowchart TD
      subgraph ZDS[ZDS]
          A[User clicks Share / Upload]
          B[Read local project.toml]
          C[Determine active API environment]
          D{cloud.env.project_id present?}
          E[Choose Create request]
          F[Choose Update request]
          G[Write cloud.env.project_id to project.toml]
          H[Leave other cloud.other-env bindings unchanged]
      end

      subgraph API[API]
          I[Receive create request]
          J[Upload current project files]
          K[Create DB record in active environment]
          L[Return success + remote project_id]

          M[Receive update request]
          N[Upload current project files]
          O[Update DB record for existing remote project_id]
          P[Return success]
      end

      A --> B
      B --> C
      C --> D

      D -- No --> E
      E --> I
      I --> J
      J --> K
      K --> L
      L --> G
      G --> H

      D -- Yes --> F
      F --> M
      M --> N
      N --> O
      O --> P
      P --> H

Loading

Relates to https://github.com/KittyCAD/roadmap/issues/296
Prereq for #10903

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
modeling-app	Ready	Preview, Comment	Apr 9, 2026 1:31pm

[codspeed-hq]

Merging this PR will not alter performance

✅ 167 untouched benchmarks
⏩ 93 skipped benchmarks¹

---

_{Comparing push-nrzrlxzxrtzm (e24228a) with main (78ae4c6)}

Footnotes

1. 93 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[iterion]

This never existed in the schema, so I'm not sure where it's coming from. This came from regenerating docs locally.

[lee-at-zoo-corp]

automatic merge behavior when the same local meta.id appears in multiple places

Maybe even preferable to never do it, since meta.id is user controlled!