@procedures/git 0.1.0 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,43 @@
 # @procedures/git
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [a9dc8c8]
+  - @procedures/client@0.2.1
+  - @procedures/shell@0.2.1
+
+## 0.2.0
+
+### Minor Changes
+
+- 0cf4bea: **Invocation capabilities** (packages/documentation/CAPABILITIES-2026-10.md, the guide is client/docs/CAPABILITIES.md). Each call operates with a capability: a clearance, permitted effects and a deadline. A nested call gets the same capability or a narrower one.
+  
+  - Procedures declare `metadata.effects` (`reads`, `writes`, `destructive`, `idempotent`). Each procedure of these packages declares them.
+  - `hostPolicy({ capability, readOnly, clearanceOrder, resources, admitItem })`, and `new Client({ capability })`. A refused call gives `FORBIDDEN` (HTTP 403) with a reason.
+  - `ctx.capability` and `ctx.resources` are new required fields of `ProcedureContext`. A test that makes a context by hand adds `capability: {}` and `resources: {}`.
+  - An application gives its clearance and resource types by augmenting `Register`.
+  - The timeout interceptor sets the deadline of the capability, and a remote call sends the remaining time.
+  - The MCP tools have hints (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`) from the effects. `mark mcp --read-only` (or `MCP_READ_ONLY=1`) serves only the tools that change nothing.
+  - **Breaking:** `git.remote` only reads the URL. `git.remote.set` sets it (before: `git.remote` with `url`).
+- 76d0d64: **Breaking:** an import of a package registers nothing. The `./register` entry of a package registers its procedures, and the procedures of the modules that they need, in the global registry (ARCHITECTURE-PROPOSALS-2026-10, P9).
+  
+  - `import "@procedures/git"` gives the exports and registers nothing. Use `import "@procedures/git/register"`, or give `gitModule` (`@procedures/git/module`) to `createRegistry()`.
+  - `import "@procedures/client/register"` registers the control flow (`client.chain` and the others) and `procedure.define`/`get`/`list`/`delete`. `createRegistry()` adds them to each new registry, as before. The new `registerClientProcedures(registry?)` does the same for any registry.
+  - Each `register<Name>Procedures(registry?)` function is in the module of its package, takes a registry (the global one by default) and registers the modules that the package requires. `registerBridge` (splay) and `register` (store) are now `registerSplayProcedures` and `registerStoreProcedures`. The old names stay for one version.
+  - `sideEffects` names only `./dist/register.js`, so a bundler can drop the rest of a package.
+  - The bundles require `clientModule`, so `@procedures/bundle-mcp/register` gives the whole tool surface.
+  - `lib new` makes `src/module.ts` and a root without side effects, and `procedure new` adds procedures to the module.
+
+### Patch Changes
+
+- Updated dependencies [0cf4bea]
+- Updated dependencies [44d3e30]
+- Updated dependencies [76d0d64]
+  - @procedures/client@0.2.0
+  - @procedures/shell@0.2.0
+
 ## 0.1.0
 
 The first release on npm. The packages of the client monorepo have one version together.

package/README.md

@@ -73,7 +73,7 @@ yarn add @procedures/git
 
 ```typescript
 import { Client, LocalTransport, PROCEDURE_REGISTRY } from "@procedures/client";
-import "@procedures/git"; // registers its procedures
+import "@procedures/git/register"; // registers its procedures
 
 const client = new Client(new LocalTransport({ registry: PROCEDURE_REGISTRY }));
 
@@ -538,7 +538,7 @@ console.log(`Cloned to ${clone.path}`);
 
 #### `git.remote`
 
-Get or set remote URLs.
+Get the URL of a remote. It changes nothing.
 
 **Path:** `["git", "remote"]`
 
@@ -546,8 +546,6 @@ Get or set remote URLs.
 interface GitRemoteInput {
   /** Remote name (default: origin) */
   name?: string;
-  /** New URL to set (if provided, sets the URL; otherwise gets it) */
-  url?: string;
   /** Working directory */
   cwd?: string;
 }
@@ -560,6 +558,23 @@ interface GitRemoteOutput {
 }
 ```
 
+#### `git.remote.set`
+
+Set the URL of a remote, or add the remote when it is missing. Before 0.2.0, `git.remote` with `url` did this.
+
+**Path:** `["git", "remote", "set"]`
+
+```typescript
+interface GitRemoteSetInput {
+  /** Remote name (default: origin) */
+  name?: string;
+  /** The URL of the remote */
+  url: string;
+  /** Working directory */
+  cwd?: string;
+}
+```
+
 ### Predicate Procedures
 
 These procedures return boolean predicates useful for conditional logic.
@@ -842,7 +857,8 @@ fs.writeFileSync("backup.patch", exported.patch);
 | | `git.pull` | Pull from remote |
 | | `git.fetch` | Fetch from remote |
 | | `git.clone` | Clone repository |
-| | `git.remote` | Manage remotes |
+| | `git.remote` | Get the URL of a remote |
+| | `git.remote.set` | Set the URL of a remote |
 | **Predicates** | `git.hasChanges` | Check for any changes |
 | | `git.hasStagedChanges` | Check for staged changes |
 | | `git.hasUnstagedChanges` | Check for unstaged changes |
@@ -969,7 +985,7 @@ graph LR
 
 ```typescript
 // bundle-dev/src/register.ts
-import "@procedures/git"; // registers its procedures
+import "@procedures/git/register"; // registers its procedures
 
 // client-lib uses git procedures internally
 import { gitStatus, gitAdd, gitCommit } from "@procedures/git";