procdeck 2.0.1 → 2.1.0

package/CHANGELOG.md

@@ -1,5 +1,25 @@
 # procdeck
 
+## 2.1.0
+
+### Minor Changes
+
+- A monorepo deck can hold every project's processes and run only the slice
+  you are working on. `"group": "career"` on a proc, `"autostart": false`,
+  and then `procdeck start career` brings up every proc in the group,
+  `procdeck stop career` puts them back to idle while the deck stays up.
+  `start`, `stop` and `restart` take a proc id, a group name or a quoted glob
+  over ids (`'*-native'`), several at a time. Ids do not change; `procdeck
+status` and the UI's sidebar show each group as a section.
+- **The MCP server is gone**: `procdeck mcp` and its tools (`deck_status`,
+  `get_logs`, `get_http`, `get_errors`, `set_mark`, `wait_for`, `timeline`,
+  and the `--mutations` trio). Every one of them was a CLI verb over the same
+  deck API, and agents call a CLI fine; the duplicate surface cost a
+  dependency, a test suite and a page of docs, and its tool descriptions sat
+  in the agent's context whether or not it needed the deck. If you registered
+  it, `claude mcp remove procdeck`; `procdeck agents` gives the agent the CLI
+  instead (a `## procdeck` section in CLAUDE.md / AGENTS.md and a skill).
+
 ## 2.0.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "procdeck",
-  "version": "2.0.1",
+  "version": "2.1.0",
   "description": "Dev-process multiplexer with a web UI: terminal panes in a browser tab, declarative dependencies, assigned ports, a *.localhost proxy and captured HTTP traffic. One native binary.",
   "keywords": [
     "cli",
@@ -36,9 +36,9 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@procdeck/linux-x64": "2.0.1",
-    "@procdeck/darwin-x64": "2.0.1",
-    "@procdeck/darwin-arm64": "2.0.1",
-    "@procdeck/linux-arm64": "2.0.1"
+    "@procdeck/linux-x64": "2.1.0",
+    "@procdeck/linux-arm64": "2.1.0",
+    "@procdeck/darwin-x64": "2.1.0",
+    "@procdeck/darwin-arm64": "2.1.0"
   }
 }

package/readme.md

@@ -18,7 +18,7 @@ allocator, the log viewer and the network tab of your dev environment:
 - **Sees the traffic.** The HTTP and WebSocket requests _between_ your
   services — the half a browser's DevTools never shows.
 - **Answers from the CLI.** `procdeck logs --since-mark fix`, `http --digest`,
-  `status --json` — for you, or for a coding agent over MCP.
+  `status --json` — for you, or for a coding agent.
 
 ## Quick start
 
@@ -114,10 +114,9 @@ procdeck logs --since-mark before-fix # only what the change caused
 procdeck http --since-mark before-fix # only the requests it caused
 ```
 
-Everything takes `--json` and is bounded by default. The same verbs are served
-over MCP — `claude mcp add procdeck -- procdeck mcp`, once, globally: the
-instance registry finds the right deck per project. `procdeck agents` writes
-the discovery section into CLAUDE.md / AGENTS.md.
+Everything takes `--json` and is bounded by default. `procdeck agents` writes
+the discovery section into CLAUDE.md / AGENTS.md and a Claude Code skill, so
+the agent knows the deck exists and how to ask it.
 
 See [docs/agents.md](https://github.com/kondaurovDev/procdeck/blob/main/docs/agents.md).
 
@@ -128,6 +127,8 @@ procdeck init               # write procdeck.config.json from what the project a
 procdeck up [config]        # start (detached) and open the UI — idempotent
 procdeck down               # stop: every process tree is terminated
 procdeck restart [proc]     # one proc, or the whole deck; --all for every deck on this machine
+procdeck start <proc|group> # start idle procs — a group from the config, or a glob like '*-native'
+procdeck stop <proc|group>  # stop them again; the deck stays up
 procdeck status             # address, uptime, every proc's state (--json for agents)
 procdeck ls                 # every running deck on this machine
 procdeck open               # open the UI — no port to remember
@@ -175,7 +176,7 @@ variables of a dotenv file. Full field reference:
 ## Upgrading from 1.x
 
 2.0 is the same tool rewritten in Go — the CLI verbs, their flags and `--json`
-shapes, the MCP tools and the addresses stay. What changes:
+shapes and the addresses stay. What changes:
 
 - **Configs are JSON.** A `procdeck.config.ts` becomes `procdeck.config.jsonc`:
   quote the keys, drop the `import` and `defineConfig(…)`, keep the comments.
@@ -198,17 +199,20 @@ pnpm dev          # builds the UI, embeds it, runs the example stack on the Go p
 Then open <http://localhost:4840> for the panes, and
 <http://web.localhost:4840> / <http://api.localhost:4840> — the example's
 servers found each other, and their own ports, entirely through `${port}`
-templates. See [`example/`](https://github.com/kondaurovDev/procdeck/tree/main/example).
+templates. The `lab` group sits idle until `procdeck start lab` (from
+`example/`), the way one project's slice of a monorepo deck would. See
+[`example/`](https://github.com/kondaurovDev/procdeck/tree/main/example).
 
 ## Docs
 
 | Doc                                                                                        | What                                                   |
 | ------------------------------------------------------------------------------------------ | ------------------------------------------------------ |
 | [config.md](https://github.com/kondaurovDev/procdeck/blob/main/docs/config.md)             | Every config field, port templating, readiness, gates. |
-| [agents.md](https://github.com/kondaurovDev/procdeck/blob/main/docs/agents.md)             | The verify loop, the CLI verbs, the MCP tools.         |
+| [agents.md](https://github.com/kondaurovDev/procdeck/blob/main/docs/agents.md)             | The verify loop and the CLI verbs for coding agents.   |
 | [traffic.md](https://github.com/kondaurovDev/procdeck/blob/main/docs/traffic.md)           | What the HTTP observer captures, and what it cannot.   |
 | [architecture.md](https://github.com/kondaurovDev/procdeck/blob/main/docs/architecture.md) | How the code is put together.                          |
-| [design/](https://github.com/kondaurovDev/procdeck/tree/main/docs/design/)                 | Engineering notes behind the bigger features.          |
+| [design/](https://github.com/kondaurovDev/procdeck/tree/main/docs/design/)                 | The decisions behind the bigger features, and why.     |
+| [plan.md](https://github.com/kondaurovDev/procdeck/blob/main/docs/plan.md)                 | What is agreed on and not built yet.                   |
 
 ## Status
 

package/schema.json

@@ -105,7 +105,12 @@
           },
           "autostart": {
             "type": "boolean",
-            "description": "Spawn on startup. Defaults to true; false leaves the pane idle until Start."
+            "description": "Spawn on startup. Defaults to true; false leaves the pane idle until Start (`procdeck start <id>` or the UI)."
+          },
+          "group": {
+            "type": "string",
+            "description": "A slice of the deck this proc belongs to: `procdeck start <group>` / `stop <group>` act on every proc in it, and the UI shows the group as a section. Ids stay as they are. A group may carry the name of its main proc (`{ \"id\": \"career\", \"group\": \"career\" }`) as long as that proc is in it.",
+            "examples": ["career"]
           },
           "url": {
             "type": "string",