@sedim/cli 1.0.2 → 1.0.3

package/dist/index.js

@@ -24,7 +24,7 @@ var init_constants = __esm({
     DEFAULT_REGISTRY_URL = "https://raw.githubusercontent.com/sedimie/Sedim/main/registry";
     DEFAULT_PACKAGES_URL = "https://raw.githubusercontent.com/sedimie/Sedim/main/packages";
     MIN_NODE_VERSION = 18;
-    CLI_VERSION = "1.0.2";
+    CLI_VERSION = "1.0.3";
   }
 });
 
@@ -4404,7 +4404,7 @@ function buildProvidersImport(features) {
   if (features.includes("oauth-github")) providerFns.push("githubProvider");
   if (features.includes("oauth-discord")) providerFns.push("discordProvider");
   if (providerFns.length === 0) return "";
-  return `import { ${providerFns.join(", ")} } from './adapters/framework-config.js'`;
+  return `import { ${providerFns.join(", ")} } from './adapters/framework/framework-config.js'`;
 }
 function buildProvidersConfig(features) {
   const lines = [];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sedim/cli",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Premium codegen CLI — stamp production-ready feature modules into your project",
   "type": "module",
   "main": "./dist/index.js",

package/CONTRIBUTING.md

@@ -1,385 +0,0 @@
-# Contributing to Sedim
-
-Thank you for wanting to contribute. This guide explains everything you need to know to work on the Sedim codebase.
-
----
-
-To start off, you'll need an overview of what's happening in the library, so first going through the readme in full is recommended. Post that, let's try to understand the architecture of the whole library a bit. 
-
-This is a monorepo, with packages as the `core`, `cli`, `auth`, and other modules to be added in the future. 
-`core` contains the shared types between the `cli` and any `module`. The `cli` is built such that any module can seemlessly fit into it and give the same experience to the user. 
-
-
-
-## What can you contribute?
-
-There are lots of ways to help, no matter your experience level:
-
-- **Bug reports and bug fixes** - something is broken, you know how to fix it
-- **New features** - a framework adapter, an ORM adapter, a new module
-- **Feature additions under an existing module** - more auth providers, more UI components, more email transports
-- **UI/UX improvements** - accessibility fixes, better form states, new theme variants
-- **Documentation** - fixing broken links, clarifying confusing sections, writing guides
-- **Feature requests** - you want something that does not exist yet
-- **Testing** - adding tests to existing modules, testing on different platforms
-- **Design** - helping design better auth UI components, visual refinements
-
-If you're unsure whether something is worth contributing, just open an issue. We'd rather you ask than guess.
-
----
-
-## Getting Started
-
-### What you need
-
-- **Node.js 18+**
-- **pnpm 9+**
-
-### Set up the project
-
-```bash
-git clone https://github.com/Sedimie/Sedim.git
-cd Sedim
-pnpm install
-pnpm build
-```
-
-### Run tests
-
-```bash
-pnpm test                    # all packages
-pnpm --filter @sedim/auth test   # auth module only
-pnpm --filter @sedim/cli test   # CLI only
-```
-
----
-
-## Project Structure
-
-```
-Sedim/
-├── packages/
-│   ├── auth/          — the auth module (v0.2.0)
-│   ├── cli/           — the Sedim CLI engine
-│   └── core/          — shared types used by CLI and modules
-├── apps/
-│   ├── playground/    — fixture apps for testing
-│   └── docs/          — VitePress documentation site
-└── registry/
-    └── auth/latest.json  — module manifest
-```
-
----
-
-## Where things live
-
-| Directory | What it is |
-|----------|------------|
-| `packages/auth/src/core/` | Auth logic: hashing, sessions, tokens, PKCE, TOTP, RBAC, ABAC, JWT, email |
-| `packages/auth/src/adapters/framework/` | Framework adapters: Next.js, Express, Hono |
-| `packages/auth/src/adapters/` | ORM adapters: Drizzle, Prisma |
-| `packages/auth/src/ui/` | React components: forms, auth-client, use-auth hook |
-| `packages/auth/src/ui/themed/` | CSS token files for themed UI (modern, minimal, colorful) |
-| `packages/auth/src/templates/` | Templates with variable substitution for stamped files |
-| `packages/auth/src/schema/` | Database schemas for Drizzle and Prisma |
-| `packages/cli/src/` | CLI commands, detector, thinker, writer, showbaby, config |
-| `registry/auth/latest.json` | Module manifest that describes what gets stamped |
-
----
-
-## How Stamping Works
-
-When a user runs `sedim add auth`, the CLI reads from `packages/auth/src/` and stamps the selected files into the user's project. The user owns those files forever - they are not a runtime dependency.
-
-This means one rule you should never break: **do not add imports from `@sedim/auth` into stamped files**. Stamped files run in the user's project, which may not have `@sedim/auth` installed.
-
----
-
-## How the CLI Works
-
-When you run `sedim add auth`, the CLI moves through four stages:
-
-```
-detector  →  thinker  →  writer
-```
-
-**1. Detector** (`packages/cli/src/detector/`)
-Reads the user's project files and produces a `DetectedContext`: framework, ORM, database, language, module system, and project structure. This is what drives every decision downstream.
-
-**2. Thinker** (`packages/cli/src/thinker/`)
-`load-plan-config.ts` tries to load the module's own `plan-config.ts` via dynamic import. If it exists, it calls `createAuthPlanConfig(ctx, selectedFeatures)` to get a rich, framework-aware plan. If not, it falls back to a generic manifest-based planner.
-
-`build-plan.ts` takes the plan config and selected features and produces an `InstallPlan`: what files to create, what to inject where, what dependencies to install, what env vars to add.
-
-**3. Writer** (`packages/cli/src/writer/`)
-`apply-plan.ts` executes the approved plan. It writes files (`write-file.ts`), injects imports and code snippets (`inject-imports.ts`, `inject-code.ts`), and updates `.env` (`update-env.ts`).
-
-The session (`packages/cli/src/session/`) saves progress after each stage. If the process is interrupted, `sedim continue auth` picks up from where it left off.
-
-**The plan-config is the module interface**
-Each module's `plan-config.ts` is the contract between the module and the CLI. It exports a function that takes `DetectedContext` and `selectedFeatures[]` and returns a `PlanConfig` that describes exactly what to stamp. The CLI never needs to know anything specific about a module - it just reads the plan config and executes it.
-
----
-
-## Ways to Contribute
-
-### Fix a bug
-
-If you found a bug, open an issue with the label `bug`. If you want to fix it yourself:
-
-1. Check the issue to make sure it is confirmed
-2. Fork the repo and create a branch from `main`
-3. Fix it
-4. Run `pnpm biome check .` to check formatting
-5. Open a PR against `main`
-
-### Add a framework adapter
-
-The auth module currently supports Next.js, Express, and Hono. Adding a new framework adapter (e.g., Fastify, SvelteKit) is a great way to expand Sedim's reach.
-
-Steps:
-
-1. Create `packages/auth/src/adapters/framework/<framework>.ts` - look at `express.ts` or `hono.ts` as your reference
-2. Implement the `DatabaseAdapter` interface and wire in all auth operations from `operations.ts`
-3. Add the new framework to the detector in `packages/cli/src/detector/detect-framework.ts`
-4. Add route and middleware templates in `packages/auth/src/templates/`
-5. Test it with a new playground fixture or extend an existing one
-6. Update the manifest in `registry/auth/latest.json`
-
-### Add an ORM adapter
-
-Drizzle and Prisma are currently supported. To add a new ORM (e.g., Prisma but for a different database, or a different ORM library):
-
-1. Create `packages/auth/src/adapters/<orm>.ts`
-2. Implement the `DatabaseAdapter` interface - look at `drizzle.ts` and `prisma.ts` for the shape
-3. Add the new ORM detection in `packages/cli/src/detector/detect-orm.ts`
-4. Add the schema template for the new ORM in `packages/auth/src/schema/`
-5. Test it with the playground fixtures
-6. Update the manifest
-
-### Add a new module
-
-Sedim is designed to support any feature module, not just auth. A module lives in `packages/<module-name>/` with its own `plan-config.ts` that tells the CLI what to stamp.
-
-Steps:
-
-1. Create `packages/<module-name>/src/` with your module source
-2. Create `packages/<module-name>/src/plan-config.ts` exporting `create<ModuleName>PlanConfig`
-3. Create `registry/<module-name>/latest.json` with the module manifest
-4. The CLI will automatically pick it up via `load-plan-config.ts`
-
-See the auth module's `plan-config.ts` as a reference - it maps feature selections to template keys and output paths.
-
-### Add more features to the auth module
-
-You can add to the auth module without building a whole new adapter:
-
-- **New auth provider** (e.g., Apple OAuth, Microsoft OAuth) - add the provider to `framework-config.ts`, add PKCE flow to `operations.ts`, add UI button
-- **New email transport** (e.g., Mailgun, AWS SES beyond the current setup) - extend `email-transport.ts`
-- **New UI component** - add to `packages/auth/src/ui/` and wire it into `plan-config.ts`
-- **New theme variant** - create a new CSS token file in `packages/auth/src/ui/themed/`
-- **New database feature** - add to the schema files in `packages/auth/src/schema/`
-
-Steps:
-
-1. Add the feature code in the appropriate directory
-2. Update `plan-config.ts` to include the new files when the feature is selected
-3. Update `registry/auth/latest.json` if adding new features that change what gets stamped
-4. Add tests
-5. Test with `sedim add auth` in a playground fixture
-
-### Improve the CLI
-
-The CLI is in `packages/cli/src/`. You can work on:
-
-- New commands (`src/commands/`)
-- New detector strategies for frameworks, ORMs, or databases (`src/detector/`)
-- Improving the thinker / planning engine (`src/thinker/`)
-- Improving the writer / file operations (`src/writer/`)
-- Improving the UX, prompts, spinners, and summaries (`src/showbaby/`)
-
-### Improve documentation
-
-The docs live in `apps/docs/`. If you find a broken link, an unclear explanation, or a missing guide, fix it. The docs are just Markdown files - you can edit them directly.
-
-### Improve UI / accessibility
-
-The auth module's UI components are in `packages/auth/src/ui/`. If you want to improve them:
-
-- Accessibility: ARIA labels, keyboard navigation, focus management, screen reader support
-- UX: better error states, loading states, form validation messages
-- Design: visual refinements to the themed components, new theme variants
-
-### Suggest a feature
-
-Open an issue with the label `enhancement` or `feature-request`. Describe what you want to build, why it would be useful, and if possible, how you would approach it. For big features, it's good to discuss before implementing.
-
----
-
-## Playground Fixtures
-
-Fixtures are real apps in `apps/playground/` that the CLI is tested against. Each fixture is a minimal project with a specific stack.
-
-Current fixtures:
-
-| Fixture | Stack |
-|---------|-------|
-| `nextjs-drizzle-ts` | Next.js + Drizzle + TypeScript |
-| `express-prisma-ts` | Express + Prisma + TypeScript |
-| `hono-no-orm-js` | Hono + plain JS, no ORM |
-| `nextjs-existing-auth` | Next.js with existing next-auth (tests conflict detection) |
-
-To add a new fixture:
-
-1. Create the project structure in `apps/playground/<fixture-name>/`
-2. Add a minimal `sedim.config.ts` and the minimum files needed for the framework
-3. Run through the full `sedim add auth` flow to verify it works
-4. Test with `sedim diff auth` and `sedim add auth --dry-run` before running for real
-
-To run a fixture test:
-
-```bash
-# Initialize
-pnpm --filter @sedim/cli exec tsx src/index.ts init --force --cwd apps/playground/nextjs-drizzle-ts
-
-# Preview what would be stamped
-pnpm --filter @sedim/cli exec tsx src/index.ts diff auth --cwd apps/playground/nextjs-drizzle-ts
-
-# Actually stamp
-pnpm --filter @sedim/cli exec tsx src/index.ts add auth --cwd apps/playground/nextjs-drizzle-ts
-```
-
-To reset a fixture:
-
-```bash
-rm apps/playground/<fixture-name>/sedim.config.ts
-rm -rf apps/playground/<fixture-name>/src/sedim/
-```
-
-Do not push any code changes that you do in the playground except setting up a new fixture. It's only for proof of work and testing integration locally instead of having to do npm link each time changes are made.
-
----
-
-## Testing
-
-### Auth module tests
-
-Tests are in `packages/auth/src/__tests__/`. Run them with:
-
-```bash
-cd packages/auth
-pnpm test
-```
-
-To add a new test:
-
-1. Create `packages/auth/src/__tests__/your-feature.test.ts`
-2. Use `mock-db.ts` for the `DatabaseAdapter`
-3. Import from the actual source files, not from stamped paths
-
-### CLI tests
-
-CLI tests are in `packages/cli/src/__tests__/` or similar. Run them with:
-
-```bash
-cd packages/cli
-pnpm test
-```
-
-### TypeScript must pass
-
-Before submitting any PR:
-
-```bash
-cd packages/auth
-npx tsc --noEmit --skipLibCheck
-```
-
-All non-template source must compile without errors. Only files with `{{PLACEHOLDERS}}` (template files) are allowed to have deliberate TS errors.
-
----
-
-## Code Style
-
-- **TypeScript** - strict mode, no `any`, narrow properly
-- **Vitest** for all tests
-- **Biome** for linting and formatting
-
-Run Biome before committing:
-
-```bash
-pnpm biome check .
-pnpm biome format --write .
-```
-
-Biome runs in CI. PRs that fail Biome checks will be blocked.
-
----
-
-## Commit Messages
-
-Use the `[type](scope)` format:
-
-```
-[CLI](commands) : add interactive confirm prompt before stamping
-[AUTH](core) : add Apple OAuth provider support
-[CLI](detector) : add SvelteKit framework detection
-[AUTH](ui) : fix keyboard navigation on LoginForm
-[DOCS] : add guide for setting up OAuth providers
-[PLAYGROUND] : add Fastify fixture
-```
-
-Valid scope options:
-
-| Scope | Where |
-|-------|-------|
-| `core` | packages/auth/src/core/ |
-| `adapters` | packages/auth/src/adapters/ |
-| `ui` | packages/auth/src/ui/ |
-| `templates` | packages/auth/src/templates/ |
-| `schema` | packages/auth/src/schema/ |
-| `plan-config` | packages/auth/src/plan-config.ts |
-| `thinker` | packages/cli/src/thinker/ |
-| `writer` | packages/cli/src/writer/ |
-| `detector` | packages/cli/src/detector/ |
-| `showbaby` | packages/cli/src/showbaby/ |
-| `commands` | packages/cli/src/commands/ |
-| `docs` | apps/docs/ |
-| `registry` | registry/ |
-
----
-
-## Opening an Issue
-
-If you find a bug or want to suggest a feature:
-
-1. Search first to check if it already exists
-2. For bugs: include what you expected, what happened, and steps to reproduce
-3. For features: describe what you want to build and why it would help
-
-Use the issue templates if they are available. Good issues get faster responses.
-
----
-
-## Opening a Pull Request
-
-1. Fork the repo and create a branch from `main`
-2. Run `pnpm biome check .` and fix any issues
-3. Make your changes
-4. Test them - run the relevant fixture or tests
-5. Push and open a PR against `main`
-6. Describe what changed and why in the PR body
-
-For big changes (a new framework adapter, a new module, a significant feature), open an issue first to discuss before doing the work. This saves you from building something that might need a different approach.
-
-PRs are reviewed within a few days.
-
----
-
-## Questions?
-
-Open an issue at https://github.com/Sedimie/Sedim or drop a message on Discord.
-
----
-
-*Last updated: 2026-05-24*

package/README.md

@@ -1,299 +0,0 @@
-# Sedim
-
-[![Discord](https://img.shields.io/discord/1507846093105397993?color=7289DA&logo=discord&logoColor=white&label=discord)](https://discord.com/invite/H7yutstM)
-[![GitHub Stars](https://img.shields.io/github/stars/Sedimie/Sedim?style=flat&logo=github)](https://github.com/Sedimie/Sedim)
-[![npm downloads](https://img.shields.io/npm/dw/@sedim/cli?label=weekly%20downloads)](https://www.npmjs.com/package/@sedim/cli)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)
-
-**Install complete features. Own every line.**
-
-Sedim is an open-source codegen CLI that stamps full-stack modules into your project, with out of the box working defaults. No runtime dependencies, no black boxes - every stamped file is readable, editable, and owned by you. Skip the 80% work done repetitively for just the 20% customizations on top.
-
-```bash
-npm install -g @sedim/cli
-
-sedim init         # detects your stack
-sedim add auth     # stamps auth into your project
-```
-
-The first POC for the stamping model is the Auth Module. Currently supports NextJS (full stack), Hono and Express (with React and Vue frontends).
-
----
-
-## See It In Action
-
-[![Sedim Full Walkthrough](https://img.youtube.com/vi/HPEjs7-O_vk/maxresdefault.jpg)](https://youtu.be/HPEjs7-O_vk)
-
-> 10-minute walkthrough - init, auth install, OAuth, TOTP, UI themes, and customization.
-
----
-
-## Quick Start
-
-**Requirements:** Node ≥ 18, an existing project with a supported framework and ORM.
-
-### 1. Install the CLI
-
-```bash
-npm install -g @sedim/cli
-```
-
-### 2. Initialise your project
-
-```bash
-cd my-project
-sedim init
-```
-
-Sedim detects your framework, ORM, and language and writes a `sedim.config.ts`. If anything is detected incorrectly, edit the config file directly.
-
-### 3. Add auth
-
-```bash
-sedim add auth
-```
-
-> Before writing the module directly, you can also run `plan`, `diff`, or `--dry-run` commands for the module!
-
-The CLI walks you through:
-
-- **Environment detection**: confirms your framework, ORM, and language
-- **Feature selection**: email/password, OAuth providers, TOTP, magic links, JWT, RBAC/ABAC
-- **Frontend style**: headless, Tailwind styled, or themed with CSS tokens
-- **Confirm the plan**: review exactly what files will be stamped before anything is written
-- **Stamp**: files land in `src/sedim/auth/`
-- **Environment variables**: add them on the spot or copy the printed list to your `.env`
-
-### 4. Migrate and run
-
-```bash
-# Drizzle
-npx drizzle-kit push
-
-# or Prisma
-npx prisma migrate dev --name add_auth
-
-npm run dev
-```
-
----
-
-## What Gets Stamped
-
-Running `sedim add auth` generates this structure in your project. You own every file.
-
-The exact files that get stamped depend on the features you select during `sedim add auth` - OAuth providers, TOTP, magic links, JWT, and UI tier all gate which files are written. The structure below shows the full set of possible files; your install will include only the ones your selections require.
-
-```
-src/sedim/auth/
-├── core/
-│   ├── hash-password.ts      - Argon2id password hashing
-│   ├── generate-token.ts     - session tokens, OTP codes, backup codes, PKCE verifiers
-│   ├── session.ts            - session building and sliding-window validation
-│   ├── pkce.ts               - RFC 7636 PKCE (S256 only)
-│   ├── totp.ts               - RFC 6238 TOTP (Google Authenticator compatible)
-│   ├── totp-crypto.ts        - AES-256-GCM encryption for TOTP secrets
-│   ├── rate-limit.ts         - sliding-window rate limiter
-│   ├── rbac.ts                - role-based access control
-│   ├── abac.ts                - attribute-based access control
-│   ├── jwt.ts                 - hybrid JWT (short-lived signed + DB-backed refresh)
-│   ├── oidc.ts                - OIDC discovery and id_token validation
-│   └── email-transport.ts     - multi-transport email (nodemailer/resend/postmark/ses)
-├── adapters/
-│   ├── framework/
-│   │   ├── nextjs.ts          - Next.js App Router handler factory
-│   │   ├── express.ts         - Express router
-│   │   ├── hono.ts            - Hono route registration
-│   │   ├── operations.ts      - all auth operations (login, signup, OAuth, TOTP, etc.)
-│   │   └── framework-config.ts - OAuth provider configuration
-│   ├── drizzle.ts             - Drizzle ORM adapter
-│   ├── prisma.ts              - Prisma ORM adapter
-│   └── types.ts               - DatabaseAdapter interface and types
-├── ui/
-│   ├── auth-client.ts          - client-side auth fetch utilities
-│   ├── use-auth.ts             - React hook for auth state
-│   ├── headless/              - unstyled, logic-only components
-│   │   ├── LoginForm.tsx
-│   │   ├── SignupForm.tsx
-│   │   ├── ForgotPasswordForm.tsx
-│   │   ├── ResetPasswordForm.tsx
-│   │   ├── MagicLinkForm.tsx
-│   │   ├── OAuthButton.tsx
-│   │   └── TotpVerifyForm.tsx
-│   ├── tailwind/               - Tailwind-styled components
-│   └── themed/                 - pre-built themes with CSS tokens
-│       ├── modern-tokens.css   - glassmorphism theme
-│       ├── minimal-tokens.css  - neumorphism theme
-│       └── colorful-tokens.css - neubrutalism theme
-├── emails/
-│   └── email-verification.ts   - email template for verification
-├── schema.ts                   - Drizzle schema (users, sessions, oauth_accounts, etc.)
-└── index.ts                    - module barrel export
-```
-
-The stamped auth route handler lands at `src/app/api/auth/[...all]/route.ts` (Next.js) or equivalent for other frameworks.
-
----
-
-## Auth Module
-
-Auth is the first Sedim module. It ships with everything, none of it is a black box.
-
-### Features
-
-| Feature | Detail |
-|---|---|
-| **Password auth** | Argon2id (OWASP params), account lockout after 10 failed attempts |
-| **Session management** | SHA-256 hashed tokens, httpOnly cookies, full revocation |
-| **OAuth** | Google, GitHub, Discord: PKCE (RFC 7636) on all flows |
-| **TOTP** | RFC 6238, AES-256-GCM encrypted secrets at rest, backup codes |
-| **Magic links** | No email enumeration, supports SMTP / Resend / Postmark / SES |
-| **JWT** | Hybrid: short-lived signed JWTs + DB-backed refresh tokens |
-| **RBAC / ABAC** | Role and attribute-based access control middleware |
-| **Rate limiting** | Sliding window, in-memory or Redis store |
-
-### Stack Support
-
-| Framework | Drizzle | Prisma |
-|-----------|:-------:|:------:|
-| Next.js (App Router) | ✓ | ✓ |
-| Express | ✓ | ✓ |
-| Hono | ✓ | ✓ |
-
-| Email provider | Supported |
-|---|:---:|
-| Nodemailer (SMTP) | ✓ |
-| Resend | ✓ |
-| Postmark | ✓ |
-| AWS SES | ✓ |
-
-### UI Tiers
-
-Three levels so you use your own design system or ship immediately.
-
-**Headless** - zero CSS, pure logic and markup. Bring your own styles.
-
-**Tailwind** - fully styled with Tailwind classes, works with your existing Tailwind config.
-
-**Themed** - pre-built themes with CSS tokens. Currently ships `minimal` and `glass`.
-
-### Environment Variables
-
-```bash
-# Required
-AUTH_SECRET=                    # min 32 chars, used for session signing
-DATABASE_URL=                   # your database connection string
-
-# OAuth - add only the providers you selected
-GOOGLE_CLIENT_ID=
-GOOGLE_CLIENT_SECRET=
-GITHUB_CLIENT_ID=
-GITHUB_CLIENT_SECRET=
-DISCORD_CLIENT_ID=
-DISCORD_CLIENT_SECRET=
-
-# Email - add only the provider you selected
-SMTP_HOST=
-SMTP_PORT=
-SMTP_USER=
-SMTP_PASS=
-RESEND_API_KEY=
-POSTMARK_API_KEY=
-AWS_ACCESS_KEY_ID=
-AWS_SECRET_ACCESS_KEY=
-AWS_SES_REGION=
-
-# Optional
-REDIS_URL=                      # if using Redis for rate limiting or sessions
-TOTP_ENCRYPTION_KEY=           # required if TOTP is enabled, 32-byte hex
-```
-
----
-
-## Architecture
-
-Sedim uses a **stamp model**, not a runtime SDK:
-
-```
-sedim add auth  →  generates files into src/sedim/auth/
-                   (standalone forever, no sedim dependency at runtime)
-```
-
-The CLI has four components:
-
-| Component | What it does |
-|---|---|
-| **Detector** | Reads your project, framework, ORM, language, existing config |
-| **Planner (Thinker)** | Combines the module manifest with your feature selections into a stamp plan |
-| **Writer** | Executes the plan, generates files, migrations, env var list |
-| **Showbaby** | Shows you exactly what was stamped and what to do next |
-
-Every module is described by a **manifest** (`registry/<module>/latest.json`) - a declarative spec of every file the module can stamp, what features gate each file, and what environment variables are required. The CLI reads the manifest, applies your choices, and stamps only what you need.
-
-### Flow
-
-```
-Developer runs "sedim add auth"
-        ↓
-    Detector → identifies framework, ORM, language
-        ↓
-    Thinker  → loads registry manifest + module plan-config
-               + feature selections → InstallPlan
-        ↓
-    Writer   → stamps files to src/sedim/auth/
-               → writes migrations
-               → lists env vars
-        ↓
-    Showbaby → confirms what was written + next steps
-```
-
-The module source lives in `packages/<module>/src/` - this is where auth logic, UI components, adapters, and templates live. The CLI reads from here when stamping. `packages/core/` holds shared TypeScript types used by both the CLI and all modules.
-
----
-
-## Registry
-
-Module manifests live in the [`registry/`](https://github.com/Sedimie/Sedim/tree/main/registry) directory. The CLI uses the local registry during development and falls back to the GitHub raw URL for published releases.
-
-**Available modules:**
-
-| Module | Status |
-|---|---|
-| `auth` | Available |
-| `notifications` | On the roadmap |
-| `chat` | On the roadmap |
-| `WebRTC` | On the roadmap |
-| `WalletAdapters` | On the roadmap |
-| `ai-rag` | On the roadmap |
-| `payments` | On the roadmap |
-
----
-
-## Philosophy
-
-Most tools give you an API to call. Customization is what's keeping modularizing full stack features at bay, but with the codegen model, you own the code, and hence customize it however much you want. This is not just a library to cut your grunt work - you can learn the overall implementations it uses to be able to basically use the full stack features as boilerplate code.
-
-When you run `sedim add auth`, you get the auth system, not a dependency on one. The files live in your repo, show up in your git history, and bend to whatever you need them to do. Sedim writes the first version. Everything after that is yours.
-
-*The best code is code you own.*
-
-AI Agentic coding is another thing that this might clash with, but an AI tool might hallucinate and give 90% accuracy, leave out security considerations and make it tough to customize while also using up 3 hours and a considerable amount of tokens. This allows you to skip directly to the customizations part, with 100% hit-rate since it's static codegen, and 0 cost for the grunt work with upto date security standards being followed. Use AI tools on top of this to speed you up and make your workflow unbelievably fast.
-
----
-
-### Check out the docs
-
-Full documentation - customization guides, adapter references, module authoring, and escape hatches - is at [sedim.dev/docs](https://sedim.dev/docs).
-
-### Contributions
-
-To add a framework adapter, ORM adapter, or new module, see [CONTRIBUTING.md](./CONTRIBUTING.md).
-
-The module spec and adapter interface are documented there - adding a new adapter for a supported module takes a few hours once you understand the pattern.
-
-### Watch the Full Walkthrough
-
-[![Sedim Full Walkthrough](https://img.youtube.com/vi/HPEjs7-O_vk/maxresdefault.jpg)](https://youtu.be/HPEjs7-O_vk)
-
-> 10-minute walkthrough - init, auth install, OAuth, TOTP, UI themes, and customization.
-> [Watch on YouTube](https://youtu.be/HPEjs7-O_vk)