fix(tables): make the atomic per-cell merge the only row-write path (fix row-level LWW)

[waleedlatif1]

Summary

• A table row stores every cell in one jsonb data column. Row updates ran a full-object read-modify-write (write the whole data), which is row-level last-write-wins: two users — or a user and an agent/copilot — editing different cells of the same row concurrently clobbered each other.
• updateRow now always writes the changed cells via a shared jsonbMergePatch helper (data = data || {changed}::jsonb), which Postgres evaluates against the current committed row under its write lock — so concurrent edits to different cells both survive. The dataWriteMode: 'replace' | 'patch' option is removed: replace never actually replaced (the merge only ever adds/overwrites keys, never deletes), so it was content-identical to patch and differed only by being racy — no caller benefited from it.
• batchUpdateRows (the multi-cell grid / copilot batch path) applies the same per-row merge, so batch edits can't clobber a concurrent single-cell edit either.
• Because the fix lives entirely in the service layer, the user-facing route + copilot callers are unchanged vs staging, and the two data:{} exec-clear writes in background/workflow-column-execution.ts are covered automatically. upsertRow (whole-row by design) and updateRowsByFilter (already ||-concat) are untouched. computedWrite (the workflow-engine lock exemption) is unaffected.

Type of Change

• Bug fix

Testing

• update-row.test.ts: asserts updateRow and batchUpdateRows each write data || {changed}::jsonb carrying only the changed cells (never the whole row).
• Reviewed via a 4-lens parallel audit (correctness/concurrency, downstream side-effects, completeness/scope, conventions): confirmed non-concurrent parity, no side effects (returned row unchanged; peers reconcile via authoritative refetch), and the mechanism is already prod-proven by cell-write.ts.
• check:api-validation:strict, check:utils, tsc --noEmit, biome, and the table + copilot suites (481 + 111 + 46) pass.

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 (UTC)
docs	Skipped		Jul 27, 2026 4:01pm

[cursor]

PR Summary

Medium Risk
Touches core table row persistence and concurrency behavior for all updateRow/batchUpdateRows callers; behavior change is intentional but widespread across user edits and workflow writes.

Overview
Fixes row-level last-write-wins when concurrent writers touch different cells on the same row (users, copilot, or workflow progress).

updateRow now always persists via a shared jsonbMergePatch (data = data || {changed}::jsonb) instead of sometimes writing the full merged data object. The dataWriteMode: 'replace' | 'patch' option is removed — callers no longer opt into patch mode; cell-write only passes computedWrite.

batchUpdateRows uses the same per-row merge (changed column ids only), so grid/copilot batch edits don’t overwrite concurrent single-cell edits.

Tests in update-row.test.ts assert the SQL merge shape for updateRow and add coverage for batchUpdateRows; the duplicate patch-mode test is dropped because patch is the only path.

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

[greptile-apps]

Greptile Summary

The PR makes atomic JSONB cell merging the sole row-update strategy.

• Adds a shared jsonbMergePatch helper for updateRow and batchUpdateRows.
• Removes the obsolete dataWriteMode option and updates workflow-cell callers.
• Adds tests verifying that writes contain only explicitly changed cells.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
apps/sim/lib/table/rows/service.ts	Centralizes partial JSONB row writes and applies them consistently to single and batched updates.
apps/sim/lib/table/tests/update-row.test.ts	Verifies single-row and batch paths persist only changed cells through JSONB concatenation.
apps/sim/lib/table/cell-write.ts	Removes the obsolete write-mode option while preserving the computed-write lock exemption.
apps/sim/lib/table/workflow-columns.ts	Documents that execution-only updates now produce an empty, non-destructive cell patch.

Sequence Diagram

sequenceDiagram
  participant A as Editor A
  participant B as Editor B
  participant DB as PostgreSQL row
  A->>DB: "UPDATE data = data || {cellA}"
  DB->>DB: Lock row and merge cellA
  B->>DB: "UPDATE data = data || {cellB}"
  DB->>DB: Wait, then merge cellB into committed row
  DB-->>A: Updated
  DB-->>B: Updated
  Note over DB: Both distinct-cell changes survive

Loading

_{Reviews (3): Last reviewed commit: "refactor(tables): make the atomic cell-m..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@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 7aff1ee. Configure here.}

[waleedlatif1]

@greptile

[waleedlatif1]

@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 e7c903b. Configure here.}