Cover the arm that tells a stopped command from a stuck server

The authoritative read is best-effort so a server that cannot answer costs a dashed STATUS rather than the whole table, and 9527de69b6 carved out context errors from that leniency: an interrupted command must not print a table built on the stale state and exit 0. It added the arm and no test.

The cancellation assertions already in this file all exercise awaitRepoActive, the create/poll path, so nothing covered the view's own read. Removing the arm now turns this red with the exact symptom — ExecuteContext returns nil for a command the user stopped.