Commit stories
Manual QA scenarios for the async cell-commit pipeline. Each one is a live table — edit a cell and watch the optimistic commit, retry, and error states behave under different network conditions.
01Flaky networkHalf of all commits fail at random — watch the retry and error states recover an edit.→02Slow networkA 2-second commit delay surfaces the per-cell pending and saving states.→03External conflictA background write lands mid-edit so you can see conflict handling kick in.→04Bulk saveautoCommit: false — stage many edits, then flush them to the server in one batch.→05Per-column commitOverride the commit strategy on a single column without touching the rest.→