@savvy-web/cli 2.2.1 → 2.3.0

package/README.md

@@ -55,6 +55,21 @@ npx savvy clean --globs dist,.turbo,coverage
 - `savvy commit` — the husky/Claude hook handlers (session-start, pre-commit-message, post-commit-verify).
 - `savvy changeset` — changeset lint, check, transform, version, config validation, and dependency changesets.
 - `savvy lint` — formatters for package.json, the pnpm workspace file and YAML.
+- `savvy repos` — the vendored reference repos declared in `.repos/config.json`: `status`, `sync`, `pin`, `add` and `note`.
+
+## Vendored repos are read-only
+
+`savvy repos sync`, `add` and `pin` leave every vendored tree under `.repos/` read-only at the OS level — files `0444`, directories `0555`. Reading a vendored source needs no extra step; writing to one fails with `EACCES` by design, because those trees mirror an upstream repo at a pinned ref and any local edit is lost on the next sync.
+
+```bash
+npx savvy repos sync
+# reconciles .repos/ with the manifest and re-locks every tree
+
+npx savvy repos pin effect v4.0.0
+# fetches, checks out the new ref, re-locks, and stages the gitlink and manifest
+```
+
+A manual `chmod` only holds until the next `sync` or `pin`. Route changes through `savvy repos` instead.
 
 Run any command with `--help` to see its full surface:
 

package/cli/index.js

@@ -76,7 +76,7 @@ const rootCommand = Command.make("savvy").pipe(Command.withSubcommands([
 * CLI application: reads argv from the Stdio service provided by NodeServices.
 * (v4's `Command.run` takes only `version` — the name comes from the root command.)
 */
-const cli = Command.run(rootCommand, { version: "2.2.1" });
+const cli = Command.run(rootCommand, { version: "2.3.0" });
 /**
 * Shared workspace services from `@effected/workspaces`, wired as a
 * self-contained unit and built ONCE (layers memoize by reference).
@@ -111,11 +111,11 @@ const BaseLive = Layer.mergeAll(WorkspaceLive, GitLive, ChangesetConfigReader.la
 */
 const InspectorAndAnalyzerLive = Changesets.BranchAnalyzer.layer.pipe(Layer.provideMerge(Changesets.ReleasePlanner.layer), Layer.provideMerge(Changesets.ConfigInspector.layer));
 /**
-* `Repos.ReposManager`, provided its `Repos.ReposConfigStore.layer` dependency
-* and the shared `Git` service. Platform requirements (`FileSystem`, `Path`)
-* flow up to `NodeServices.layer`.
+* `Repos.ReposManager`, provided its `Repos.ReposConfigStore.layer` and
+* `Repos.ReposLockdown.layer` dependencies plus the shared `Git` service.
+* Platform requirements (`FileSystem`, `Path`) flow up to `NodeServices.layer`.
 */
-const ReposGroupLive = Repos.ReposManager.layer.pipe(Layer.provide(Repos.ReposConfigStore.layer), Layer.provide(GitLive));
+const ReposGroupLive = Repos.ReposManager.layer.pipe(Layer.provide(Repos.ReposConfigStore.layer), Layer.provide(Repos.ReposLockdown.layer), Layer.provide(GitLive));
 /**
 * `ToolDiscovery` from `@effected/commands`, wired to this workspace. Its
 * `LocalExec` contract — the argv prefix that runs a project-local binary — is

package/commands/repos/commands/add.js

@@ -15,9 +15,10 @@ import { Argument, Command, Flag } from "effect/unstable/cli";
 * is the common, friendly case and always exits 0 (the manifest is created
 * on demand by `add` itself, so this only fires on a read that raced a
 * concurrent removal). A `ReposConfigError` with kind `"invalid"` means the
-* manifest exists but is corrupt or unreadable, and `GitSubmoduleError`
-* means the underlying git command failed -- both are real failures, logged
-* and reported via a non-zero exit code.
+* manifest exists but is corrupt or unreadable, `GitSubmoduleError` means
+* the underlying git command failed, and `ReposLockdownError` means the
+* OS-permission lockdown pass on a vendored tree failed -- all three are
+* real failures, logged and reported via a non-zero exit code.
 *
 * @example
 * ```bash
@@ -51,6 +52,9 @@ const runReposAdd = (cwd, opts) => Effect.gen(function* () {
 }), Effect.catchTag("GitSubmoduleError", (error) => {
 	process.exitCode = 1;
 	return Effect.log(error.message);
+}), Effect.catchTag("ReposLockdownError", (error) => {
+	process.exitCode = 1;
+	return Effect.log(error.message);
 }));
 /* v8 ignore start -- CLI registration; handler tested via runReposAdd */
 const addCommand = Command.make("add", {

package/commands/repos/commands/pin.js

@@ -14,9 +14,11 @@ import { Argument, Command, Flag } from "effect/unstable/cli";
 * A `ReposConfigError` with kind `"missing"` -- nothing vendored yet -- is
 * the common, friendly case and always exits 0. A `ReposConfigError` with
 * kind `"invalid"` means the manifest exists but is corrupt or unreadable,
-* `GitSubmoduleError` means the underlying git command failed, and
-* `RepoNotFoundError` means the named repo isn't in the manifest -- all
-* three are real failures, logged and reported via a non-zero exit code.
+* `GitSubmoduleError` means the underlying git command failed,
+* `RepoNotFoundError` means the named repo isn't in the manifest, and
+* `ReposLockdownError` means the OS-permission lockdown pass on a vendored
+* tree failed -- all four are real failures, logged and reported via a
+* non-zero exit code.
 *
 * @example
 * ```bash
@@ -51,6 +53,9 @@ const runReposPin = (cwd, name, ref) => Effect.gen(function* () {
 }), Effect.catchTag("RepoNotFoundError", (error) => {
 	process.exitCode = 1;
 	return Effect.log(error.message);
+}), Effect.catchTag("ReposLockdownError", (error) => {
+	process.exitCode = 1;
+	return Effect.log(error.message);
 }));
 /* v8 ignore start -- CLI registration; handler tested via runReposPin */
 const pinCommand = Command.make("pin", {

package/commands/repos/commands/sync.js

@@ -12,9 +12,11 @@ import { Command, Flag } from "effect/unstable/cli";
 * locks left behind by an interrupted fetch. Sync is idempotent repair, so
 * a `ReposConfigError` with kind `"missing"` -- the common, friendly case
 * (nothing to sync yet) -- always exits 0. A `ReposConfigError` with kind
-* `"invalid"` means the manifest exists but is corrupt or unreadable, and
-* `GitSubmoduleError` means the underlying git command failed -- both are
-* real failures, logged and reported via a non-zero exit code.
+* `"invalid"` means the manifest exists but is corrupt or unreadable,
+* `GitSubmoduleError` means the underlying git command failed, and
+* `ReposLockdownError` means the OS-permission lockdown pass on a vendored
+* tree failed -- all three are real failures, logged and reported via a
+* non-zero exit code.
 *
 * @example
 * ```bash
@@ -44,6 +46,9 @@ const runReposSync = (cwd) => Effect.gen(function* () {
 }), Effect.catchTag("GitSubmoduleError", (error) => {
 	process.exitCode = 1;
 	return Effect.log(error.message);
+}), Effect.catchTag("ReposLockdownError", (error) => {
+	process.exitCode = 1;
+	return Effect.log(error.message);
 }));
 /* v8 ignore start -- CLI registration; handler tested via runReposSync */
 const syncCommand = Command.make("sync", { cwd: cwdOption }, ({ cwd }) => runReposSync(cwd)).pipe(Command.withDescription("Reconcile vendored submodules with the manifest: init missing, apply sparse, clear locks"));

package/commands/repos/index.js

@@ -28,6 +28,10 @@ const _reposCommand = Command.make("repos").pipe(Command.withSubcommands([
 * The requirements channel names `Repos.ReposManager` rather than `never`:
 * `Command.withSubcommands` propagates each subcommand's requirements up into
 * the group's `R`, which the root assembly discharges via `AppLive`.
+*
+* The error channel now also names `Repos.ReposLockdownError`: `sync`/`add`/
+* `pin` unlock and re-lock the vendored tree around their git mutations
+* (Task 2), so a lockdown chmod failure can surface from any of the three.
 */
 const reposCommand = _reposCommand;
 

package/index.d.ts

@@ -297,8 +297,12 @@ declare const runReposSync: (cwd: string) => Effect.Effect<void, never, Repos.Re
  * The requirements channel names `Repos.ReposManager` rather than `never`:
  * `Command.withSubcommands` propagates each subcommand's requirements up into
  * the group's `R`, which the root assembly discharges via `AppLive`.
+ *
+ * The error channel now also names `Repos.ReposLockdownError`: `sync`/`add`/
+ * `pin` unlock and re-lock the vendored tree around their git mutations
+ * (Task 2), so a lockdown chmod failure can surface from any of the three.
  */
-declare const reposCommand: Command.Command<"repos", Record<string, never>, Record<string, never>, Repos.GitSubmoduleError, Repos.ReposManager>;
+declare const reposCommand: Command.Command<"repos", Record<string, never>, Record<string, never>, Repos.GitSubmoduleError | Repos.ReposLockdownError, Repos.ReposManager>;
 //#endregion
 export { changesetCommand, checkCommand, commitCommand, initCommand, lintCommand, reposCommand, runChangesetCheck, runChangesetInit, runCheck, runCli, runCommitCheck, runCommitInit, runInit, runLintCheck, runLintInit, runReposStatus, runReposSync };
 //# sourceMappingURL=index.d.ts.map

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@savvy-web/cli",
-	"version": "2.2.1",
+	"version": "2.3.0",
 	"private": false,
 	"description": "The savvy CLI — unified commit, changeset, and lint commands for the Silk Suite",
 	"homepage": "https://github.com/savvy-web/systems/tree/main/packages/cli",
@@ -32,13 +32,13 @@
 	},
 	"dependencies": {
 		"@effect/platform-node": "4.0.0-beta.101",
-		"@effected/commands": "^0.2.1",
+		"@effected/commands": "^0.3.1",
 		"@effected/git": "^0.5.2",
 		"@effected/jsonc": "^0.5.2",
 		"@effected/templates": "^0.1.1",
-		"@effected/workspaces": "^0.9.5",
+		"@effected/workspaces": "^0.10.0",
 		"@effected/yaml": "^0.6.1",
-		"@savvy-web/silk-effects": "5.3.1",
+		"@savvy-web/silk-effects": "5.4.0",
 		"effect": "4.0.0-beta.101"
 	}
 }