bit CLI and bit Boilerplate need better co-operation

A batch of gaps in bit Boilerplate, the bit CLI and the create project page.

bit Boilerplate

Every generated project seeds its accounts with the password 123456, the same one the public template and docs show, so anyone can sign in as a global admin on a deployment that still has them. The template should use 12345678, and dotnet new should replace it with a random 8 digit password per project.
/healthz answers 200 even when a check is Unhealthy, so a monitor can't go by its status code.
Without Docker, a project with SQLite should still come up with aspire start, only without Keycloak and Mailpit. Today the app host stops about two minutes in, because Keycloak's and Mailpit's data volumes never get ready without a container runtime. The containers keeper also always calls docker, even when Aspire picked Podman.

bit CLI

After bit new, Aspire starts the project once and stops it. It should keep it running (aspire start, or dotnet run without Aspire), open the Aspire dashboard and then the app in the browser, and stop only when the terminal is closed.
On Windows and macOS it installs Docker Desktop, which needs a paid subscription for larger companies.
It doesn't start a project without Docker, even when the project doesn't need any container to run.
It warns about memory under 23 GB. Under 15 GB is the right line.
When a project doesn't need Docker, WSL or virtualization, it still installs them, which is fine, but it warns about the restart they ask for as if something were wrong.
There's no way to bring a newer bit Boilerplate version into an existing project. A bit diff that creates the project with both versions into one git repository, so the second commit is the upgrade, plus a Boilerplate skill that applies it to the project, would cover it.

Create project page

The command copied on the page goes to Telegram with the project's name in it.
"Just the web app" next to the native apps reads like a choice that excludes them. The web app is always there.
The page and the getting started page still recommend Docker Desktop.