By default, blocks have a margin of 1.5em to create a consistent
vertical rhythm. However, sometimes elements need to be associated with
the element above them. In this cases, the gap between elements needs to
be tighter. There are many ways to do this, but this approach asks the
latter content to be marked as associative. The implication is that the
association is with the previous block.

…mponent

This has bit me more than once. It's best just to make Mirage consistent
with the API even if it currently means indeterminate job ids

… dom selector

UI: Run a job from the Web UI

…leaf nodes

The lowest valid blocking query index is 1, but the API will return 0 if
there has yet to be an index set (no response). This in conjunction with
that 0 being stored as a string made the "fallback to 1" guard not work.

Caused by the re-indexing that occurs to remove zero-value bars.

Instead it was using the page-layout is-right div

…eeded

This exports a function that returns the pertinent function when given a
container. This way it works in registerHelper and in integration tests
beforeEach hooks

Most of this was ported over from the existing job run acceptance tests

UI: New job improved plan screen

…tton

Before it would say the deployment required promotion, now it has a
button that triggers the promotion.

UI: Edit a job

When the server doesn't respond immediately, there is a visible window
of time between the action being submitted and the blocking query coming
back with the new job status.

UI: Promote canary

UI: Restart stopped job