@lenne.tech/cli 1.35.1 → 1.37.0

package/docs/commands.md

@@ -14,6 +14,7 @@ This document provides a comprehensive reference for all `lt` CLI commands. For
 - [CLI Commands](#cli-commands)
 - [Server Commands](#server-commands)
 - [Local Development Commands](#local-development-commands)
+- [Ticket Commands](#ticket-commands)
 - [Ports Commands](#ports-commands)
 - [Git Commands](#git-commands)
 - [Fullstack Commands](#fullstack-commands)
@@ -488,6 +489,27 @@ Sends `SIGTERM` to the detached process group (negative PID) so descendants —
 
 ---
 
+### `lt dev prune`
+
+Remove the leftovers that accumulate around parallel ticket work.
+
+**Usage:**
+```bash
+lt dev prune             # interactive (confirms DB drops, default yes)
+lt dev prune --dry-run   # show the plan, change nothing
+lt dev prune --noConfirm # documented default without a prompt
+```
+
+Collects three classes of orphans:
+
+1. **Orphaned ticket databases** of the current project — `<base>-<id>` (+`-test`, `-test-<n>`) whose ticket has neither a live worktree nor a live registry entry. Ticket ids come from this repo's own `feat/*` branches (the durable record `lt ticket stop` keeps), never from name shapes — so sibling projects sharing a name prefix are safe. Databases recorded via `lt ticket stop --keep-db` are never touched.
+2. **Stale shard test databases** (`<base>-test-<n>` from `lt dev test --shard`) when no test session is running.
+3. **Dead registry entries** (any project) — the recorded path no longer exists, so the entry and its reserved internal ports are reclaimed. Databases of dead MAIN projects are never dropped (a deleted folder is not consent to destroy data).
+
+`lt dev up` runs the same collection automatically after a successful start (opt out with `--no-prune`), so restarting an environment always cleans up after its predecessors. Database access uses `mongosh` when available and falls back to the project's own `mongodb` driver otherwise — a machine without mongosh no longer silently skips every drop.
+
+---
+
 ### `lt dev status`
 
 Show what is registered + running.
@@ -616,6 +638,114 @@ lt dev test -- --ui spec.ts      # everything after `--` is forwarded to playwri
 
 ---
 
+## Ticket Commands
+
+One fully isolated dev environment per ticket: a git worktree on its own branch, its own
+`lt dev` stack, its own URLs (`<slug>-<id>.localhost`), its own ports, and its own database
+(`<base>-<id>`). Several tickets run side by side without colliding.
+
+### `lt ticket start`
+
+Create a ticket environment: worktree + branch + isolated stack.
+
+**Usage:**
+```bash
+lt ticket start DEV-2200
+lt ticket start login-fix --as lf
+lt ticket start DEV-2200 --base origin/develop --no-up
+```
+
+**Parameters:**
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `<name>` | Ticket id (`DEV-2200` → id `2200`) or free feature name (slugified) | — |
+| `--as` | Explicit short id, overriding the derived one | derived from name |
+| `--base` | Base ref for the new branch | probes `origin/dev` → `develop` → remote HEAD → `main` → `master` |
+| `--branch` | Explicit branch name | `feat/<name>` |
+| `--no-up` | Only create the worktree; do not boot the stack | `false` |
+
+**Reserved ids:** `local`, `dev`, `test`, `e2e`, `ci`, `prod`, `production`, `staging` are
+refused. Their derived database name would collide with the *project's own* dev/test
+database (both derivations strip a trailing `-(local|dev)` before appending their suffix,
+so e.g. project DB `imo-local` + ticket id `local` derives back to `imo-local`). Use `--as`
+to map such a name to a distinct id.
+
+---
+
+### `lt ticket stop`
+
+Tear a ticket environment down: stop the stack, remove the worktree, **drop the ticket's
+databases**. The branch is kept, so committed work is never lost.
+
+**Usage:**
+```bash
+lt ticket stop 2200
+lt ticket stop 2200 --keep-db
+lt ticket stop                  # from INSIDE a ticket worktree → cleans up "this" env
+```
+
+**Parameters:**
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `<id>` | Ticket id. Omit it inside a ticket worktree to stop *that* environment | from `.lt-dev/ticket` marker |
+| `--keep-db` | Keep the ticket databases instead of dropping them | `false` (they ARE dropped) |
+| `--force` | Remove even with uncommitted changes / unpushed commits | `false` |
+| `--noConfirm` | Skip the confirmation prompt for the database drop | `false` |
+| `--drop-db` | **Deprecated no-op** — dropping is the default now | — |
+
+**Databases are dropped by default.** `lt ticket stop` removes the whole environment —
+worktree *and* registry entry — so its databases are orphans the moment it returns: nothing
+references them, nothing lists them, nothing reuses them. Left behind, they simply
+accumulate. The command asks before dropping (unless `--noConfirm`), and `--keep-db` opts
+out entirely.
+
+**What it will never drop:** the project's own `<base>-local` / `<base>-test` databases, a
+database belonging to a *different* ticket, or one named by a registry entry that turns out
+to belong to another checkout. Anything that is not provably this ticket's database is
+refused with a warning rather than guessed at.
+
+**Ordering:** the worktree is removed *before* the databases are dropped. Removing a worktree
+can fail (locked, modified submodule, permissions); dropping a database cannot be undone. So
+the fallible step runs first — if it fails, nothing was destroyed.
+
+---
+
+### `lt ticket list`
+
+Dashboard of all ticket environments: URLs, branch, status, database.
+
+**Usage:**
+```bash
+lt ticket list
+```
+
+---
+
+### `lt ticket switch`
+
+Print a ticket worktree's path and open it in the editor.
+
+**Usage:**
+```bash
+lt ticket switch 2200
+```
+
+---
+
+### `lt ticket test`
+
+Run the E2E suite inside a ticket's isolated stack and database.
+
+**Usage:**
+```bash
+lt ticket test 2200
+lt ticket test 2200 --shard 2
+```
+
+---
+
 ## Git Commands
 
 All git commands support the `--noConfirm` flag and can be configured via `defaults.noConfirm` or `commands.git.noConfirm`.

package/docs/lt-dev-ticket-workflow.html

@@ -316,7 +316,7 @@
   <div class="page">
     <span class="eyebrow">Baustein 2</span>
     <h2><code style="font-size:.8em">lt ticket</code> — mehrere Tickets gleichzeitig</h2>
-    <p class="lead">Ein Repo, beliebig viele Tickets — jedes in einem eigenen <b>git&nbsp;worktree</b> mit eigenem <code>lt dev</code>-Stack. Frisch aus <code>origin/dev</code>, in Sekunden startklar, voneinander komplett unabhängig.</p>
+    <p class="lead">Ein Repo, beliebig viele Tickets — jedes in einem eigenen <b>git&nbsp;worktree</b> mit eigenem <code>lt dev</code>-Stack. Frisch aus dem Basis-Branch (<code>origin/dev</code>, <code>origin/develop</code>, …), in Sekunden startklar, voneinander komplett unabhängig.</p>
 
     <figure>
       <!-- DIAGRAM B: one repo -> N worktrees -> N stacks -->
@@ -375,7 +375,7 @@
     </figure>
 
     <h3>So einfach geht's</h3>
-<pre><span class="k">lt ticket start</span> <span class="a">DEV-2200</span>           <span class="c"># fetch + worktree aus origin/dev + install + lt dev up</span>
+<pre><span class="k">lt ticket start</span> <span class="a">DEV-2200</span>           <span class="c"># fetch + worktree aus dem Basis-Branch + install + lt dev up</span>
                                 <span class="c">→ <span class="s">https://svl-2200.localhost</span> · DB svl-…-2200 (leer)</span>
 <span class="k">lt ticket start</span> <span class="a">login-fix</span>          <span class="c"># kein Ticket? freier Name → svl-login-fix.localhost</span>
 <span class="k">lt ticket start</span> <span class="a">DEV-2200 --as cof</span>  <span class="c"># Kurzname überschreiben; --branch / --base ebenso</span>
@@ -383,7 +383,7 @@
 <span class="k">lt ticket list</span>                    <span class="c"># Dashboard: alle Tickets + URLs + Branch + Status + DB</span>
 <span class="k">lt ticket switch</span> <span class="a">2200</span>           <span class="c"># Pfad zeigen + im Editor öffnen</span>
 <span class="k">lt ticket test</span> <span class="a">2200 --shard 2</span>    <span class="c"># E2E im isolierten Ticket-Stack/-DB</span>
-<span class="k">lt ticket stop</span> <span class="a">2200 --drop-db</span>    <span class="c"># down + worktree entfernen (Branch bleibt); --drop-db löscht DBs</span></pre>
+<span class="k">lt ticket stop</span> <span class="a">2200</span>             <span class="c"># down + worktree + DBs entfernen (Branch bleibt); --keep-db behält die DBs</span></pre>
 
     <div class="grid g3" style="margin-top:8px">
       <div class="card"><div class="ico" style="background:linear-gradient(135deg,#6366f1,#8b5cf6)">🎯</div>
@@ -391,7 +391,7 @@
         <p class="small">Jedes Ticket bekommt <code>&lt;slug&gt;-&lt;id&gt;</code> in URL, DB, Ports, Caddy-Block, Ordnername. Verwechslung ausgeschlossen.</p></div>
       <div class="card"><div class="ico" style="background:linear-gradient(135deg,#06b6d4,#0e7490)">🌱</div>
         <h3>Immer frisch aus dev</h3>
-        <p class="small">Jeder Start macht <code>git fetch</code> und zweigt von <code>origin/dev</code> ab — alle Tickets unabhängig. <code>--base</code> für Ausnahmen.</p></div>
+        <p class="small">Jeder Start macht <code>git fetch</code> und zweigt vom Basis-Branch ab — gesucht wird <code>origin/dev</code>, dann <code>origin/develop</code>, dann der Remote-HEAD (<code>main</code>/<code>master</code>). Findet sich keiner, fragt die CLI nach dem Branch. <code>--base</code> setzt ihn direkt (Pflicht im nicht-interaktiven Betrieb).</p></div>
       <div class="card"><div class="ico" style="background:linear-gradient(135deg,#10b981,#047857)">⚡</div>
         <h3>0&nbsp;s &amp; leicht</h3>
         <p class="small">Worktree teilt das <code>.git</code> — kein Re-Clone. Ein <code>git fetch</code> aktualisiert alle. pnpm hardlinkt aus dem Store.</p></div>
@@ -457,7 +457,7 @@
     <div class="steps">
       <div class="step"><div class="n"></div><div><b>Morgens:</b> <code>lt ticket start DEV-2200</code>, <code>lt ticket start DEV-2201</code>, <code>lt ticket start login-fix</code> — drei Tabs, drei VS-Code-Fenster, drei Claude-Sessions. Jede Umgebung ist sofort im Browser unter ihrer eigenen URL.</div></div>
       <div class="step"><div class="n"></div><div><b>Mittags:</b> Review-Feedback zu 2201 kommt rein — du wechselst per <code>lt ticket switch 2201</code>, fixst, <code>lt ticket test 2201</code> läuft <i>parallel</i> während 2200 weiter im Browser offen ist.</div></div>
-      <div class="step"><div class="n"></div><div><b>Nachmittags:</b> 2200 ist fertig → committen, pushen, MR. <code>lt ticket stop 2200 --drop-db</code> räumt restlos auf. 2201 und login-fix laufen ungestört weiter.</div></div>
+      <div class="step"><div class="n"></div><div><b>Nachmittags:</b> 2200 ist fertig → committen, pushen, MR. <code>lt ticket stop 2200</code> räumt restlos auf (Stack, Worktree und DBs). 2201 und login-fix laufen ungestört weiter.</div></div>
       <div class="step"><div class="n"></div><div><b>Überblick jederzeit:</b> <code>lt ticket list</code> zeigt alle Umgebungen mit URLs, Branch, Status und DB — du verlierst nie den Faden.</div></div>
     </div>
   </div>
@@ -532,7 +532,7 @@
     <div class="grid g2">
       <div class="card"><div class="ico" style="background:linear-gradient(135deg,#f43f5e,#be123c)">🛡️</div>
         <h3>Kein versehentlicher Datenverlust</h3>
-        <p class="small"><code>lt ticket stop</code> verweigert das Entfernen, solange <b>uncommittete</b> oder <b>ungepushte</b> Arbeit existiert — mit klarer Auflistung. <code>--force</code> überschreibt bewusst. Generierte Dateien (<code>.nuxtrc</code> &amp; Co.) blockieren nicht.</p></div>
+        <p class="small"><code>lt ticket stop</code> verweigert das Entfernen, solange <b>uncommittete</b> oder <b>ungepushte</b> Arbeit existiert — mit klarer Auflistung. <code>--force</code> überschreibt bewusst. Generierte Dateien (<code>.nuxtrc</code> &amp; Co.) blockieren nicht. Die <b>Ticket-DBs</b> werden dabei gelöscht (sie wären danach verwaist) — vorher fragt der Befehl nach; <code>--keep-db</code> behält sie. Die Projekt-DBs werden dabei <i>nie</i> angefasst.</p></div>
       <div class="card"><div class="ico" style="background:linear-gradient(135deg,#f59e0b,#b45309)">🩺</div>
         <h3>Selbstdiagnose</h3>
         <p class="small"><code>lt dev doctor</code> prüft Caddy, CA, DNS, Ports — und warnt, wenn ein <code>global-setup</code> Ticket-Test-DBs nicht zurücksetzen würde, samt exaktem Fix.</p></div>
@@ -541,7 +541,7 @@
         <p class="small">Jede Claude-Session in einem Ticket-Worktree erkennt am <code>.lt-dev/ticket</code>-Marker automatisch ihr Ticket — und sieht jede Runde Ticket-ID, URLs und DB. Keine getrackte Datei wird verändert.</p></div>
       <div class="card"><div class="ico" style="background:linear-gradient(135deg,#10b981,#047857)">🧹</div>
         <h3>Restfreier Teardown</h3>
-        <p class="small">Prozesse, Caddy-Block, Session, Registry-Eintrag, Ports — alles wird sauber zurückgegeben. <code>lt ticket stop</code> ohne ID räumt sogar das <i>aktuelle</i> Worktree auf.</p></div>
+        <p class="small">Prozesse, Caddy-Block, Session, Registry-Eintrag, Ports und die <b>Ticket-Datenbanken</b> — alles wird sauber zurückgegeben. <code>lt ticket stop</code> ohne ID räumt sogar das <i>aktuelle</i> Worktree auf.</p></div>
     </div>
   </div>
 </section>
@@ -569,7 +569,7 @@
 <span class="k">lt ticket list</span>            <span class="c"># Dashboard</span>
 <span class="k">lt ticket switch</span> <span class="a">2200</span>     <span class="c"># öffnen</span>
 <span class="k">lt ticket test</span> <span class="a">2200</span>       <span class="c"># isolierte E2E</span>
-<span class="k">lt ticket stop</span> <span class="a">2200</span>       <span class="c"># aufräumen (Branch bleibt)</span>
+<span class="k">lt ticket stop</span> <span class="a">2200</span>       <span class="c"># aufräumen: Worktree + DBs (Branch bleibt)</span>
 <span class="m">/lt-dev:take-ticket</span>        <span class="c"># Ticket im aktuellen Checkout</span>
 <span class="m">/lt-dev:git:ship</span>           <span class="c"># fertig → autonom nach dev</span></pre>
       </div>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lenne.tech/cli",
-  "version": "1.35.1",
+  "version": "1.37.0",
   "description": "lenne.Tech CLI: lt",
   "keywords": [
     "lenne.Tech",