The receipt keeps up while the database is being built #32

What to build

While a run is in progress the receipt re-reads the instance record and the organization's activity feed every few seconds, so the elapsed clock advances and a step that has just been confirmed appears without the user touching anything. Once every row has settled, the refreshing stops.

A slow or failed refresh must not damage what is already on screen: the last good rows stay, and the footer says what failed.

Acceptance criteria

• While a run is in progress the rows and the elapsed clock update without a key press.
• Refreshing stops once every row of the receipt has settled.
• A refresh reply that arrives after the user has left the view is dropped, never painted over the new view.
• A failed refresh keeps the last good rows and names the failure in the footer.
• The cadence is one place in the code, so it can be changed without hunting for it.

Blocked by

• See everything that is provisioning, and open the steps behind it #31