xcorecli 1.1.1__tar.gz → 2.1.0__tar.gz

xcorecli-2.1.0/PKG-INFO

@@ -0,0 +1,77 @@
+Metadata-Version: 2.5
+Name: xcorecli
+Version: 2.1.0
+Summary: CLI for xcore — configuration, plugins, monitoring
+Requires-Python: >=3.12
+Requires-Dist: alembic>=1.18.0
+Requires-Dist: httpx>=0.27
+Requires-Dist: psutil>=5.9
+Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: pyyaml>=6.0.1
+Requires-Dist: rich>=14.3.4
+Requires-Dist: sqlalchemy>=2.0.0
+Requires-Dist: typer>=0.25.1
+Description-Content-Type: text/markdown
+
+# xcli — xcore project manager
+
+Official CLI for the `xcore` framework: scaffold a project, manage
+plugins (local dev, marketplace install, runtime control, signing), run
+migrations, control the Celery worker, and monitor a running deployment.
+
+```bash
+pip install xcorecli
+xcli --help
+```
+
+Full docs: https://docs.xcorehub.dev (built from `docs/` with
+`mkdocs-material` — `mkdocs serve` locally).
+
+## Quick start
+
+```bash
+xcli init my-app                # scaffold a new xcore project
+cd my-app
+pip install -r requirements.txt
+xcli manager start --reload     # run it
+```
+
+## Installing plugins from the marketplace
+
+Browsing is public, no credentials needed:
+
+```bash
+xcli plugin marketplace browse
+xcli plugin marketplace search "auth"
+xcli plugin marketplace info xlicense
+```
+
+Installing needs two credentials — see
+[docs/getting-started/auth.md](docs/getting-started/auth.md):
+
+```bash
+xcli config set api-key xdk_...
+xcli config set signing-key <your-signing-secret>
+xcli plugin install xlicense
+```
+
+## Command groups
+
+| Group | Purpose |
+|-------|---------|
+| `xcli init` / `xcli upgrade` | Scaffold a project / migrate `integration.yaml` to the latest schema |
+| `xcli health` / `xcli services` | Health-check and status of all configured services |
+| `xcli config` | Store local credentials (`api-key`, `signing-key`) |
+| `xcli plugin` | Local dev, marketplace browse/install, runtime control, signing, updates — see `xcli plugin --help` |
+| `xcli deploy` | Deploy plugins to remote servers |
+| `xcli sandbox` | Inspect the plugin sandbox |
+| `xcli worker` | Manage Celery workers |
+| `xcli manager` | Runtime monitoring of a running instance |
+| `xcli migration` | Alembic migrations for plugins |
+
+Short hidden aliases exist for the busiest groups: `p` (plugin), `sb`
+(sandbox), `w` (worker), `m` (manager), `mig` (migration).
+
+`xcli` expects to run **inside** an xcore project directory (it reads that
+project's `integration.yaml` and needs `xcore` importable in the current
+environment) — it's a project-management tool, not a standalone service.

xcorecli-2.1.0/README.md

@@ -0,0 +1,62 @@
+# xcli — xcore project manager
+
+Official CLI for the `xcore` framework: scaffold a project, manage
+plugins (local dev, marketplace install, runtime control, signing), run
+migrations, control the Celery worker, and monitor a running deployment.
+
+```bash
+pip install xcorecli
+xcli --help
+```
+
+Full docs: https://docs.xcorehub.dev (built from `docs/` with
+`mkdocs-material` — `mkdocs serve` locally).
+
+## Quick start
+
+```bash
+xcli init my-app                # scaffold a new xcore project
+cd my-app
+pip install -r requirements.txt
+xcli manager start --reload     # run it
+```
+
+## Installing plugins from the marketplace
+
+Browsing is public, no credentials needed:
+
+```bash
+xcli plugin marketplace browse
+xcli plugin marketplace search "auth"
+xcli plugin marketplace info xlicense
+```
+
+Installing needs two credentials — see
+[docs/getting-started/auth.md](docs/getting-started/auth.md):
+
+```bash
+xcli config set api-key xdk_...
+xcli config set signing-key <your-signing-secret>
+xcli plugin install xlicense
+```
+
+## Command groups
+
+| Group | Purpose |
+|-------|---------|
+| `xcli init` / `xcli upgrade` | Scaffold a project / migrate `integration.yaml` to the latest schema |
+| `xcli health` / `xcli services` | Health-check and status of all configured services |
+| `xcli config` | Store local credentials (`api-key`, `signing-key`) |
+| `xcli plugin` | Local dev, marketplace browse/install, runtime control, signing, updates — see `xcli plugin --help` |
+| `xcli deploy` | Deploy plugins to remote servers |
+| `xcli sandbox` | Inspect the plugin sandbox |
+| `xcli worker` | Manage Celery workers |
+| `xcli manager` | Runtime monitoring of a running instance |
+| `xcli migration` | Alembic migrations for plugins |
+
+Short hidden aliases exist for the busiest groups: `p` (plugin), `sb`
+(sandbox), `w` (worker), `m` (manager), `mig` (migration).
+
+`xcli` expects to run **inside** an xcore project directory (it reads that
+project's `integration.yaml` and needs `xcore` importable in the current
+environment) — it's a project-management tool, not a standalone service.

xcorecli-2.1.0/docs/commands/login.md

@@ -0,0 +1,34 @@
+# Login & Install Shortcut
+
+Two small top-level commands, both really about the marketplace rather
+than the local xcore runtime.
+
+## `xcli login`
+
+Authorizes this machine with the marketplace via a device-code flow —
+opens a browser, you confirm a 6-digit code, `xcli` saves the resulting
+credentials on its own. Full walkthrough:
+[Authentication → Quick Start](../getting-started/auth.md#quick-start-xcli-login).
+
+```bash
+xcli login
+```
+
+!!! tip "For CI, not this"
+    `xcli login` mints a **personal** credential meant for a human running
+    it interactively. CI pipelines should use a project-scoped key and the
+    `XCLI_API_KEY`/`XCLI_SIGNING_KEY` environment variables instead — see
+    [Environment variables](../getting-started/auth.md#environment-variables).
+
+## `xcli install`
+
+A shortcut for [`xcli plugin install`](../plugin/install.md) — same
+command, same options, one less word to type:
+
+```bash
+xcli install name-of-plugin
+xcli install name-of-plugin@1.2.3
+```
+
+There's no equivalent top-level shortcut for service extensions — use
+[`xcli service install`](../service/index.md) directly.

xcorecli-2.1.0/docs/getting-started/auth.md

@@ -0,0 +1,110 @@
+# Authentication
+
+To interact with the **xcore marketplace** and install plugins, you need
+two separate credentials — they protect different things and neither
+substitutes for the other:
+
+## Quick Start: `xcli login`
+
+The fastest way to get both credentials — no copy-pasting required.
+
+```bash title="Device-code login"
+xcli login
+```
+
+This opens the marketplace in your browser with a 6-digit code pre-filled,
+and waits. Once you confirm it there (you must already be logged into the
+marketplace website, and the confirmation is an explicit click — it never
+happens automatically just by opening the link), `xcli` retrieves both
+credentials on its own and saves them to `~/.xcli/config.json` — the exact
+same file `xcli config set` writes to, just without the manual steps.
+
+```text
+To authorize this device, visit: https://marketplace.xcorehub.dev/cli/confirm
+And enter code: 042817
+
+✓ Logged in — credentials saved to ~/.xcli/config.json
+```
+
+If the browser can't be opened automatically (headless environment, remote
+shell), the URL and code are printed regardless — open it manually.
+
+!!! info "What kind of key does this create?"
+    `xcli login` mints a **personal** API key — unlike a key created
+    through the marketplace's project UI (which is scoped to exactly one
+    plugin or service), a personal key works for installing **any public**
+    plugin or service, and any private one you own or have team access to.
+    It's meant for day-to-day `xcli install`/`xcli service install` usage,
+    not for CI — see [Environment variables](#environment-variables) below
+    for the project-scoped alternative CI pipelines should use instead.
+
+The device-code request expires after a few minutes if left unconfirmed;
+just run `xcli login` again.
+
+## Manual Setup
+
+Prefer to configure credentials by hand, or need a **project-scoped** key
+(tied to one specific plugin/service — the right choice for CI/CD, see
+below) instead of a personal one? Both credentials can also be set directly:
+
+| Credential | What it's for | Where to get it |
+|------------|----------------|------------------|
+| **API key** (`xdk_...`) | Authorizes the download itself (`X-API-Key` header on `GET /plugins/{slug}/install`) — tied to one project (`kind=plugin`, matching the target plugin's slug) | XCoreHub → Déploiements → Projets & clés |
+| **Signing key** | An HMAC-SHA256 secret used to verify the `X-Signature` header on the downloaded ZIP — installation is refused if it doesn't match | XCoreHub → Déploiements → Clé de signature |
+
+`browse`/`search`/`info` (read-only discovery) need **neither** — the
+marketplace listing is public.
+
+## Configuration Commands
+
+`xcorecli` provides a `config` command group to manage your local settings.
+
+### Store your credentials
+
+```bash title="Configuration"
+xcli config set api-key xdk_...
+xcli config set signing-key <your-signing-secret>
+```
+
+Both are required before `xcli plugin install <name>` will succeed —
+`install` checks for each explicitly and tells you exactly which one is
+missing.
+
+!!! warning "Security First"
+    Never share your API key or signing key, or commit them to version
+    control. They're stored in `~/.xcli/config.json` (mode `0600`), never in
+    your project's `integration.yaml`.
+
+### View current configuration
+
+To check your current configuration (with sensitive data masked):
+
+```bash
+xcli config show
+```
+
+## Credential storage
+
+Managed by `xcli/_credentials.py` — a flat `~/.xcli/config.json`, keyed
+`api-key` / `signing-key`. Only these two keys are valid; anything else
+passed to `xcli config set` is rejected.
+
+!!! info "Marketplace URL"
+    By default, `xcorecli` connects to `https://marketplace.xcorehub.dev`.
+    Override it via `marketplace.url` in the project's `integration.yaml`
+    (the same value the project's own backend uses) — always include the
+    `https://` scheme, a bare domain will fail to resolve as a URL.
+
+## Environment variables
+
+For CI/CD environments, both credentials can be supplied via environment
+variables instead of `xcli config set` — these take priority over
+`~/.xcli/config.json` when present. Use a **project-scoped** key here (one
+plugin/service, created from the marketplace's project page), not a
+personal one from `xcli login` — a CI pipeline should only ever be able to
+touch the one target it's meant to deploy:
+
+```bash title=".env"
+XCLI_API_KEY=xdk_...
+XCLI_SIGNING_KEY=your-signing-secret
+```

{xcorecli-1.1.1 → xcorecli-2.1.0}/docs/index.md

@@ -9,7 +9,6 @@
 
 - **Project Initialization**: Seamlessly scaffold new projects and manage `integration.yaml`.
 - **Plugin Lifecycle**: Full control over installing, signing, and updating plugins.
-- **Production Deploy**: Deploy plugins to remote servers via SSH with pre/post hooks.
 - **Real-time Monitoring**: Integrated dashboard for service health and resource usage.
 - **Worker Orchestration**: Manage Celery/XWorker processes with ease.
 - **Security & Sandboxing**: Resource isolation and AST-based whitelisting for plugins.
@@ -30,5 +29,11 @@ make install
 
 - [Installation Guide](getting-started/install.md)
 - [Authentication Setup](getting-started/auth.md)
-- [Deploy to Production](deploy/index.md)
 - [Core Commands Reference](reference.md)
+
+!!! info "Production deployment"
+    Deploying plugin bundles to remote servers is no longer part of
+    `xcorecli` — it's fully handled by the standalone
+    [`xcore-agent`](https://github.com/traoreera/xcore-agent) deployment
+    agent (Hub artifact fetch, signature verification, install/rollback,
+    systemd/Docker/Kubernetes supervisors, CI/CD watch loop).

{xcorecli-1.1.1 → xcorecli-2.1.0}/docs/migration/index.md

@@ -2,6 +2,13 @@
 
 `xcorecli` provides a streamlined wrapper around **Alembic** to manage your database schema migrations, with added safety features like automated backups.
 
+!!! info "Async database support"
+    `upgrade`/`downgrade`/`revision`/`current`/`stamp` all transparently
+    bridge to an async engine first when your `integration.yaml` database
+    URL uses an async driver (`sqlite+aiosqlite`, `postgresql+asyncpg`,
+    ...) — the normal case for an xcore project. No configuration needed;
+    it's detected from the URL itself.
+
 ## Getting Started
 
 Migrations are managed via the `migration` command group.

{xcorecli-1.1.1 → xcorecli-2.1.0}/docs/plugin/install.md

@@ -6,10 +6,21 @@ Plugins can be installed from the official **xcore Marketplace** or from externa
 
 The easiest way to add features. `xcorecli` handles downloads and HMAC signature verification.
 
+!!! warning "Two credentials required"
+    Marketplace installs need **both** an API key and a signing key
+    configured first — see [Authentication](../getting-started/auth.md).
+    Missing either one fails fast with a clear message telling you which
+    one and how to set it; nothing is extracted until the signature checks
+    out.
+
 ```bash title="Marketplace Install"
 xcli plugin install name-of-plugin
 ```
 
+!!! tip "Shortcut"
+    `xcli install name-of-plugin` works too — a top-level alias for
+    `xcli plugin install`, same command underneath.
+
 ### Installing a Specific Version
 
 ```bash

xcorecli-2.1.0/docs/plugin/marketplace.md

@@ -0,0 +1,46 @@
+# Plugin Marketplace
+
+Discover plugins available on the marketplace before installing them — all
+three commands here are read-only and public, no credentials required.
+
+## Browse All
+
+List published plugins, sorted `newest` (default), `downloads`, or `rating`.
+
+```bash
+xcli plugin marketplace browse
+xcli plugin marketplace browse --sort downloads --limit 50
+```
+
+## Search
+
+Find plugins by name or description.
+
+```bash title="Search"
+xcli plugin marketplace search "monitoring"
+```
+
+## Plugin Details
+
+Get in-depth information about a specific marketplace plugin before
+installing it — description, rating, download count, repository, and
+published versions.
+
+```bash title="Plugin Info"
+xcli plugin marketplace info name-of-plugin
+```
+
+## What's not here
+
+Rating a plugin (`POST /plugins/{slug}/ratings`) requires a full user
+session (Bearer JWT), not the API key `xcli` stores — that's a web-app
+action, not a CLI one; rate plugins from the XCoreHub dashboard instead.
+There's also no dedicated "trending" endpoint server-side — use
+`browse --sort downloads` or `--sort rating` for the same effect.
+
+## Installing
+
+Once you've found a plugin, see [Installing Plugins](install.md) — it
+needs the API key and signing key described in
+[Authentication](../getting-started/auth.md), which discovery commands on
+this page don't.

{xcorecli-1.1.1 → xcorecli-2.1.0}/docs/reference.md

@@ -6,8 +6,11 @@ A comprehensive list of all commands available in `xcorecli`.
 
 - `xcli init`: Initialize a new xcore project.
 - `xcli upgrade`: Migrate `integration.yaml` to the latest schema.
+- `xcli login`: Authorize this machine with the marketplace (device-code flow).
+- `xcli install`: Shortcut for `xcli plugin install`.
 - `xcli health`: Global health check of all configured services.
-- `xcli services`: Show status and details of all system services.
+- `xcli services`: Show status and details of all system services (local
+  runtime — not the marketplace catalog, see `xcli service` below).
 
 ## `manager`  Administration
 
@@ -21,32 +24,11 @@ A comprehensive list of all commands available in `xcorecli`.
 - `manager services reload`: Reconnect a service.
 - `manager services unload`: Shutdown a service.
 
-## `deploy`  Production Deployment
-
-- `deploy init`: Generate a `xcore-deploy.yaml` template file.
-- `deploy list`: Show targets, plugins, extensions, and hooks declared in the config.
-- `deploy <target>`: Deploy integration.yaml + extensions + plugins to a remote server.
-- `deploy status <target>`: Show plugin state on a remote server via the XCore API.
-
-**Key options for `deploy <target>`:**
-
-| Option | Description |
-|---|---|
-| `--plugin <name>` | Deploy only one plugin (skips extensions + integration) |
-| `--dry-run` | Simulate without sending anything |
-| `--no-reload` | Transfer files without triggering reload/restart |
-| `--file <path>` | Use an alternate config file |
-
-**Deploy order:** `integration.yaml` → extensions (services) → plugins
-
-**Sources:** each plugin/extension accepts `source: ./local/path` OR `repo: https://github.com/org/repo` (public), with optional `token: "${GITHUB_TOKEN}"` for private repos or `git@github.com:...` SSH URLs.
-
-**Hook levels:**
-
-| Level | Keys | When |
-|---|---|---|
-| Global | `hooks.pre_deploy` / `hooks.post_deploy` | Once per full deploy run |
-| Per-plugin/extension | `hooks.pre_deploy` / `post_deploy` | Before/after each item |
+!!! info "Production deployment moved"
+    `deploy` (init/list/status, SSH transfer, pre/post hooks) is no
+    longer part of `xcorecli` — it's fully replaced by the standalone
+    [`xcore-agent`](https://github.com/traoreera/xcore-agent) deployment
+    agent.
 
 ---
 
@@ -65,11 +47,12 @@ A comprehensive list of all commands available in `xcorecli`.
 - `local list`: List all plugins with link type.
 
 ### `plugin marketplace`  Discovery
-- `marketplace browse`: List all available plugins.
-- `marketplace search`: Search by keyword.
-- `marketplace info`: Pre-install details.
-- `marketplace trending`: Show popular plugins.
-- `marketplace rate`: Rate 15 stars.
+- `marketplace browse`: List published plugins (`--sort newest|downloads|rating`).
+- `marketplace search`: Search by name or description.
+- `marketplace info`: Pre-install details, including published versions.
+
+No `rate` command — rating requires a full user session (JWT), not an API
+key; rate plugins from the XCoreHub dashboard.
 
 ### `plugin update`  Maintenance
 - `update check`: Check for new versions.
@@ -81,6 +64,22 @@ A comprehensive list of all commands available in `xcorecli`.
 - `runtime reload`: Restart a plugin.
 - `runtime status`: Show active plugins.
 
+## `service`  Marketplace Extensions
+
+Mirror of `plugin` for the separate `xservices` catalog — not to be
+confused with `xcli services`/`xcli manager services` (local runtime).
+
+- `service info`: Detailed local extension report.
+- `service health`: Health check of all installed extensions.
+- `service remove`: Uninstall an extension.
+- `service install`: Install from marketplace.
+- `service versions`: List marketplace versions.
+
+### `service marketplace`  Discovery
+- `marketplace browse`: List published extensions (`--sort newest|installs|rating`).
+- `marketplace search`: Search by name or description.
+- `marketplace info`: Pre-install details, including published versions.
+
 ## `worker`  Background Tasks
 
 - `worker start`: Start a Celery worker.

xcorecli-2.1.0/docs/service/index.md

@@ -0,0 +1,69 @@
+# Service Extensions
+
+The marketplace also hosts **service extensions** (`xservices`) — a
+separate catalog from plugins, for reusable service-shaped dependencies a
+plugin might need (databases, caches, message queues...). The `service`
+command group mirrors `plugin` one-for-one, just pointed at that other
+catalog.
+
+!!! warning "Not `xcli services`"
+    `xcli service` (singular, this page) is the marketplace catalog.
+    `xcli services` and `xcli manager services` (plural) show your
+    **local** xcore runtime's own service status — an unrelated command
+    that happens to share a similar name. If a command errors with
+    something about your local `ServiceContainer`, you probably typed the
+    plural by mistake.
+
+## Discovery
+
+Read-only, public, no credentials required — same shape as
+[Plugin Marketplace](../plugin/marketplace.md):
+
+```bash
+xcli service marketplace browse
+xcli service marketplace browse --sort installs --limit 50
+xcli service marketplace search "cache"
+xcli service marketplace info name-of-service
+```
+
+`--sort` accepts `newest` (default), `installs`, or `rating` — note
+`installs`, not `downloads`; the service catalog counts installs, not
+downloads.
+
+## Installing
+
+Same two credentials as plugins — see [Authentication](../getting-started/auth.md)
+(`xcli login` covers both catalogs at once; a project-scoped key is
+per-catalog, so make sure the project you created it for has
+`kind=service`).
+
+```bash title="Install"
+xcli service install name-of-service
+xcli service install name-of-service@1.2.3
+```
+
+Installed extensions land in the directory configured under
+`marketplace_services.directory` in `integration.yaml` (defaults to
+`./services`) — deliberately a separate key from `plugins.directory` and
+from `services.databases.*` (xcore's own internal service container
+config), which already both use `services`/`plugins` for something else.
+
+```bash
+xcli service versions name-of-service
+```
+
+## Management Commands
+
+Identical shape to `plugin`:
+
+```bash
+xcli service info name-of-service      # manifest, permissions, signature status
+xcli service health                    # signature + AST + manifest check, all installed
+xcli service remove name-of-service    # uninstall
+```
+
+!!! info "Smaller surface than `plugin`"
+    There's no `service local`/`service runtime`/`service security`/
+    `service update` today — service extensions don't have the same
+    local-dev-scaffolding or hot-reload workflow plugins do. Everything
+    that exists lives directly under `xcli service`.

{xcorecli-1.1.1 → xcorecli-2.1.0}/mkdocs.yml

@@ -58,6 +58,7 @@ nav:
   - Global Commands:
     - init & upgrade: commands/init.md
     - health & services: commands/health.md
+    - login & install: commands/login.md
   - Config: config/index.md
   - Plugin:
     - Overview: plugin/index.md
@@ -67,8 +68,7 @@ nav:
     - Marketplace: plugin/marketplace.md
     - Security: plugin/security.md
     - Updates: plugin/update.md
-  - Deploy:
-    - Overview: deploy/index.md
+  - Service: service/index.md
   - Sandbox: sandbox/index.md
   - Worker:
     - Overview: worker/index.md

{xcorecli-1.1.1 → xcorecli-2.1.0}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "hatchling.build"
 
 [project]
 name = "xcorecli"
-version = "1.1.1"
-description = "CLI for xcore — configuration, plugins, deployment"
+version = "2.1.0"
+description = "CLI for xcore — configuration, plugins, monitoring"
 readme = "README.md"
 requires-python = ">=3.12"
 dependencies = [
@@ -16,6 +16,12 @@ dependencies = [
     "pyyaml>=6.0.1",
     "psutil>=5.9",
     "httpx>=0.27",
+    # xcli migration needs to resolve ${VAR}-style placeholders in
+    # integration.yaml's services.databases.*.url the same way the app
+    # itself does at runtime (xcore.configurations.loader.ConfigLoader,
+    # same app.dotenv key, same library) — declared directly rather than
+    # relying on it being transitively present via an installed `xcore`.
+    "python-dotenv>=1.0.0",
 ]
 
 [project.scripts]

{xcorecli-1.1.1 → xcorecli-2.1.0}/uv.lock

@@ -569,6 +569,15 @@ wheels = [
     { url = "https://files.pythonhosted.org/packages/ec/57/56b9bcc3c9c6a792fcbaf139543cee77261f3651ca9da0c93f5c1221264b/python_dateutil-2.9.0.post0-py2.py3-none-any.whl", hash = "sha256:a8b2bc7bffae282281c8140a97d3aa9c14da0b136dfe83f850eea9a5f7470427", size = 229892, upload-time = "2024-03-01T18:36:18.57Z" },
 ]
 
+[[package]]
+name = "python-dotenv"
+version = "1.2.3"
+source = { registry = "https://pypi.org/simple" }
+sdist = { url = "https://files.pythonhosted.org/packages/6a/53/ed9d74092561d4b01a2ef1349d52cdbc135e526c245f366b089cfca6de49/python_dotenv-1.2.3.tar.gz", hash = "sha256:a20a594dabeaa385725aa239d5244871c143ecb356add8a20fcf23773a6c3a35", size = 58945, upload-time = "2026-08-16T16:54:54.067Z" }
+wheels = [
+    { url = "https://files.pythonhosted.org/packages/0d/17/c5c6b53ddc18f297992099b3d9ec16c855c0ccc83263a21fe4d1c625ec6c/python_dotenv-1.2.3-py3-none-any.whl", hash = "sha256:904552145e8bfed22162c09dab1c2b9b54fefa7b23ba780f4f26ca0316b0f0d9", size = 22780, upload-time = "2026-08-16T16:54:52.473Z" },
+]
+
 [[package]]
 name = "pyyaml"
 version = "6.0.3"
@@ -773,12 +782,13 @@ wheels = [
 
 [[package]]
 name = "xcorecli"
-version = "1.1.1"
+version = "2.0.0"
 source = { editable = "." }
 dependencies = [
     { name = "alembic" },
     { name = "httpx" },
     { name = "psutil" },
+    { name = "python-dotenv" },
     { name = "pyyaml" },
     { name = "rich" },
     { name = "sqlalchemy" },
@@ -795,6 +805,7 @@ requires-dist = [
     { name = "alembic", specifier = ">=1.18.0" },
     { name = "httpx", specifier = ">=0.27" },
     { name = "psutil", specifier = ">=5.9" },
+    { name = "python-dotenv", specifier = ">=1.0.0" },
     { name = "pyyaml", specifier = ">=6.0.1" },
     { name = "rich", specifier = ">=14.3.4" },
     { name = "sqlalchemy", specifier = ">=2.0.0" },