GeezerVison

Summary

• Deleting a workflow archives its chat with isActive: false; restore clears only archivedAt, so the restored chat kept answering 403 "This chat is currently unavailable"
• "Launch Chat" (the update path) redeployed the workflow and reported success but never set isActive, so the chat stayed offline and the modal kept offering "Launch Chat" with Delete hidden — no way out from the UI
• Deploying or updating a chat now sets isActive: true in both paths: updateChatDeployment (editor PATCH, v2 PATCH) and performChatDeploy's update branch (internal POST, v2 deploy, Copilot deploy_chat). Both already guarantee an active workflow deployment before writing the row, so the chat is only marked live when it can answer
• Restore itself is unchanged: re-enabling stays explicit, matching how redeploy re-activates schedules and webhooks (comment in lib/folders/config.ts updated)

Side effects checked

• Every writer that sets chat.isActive = false (workflow archive, fork promote, fork rollback) sets archivedAt in the same statement, and no API accepts isActive as input. The only rows this can change are chats restored after an archive
• Both update paths resolve the chat with archivedAt IS NULL, so a chat whose workflow is still deleted cannot be reactivated (covered by a test)
• The update mutation already invalidates the chat status query, so after a relaunch the modal shows the chat as launched and Delete comes back

Type of Change

• Bug fix

Testing

• New lib/chat-deployments/__integration__/relaunch-after-restore.integration.ts against real Postgres: real deploy → archive → restore → relaunch through updateChatDeployment and through performChatDeploy, plus a deleted-workflow negative case
• Red on the pre-fix code; reverting each half of the fix separately turns its own test red, then green with the full fix
• Existing chat deploy/manage/status/v2 route and orchestration tests pass (6 files, 76 tests)
• biome on changed files; full type-check, check:audits and the suite run in CI

Checklist

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