STACK — the stack description

Raised about the manifest that describes what would be started. See the stack manifest.

Code	Severity	Exit	What it means	What to do
STACK-1	error	5	No readable manifest was found where a stack was expected. A stack directory holds a stack.toml describing its services.	Point at a directory containing stack.toml, with lemonfiber --stack-dir <path>.
STACK-2	error	1	The manifest is readable and was written for a different version of lemonfiber.	Update lemonfiber, or point at a stack this version reads.
STACK-3	critical	1	This build of lemonfiber is not intact: the stack that ships inside the binary is missing. The build is supposed to make this impossible.	Nothing is known to fix this. Send a support bundle.
STACK-4	error	1	There is nowhere to write the stack, because no location has been chosen.	Run lemonfiber setup.
STACK-5	error	1	The stack could not be written to disk, so nothing can start. Usually a permission problem or a full disk.	Check the location is writable and has space.
STACK-6	error	5	The manifest parses and contradicts itself: it says things about itself that cannot all be true.	Fix the faults listed under the message. All of them were found in one pass.
STACK-7	error	5	The file is not written in the format a stack.toml uses, so nothing in it has been read. The message names the line the reader stopped on.	Fix the file at the line the message names.
STACK-8	error	5	The file is well formed and declares things in words this version of lemonfiber has no meaning for — usually a stack from a newer lemonfiber, or one with something of its own added. Starting it would quietly leave out whatever was named.	Update lemonfiber, or change the named declarations to ones it knows. Every one of them is listed, found in a single pass.
STACK-9	error	1	The stack names the oldest lemonfiber it works with, and the one running is older. It relies on something this version cannot do, so nothing in it is started rather than started in part. The message names both versions.	Update lemonfiber to the version named, with lemonfiber update self. Or point at a stack this version runs, with lemonfiber --stack-dir <path>.
STACK-10	error	5	The stack's manifest files are not laid out as a stack is: a stack.toml whose include list names one file per service under services/, each describing one service. Which services the stack holds cannot be told, so nothing in it was started. A stack that keeps every service in stack.toml itself is refused this way.	Fix the files named under the message. All of them were found in one pass.
STACK-11	error	1	The project lemonfiber generates no longer holds what lemonfiber last wrote there: somebody edited it. A change that has to write the project again would discard that edit, so nothing was changed. The message names the file.	Move the edit into overlay.yml in lemonfiber's configuration directory, which is merged over the project and kept, then run lemonfiber reset to put the project back and make the change again.
STACK-12	error	1	A service kept its state in a volume the container engine holds, and from now on it keeps it in its own directory. The state could not be copied there, so nothing was started: starting it now would start it on nothing and its old state would never be read again. The volume is as it was.	Check the container engine is running and the project directory can be written, then start again. The message names the volume and the directory.
STACK-13	error	1	That agreement was given for a different reading of what a reset would revert: since it was read, an edit or a connection changed. Agreeing to it now would be agreeing to lose something nobody read, so nothing was reverted; the message names what moved.	Read what a reset would revert again, and answer the name it prints.

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