fix(platform): stable block chat ids, held-listing sync status, session cleanup on account deletion

[waleedlatif1]

Summary

• Sim block: every Conversation ID is mapped to a UUID v5 of workspaceId:id. Builder strings like customer-456 no longer fail every uuid-keyed read, two workspaces using the same id no longer share a thread in the copilot store, and a block can only continue a chat it derived. The block still exposes the builder's own id so chaining keeps the thread. The fork feature's UUID v5 helper moves to a shared module.
• Connector sync: checkpoint.unsafe (provider cannot promise a stable listing) is back to gating only deletion reconciliation. Since feat(search): add organization search and private assistant #7477 it also marked the run partial and froze last_sync_at, so stable-but-unsafe providers (Fireflies, Notion search, capped Gmail/Slack) showed stale "last synced" and Partial rows on every run. One isContentPassIncomplete predicate now drives status, watermark, and task outcome. Restores pre-feat(search): add organization search and private assistant #7477 behavior: KB sync history rows go back to Completed and the org Search overview stops flagging these sources as needing attention. Affected connectors self-correct on their next run.
• Account deletion: the deletion response clears the session cookies itself, since the signed cookie cache otherwise keeps authenticating the browser for its TTL and the page's query-cache reset refetches the workspace list, which auto-creates a workspace for a user who no longer exists. The route builder keeps each cleared cookie on its own header line. A workspace → user FK violation on create is now WorkspaceOwnerMissingError, answered 401 by both workspace routes instead of a logged 500.

Rollout note

• Conversation ids are derived from this version on, including UUID-shaped ones. A thread whose id was minted before this deploy and stored for reuse starts fresh once; ids chained from the block's output after this deploy keep their thread. Passing UUIDs through is what let a block continue any chat in the copilot store, so there is no compatibility path to keep.

Type of Change

• Bug fix

Testing

• New tests for each change, each confirmed to fail without its fix: resolver derivation/scoping/chaining, UUID v5 RFC vector, handler wire vs. exposed id, isContentPassIncomplete over all flag combinations, held pass completes with advanced watermark, classifier wiring, set-cookie append, deletion finalizer (success and swallowed failure), FK → typed error (plus negative case), GET auto-create → 401
• vitest over every touched area: 204 files / 2,981 tests passing
• bun run type-check, bun run lint, check:api-validation, check:audits (46/46), docs-manifest:check all passing

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)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 11, 2026 1:49am UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge, with no outstanding or newly introduced actionable defects identified.

Summary

• Derives stable, workspace-scoped UUIDv5 chat IDs while preserving builder-facing conversation IDs for chaining.
• Treats unsafe-but-complete connector listings as completed syncs while continuing to hold deletion reconciliation.
• Clears authentication cookies after account deletion and maps workspace creation races with deleted users to unauthorized responses.
• Consolidates UUIDv5 generation into a shared utility and adds focused regression coverage.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Sim block conversation ID] --> B[UUIDv5 of workspace ID and conversation ID]
  B --> C[Workspace-scoped copilot chat ID]
  C --> D[Builder receives original conversation ID for chaining]

  E[Connector content pass] --> F{Listing incomplete or content read failed?}
  F -->|Yes| G[Partial status and retained watermark]
  F -->|No| H[Completed status and advanced watermark]
  H --> I{Listing marked unsafe?}
  I -->|Yes| J[Hold deletion reconciliation]
  I -->|No| K[Perform normal reconciliation]

  L[Account deletion completes] --> M[Clear session cookies on response]
  N[Stale cached session reaches workspace creation] --> O[Owner foreign key violation]
  O --> P[WorkspaceOwnerMissingError]
  P --> Q[HTTP 401 Unauthorized]

Loading

_{Reviews (2) · Last reviewed commit: "fix(auth): end the session on account de..."}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.