fix: preserve workspaceId in bulkUpdateChatflows + optional template name sync

[ct3685]

Summary

• Bug fix: bulkUpdateChatflows was spreading the admin template entity without overriding workspaceId, causing every bulk template push to overwrite each user's chatflow workspace with the template owner's workspace ('Default Workspace'). This is the root cause of the repeated prod SQL hotfixes.
• Enhancement: Adds an optional updateName flag so admins can choose to propagate the template name to all user copies during a bulk push (off by default — no behaviour change without opt-in).
• Data migration: 1770000000002-FixBulkUpdateChatflowWorkspace idempotently repairs chatflows already corrupted by previous bulk updates across all orgs (generalises the prod SQL fix, registered in postgresMigrations).

Changes

File	Change
packages/server/src/services/chatflows/index.ts	Add workspaceId: targetChatflow.workspaceId override + options.updateName conditional name logic
packages/server/src/controllers/chatflows/index.ts	Extract and pass options from request body
packages/ui/src/api/chatflows.js	Accept and forward options in PUT body
packages-answers/ui/src/Admin/Chatflows/index.tsx	Replace raw button click with confirmation dialog + "Also update chatflow name" checkbox
packages/server/src/database/migrations/postgres/aai/1770000000002-FixBulkUpdateChatflowWorkspace.ts	New idempotent data migration
packages/server/src/database/migrations/postgres/index.ts	Import + register new migration

Root Cause

// Before — templateChatflow.workspaceId leaked onto every user's copy
const updatedChatflow = {
    ...templateChatflow,   // workspaceId from admin workspace leaked in
    id: targetChatflow.id,
    userId: targetChatflow.userId,
    // workspaceId NOT overridden
}

// After — workspace always preserved from the target
const updatedChatflow = {
    ...templateChatflow,
    id: targetChatflow.id,
    userId: targetChatflow.userId,
    workspaceId: targetChatflow.workspaceId,  // fixed
    name: options?.updateName ? templateChatflow.name : targetChatflow.name,
}

Test Plan

• Run migration on staging DB — chatflows in Default Workspace with parentChatflowId move to Personal Workspace
• Trigger bulk update via Admin Chatflows UI — user chatflows stay in their Personal Workspace after push
• Confirm "Update Selected" now opens a confirmation dialog before acting
• Check "Also update chatflow name" — names synced to template post-update
• Leave checkbox unchecked — names preserved as-is

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
answerai-docs	Building	Preview	May 15, 2026 4:53pm
the-answerai	Building	Preview	May 15, 2026 4:53pm

[ct3685]

@copilot please review this pr, thanks!

[Copilot]

@copilot please review this pr, thanks!

Reviewed the PR at commit 72f32ea — no blocking issues found in this change set. The workspaceId preservation fix, optional updateName wiring, and migration intent all look correct. Current failing checks appear unrelated to this PR diff (Claude review job missing API/OAuth token, plus existing lint errors in other files). If you want, I can follow up in a separate PR to address those CI failures.