Merged isn't done

At 5:57 UTC on September 24, a settings-layout change merged into Hydrant. The issue stayed in Human Review.

The pull request was healthy. Its final head had passed every configured check, and an independent review had no unresolved findings. Merge still answered only one question: had the accepted change entered the main branch?

Acceptance came before and after the code

The work had already shown why these stages need separate names. Its first visual specimen passed compilation, lint, keyboard checks, narrow layouts, forced colours and sampled accessibility checks. I liked the grouped navigation and the general page frame. The records, Danger zone and Labels & views page felt unfinished, so they went back for another pass.

Technical evidence made that specimen safe to review. It did not make the design good enough to keep.

The revised specimen became the visual direction after another review, rendered state checks and a small correction to the separators. Production implementation followed. The code review then covered the actual change, including drafts, stale writes, focus, dialogs and error recovery. Product acceptance used the rendered behaviour as well as the diff.

By merge time, the candidate had earned its place in the branch. It had not yet proved that the combined main tree passed or that production served it.

After the merge

The merged-main checks passed at 6:06. The checked deployment ran next. Production then had to report one serving version at the merged revision, answer its health check, reject an anonymous workspace request and accept an authenticated tracker read.

A bounded browser check opened the live Labels & views page. It confirmed the grouped navigation, copy, editor state, keyboard behaviour, focus return, collapsed history and saved-view round trip without changing production data. The backup serving record was updated and read back.

At 6:13, with those claims supported, the issue moved to Done.

That sequence can feel fussy when the merge button is the most visible event. It is also what keeps “the code exists” from quietly turning into “the product works.” Review covers the candidate. Merge integrates it. Deployment puts it somewhere people can reach. Verification checks what is actually there. Done is allowed to mean all of them.