@mostajs/orm-cli 0.6.4 → 0.7.0

package/CHANGELOG.md

@@ -0,0 +1,474 @@
+# Changelog
+
+All notable changes to `@mostajs/orm-cli` will be documented in this file.
+
+## [0.7.0] — 2026-06-15
+
+### Added — Mongo migration trio : `mongo-introspect` · `validate` · `fix-ids`
+
+Three commands turn a live Mongo project into a data-plug one, using the ORM's
+own mongo dialect (which normalizes `_id`→`id`, ids as strings, every dialect) :
+
+- **`mostajs mongo-introspect`** (`bin/mongo-introspect.mjs`, menu `m`) — *migrer* :
+  connects to a live MongoDB, samples docs per collection, infers `EntitySchema[]`
+  (types, `required`, real indexes, `timestamps`; `_id`/`__v` dropped, ObjectId →
+  `string`) and writes `.mostajs/generated/entities.json` — so a Mongo project with
+  no Prisma/OpenAPI schema can adopt `@mostajs/orm`. Uses `$SGBD_URI` by default.
+- **`mostajs validate`** (`bin/validate.mjs`, menu `v`) — *valider* : runs the
+  published `@mostajs/orm/validator` (ORMConceptValidator, rules R001–R021) over
+  `entities.json` with text/json/markdown reporters, `--src` for cross-file rules,
+  and a `--ci`/`--max-warnings` gate.
+- **`mostajs fix-ids`** (`bin/fix-mongo-id.mjs`, menu `f`) — *corriger* : see below.
+- **`mostajs load-data`** (menu `l`) — *charger* : `.env`-piloted cross-dialect data
+  load. Thin DELEGATE to `@mostajs/orm-copy-data`'s new `mostajs-load` bin (where the
+  feature lives) — picks one of four sources (live Mongo · mongodump+mongorestore ·
+  JSON · SQL), reads the destination from `.env` (`DB_DIALECT`/`SGBD_URI`, MOSTA_ENV
+  cascade), and calls `copyData()`. Schemas from `entities.json` (chain with
+  `mongo-introspect`). NB : for large collections use `--batch-size ≥ collection size`
+  (a skip/limit pagination instability in copy-data's db-loader can otherwise re-read
+  rows → duplicate-PK errors ; copy-data's writer now surfaces the first error).
+
+### Added — `mostajs fix-ids` : Mongo → data-plug code repair codemod
+
+New codemod (`bin/fix-mongo-id.mjs`, menu `f`, subcommand `fix-ids`) that repairs
+the residue a Mongoose → `@mostajs/orm` migration leaves in **application code**.
+The ORM normalizer maps `_id`→`id` and exposes ids as plain strings for **every
+dialect, MongoDB included** — so the app must read `obj.id`, never `obj._id`, and
+must stop wrapping ids in `ObjectId`. The codemod, conservative and reversible:
+
+- renames member access `obj._id` / `obj?._id` / `obj['_id']` → `obj.id`
+  (object **keys** like a schema's `_id:` declaration are left intact) ;
+- unwraps `new ObjectId(x)` / `mongoose.Types.ObjectId(x)` / `Types.ObjectId(x)`
+  → `x` (balanced-paren aware) ;
+- reports `ObjectId.isValid(...)` and `ObjectId` imports for manual review ;
+- skips files importing `mongoose` (real models) unless `--include-mongoose` ;
+- dry-run by default ; `--apply` writes with `*.mongoid.bak` backups ;
+  `--restore --apply` reverts. Extra `--map old:new` for custom member renames.
+
+Usage : `mostajs fix-ids` (preview) · `mostajs fix-ids --apply` · `--restore --apply`.
+
+## [0.5.10] — 2026-04-15
+
+### Changed — `'*'` kept literal in tree for dynamic resolution
+
+Previous behaviour (0.5.9) expanded `'*'` into the entity list from
+`entities.json` at config time. Problem : if you add a table later, the
+rule stays frozen on the old list. Fix requires re-running menu r → 6.
+
+Now `'*'` is stored **verbatim** in the tree. The `services/replicator.mjs`
+generated by `@mostajs/replicator@0.2.2+` resolves the wildcard at every
+sync tick by introspecting the master DB catalogue — so new tables are
+replicated automatically.
+
+Prompt text updated to make the behaviour explicit :
+
+```
+  Collections : '*' = all tables of the master DB — resolved LIVE at
+                each sync tick from the master's table catalogue
+                (so new tables added later are picked up automatically).
+```
+
+## [0.5.9] — 2026-04-15
+
+### Added — menu `r → 6` accepts `*` for full-DB replication
+
+Previously the user had to list every collection manually
+(`User,Member,Payment,…`). Now the prompt defaults to `*` which expands
+into the full list of entity names read from
+`.mostajs/generated/entities.json`. The tree.json stays self-contained
+(explicit list, not a wildcard) so the emitted `replicator.mjs` doesn't
+need any special-case handling — it iterates the same way whether you
+picked all 40 or just 2 entities.
+
+```
+? Collections  [*]:
+  ✓ expanded '*' → 40 tables from entities.json
+     User, Profile, Session, Member, Note, SubscriptionPlan, …
+```
+
+Fallback : if `entities.json` is missing or empty, the wildcard is kept
+as-is and a warning recommends running menu 1 (Convert) first.
+
+## [0.5.8] — 2026-04-15
+
+### Fixed — menu `r → s` scaffold crash on force-overwrite
+
+Bash `${var:+true}${var:-false}` substitution produced `true--force` when
+the user answered "yes" to "Overwrite existing services/*.mjs?", which
+generated invalid JavaScript (`force: true--force`) → both scaffolders
+threw SyntaxError. `services/*.mjs` were never written, then `dev:all`
+crashed with `MODULE_NOT_FOUND`.
+
+Now the shell passes `FORCE=true|false` via env var to the Node snippet,
+and the snippet uses `process.env.FORCE === 'true'`.
+
+## [0.5.7] — 2026-04-15
+
+### Fixed — menu `r → m` proposes restart when a monitor is already running
+
+Previously the menu printed `Monitor already running at …` and returned,
+leaving the user stuck with an old (possibly pre-0.2.0) monitor process
+showing a stale / empty dashboard. Now the user is prompted :
+
+```
+Monitor already running (pid=12345) at http://127.0.0.1:14499
+? Restart it now? (picks up recent tree-file changes) [y/N]:
+```
+
+Answering `y` kills the old process and spawns a fresh one against the
+latest tree. `n` keeps the existing instance and just re-opens the URL.
+
+## [0.5.6] — 2026-04-15
+
+### Fixed — state loss across menu actions
+
+Root cause : `ReplicationManager.saveToFile()` masks credentials in the
+tree JSON (`oracle://user:***@host`), and `loadFromFile()` can't then
+rebuild the live manager — every subsequent `getReplicaStatus()` returned
+an empty array, making it look like replicas had disappeared.
+
+Also : adding a slave with a dialect whose driver isn't installed
+(`better-sqlite3`, `oracledb`, etc.) threw at `addReplica()` time before
+state could be persisted, preventing experimental topologies from being
+saved.
+
+**Fix** : the menu no longer routes add/list/remove/set-routing/add-rule/
+remove-rule actions through the live `ReplicationManager`. Instead it
+reads and writes the tree JSON directly (via new `_tree_patch`
+helper), preserving URIs verbatim. The services (`replicator.mjs` +
+`monitor.mjs` scaffolded via menu `r → s`) still use the real lib for
+actual sync/monitoring work.
+
+Side benefits :
+- No DB driver required just to *register* a slave in the config
+- Credentials preserved (no masking) so `loadFromFile` in services can
+  reconnect — `.mostajs/replicator-tree.json` should be in `.gitignore`
+  (ensured by `mostajs init`).
+
+## [0.5.5] — 2026-04-15
+
+### Fixed — Replicator menu : smart project picker
+
+Every replicator action that asked for a project name was hard-coded to
+default to `'default'`, even when the tree-file had `'fitzone'` registered.
+Result : after adding a replica to `fitzone`, listing replicas
+(`menu r → 2`) showed an empty list because the user pressed Enter and
+got `default`.
+
+New `_pick_project` helper :
+- Reads `.mostajs/replicator-tree.json` and lists known projects
+- Defaults to the first one (or `'fitzone'` if empty)
+- When >1 projects exist, displays them inline above the prompt
+- Used by Add / List / Promote / Remove / Set-routing actions
+
+## [0.5.4] — 2026-04-15
+
+### Fixed — Menu `r → 1` (Add replica) UX
+
+- **Clearer prompts.** The previous prompts ("Project name", "Replica name")
+  were ambiguous — a user reported typing a full URI into the project name
+  and hitting `Projet "…" introuvable dans ProjectManager`.
+  Prompts now include hints and examples, and the dialect prompt lists the
+  13 supported options inline.
+- **Auto-register the project.** `rm.addReplica('fitzone', …)` requires the
+  project to exist in `ProjectManager` — previously the user had to run
+  something else first. The CLI now calls `pm.addProject({ name, dialect,
+  uri, schemas: [] })` behind the scenes when the project is missing, using
+  the replica's own dialect/uri as the baseline config (typically the master).
+- **Basic input validation** rejects project/replica names that look like
+  URIs or paths.
+
+## [0.5.3] — 2026-04-15
+
+### Added — Menu `r → s) Scaffold services`
+
+One-shot bootstrap for background replicator + monitor processes :
+
+1. Calls `scaffoldReplicatorService()` from `@mostajs/replicator@0.2.0+` →
+   emits `services/replicator.mjs` (sync loop reading .env + tree.json).
+2. Calls `scaffoldMonitorService()` from `@mostajs/replica-monitor@0.2.0+` →
+   emits `services/monitor.mjs` (read-only tree-backed dashboard).
+3. Patches `package.json` scripts (only adds keys that don't already exist) :
+   - `replicator`  : `node services/replicator.mjs`
+   - `monitor`     : `node services/monitor.mjs`
+   - `dev:all`     : `concurrently --names next,rep,mon -c blue,magenta,cyan "npm:dev" "npm:replicator" "npm:monitor"`
+4. Installs `concurrently` as devDependency if missing (Braille spinner UX).
+
+After scaffold : `npm run dev:all` launches the three processes in parallel
+with coloured per-stream prefixes. Monitor opens on `http://localhost:14499`.
+
+### Design
+
+Each lib owns its own template — orm-cli is just the orchestrator. When a
+scaffolder evolves (new config, new env var), the emitted file moves in
+lockstep with the lib version.
+
+## [0.5.2] — 2026-04-15
+
+### Added
+
+- **Menu `r → m) Open monitor`** — spawns
+  [`@mostajs/replica-monitor`](https://www.npmjs.com/package/@mostajs/replica-monitor)
+  in background and opens the dashboard in the default browser :
+  - auto-installs `@mostajs/replica-monitor` if missing
+  - port + token prompted (default `14499`, no auth)
+  - pid tracked in `.mostajs/monitor.pid`, logs to `.mostajs/monitor.log`
+  - idempotent : if a monitor is already running, just re-opens the URL
+  - launcher : `xdg-open` (Linux) / `open` (macOS)
+  - stop with `kill $(cat .mostajs/monitor.pid)`
+
+## [0.5.1] — 2026-04-15
+
+### Added — Replicator menu (`r`)
+
+- **Menu `r) Replicator`** — thin CLI wrapper around
+  [`@mostajs/replicator`](https://www.npmjs.com/package/@mostajs/replicator).
+  State is persisted to `.mostajs/replicator-tree.json` (auto-loaded at menu
+  start, auto-saved after each mutating action).
+- Actions exposed :
+  1. **Add replica** (master / slave) to a project (dialect, URI, pool,
+     lag tolerance).
+  2. **List replicas** with role + live lag.
+  3. **Promote a slave to master** (failover).
+  4. **Remove a replica**.
+  5. **Set read-routing strategy** (`round-robin` / `least-lag` / `random`).
+  6. **Add CDC rule** (source → target, mode `snapshot` / `cdc` /
+     `bidirectional`, collections, conflict resolution).
+  7. **List CDC rules**.
+  8. **Run a CDC sync** + show stats (inserted / updated / deleted / failed).
+  9. **Remove a CDC rule**.
+  - **`v`** view the raw tree file (pretty-printed with `jq` when available).
+  - **`c`** clear (delete tree file — destructive, confirms).
+- Auto-installs `@mostajs/replicator` + `@mostajs/mproject` if missing
+  (uses the existing `ensure_pkg` Braille spinner UX from 0.4.6).
+
+## [0.5.0] — 2026-04-15
+
+### Added — `mostajs init` + `mostajs migrate` subcommands (Sprint 3)
+
+- **`mostajs init [--dialect sqlite|postgres|…] [--uri URI] [--force]`**
+  Scaffolds a fresh bridge-ready project in PROJECT_ROOT :
+  - `.env`  (PORT=3000, DB_DIALECT, SGBD_URI, DB_SCHEMA_STRATEGY, NEXTAUTH_URL,
+    AUTH_SECRET auto-generated via `crypto.randomBytes`)
+  - `.mostajs/config.env`  (mirror consumed by the seed-runner)
+  - `.mostajs/generated/entities.json`  (empty array, filled by menu 1)
+  - `prisma/schema.prisma`  (minimal `User` model — provider auto-mapped :
+    `postgres → postgresql`, `mssql → sqlserver`, `mariadb → mysql`)
+  - `src/lib/db.ts`  (the 3-line `createPrismaLikeDb` bridge)
+  Refuses to overwrite existing files unless `--force`.
+
+- **`mostajs migrate <diff | apply | status>`** — incremental DDL diff.
+  Compares `entities.json` to the live DB's column catalogue (via dialect
+  `getExistingColumns`) and :
+  - **`diff`**   : prints the ALTER TABLE statements needed to make the live
+    DB match the schema.
+  - **`apply`**  : executes those ALTERs (confirmation prompt, or `--yes` to
+    skip). Reports `N ok, M failed`.
+  - **`status`** : per-entity summary `✓ / ⚠ missing N cols / ✗ table missing`
+    + global counter.
+
+  Validated end-to-end on the FitZoneGym fixture (Oracle, 40 entities) :
+  detected 3 missing inverse-1:1 FK columns, ALTERed them, subsequent diff
+  returned `✓ Schema is up to date`.
+
+### Fixed
+
+- **`load_env` preserves existing env vars.** Pre-0.5.0, `load_env` did
+  `set -a; source config.env; set +a` — which overwrote any CLI-provided
+  `DB_DIALECT=… mostajs migrate` env, breaking multi-DB workflows. Now
+  parses `.mostajs/config.env` line-by-line and only exports keys not
+  already set in the process environment.
+- **`PROJECT_ROOT` is now overridable.** `PROJECT_ROOT=/path/to/target
+  mostajs init` previously ignored the override (hardcoded `$(pwd)`).
+  Now uses `"${PROJECT_ROOT:-$(pwd)}"` so automated tests and scripts
+  can target arbitrary directories.
+
+## [0.4.7] — 2026-04-15
+
+### Added — Export entities menu
+
+- **Menu `e`) Export entities** — interactive picker that converts the
+  project's `entities.json` into another schema format using
+  `@mostajs/orm-adapter@0.6.0+` reverse adapters :
+  - `1) Prisma`        → `prisma/schema.prisma`
+  - `2) JSON Schema`   → `schema.json` (2020-12)
+  - `3) OpenAPI 3.1`   → `openapi.json`
+  - `4) Native (TS)`   → `src/schemas.ts` (`export const schemas: EntitySchema[]`)
+- Output path is configurable at prompt time. Parent directory is
+  auto-created if missing.
+
+## [0.4.6] — 2026-04-15
+
+### Fixed
+
+- **`ensure_pkg` now shows a live spinner** while npm/pnpm/yarn/bun installs
+  missing packages. Pre-0.4.6 the install ran inside `... 2>&1 | tail -5`,
+  which buffers all output until completion — leaving the user staring at
+  a blank line for 1-2 minutes with no feedback. Now a Braille spinner +
+  elapsed seconds tick every 200ms while the install runs in background.
+
+## [0.4.5] — 2026-04-15
+
+### Added — Drop table(s) action in seed menu
+
+- **Menu S → d) Drop table(s)** — interactive picker that lists the live
+  tables (intersected with the project's entities — junction tables
+  included), lets the user pick one / many / all, asks for explicit
+  `DROP` typing as confirmation, then issues `dialect.dropTable()` for
+  each. Useful when a legacy schema has incompatible NOT NULL columns
+  that ALTER cannot reconcile (e.g. the `users.firstName` Prisma legacy
+  refactored out of the new schema). Drop + menu 3 (init) recreates the
+  table cleanly so menu S → 4 (apply) succeeds.
+
+## [0.4.4] — 2026-04-14
+
+### Added — seed-aware codemod + new menu actions
+
+- **`install-bridge` skips seed scripts by default.** Files matching
+  `**/seeds/**`, `**/seeders/**`, `**/fixtures/**`, `**/seed-*.{ts,js}`,
+  `**/seeder-*.{ts,js}` or `prisma/seed.{ts,js}` are now **preserved** instead
+  of being rewritten to a 2-line `createPrismaLikeDb()` stub. These files are
+  usually standalone scripts that create their own Prisma client inline —
+  rewriting them destroys their logic.
+  ```bash
+  # legacy behavior (if you really want it)
+  mostajs install-bridge --apply --rewrite-seeds
+  ```
+- **`install-bridge --restore-seeds`** — restores only seed-like `.prisma.bak`
+  files. Useful when a previous run of `install-bridge` (pre-0.4.4) destroyed
+  your seed scripts :
+  ```bash
+  mostajs install-bridge --restore-seeds --apply
+  ```
+- **Menu S → r)** — interactive version of `--restore-seeds` with a dry-run
+  preview before applying.
+- **Menu S → s)** — **Run seed scripts**. Auto-detects `prisma/seed.ts`,
+  `scripts/seed.ts`, `scripts/seed-*.ts` (and `.js` variants) and runs them
+  with `tsx` (or `npx tsx`). Preserves the `a` option to run all sequentially.
+
+### Fixed
+
+- **`walk()` now yields `.prisma.bak` files** so `--restore` actually finds
+  backups to restore (the pre-0.4.4 version filtered by extension and
+  silently missed every `.bak`, leaving the feature non-functional).
+- **Seed validator recognises relation FK columns.** Fields declared via a
+  relation `joinColumn` (e.g. `User.profile → profileId`, `UserRole.user →
+  userId`) no longer trigger spurious `unknown field` warnings when present
+  in seed JSONs. The validator now accepts : explicit fields + relation
+  names + resolved `joinColumn` (or conventional `<relation>Id` fallback).
+
+## [0.4.3] — 2026-04-14
+
+### Added
+
+- **`bootstrap` now asks for the database.** Instead of silently writing
+  `DB_DIALECT=sqlite` / `SGBD_URI=./data.sqlite`, bootstrap now presents an
+  interactive picker covering the 13 supported dialects, with a sensible
+  example URI for each. Users who want SQLite still type Enter.
+- **Non-interactive flags** for CI / scripting :
+  ```
+  mostajs bootstrap --dialect=postgres --uri=postgres://... --strategy=update
+  ```
+  Also honours `DB_DIALECT` / `SGBD_URI` environment variables if present.
+- **Existing `.mostajs/config.env` is honoured** with no prompt — so a user
+  who runs `mostajs` menu 2 (Configure database URIs) first then runs
+  `bootstrap` flows smoothly into DDL init without being re-asked.
+
+### Fixed
+
+- **Cosmetic bug in the success banner** — the final line used an escaped
+  shell substitution (`\$(...)`) which printed literally instead of being
+  expanded. Replaced with direct `$DB_DIALECT` / `$SGBD_URI` variables.
+
+## [0.4.2] — 2026-04-14
+
+### Fixed
+
+- Codemod no longer emits `import 'server-only'` in the generated `db.ts`
+  template. The guard crashed apps that still use the Next.js `pages/`
+  directory alongside `app/` (FitZoneGym-style mixed projects). The lazy
+  dialect loading in `@mostajs/orm@1.9.3+` makes the guard redundant for
+  correctness.
+
+## [0.4.1] — 2026-04-14
+
+### Fixed — `mostajs bootstrap` reliability
+
+- **Hard stop-on-error** : each step now verifies its outcome and aborts
+  with an actionable message instead of silently continuing. Previous
+  behaviour printed a success banner even when convert/DDL had failed.
+- **Install `@mostajs/orm-adapter`** alongside `@mostajs/orm` / `-bridge` /
+  `server-only` in step 2. Without the adapter, step 3 (schema conversion)
+  was failing silently on a fresh project. Root cause : 0.4.0 only
+  installed the runtime packages, not the build-time adapter.
+- **Visible npm output** : step 2 no longer pipes through `tail -3`. Users
+  can see the installer progress, which matters on slow networks.
+- **Reload config.env** : after writing the default config, reload env
+  vars so `action_init_dialects` sees `DB_DIALECT=sqlite` + `SGBD_URI`.
+
+## [0.4.0] — 2026-04-14
+
+### Added — the automated migration release
+
+- **`mostajs install-bridge`** : codemod that scans a Prisma project, finds
+  every `new PrismaClient(...)` instantiation site, and rewrites each file
+  to use `createPrismaLikeDb()` from `@mostajs/orm-bridge`. Preserves the
+  original export name (`prisma`, `db`, `client`, `default`), so none of
+  the call-sites elsewhere in the codebase have to change.
+
+  Dry-run by default. Flags :
+  - `--apply`             actually write files
+  - `--file <path>`       restrict to a single file
+  - `--project <root>`    override working directory
+  - `--restore --apply`   revert .prisma.bak backups
+
+  Example :
+  ```
+  $ mostajs install-bridge
+  ▶ mostajs install-bridge — scanning /home/me/my-app
+  Found 3 PrismaClient instantiation site(s):
+    → src/lib/db.ts         (const db)
+    → src/server/prisma.ts  (const prisma)
+    → scripts/seed.ts       (const prisma)
+  Dry-run — no files written. Re-run with --apply to execute.
+
+  $ mostajs install-bridge --apply
+  ✓ rewrote src/lib/db.ts  (backup: src/lib/db.ts.prisma.bak)
+  ✓ rewrote src/server/prisma.ts  (backup: …)
+  ✓ rewrote scripts/seed.ts  (backup: …)
+  ```
+
+- **`mostajs bootstrap`** : one-shot full migration for a Prisma project.
+  Runs the codemod, installs runtime deps, converts `schema.prisma` to
+  `entities.json`, writes `.mostajs/config.env`, and applies DDL. Zero
+  manual file edits required after this point.
+
+  ```
+  $ cd my-prisma-app
+  $ npx @mostajs/orm-cli bootstrap
+  ▶ Step 1/4 : rewrite PrismaClient sites
+    ✓ rewrote src/lib/db.ts (backup: src/lib/db.ts.prisma.bak)
+  ▶ Step 2/4 : install runtime deps
+    added 42 packages in 3s
+  ▶ Step 3/4 : convert schema + init DDL
+    ✓ 18 entities extracted
+    ✓ 18 tables created in ./data.sqlite
+  ▶ Step 4/4 : done
+  ```
+
+- **Interactive menu entries** : `b` (Bootstrap) and `i` (Install bridge)
+  for users who prefer the menu flow.
+
+### Why this matters
+
+Before 0.4.0, migrating a Prisma project required hand-editing every
+`db.ts`-style file. For a project like FitZoneGym (15 instantiation
+sites across `src/` and `scripts/`), that was 15 error-prone edits.
+With `install-bridge`, the same migration takes one command and is
+reversible with `--restore --apply`.
+
+## [0.3.2] and earlier
+
+See git history. Covers the interactive menu, Prisma/OpenAPI/JSON Schema
+conversion, seeding pipeline (hash + validate + apply), health checks,
+subcommands `convert`, `hash`, `verify`, `diagnose`, `health`, `detect`.