@procedures/store 0.1.0 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # @procedures/store
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [a9dc8c8]
+  - @procedures/client@0.2.1
+  - @procedures/collections@0.2.1
+
+## 0.2.0
+
+### Minor Changes
+
+- 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/collections@0.2.0
+
 ## 0.1.0
 
 The first release on npm. The packages of the client monorepo have one version together.

package/README.md

@@ -59,7 +59,7 @@ These parts moved here from `@procedures/client` (roadmap 3.2):
 - The synced registry (`createSyncedRegistry()`, `SyncedProcedureRegistry`), the serialization of procedures, and the dynamic handler loader with an allowlist (`createDynamicHandlerLoader`).
 - `procedure.register`, which registers a procedure from a handler reference.
 
-Importing the package registers its procedures.
+Importing `@procedures/store/register` registers its procedures. An import of the package root registers nothing.
 
 ## License