SEED — wiring the services together

Raised while seeding, when a service will not co-operate. Seeding is resumable: everything already made is valid, and running it again finishes the rest.

Code	Severity	Exit	What it means	What to do
SEED-1	warning	1	A service was not answering yet, so it was skipped. Nothing was changed for it.	Wait for it to finish starting, then run lemonfiber seed again.
SEED-2	error	1	A service rejected the credential lemonfiber holds, usually because it was changed in the service's own interface.	Have lemonfiber re-read the service's credential with lemonfiber doctor --fix.
SEED-3	error	1	A service answered in a way lemonfiber does not recognise, so it will not guess at what would fix it.	Nothing is known to fix this. Send a support bundle; the service's own words are attached to the message.
SEED-4	error	1	A service answered that it does not offer what was asked: it speaks a release this build does not, or cannot do this at all. Nothing was changed for it.	Where the service's release is the cause, match it to the version lemonfiber supports or update lemonfiber, then run lemonfiber seed again.

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