feat(cli): sm new wizard + standalone simple_module_cli distribution

.github/workflows/release.yml

@@ -108,6 +108,7 @@ jobs:
       fail-fast: false
       matrix:
         package:
+          - simple_module_cli
           - simple_module_core
           - simple_module_db
           - simple_module_hosting

CHANGELOG.md

@@ -33,7 +33,7 @@ Initial public release. All 14 Python packages publish to PyPI and all 3 JS pack
 
 ### Added
 
-- `simple-module new <app>` / `sm new <app>` CLI generator scaffolding a working app with `users + dashboard + permissions` pre-wired.
+- `sm new <app>` CLI generator (shipped via the `simple_module_cli` PyPI distribution) scaffolding a working app with `users + dashboard + permissions` pre-wired.
 - PyPI Trusted Publishing workflow (`.github/workflows/release.yml`) for zero-secret releases.
 - npm Trusted Publishing for all three JS packages.
 

Makefile

@@ -25,12 +25,12 @@ dev-ui:
 
 # Regenerate host/client_app/modules.{manifest.json,generated.ts,generated.css} from installed modules.
 gen-pages:
-	uv run --project host sm gen-pages --host-dir=host/client_app
+	uv run --project host sm host gen-pages --host-dir=host/client_app
 
 # Install JS deps declared by installed modules into host/client_app/node_modules.
 # Wheel-installed modules need this; in-repo workspace modules do not.
 sync-module-deps:
-	uv run --project host sm sync-js-deps --host-client-app=host/client_app
+	uv run --project host sm host sync-js-deps --host-client-app=host/client_app
 
 # Build
 build:

README.md

@@ -14,7 +14,7 @@ A modular-monolith framework for Python. Each feature lives in its own self-cont
 If you want to **build an app on simple_module**, not hack on the framework itself:
 
 ```bash
-uvx --from simple_module_hosting simple-module new my-app
+uvx --from simple_module_cli sm new my-app
 cd my-app
 make dev
 ```
@@ -119,7 +119,7 @@ Power users can still override the following bootstrap knobs via env if needed:
 All module-level settings — users, SMTP, Celery broker, file storage backend, etc. — live in the admin UI. After upgrading an existing deployment, run once:
 
 ```bash
-uv run sm-settings import-from-env
+uv run sm settings import-from-env
 ```
 
 to seed DB overrides from the current `SM_*` environment.
@@ -135,7 +135,7 @@ See `framework-conventions.md` for the settings-per-module convention.
 Either use the CLI:
 
 ```bash
-uv run sm-users create-admin --email admin@example.com --password changeme
+uv run sm users create-admin --email admin@example.com --password changeme
 ```
 
 Or let the app bootstrap it automatically on first boot by setting env vars **before** running `make migrate && make dev`: