Flisk is kind to a new service. That kindness is the bug.

A scaffolded backend, read from the files flisk project and flisk resource generated in Flisk 1.3.86, boots with a working login, a working database, a working URL, and a migration that already ran. A real application and a staging environment were not part of that reading. If your code treats those conveniences as the world, it will pass every local test and fail the first time it meets an identity provider.

The scope note says this plainly. Local is the intended use. CI can be a throwaway copy of local. Staging and production are out of scope. There is no command that deploys, exports a chart, or writes cluster config.

The harness, line by line

These are not opinions. They were read from the generated Compose file and .env of that scaffolded backend. Check them against your own tree before you quote them in a design doc.

What your app sees What Flisk actually gave it What production will not give it

NODE_ENV=development Set in the container.…