remove datasets and products modules, reset migrations (#96)

* remove datasets and products modules, reset migration history

The datasets and products example modules are removed from the workspace
along with all wiring (host pyproject, root pyproject, CLI catalog) and
the integration/e2e tests that exercised them as their CRUD subject.
Dashboard's product-count tile and the workspace dep on simple_module_products
are also dropped.

To avoid leaving frozen migrations referencing deleted modules, every file
under host/migrations/versions/ is replaced by a single autogenerated
77162e7b184b_initial_schema.py. The fresh schema contains tables for the
remaining 8 modules (auth/users/permissions/dashboard/settings/feature_flags/
file_storage/background_tasks) and `alembic check` reports no drift.

Verified: 943 Python tests pass, 8 JS tests pass, make lint clean, doctor
exits 0, host boots and /health reports the new revision as current.

* exempt host/migrations/versions from 300-line file cap

Alembic autogen rolls every installed module's tables into a single
initial migration. The current 77162e7b184b lands at 382 lines and
growing the schema will only push it higher. Migrations aren't
hand-authored, so the cap doesn't add value here.

Author: antosubash

README.md

@@ -44,7 +44,7 @@ make migrate
 make dev
 ```
 
-Hit `http://localhost:8000` — you land on the public page. `/users/login` is the email+password login, `/dashboard` is the authenticated home, `/products` is a fully-working example module.
+Hit `http://localhost:8000` — you land on the public page. `/users/login` is the email+password login, `/dashboard` is the authenticated home.
 
 ## Create a new module
 
@@ -73,7 +73,7 @@ framework/
   core/        # module system, discovery, events, diagnostics
   db/          # per-module Base, session, mixins, listeners
   hosting/     # app_builder, middleware, settings, Inertia glue
-modules/       # plugin modules (auth, dashboard, products, ...)
+modules/       # plugin modules (auth, dashboard, users, settings, ...)
 host/
   main.py      # FastAPI entry point
   routes.py    # host-level routes (landing page)

docs/e2e-testing.md

@@ -1,22 +1,9 @@
 # End-to-End Testing
 
-The repo ships Playwright-driven smoke tests at
-[tests/e2e/test_smoke.py](../tests/e2e/test_smoke.py). Four tests drive a real
-Chromium browser through the core flows:
-
-* **`test_login_and_browse_smoke`** — landing → local email+password login →
-  dashboard → products browse → logout. Minimal regression guard.
-* **`test_products_crud_smoke`** — same login + a full create / edit / delete
-  round-trip against the products module.
-* **`test_password_reset_smoke`** — **skipped** (see inline comment in the
-  test file).  `fastapi-users` `reset_password()` validates a password
-  fingerprint (`password_fgpt`) that is only available server-side.  The
-  full HTTP-layer flow is covered by unit tests in
-  `modules/users/tests/test_api_auth.py`.
-* **`test_admin_invite_smoke`** — admin invites a new user via the UI; the
-  invitee accepts the invite in a fresh browser context and lands on the
-  dashboard.  Token is minted locally using the dev-default verify secret
-  (equivalent to what the ConsoleMailer logs).
+Playwright-driven smoke tests live in [tests/e2e/](../tests/e2e/) — currently
+just [`test_settings_ui.py`](../tests/e2e/test_settings_ui.py), which logs in,
+navigates to `/settings/modules`, toggles a module setting, and verifies the
+change hot-reloads into `app.state` without a server restart.
 
 End-to-end tests are gated behind the `e2e` pytest marker (declared in
 [pyproject.toml](../pyproject.toml)) and are **excluded from the default
@@ -62,7 +49,7 @@ uv run pytest -m e2e tests/e2e
 
 ## Configuration
 
-The tests read these environment variables (all optional):
+When you write e2e tests, read these environment variables (all optional):
 
 | Variable       | Default                   | Notes                                                        |
 | -------------- | ------------------------- | ------------------------------------------------------------ |
@@ -71,38 +58,6 @@ The tests read these environment variables (all optional):
 | `E2E_PASSWORD` | `admin`                   | Password of the above admin user.                            |
 | `SM_USERS_VERIFICATION_TOKEN_SECRET` | `dev-verify-token-secret-change-me` | Must match the running server's value so locally-minted invite tokens are accepted. |
 
-## What the smoke tests cover
-
-**`test_login_and_browse_smoke`**
-
-1. Landing page renders (`/`) with the "Get Started" CTA.
-2. Local email+password login via `/users/login`.
-3. Dashboard (`/dashboard/`) renders — proves session cookie + AuthMiddleware +
-   Inertia resolver + AuthenticatedLayout.
-4. Products browse (`/products/`) renders — proves module pages resolve.
-5. Logout returns the user to the public landing page.
-
-**`test_products_crud_smoke`**
-
-1. Login as admin.
-2. Create a timestamped product via the Create form.
-3. Edit its name and verify the new name appears in the list.
-4. Delete it through the confirm dialog and verify the row disappears.
-
-The CRUD test relies on the admin user having the `admin` role (created
-automatically by `sm-users create-admin` or the bootstrap env vars).
-
-**`test_admin_invite_smoke`**
-
-1. Admin logs in and submits the invite form at `/users/admin/invite`.
-2. The test looks up the new user's UUID via the admin API.
-3. A verify token is minted locally (same secret the server uses).
-4. A fresh browser context navigates to `/users/invite/accept?token=…`, sets
-   a password, and verifies a redirect to `/dashboard`.
-
-These are **not** pixel-perfect regression tests — the goal is to catch broad
-breakage in the auth + render + CRUD spine.
-
 ## Debugging
 
 To see what the browser is doing, run headed with the Playwright trace

docs/guide/project-structure.md

@@ -12,11 +12,9 @@ simple_module_python/
 │   ├── auth/                  # session cookie, CSRF defences
 │   ├── background_tasks/      # Celery broker + worker integration
 │   ├── dashboard/             # authenticated landing page
-│   ├── datasets/              # CSV / dataset uploads
 │   ├── feature_flags/         # admin UI for flag toggles
 │   ├── file_storage/          # pluggable storage backends (local, S3)
 │   ├── permissions/           # role/permission admin UI
-│   ├── products/              # reference CRUD module (used in examples)
 │   ├── settings/              # DB-backed module settings + admin UI
 │   └── users/                 # email+password auth, invites, bootstrap
 │

docs/guide/quickstart.md

@@ -29,7 +29,7 @@ The API and Vite dev servers start side by side. Visit:
 
 - `http://localhost:8000` — landing page
 - `http://localhost:8000/users/login` — sign-in screen
-- `http://localhost:8000/products` — a fully-working example module (CRUD on a `products` table)
+- `http://localhost:8000/dashboard` — the authenticated home (log in first)
 - `http://localhost:8000/settings/modules` — the admin settings UI (log in first)
 
 ## 4. Create an admin

docs/release.md

@@ -45,11 +45,9 @@ simple_module_test
 simple_module_auth
 simple_module_background_tasks
 simple_module_dashboard
-simple_module_datasets
 simple_module_feature_flags
 simple_module_file_storage
 simple_module_permissions
-simple_module_products
 simple_module_settings
 simple_module_users
 ```
@@ -223,11 +221,9 @@ Trusted Publishing is tied to the GitHub repo, not any personal account — so a
 | PyPI | `simple_module_auth` | [modules/auth/](../modules/auth/) |
 | PyPI | `simple_module_background_tasks` | [modules/background_tasks/](../modules/background_tasks/) |
 | PyPI | `simple_module_dashboard` | [modules/dashboard/](../modules/dashboard/) |
-| PyPI | `simple_module_datasets` | [modules/datasets/](../modules/datasets/) |
 | PyPI | `simple_module_feature_flags` | [modules/feature_flags/](../modules/feature_flags/) |
 | PyPI | `simple_module_file_storage` | [modules/file_storage/](../modules/file_storage/) |
 | PyPI | `simple_module_permissions` | [modules/permissions/](../modules/permissions/) |
-| PyPI | `simple_module_products` | [modules/products/](../modules/products/) — reference CRUD example |
 | PyPI | `simple_module_settings` | [modules/settings/](../modules/settings/) |
 | PyPI | `simple_module_users` | [modules/users/](../modules/users/) |
 | npm | `@simple-module-py/ui` | [packages/ui/](../packages/ui/) |

framework/cli/simple_module_cli/catalog.py

@@ -36,12 +36,11 @@ class ModuleEntry:
         "Permissions",
         requires=("auth", "users"),
     ),
-    "products": ModuleEntry("products", "simple_module_products", "Products"),
     "dashboard": ModuleEntry(
         "dashboard",
         "simple_module_dashboard",
         "Dashboard",
-        requires=("users", "products"),
+        requires=("users",),
     ),
     "settings": ModuleEntry("settings", "simple_module_settings", "Settings"),
     "feature_flags": ModuleEntry("feature_flags", "simple_module_feature_flags", "Feature Flags"),
@@ -58,26 +57,13 @@ class ModuleEntry:
         requires=("users",),
         recipe="background_tasks",
     ),
-    "datasets": ModuleEntry(
-        "datasets",
-        "simple_module_datasets",
-        "Datasets",
-        requires=("file_storage", "background_tasks"),
-    ),
 }
 
 
-# Example modules — `datasets` and `products` are intentionally excluded
-# from every default preset because their module names collide with custom
-# modules users typically want to register themselves. Pass them via
-# `--with datasets,products` (or pick the `examples` preset) to opt in.
-_EXAMPLE_MODULES: frozenset[str] = frozenset({"datasets", "products"})
-
 PRESETS: dict[str, tuple[str, ...]] = {
     "minimal": ("users",),
     "standard": ("users", "dashboard", "permissions"),
-    "full": tuple(name for name in CATALOG if name not in _EXAMPLE_MODULES),
-    "examples": tuple(CATALOG),
+    "full": tuple(CATALOG),
 }
 
 

framework/cli/simple_module_cli/cli.py

@@ -45,7 +45,7 @@ def create_host(
         str,
         typer.Option(
             "--with",
-            help="Comma-separated module names to declare as deps (e.g. Auth,Products).",
+            help="Comma-separated module names to declare as deps (e.g. Auth,Dashboard).",
         ),
     ] = "",
 ) -> None:

framework/cli/simple_module_cli/new.py

@@ -25,7 +25,6 @@ class Preset(StrEnum):
     minimal = "minimal"
     standard = "standard"
     full = "full"
-    examples = "examples"
 
 
 def new_project(

framework/cli/tests/test_cli_catalog.py

@@ -41,17 +41,10 @@ def test_expand_deps_pulls_in_transitive_dep() -> None:
 
 
 def test_expand_deps_pulls_in_chain() -> None:
-    resolved, added = expand_deps(["datasets"])
-    assert set(resolved) == {
-        "datasets",
-        "file_storage",
-        "settings",
-        "background_tasks",
-        "users",
-        "auth",
-    }
+    resolved, added = expand_deps(["permissions"])
+    assert set(resolved) == {"permissions", "users", "auth"}
     added_names = {a for a, _ in added}
-    assert added_names == {"file_storage", "settings", "background_tasks", "users", "auth"}
+    assert added_names == {"users", "auth"}
 
 
 def test_expand_deps_idempotent_when_input_already_complete() -> None:

framework/cli/tests/test_cli_wizard.py

@@ -48,12 +48,11 @@ def test_wizard_minimal_preset() -> None:
 def test_wizard_full_preset_includes_background_tasks() -> None:
     _, _, selected, _ = _drive(["", "", "3", ""])
     assert "background_tasks" in selected
-    assert "datasets" not in selected
     assert len(selected) >= 7
 
 
 def test_wizard_custom_picks_only_yes_answers() -> None:
-    answers = ["", "", "4"] + ["n"] * 8 + ["y", "n", ""]
+    answers = ["", "", "4"] + ["n"] * 7 + ["y", ""]
     _, _, selected, out = _drive(answers)
     assert set(selected) == {"background_tasks", "users", "auth"}
     assert "Added users (required by background_tasks)" in out