Create the database, then land on its receipt #33

What to build

Confirming the review page creates the database: the request the review page showed is the request that is sent, the response names the new instance, and the terminal opens that instance's receipt so the user is already watching it come up.

Confirming is a deliberate act of its own. Filling the form, scrolling the review or opening a picker can never reach the create.

Acceptance criteria

• The create is sent only from an explicit confirm on the review page, and that confirm names the action.
• The request is the one the review page displayed: the region as the query parameter, the chosen fields in the body.
• The new instance opens on its own receipt as soon as the platform answers.
• The database views include the new instance once the platform reports it.
• A wait-style flow is not required: the receipt is the progress, and it never claims a step the platform has not confirmed.
• The built request is testable without sending it, through a source that records instead of posting.

Blocked by

• The receipt keeps up while the database is being built #32
• Ask for a new database on a form the platform can satisfy #30