@savvy-web/mcp 2.0.19 → 2.1.0

package/README.md

@@ -50,7 +50,7 @@ npx @modelcontextprotocol/inspector savvy-mcp .
 - `changeset_deps_regen` — regenerates pure-dependency changesets: deletes stale ones and writes fresh single-package, patch-bump changesets from the cumulative dependency diff. Mutating unless `dryRun` is set, in which case it reports what it would delete and write without touching the filesystem. Backed by `silk-effects`' `Changesets.DepsRegen`.
 - `biome_check` — run Biome over a path and get structured diagnostics back: `mode=check` (lint, format and organize-imports) or `mode=lint`. Unlike most of the other tools it can mutate — pass `write` for safe fixes or `unsafe` for unsafe ones (both git-reversible) — so it returns the same diagnostics the Biome LSP surfaces for files you have edited.
 - `repos_inspect` — read-only inspection of vendored repositories: `mode=status` reports per-repo presence, the gitlink commit, working-tree dirtiness, and stale note ids; `mode=config` surfaces the validated `.repos/config.json` manifest and its entries. Returns markdown-escaped output since vendored-repo content is untrusted input. Backed by the same `silk-effects` `Repos` services the `savvy` CLI uses.
-- `repos_manage` — manages vendored repositories (mutating counterpart to repos_inspect): `action=sync` initializes any missing submodules (`git submodule update --init --depth 1`), applies sparse-checkout from the manifest, and clears stale git locks; `action=pin` fetches and checks out the new ref, staging the updated gitlink and manifest; `action=add` adds a new repo entry; `action=note` appends a short note to a repo. Pin and add stage git changes for the caller to commit. Backed by the same `silk-effects` `Repos` services the `savvy` CLI uses.
+- `repos_manage` — manages vendored repositories (mutating counterpart to repos_inspect): `action=sync` initializes any missing submodules (`git submodule update --init --depth 1`), applies sparse-checkout from the manifest, and clears stale git locks; `action=pin` fetches and checks out the new ref, staging the updated gitlink and manifest; `action=add` adds a new repo entry; `action=note` appends a short note to a repo. Pin and add stage git changes for the caller to commit. `sync`, `pin` and `add` unlock the vendored tree for the duration of their git work and leave it read-only again afterwards (files `0444`, directories `0555`), so an agent that hits `EACCES` writing into `.repos/` should route the change through this tool rather than `chmod`. Backed by the same `silk-effects` `Repos` services the `savvy` CLI uses.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@savvy-web/mcp",
-	"version": "2.0.19",
+	"version": "2.1.0",
 	"private": false,
 	"description": "The savvy MCP server — Silk Suite tooling and library knowledge for coding agents",
 	"homepage": "https://github.com/savvy-web/systems/tree/main/packages/mcp",
@@ -32,10 +32,10 @@
 	},
 	"dependencies": {
 		"@effect/platform-node": "4.0.0-beta.101",
-		"@effected/commands": "^0.2.1",
-		"@effected/workspaces": "^0.9.5",
+		"@effected/commands": "^0.3.1",
+		"@effected/workspaces": "^0.10.0",
 		"@modelcontextprotocol/sdk": "^1.29.0",
-		"@savvy-web/silk-effects": "5.3.1",
+		"@savvy-web/silk-effects": "5.4.0",
 		"effect": "4.0.0-beta.101",
 		"zod": "^4.4.3"
 	}

package/runtime.js

@@ -59,12 +59,14 @@ const makeSilkRuntimeLayer = (cwd) => {
 	const changesetConfig = ChangesetConfig.layer.pipe(Layer.provide(ChangesetConfigReader.layer));
 	const depsRegen = Changesets.DepsRegen.layer.pipe(Layer.provide(inspectorAndAnalyzer), Layer.provide(SilkPublishability.layerAdaptive.pipe(Layer.provide(changesetConfig))), Layer.provide(changesetConfig));
 	/**
-	* `ReposManager.layer` requires `ReposConfigStore`, so it is given its own
-	* `ReposConfigStore.layer` reference; the store is ALSO merged in directly so
-	* `repos_inspect`'s config mode can resolve it on its own. Same reference —
-	* one store instance.
+	* `ReposManager.layer` requires `ReposConfigStore | ReposLockdown`, so it is
+	* given its own `ReposConfigStore.layer` reference; the store is ALSO merged
+	* in directly so `repos_inspect`'s config mode can resolve it on its own.
+	* Same reference — one store instance. `ReposLockdown.layer` needs only the
+	* platform services, which flow up from the outer `NodeServices.layer`
+	* provision like `ReposManager`'s own `FileSystem`/`Path` requirement does.
 	*/
-	const repos = Layer.mergeAll(Repos.ReposConfigStore.layer, Repos.ReposManager.layer.pipe(Layer.provide(Repos.ReposConfigStore.layer)));
+	const repos = Layer.mergeAll(Repos.ReposConfigStore.layer, Repos.ReposManager.layer.pipe(Layer.provide(Repos.ReposConfigStore.layer), Layer.provide(Repos.ReposLockdown.layer)));
 	return Layer.mergeAll(SilkWorkspaceAnalyzer.layer.pipe(Layer.provide(analyzerDeps)), Turbo.TurboInspector.layer.pipe(Layer.provide(toolDiscovery)), inspectorAndAnalyzer, depsRegen, repos).pipe(Layer.provideMerge(kitGraph));
 };