kith-coord 0.1.2 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,25 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.4 — 2026-10-22
4
+
5
+ - Include the optional existing VS Code/Cursor adapter, bundling the same Kith core and a read-only view. Preserve existing MCP configuration and native trust/approval controls.
6
+
7
+ - Stop inventing fresh edit times for deleted files or future mtimes in repeated passive scans. Keep overlap detection independent of timed recent-file visibility.
8
+ - Diagnose existing global MCP configurations as well as project entries, recognize the uninitialized first-task state, and identify moved launchers or incorrect repository pins without changing files. Clarify global setup versus project instructions and per-call repository selection.
9
+ - Query Windows process creation time through the kernel-backed .NET Process API directly, avoiding Get-Process module auto-loading while retaining bounded fail-closed identity inspection.
10
+
11
+ - Launch dev servers with `kith dev`: allocate a port, set `PORT`/`KITH_PORT`, substitute literal `{port}` arguments, renew the reservation during supervision, and stop the process group before release. Add foreground `kith_run_dev_server` with the same permission/cancellation boundary as mutex commands. Native Windows supervision remains refused.
12
+ - Add optional bounded waiting to `begin`, `lock acquire`, `kith_begin_work`, and `kith_check_and_lock_files`. Defaults remain fail-fast; timeout/cancellation leave no partial claim. Worktree creation follows successful ownership. File retry does not promise FIFO order; task dependencies provide explicit ordering.
13
+ - Advance the additive MCP protocol to 1.3 and refresh its schema snapshot. No SQLite migration is required.
14
+
15
+ ## 0.1.3 — 2026-10-22
16
+
17
+ - Repair automatic client setup: merge existing settings, preserve custom transports, keep private original-byte backups and refuse malformed or redirected configuration before client writes. Register Claude Code in its user MCP configuration and use the installed Node/CLI paths. Global clients select repositories per task; project configurations retain their pinned checkout. Existing hooks, permissions and session ownership stay intact.
18
+ - Canonicalize Windows short home paths before containment checks; allow a bounded cold-start window for Windows process inspection and report probe failures while retaining fail-closed ownership. Keep the MCP renewal test running past its initial expiry with allowance for OS inspection overhead.
19
+ - Add optional per-call `repository` routing (protocol 1.2) for one global MCP connection across projects. Desktop startup at `/` or HOME connects without creating a project database; missing project context returns a tool error. Keep capabilities and command cleanup scoped to each repository, retain pinned `--repo` connections, and refuse filesystem-root coordination. Global setup from HOME writes private configuration backups without initializing a project database.
20
+ - Make the optional read-only watcher compare full paths across linked worktrees of the same Git repository, including common hotspot files. Discover retained/hidden linked worktrees, exclude byte-identical dirty copies, clear resolved alerts, retain unavailable scan health and handle NUL-delimited filenames. Remove speculative cross-repository contract and agent-attribution heuristics.
21
+ - Bound menu-bar subprocess polling, drain stdout/stderr concurrently and show unavailable scans without a clean verdict. Include a universal Intel/Apple Silicon macOS helper in the package and exercise the process runner in macOS CI. Cap overlap rows at eight and label them as observations rather than proven collisions. The view observes differing or unverified uncommitted paths; it does not enforce claims or prove compatibility.
22
+
3
23
  ## 0.1.2 — 2026-10-21
4
24
 
5
25
  - Address AgentScrum’s first external Claude Code/OpenCode task trial: compact default MCP status (protocol 1.1; full contracts remain opt-in), omit unchanged contracts from edit reports, and return the current worktree-bearing agent record immediately.
package/README.md CHANGED
@@ -38,15 +38,27 @@ The [reliability contract](docs/reliability.md) defines ownership, verification,
38
38
 
39
39
  Requires **Git 2.38+** and **Node.js 22.13+ on 22.x or Node.js 24+**. Full workflows target macOS and Linux. Version 0.1.1 also validates native Windows MCP claims, worktrees, ports, integration and recovery; supervised mutex commands and shell hooks require macOS/Linux or WSL. See the [support evidence](docs/client-validation.md#native-windows).
40
40
 
41
- Install the release, then configure your project:
41
+ Git recording and integration require a commit identity configured for the repository (`user.name` and `user.email`). Kith does not change your global Git identity.
42
+
43
+ Install the release:
44
+
45
+ ```sh
46
+ npm install --global kith-coord@0.1.4
47
+ ```
48
+
49
+ Choose the setup scope your client needs:
50
+
51
+ - **Global desktop/CLI connection:** run `kith setup --dry-run`, then `kith setup`. Restart/reconnect the configured client. A desktop agent supplies the absolute Git `repository` on each tool call; no whole-Mac ownership database is created.
52
+ - **Project configuration and agent instructions:** run the following inside the checkout. This is the default for project-scoped clients. Existing global connections need not be registered again; use `kith init --only agents` when only project guidance is needed.
42
53
 
43
54
  ```sh
44
- npm install --global kith-coord@0.1.2
45
55
  cd /path/to/your/project
46
56
  kith init --dry-run
47
57
  kith init
48
58
  ```
49
59
 
60
+ Setup preserves peer configurations, hooks and permissions. A written configuration is not a confirmed connection: check Kith's server status in the client, then ask it to begin an isolated task. `kith doctor /absolute/checkout` checks global and project launcher files without starting clients or creating project state. See [client setup](docs/integrations.md#configure-detected-local-clients).
61
+
50
62
  For source installation and the disposable demo, use the pinned **pnpm 10.20.0**:
51
63
 
52
64
  ```sh
@@ -91,10 +103,24 @@ Default setup installs MCP configuration for Claude, Codex and Cursor plus agent
91
103
  | Cursor | Native CLI workflow and fail-closed edit hooks validated; GUI discovery/trust unvalidated |
92
104
  | Other MCP clients | stdio server via `kith mcp`; client-specific validation required |
93
105
 
106
+ For VS Code and Cursor, the [editor extension](extensions/editor) offers a bundled MCP server and a small read-only status indicator. Install its VSIX through **Extensions → Install from VSIX**. It preserves existing MCP entries and leaves server approval and tool permissions to the editor. No global npm installation is needed; compatible Node.js is still required.
107
+
94
108
  Native checks are version-specific. GUI discovery and persisted project trust need separate checks. See [integration setup](docs/integrations.md), [recorded validation](docs/client-validation.md), and [session ownership](docs/sessions-and-mutexes.md) before mixing hooks, CLI commands, and MCP clients.
95
109
 
96
110
  The npm package is **`kith-coord`**, with the command name **`kith`**. For a pinned npx MCP launcher, see [registry setup](docs/integrations.md#registry-installation). The unrelated npm package `kith` is not this project.
97
111
 
112
+ ## Dev servers and shared config
113
+
114
+ In version 0.1.4, `kith dev` runs a server with its allocated `PORT` and supports explicit `{port}` arguments. File claims also accept an optional bounded wait:
115
+
116
+ ```sh
117
+ kith dev --agent web-a -- npm run dev -- --port '{port}'
118
+ # Within an existing owned session:
119
+ kith lock acquire --agent worker-1 --scope package.json --wait --wait-ms 30000
120
+ ```
121
+
122
+ See [dev-server launch and waiting claims](docs/usage.md#launch-a-dev-server-on-its-allocated-port) for framework flags, session setup, cancellation, and MCP usage.
123
+
98
124
  ## How a task moves through Kith
99
125
 
100
126
  1. **Begin through MCP.** Call `kith_begin_work` with a unique `agentId`, explicit `scopeGlobs`, and `isolateWorktree: true`. The connection retains session ownership; no shell exports are needed for this MCP-only workflow.
Binary file