docs: bump to 1.3.0 and document new commands/flags

- README: validate section, dry-run, snapshot restore safety + delete, share validate-only, updated command table
- STATUS.md + DEVELOPMENT.md: new commands
- AUDIT.md: mark v1.3.0 improvements done, correct outdated healthcheck note
- .dev-env.example.yml: seed path + generic service healthcheck (test) example
- package.json: 1.2.0 -> 1.3.0

Author: nazarli-shabnam

.dev-env.example.yml

@@ -26,6 +26,7 @@ databases:
         command: npm run migrate
     seed:
       command: npm run seed
+      path: .  # optional: directory to run the seed command in (default ".")
 
   # - type: redis
   #   version: "7"
@@ -53,6 +54,13 @@ health_checks:
   # - name: redis
   #   type: redis
   #   url: redis://localhost:6379
+  # Generic (non-database) services can define a raw healthcheck command with `test`:
+  # - name: rabbitmq_1        # matches the generated service name, or use type
+  #   type: rabbitmq
+  #   test: rabbitmq-diagnostics -q ping
+  #   interval: 30s
+  #   timeout: 10s
+  #   retries: 5
 
 # Snapshot configuration
 snapshot:

README.md

@@ -73,17 +73,35 @@ This installs dependencies, runs database migrations, and runs seed commands acc
 | `--skip-db`   | Skip database migrations and seed    |
 | `--dry-run`   | Show what would run, without running |
 
-### 3. Generate Docker Compose
+### 3. Validate your config
+
+Check that `.dev-env.yml` (and any `.env`) is well-formed without running setup or generate — handy for CI and pre-commit hooks:
+
+```bash
+envkit validate
+```
+
+It exits non-zero on a missing or invalid config. Add `--strict` to also fail on warnings (e.g. hardcoded passwords, port conflicts) and unresolved `${VAR}` references:
+
+```bash
+envkit validate --strict
+```
+
+### 4. Generate Docker Compose
 
 When `docker.enabled` is set in your config, you can generate a Compose file from it:
 
 ```bash
 envkit generate
 ```
 
-Output goes to `docker-compose.yml` by default. Use `-o <file>` to write elsewhere, e.g. `envkit generate -o docker-compose.dev.yml`.
+Output goes to `docker-compose.yml` by default. Use `-o <file>` to write elsewhere, e.g. `envkit generate -o docker-compose.dev.yml`. To preview the generated Compose without writing a file (e.g. to pipe or inspect it), use `--dry-run`:
 
-### 4. Snapshots
+```bash
+envkit generate --dry-run
+```
+
+### 5. Snapshots
 
 Save the current config as a named snapshot under `.devkit/snapshots/`:
 
@@ -97,13 +115,19 @@ If you omit the name, a timestamp-based name is used. List existing snapshots:
 envkit snapshot list
 ```
 
-Restore a snapshot (overwrites `.dev-env.yml`):
+Restore a snapshot. This overwrites `.dev-env.yml`, but your current config is automatically backed up to a `pre-restore-<timestamp>` snapshot first, and you'll be asked to confirm in an interactive terminal (use `--yes` to skip the prompt in scripts):
 
 ```bash
 envkit snapshot restore <name>
 ```
 
-### 5. Share config (export / import)
+Delete a snapshot you no longer need:
+
+```bash
+envkit snapshot delete <name>
+```
+
+### 6. Share config (export / import)
 
 Export a safe-to-share copy of your config (passwords and secrets become placeholders like `${DB_PASSWORD}`):
 
@@ -119,7 +143,11 @@ Import a shared config file (it is validated and then written to `.dev-env.yml`
 envkit share import path/to/dev-env.shared.yml
 ```
 
-Use `-o <file>` to write to a different path (also relative to the current directory unless you pass an absolute path).
+Use `-o <file>` to write to a different path (also relative to the current directory unless you pass an absolute path). To check a shared file is valid without writing anything (useful in CI), pass `--validate-only`:
+
+```bash
+envkit share import path/to/dev-env.shared.yml --validate-only
+```
 
 ### Global options
 
@@ -136,12 +164,14 @@ Example: `envkit -q setup`
 |--------|-------------|
 | `envkit init` | Create `.dev-env.yml` interactively (wizard). Run from a project folder when you don’t have a config yet. |
 | `envkit setup` | Install dependencies, run database migrations, and run seed commands from your config. Use `--skip-deps`, `--skip-db`, or `--dry-run` to limit what runs. |
-| `envkit generate` | Generate `docker-compose.yml` from your config (requires `docker.enabled` in config). Use `-o <file>` to set the output path. |
+| `envkit validate` | Validate `.dev-env.yml` (and `.env`) without running setup or generate. Add `--strict` to fail on warnings and unresolved `${VAR}` references. CI/pre-commit friendly. |
+| `envkit generate` | Generate `docker-compose.yml` from your config (requires `docker.enabled` in config). Use `-o <file>` to set the output path, or `--dry-run` to print without writing. |
 | `envkit snapshot create [name]` | Save the current `.dev-env.yml` as a snapshot under `.devkit/snapshots/`. Omit `name` to use a timestamp. |
 | `envkit snapshot list` | List all saved snapshots. |
-| `envkit snapshot restore <name>` | Restore a snapshot; overwrites `.dev-env.yml`. |
+| `envkit snapshot restore <name>` | Restore a snapshot; overwrites `.dev-env.yml` (current config is backed up first). Use `--yes` to skip the confirmation prompt. |
+| `envkit snapshot delete <name>` | Delete a saved snapshot. |
 | `envkit share export` | Export a sanitized config (secrets → placeholders) to share safely. Default output: `dev-env.shared.yml`; use `-o <file>` to override. |
-| `envkit share import <file>` | Import a shared config file; writes to `.dev-env.yml` by default. Use `-o <file>` to write elsewhere. |
+| `envkit share import <file>` | Import a shared config file; writes to `.dev-env.yml` by default. Use `-o <file>` to write elsewhere, or `--validate-only` to validate without writing. |
 | `envkit path-setup` or `envkit pathsetup` | Add the npm global bin folder to your PATH so `envkit` works from any directory. Use if the shell says “envkit” is not recognized after a global install. |
 
 For more detail: `envkit --help` or `envkit <command> --help`.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-env-kit",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "One-command project setup, environment snapshots, and Docker Compose generation for local development",
   "main": "dist/cli/index.js",
   "bin": {