fix(ai-builder): Disable autosave functionality while workflow builder is generating (no-changelog)

[mike12345567]

Summary

Current behaviour has workflow builder generation saving multiple times throughout the generation when the workflow is an unfinished state. This PR disables saving while generation is streaming.

I've also removed all of the logic related to saving after the workflow builder has finished as auto-save can now look after this instead - currently two saves occur at the end as auto-save detects the changes and the workflow builder triggers a save.

Addresses: https://linear.app/n8n/issue/AI-1878/feature-stop-auto-saving-when-builder-is-in-progress

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

[cubic-dev-ai]

No issues found across 3 files

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 3 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...collaboration/collaboration/collaboration.store.ts	66.66%	2 Missing ⚠️
...i/assistant/components/Agent/AskAssistantBuild.vue	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[currents-bot]

✅

E2E Tests: n8n tests passed after 7m 35s

🟢 55 · 🔴 0 · ⚪️ 3

View Run Details

Run Details

• Project: n8n

• Groups: 1

• Framework: Playwright

• Run Status: Passed

• Commit: 0bfcc39

• Spec files: 10

• Overall tests: 58

• Duration: 7m 35s

• Parallelization: 1

---

This message was posted automatically by currents.dev | Integration Settings

[mutdmour]

Implementation here looks okay. Some new tests would be nice.

But I think there's a missing piece.

the new collaboration feature adds a write lock while the user is actively working on a workflow. The workflow is locked for 20 seconds if user is inactive.

The builder does not seem to have any effect on this. When sending a message, a write lock is requested. 20 seconds later the lock is released, even while the builder is working away.

That could lead to conflicts if another user acquires the lock while the builder is working for another user.
Ideally the UI should keep the write lock while the builder is toiling away.