Fix knowledge connector sync follow-up

[TheodoreSpeaks]

Summary

• Queue synchronization when runnable connector source configuration changes, while preserving paused state and rejecting active-sync races
• Move manual sync to sim knowledge connectors sync and fix nested connector document commands
• Support Linear personal API keys and OAuth tokens with the correct authorization format
• Update the generated OpenAPI and CLI documentation without adding or changing HTTP endpoints

Type of Change

• Bug fix

Testing

• Passed focused Sim tests: 106 tests
• Passed Sim CLI tests: 450 tests, 1 skipped
• Passed Sim and CLI type checks
• Passed lint and all 32 repository audits

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.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 22, 2026 9:58pm

[cursor]

PR Summary

High Risk
Touches connector sync locking, queue dispatch, and billing attribution. Incorrect CAS or dispatch could skip, double-run, or bill the wrong workspace.

Overview
Updating a runnable knowledge connector’s source now queues an immediate sync (with billing attribution), while paused connectors keep the new config until resumed. Source and schedule changes conflict if a sync is already in progress; the worker uses the locked row’s config so it never indexes a stale source.

Automatic dispatch is stricter: it requires a matching nextSyncAt, skips paused/disabled connectors (requireRunnable), uses Trigger.dev idempotency keys, and will not steal a pending row that already has a lock token. Schedule-only updates no longer wipe an already-due source sync.

CLI: manual sync is sim knowledge connectors sync (replacing knowledge sync create), nested connector document commands nest correctly, and path args are consistently knowledgeBaseId. Linear connector auth now uses linearAuthorizationHeader so personal API keys are sent without Bearer.

^{Reviewed by Cursor Bugbot for commit 75cb92c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[greptile-apps]

Greptile Summary

The PR makes runnable connector source changes queue an immediate synchronization while preserving paused state and preventing active-sync races.

• Persists due markers and adds optimistic status/time checks so rejected or concurrent handoffs remain recoverable.
• Locks synchronization to an authoritative connector snapshot and carries runnable-state requirements through queued jobs.
• Corrects Linear authorization handling for personal API keys and OAuth tokens.
• Reorganizes connector CLI commands and updates generated API and CLI documentation.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
apps/sim/lib/knowledge/orchestration/connectors.ts	Source updates now persist durable sync intent, use optimistic concurrency checks, and await the immediate handoff.
apps/sim/lib/knowledge/connectors/queue.ts	Automatic dispatch now validates runnable state and expected due time and uses due-time-based idempotency.
apps/sim/lib/knowledge/connectors/sync-engine.ts	Synchronization acquires an authoritative connector snapshot under the lock and guards automatic work and terminal writes.
apps/sim/lib/knowledge/application/connectors.ts	Connector updates now resolve billing attribution required for source-change synchronization.
apps/sim/connectors/linear/linear.ts	Linear requests now use the shared authorization formatter for personal API keys and OAuth tokens.
packages/sim-cli/src/contract/commands.ts	Knowledge connector commands are reorganized under the corrected nested CLI hierarchy.

Sequence Diagram

sequenceDiagram
  participant Caller
  participant Update as Connector update
  participant DB
  participant Queue
  participant Worker
  Caller->>Update: Replace sourceConfig
  Update->>DB: CAS update sourceConfig + due marker
  DB-->>Update: Updated connector
  Update->>Queue: Dispatch with expected due time
  Queue->>DB: Verify due marker and runnable status
  Queue->>Worker: Enqueue idempotent sync
  Worker->>DB: Acquire sync lock and return current row
  Worker->>Worker: Sync using locked sourceConfig snapshot
  Worker->>DB: Write terminal state if lock still owned
  Update-->>Caller: Updated connector or dispatch failure

Loading

_{Reviews (6): Last reviewed commit: "Merge origin/staging into fix/kb-connect..." | Re-trigger Greptile}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

1 issue from previous review remains unresolved.

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 335c015. Configure here.}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit ea8b877. Configure here.}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 5d0ac9c. Configure here.}