ASK — putting a request to the web surface

Raised by the web API lemonfiber ui serves, where a request to act, to hear about a job, to move setup or to mint a key could not be answered as it was asked, or reached a path or a method no endpoint answers. Nothing was changed by any of them. ASK-1, ASK-7 and ASK-9 answer 404, ASK-10 answers 405, and every other one 400. See the envelope.

Code	Severity	Exit	What it means	What to do
ASK-1	error	1	There is no action by that name. An action here is a command the command line offers, and this surface offers nothing else. The message names what was asked for.	Ask for one of the actions the contract names.
ASK-2	error	1	An action was not given an argument it needs, so it was not carried out. The message names the action and the argument.	Ask again with the arguments the action takes.
ASK-3	error	1	An argument was given a value that names nothing this stack knows. The message names the argument, what it said, and what it could have said instead.	Ask again with the arguments the action takes.
ASK-4	error	1	An action was given an argument its command has nowhere to put. It is refused rather than dropped, because dropping it would carry out a different request from the one asked for.	Ask again with the arguments the action takes.
ASK-5	error	1	An action was given two arguments that each name a different request. A run carrying both would have to pick one of them and answer something nobody asked for. The message names the two.	Ask again with the arguments the action takes, choosing one of the two.
ASK-6	error	1	The body of the request is not arguments the action can read. What the reader could not take from it — a field it did not know, or where the text stopped being JSON — is given as the detail.	Ask again with the arguments the action takes.
ASK-7	error	1	No work in this run goes by that name. Jobs are named by the run that starts them, and work from an earlier run is not tracked here.	Ask about a job this run started.
ASK-8	error	1	The body of a setup step is not one of setup's answers, nor a way out of an interrupted apply, so setup did not move. What arrived is not repeated back, because an answer can carry a credential.	Answer the question setup is asking.
ASK-9	error	1	No endpoint answers this path. Every endpoint this surface answers is named in the contract, and this path is not one of them.	Ask for one of the endpoints the contract names.
ASK-10	error	1	The path is one this surface answers, asked with a method it does not answer it with, and nothing was done.	Ask again with the method the contract names.
ASK-11	error	1	The body of a request to mint a key is not a key's name, scope and purpose with the password, or the body of a request to collect one is not a claim alone, so no key was minted or collected.	Send a mint the name, scope, purpose and password, and a collection the claim alone.
ASK-12	error	1	An action's Idempotency-Key is not one to 255 visible characters, or was given more than once. The action was not carried out, and nothing was changed: a key that cannot be read is one a second send could not be recognised by.	Send the key once, as up to 255 visible characters with no spaces.
ASK-13	error	1	This Idempotency-Key was already sent with another action or other arguments. Nothing was carried out under it a second time; the attempt it names asked for something else, and that is what it was answered with.	Send a new key with each new attempt, and the same key only with the same action sent again.

What each severity and each exit means is on every error by code, beside every other family.