[huyplb]

Summary

• Saving or deleting a workflow checks the stored document as well as the new body, so dropping a saved connection no longer unlocks overwrite or delete.
• The Runs panel can cancel a live run, answer a human gate, and resume a paused one.
• The SQL editor can run a plain multi-statement batch as one transaction per destination, and Access can apply a confirmed GRANT/REVOKE. The workflow engine can start with the published app through an opt-in compose profile.

Test plan

• Workflow proxy tests: strip-and-save is refused, steering is forwarded, a member can delete
• SQLite transaction rolls back a later failure and leaves the following statement unrun
• Access confirmation applies only from Apply, and hides Apply without Grant privileges
• Runs panel cancel, answer, and resume
• One-transaction store path batches plain SQL and keeps code cells and @set on the statement loop

Made with Cursor

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 08439d07-6375-4810-ae25-c1407ef724aa)