You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
improvement(mothership): drop get_job operation — poll background jobs via query_rows
Per review, get_job is unnecessary: the model observes background
import/delete progress with query_rows (rows appearing as an import lands;
the delete mask already makes query_rows reflect the post-delete view).
Removes the operation and repoints the dispatch messages at query_rows.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
message: `Started background delete of ${doomedCount} matching rows (job ${jobId}). The rows are hidden from reads immediately; call get_job to track progress.`,
778
+
message: `Started background delete of ${doomedCount} matching rows (job ${jobId}). The rows are hidden from reads immediately — query_rows already reflects the post-delete view.`,
message: `Created table "${table.name}" (${table.id}); importing rows from "${record.name}" in the background (job ${importId}). Columns and rows appear as the import progresses — call get_job with this tableId to track it.`,
971
+
message: `Created table "${table.name}" (${table.id}); importing rows from "${record.name}" in the background (job ${importId}). Columns and rows appear as the import progresses — query_rows to check what has landed.`,
message: `Started background ${mode} import of "${record.name}" into "${table.name}" (job ${importId}). Rows appear as the import progresses — call get_job to track it.`,
1136
+
message: `Started background ${mode} import of "${record.name}" into "${table.name}" (job ${importId}). Rows appear as the import progresses — query_rows to check what has landed.`,
0 commit comments