Read a repo's state and its why from one moment

The authoritative re-read that fills the primary's STATUS copied state and nothing else, so provisionReason stayed whatever the plain registry read had returned. A repo the fresh read says has just failed then showed a failure with no reason at all, and one that has since recovered kept a reason from the attempt before. The STATUS cell is the only thing that says a repo failed to provision, and this is the only thing that says why, so pairing them across two moments makes the pair say nothing. retainRepoCreation already treats the reason as freshness-sensitive for exactly this reason; the view now does too, taking both together or neither.

A cancelled read also stops being swallowed. The authoritative call is best-effort so a server that cannot answer costs a dashed cell rather than the whole table — but a context error is not a server declining to answer, it is the command being stopped. Without the flag it fell through every case, printed a table built on the stale state, and exited 0.