fix: refresh $updatedAt after inline row edits

[cursor]

What does this PR do?

Inline spreadsheet edits called tablesDB.updateRow but kept the pre-write row in local grid state, so $updatedAt never changed until a full reload. Apply the API response system fields ($updatedAt, $permissions) before updating the grid.

Fixes #2873

Test Plan

• Manually: edit a cell inline in TablesDB spreadsheet and confirm $updatedAt updates immediately
• Sidebar "Update" path already invalidates and was unaffected

Related PRs and Issues

• Console - Databases - inline updating a row column does not update $updatedAt #2873

  

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL

Tip

Build commands execute in runtime containers during deployment

[greptile-apps]

Greptile Summary

The PR refreshes locally cached system fields after a successful inline TablesDB row edit.

• Uses the updateRow response to refresh $updatedAt and $permissions.
• Updates the paginated spreadsheet state with the refreshed row.
• Preserves the callback’s existing boolean success contract.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/spreadsheet.svelte	Applies server-returned system fields to the edited row and propagates the successful result into paginated grid state.

_{Reviews (3): Last reviewed commit: "chore: nudge CI for stuck Tests queue" | Re-trigger Greptile}

[ChiragAgg5k]

Confirmed this is a console-only bug: updateRow already returns a new $updatedAt, but inline edit ignores the response and keeps the pre-write row in the grid. Applying the API system fields before paginatedRows.update is the right fix.