Promote staging to main

[BWJ2310]

Summary

• Promote the current staging branch to main
• Roll up the three staged changes already merged on staging:
  • Tools import export (Tools import export #56): unified import/export envelope and workflow snapshot updates
  • feat(admin): add admin panel with billing, SSO, registration, and integration management (feat(admin): add admin panel with billing, SSO, registration, and integration management #57): admin, billing, SSO, registration, integrations, and CI image publishing
  • refactor(copilot): rework tooling, streaming, and platform plumbing (refactor(copilot): rework tooling, streaming, and platform plumbing #58): Copilot/tooling/streaming/workflow plumbing, auth and billing hardening, docs updates, and platform cleanup

Why

staging currently contains the release candidate changes that are not yet on main. This PR promotes the vetted branch state to production and keeps review focused on the exact staged rollup rather than reopening the individual feature branches.

Affected Areas

• apps/tradinggoose
• apps/docs
• packages/*
• Workflows / execution
• Realtime / sockets
• Market data / charting
• Dev tooling / CI / infra
• Documentation only
• Other: admin, billing, auth/SSO, import/export, copilot

Issue Links( if any )

• Rolls up Tools import export #56, feat(admin): add admin panel with billing, SSO, registration, and integration management #57, and refactor(copilot): rework tooling, streaming, and platform plumbing #58

Validation

git fetch origin main staging
git log --oneline origin/main..staging
git diff --stat origin/main...staging

• Confirmed staging is clean, pushed, and there is no existing open staging -> main PR.
• No additional local code validation was re-run in this PR-cutting session; prior validation lives in Tools import export #56, feat(admin): add admin panel with billing, SSO, registration, and integration management #57, and refactor(copilot): rework tooling, streaming, and platform plumbing #58. Reviewers should rely on CI for the aggregate branch state.

Risk / Rollout Notes

• This is a multi-area release promotion. Main rollout considerations are the combined migrations, admin/billing/auth changes, and the Copilot/workflow plumbing updates already reviewed in the child PRs.
• Database migrations 0018 through 0026 are present on staging; deployment must apply them before serving new code.
• Billing, Stripe, OAuth/SSO, and provider configuration changes should be confirmed in the target environment before merge or deploy.
• Backout: revert the merge commit or roll back to the previous main deployment if a regression appears after promotion.

Config / Data Changes

• Env vars added or changed: apps/tradinggoose/.env.example changed on staging; confirm release env matches the new billing, provider, and auth expectations.
• Database schema or migration impact: packages/db/migrations/0018 through 0026 are included on the branch.
• External services or provider behavior changed: admin-managed integrations and SSO, billing and Stripe behavior, and Copilot/provider routing changed across the rolled-up PRs.

Screenshots / Video

• See feat(admin): add admin panel with billing, SSO, registration, and integration management #57 for admin UI screenshots. Additional UI changes are distributed across Tools import export #56 and refactor(copilot): rework tooling, streaming, and platform plumbing #58.

Checklist

• I kept the change focused and reviewed my own diff
• I validated the change locally and documented the results above
• I updated docs, examples, or copy if behavior/user-facing flows changed
• I called out any env, schema, provider, or rollout impact
• I did not include secrets, tokens, or private credentials in this PR

[greptile-apps]

Too many files changed for review. (1028 files found, 500 file limit)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
studio	Ready	Preview, Comment	Apr 19, 2026 5:52pm