dev-cockpit 0.2.2 → 0.2.3

package/dist/mount/overlay-path.d.ts

@@ -0,0 +1,26 @@
+/**
+ * Resolve where the docker-compose overlay file should be written for a
+ * workspace.
+ *
+ * Default (no `mount.overlayPath` in cockpit.yaml):
+ *   <stateDir>/dev-mount-overlay.yml
+ *   — sibling to `mount.manifest.json`. Keeps the wrapper repo clean of
+ *     per-developer state; aligns the overlay's lifecycle with the
+ *     manifest's.
+ *
+ * Override (cockpit.yaml `mount.overlayPath` is set):
+ *   - Workspace-relative paths resolve against `workspaceRoot`.
+ *   - Absolute paths are honoured verbatim.
+ *
+ * Pure: no I/O. Tested in isolation.
+ */
+export interface ResolveOverlayPathOptions {
+    /** Cockpit state dir for this workspace. */
+    stateDir: string;
+    /** Workspace root, used to resolve relative `configOverride`. */
+    workspaceRoot: string;
+    /** Optional `mount.overlayPath` value from cockpit.yaml. */
+    configOverride?: string | undefined;
+}
+export declare function resolveOverlayPath(opts: ResolveOverlayPathOptions): string;
+//# sourceMappingURL=overlay-path.d.ts.map

package/dist/mount/overlay-path.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"overlay-path.d.ts","sourceRoot":"","sources":["../../src/mount/overlay-path.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAIH,MAAM,WAAW,yBAAyB;IACxC,4CAA4C;IAC5C,QAAQ,EAAE,MAAM,CAAC;IACjB,iEAAiE;IACjE,aAAa,EAAE,MAAM,CAAC;IACtB,4DAA4D;IAC5D,cAAc,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;CACrC;AAED,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,yBAAyB,GAAG,MAAM,CAM1E"}

package/docs/config-reference.md

@@ -14,7 +14,7 @@ A `cockpit.yaml` lives at the root of your project. The cockpit reads it on star
 | `highlights` | array | no | Regex patterns applied to all output streams (process + docker). Each can carry an explicit `severity:` (else inferred). |
 | `health` | array | no | Health check declarations — see `health:` below. |
 | `actions` | array | no | Named, optionally key-bound shell commands surfaced via the `:` palette and the Targets pane. |
-| `mount` | object | no | `overlayPath`, `manifestFile` overrides. Defaults: `docker-compose.dev-cockpit.yml`, `mount.manifest.json`. |
+| `mount` | object | no | `overlayPath`, `manifestFile` overrides. Defaults: `<stateDir>/dev-mount-overlay.yml` (sibling to the manifest, keeps the wrapper repo clean), `mount.manifest.json`. |
 | `mounts` | array | no | Explicit `{hostPath, containerPath, meta?}` entries for `dev-cockpit mount`. |
 | `help` | object | no | Extra `sources[]` + `defaultPage`. |
 | `notifications` | object | no | `enabled`, `onTransitionTo[]`, `exclude[]`. |
@@ -84,8 +84,9 @@ health:
 ## `mount:` + `mounts:`
 
 ```yaml
-mount:                                                # path overrides
-  overlayPath: docker-compose.dev-cockpit.yml         # workspace-relative
+mount:                                                # path overrides — omit for defaults
+  # overlayPath: docker-compose.dev-cockpit.yml       # default: <stateDir>/dev-mount-overlay.yml
+                                                      #   set to keep the overlay in-repo (workspace-relative or absolute)
   manifestFile: mount.manifest.json                   # basename within stateDir
 
 mounts:                                               # explicit candidates

package/docs/mount.md

@@ -26,22 +26,22 @@ dev-cockpit mount status         # active mounts with branch / dirty / broken-sy
 dev-cockpit mount clear          # remove overlay + manifest + symlinks
 ```
 
-Apply the generated overlay alongside your existing compose file:
+Apply the generated overlay alongside your existing compose file (the path is printed by `dev-cockpit mount` — copy it from there):
 
 ```sh
-docker compose -f docker-compose.yml -f docker-compose.dev-cockpit.yml up -d
+docker compose -f docker-compose.yml -f <stateDir>/dev-mount-overlay.yml up -d
 ```
 
 ## What gets written
 
 | File | Default path | Configurable via |
 |---|---|---|
-| Compose overlay | `<workspace>/docker-compose.dev-cockpit.yml` | `config.mount.overlayPath` |
+| Compose overlay | `<stateDir>/dev-mount-overlay.yml` | `config.mount.overlayPath` |
 | Manifest | `<stateDir>/mount.manifest.json` | `config.mount.manifestFile` |
 
-`<stateDir>` lives under `$XDG_STATE_HOME/<appName>/<workspace-hash>/`. The manifest tracks what was applied and when, and is the source of truth for `status` and `clear`.
+`<stateDir>` lives under `$XDG_STATE_HOME/<appName>/<workspace-hash>/`. Both files share that location, so anything cockpit knows about *this workspace's mounts* sits in one dir — clean wrapper repo, no per-developer artefacts to gitignore.
 
-Override the paths when the wrapper has its own conventions:
+Override the overlay path when the wrapper has its own conventions (workspace-relative or absolute):
 
 ```yaml
 mount:

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "dev-cockpit",
-	"version": "0.2.2",
+	"version": "0.2.3",
 	"description": "A reusable, domain-neutral terminal UI dev cockpit — tabbed pane shell, watcher streaming, optional Docker log tail with highlights, health framework with one-keystroke remediations, transition-only OS notifications, live-markdown Help. Profiles extend it with project-specific commands, repos, and health checks.",
 	"license": "MIT",
 	"repository": {