Skip to content

improvement(mothership): v0.2#4923

Merged
Sg312 merged 301 commits into
stagingfrom
dev
Jun 9, 2026
Merged

improvement(mothership): v0.2#4923
Sg312 merged 301 commits into
stagingfrom
dev

Conversation

@Sg312

@Sg312 Sg312 commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

Mothership improvements

Type of Change

  • Improvement

Testing

Manual

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

icecrasher321 and others added 30 commits May 7, 2026 01:05
v0.6.72: billing pool contention fix
…personation fixes, md rendering, doc/pdf/pptx generation improvements
…pentelemetry updates, data drains to snowflake, blob, datadog, bigquery
…ip md polish

v0.6.75: scheduler claim-budget drain, helm chart hardening, mothership md polish
v0.6.78: file block get
fix(migrations): remove duplicate column add (fix(migrations): remove duplicate column addition #4632)
v0.6.83: redis TLS SNI override for IP-based REDIS_URL, zod schema fixes
…s trimmed

v0.6.84: redis pub/sub SNI override, security hardening, copilot reads trimmed
…il integrations, markdown google docs creation
…oogle slides endpoints, DB access pattern improvements
…er, search & replace UX, kb connectors multi-select, mcp negative cache
icecrasher321 and others added 12 commits June 8, 2026 17:28
Drop migration 0228 and its metadata so it can be regenerated after merging staging.

Co-authored-by: Cursor <cursoragent@cursor.com>
Merge the latest staging branch after removing the stale local 0228 migration, then regenerate the branch migration on top of staging's migration chain.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Resolve copilot table tooling conflicts:
- materialize-file.ts: keep dev removal of dead executeTable (table ops routed to subagent)
- user-table.ts update_row: combine staging name->id mapping with dev actorUserId tracking

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented Jun 9, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jun 9, 2026 8:29pm

Request Review

@cursor

cursor Bot commented Jun 9, 2026

Copy link
Copy Markdown

PR Summary

High Risk
Touches payment ledger semantics (update-cost cumulative billing), copilot preflight gates, and BYOK entitlement checks—errors could block chat, mis-attribute cost, or allow/deny keys incorrectly.

Overview
This PR tightens hosted billing and workspace attribution end-to-end: internal update-cost now requires workspaceId and bills Go flushes as a monotonic cumulative top-up (replacing the prior idempotency-claim flow), with new tests for duplicates and partial flushes. Per-member org credit caps are enforced at copilot API-key validation, exposed via org-admin and self-serve member-credit APIs, and wired into voice/STT, guardrails, and knowledge paths through checkActorUsageLimits plus workspaceId on usage records. Table and import flows pass actorUserId / triggeredByUserId so metered work ties to the acting user.

Mothership v0.2 shifts execute payloads toward buildUserSkillTool, mandatory workspaceId for Go usage validation, optional E2B doc compiler metadata, and abort forwarding workspace context; it drops auto-allowed-tools, copilot stats, and workspace mothership settings routes while adding enterprise BYOK proxy/validate routes and admin mothership DELETE. Generated docs are served from precompiled S3 artifacts (409 while building, immutable cache when ?v= is set) instead of recompiling on every preview.

Smaller changes include multi-file E2B sandbox exports with VFS prevalidation, a file manage content operation, logs listing moved to lib/logs/list-logs, dev DB db:push in CI, realtime HTTP handler registration before Socket.IO, and expanded Slack trigger output fields in docs.

Reviewed by Cursor Bugbot for commit ff40a35. Configure here.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 3 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit ff40a35. Configure here.

Comment thread apps/sim/app/api/function/execute/route.ts
Comment thread apps/sim/app/api/knowledge/search/route.ts
Comment thread apps/sim/app/api/function/execute/route.ts
@Sg312 Sg312 merged commit 39418f9 into staging Jun 9, 2026
24 checks passed
ouiliame added a commit to ouiliame/sim-docs that referenced this pull request Jun 9, 2026
…ock re-visible

Staging's mothership v0.2 (simstudioai#4923) expanded the Slack trigger payload
(interactivity, slash commands: event_type, command, action_id/value/actions,
response_url, trigger_id, callback_id, ...) — regenerated so it lands on the
unified integrations/slack page; the old-layout triggers/slack.mdx from
staging's generator was dropped in the merge. The file block is visible again
upstream, so integrations/file.mdx is back in the catalog.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants