@procedures/procedure 0.1.0 → 0.2.1

package/src/procedures/procedure/registry.ts

@@ -5,7 +5,7 @@
  * Enables procedure-as-data patterns, remote registration, and persistence.
  */
 
-import { defineProcedure, PROCEDURE_REGISTRY, pathToKey, keyToPath } from "@procedures/client";
+import { defineProcedure, PROCEDURE_REGISTRY, REGISTRY_READ_EFFECTS, pathToKey, keyToPath } from "@procedures/client";
 import type { AnyProcedure, ProcedurePath } from "@procedures/client";
 import { z } from "zod";
 
@@ -57,6 +57,7 @@ export const procedureExportProcedure: AnyProcedure = defineProcedure({
   metadata: {
     description: "Export a procedure definition as JSON",
     tags: ["procedure", "registry"],
+    effects: REGISTRY_READ_EFFECTS,
     args: ["path"],
     shorts: {},
     output: "json",

package/src/register.ts

@@ -1,19 +1,11 @@
 /**
- * Importing this file registers the procedures of @procedures/procedure in the global
- * registry (DECISIONS-2026-10, "Every package root registers its procedures"). The procedures as
- * data are in `module.ts`, which registers nothing: a host with its own registry uses that one.
+ * Importing this file registers the procedures of @procedures/procedure, and of the modules that it
+ * requires, in the global registry: `import "@procedures/procedure/register"`. The package root and the
+ * `./module` entry register nothing (ARCHITECTURE-PROPOSALS-2026-10, P9).
  */
 
-import { PROCEDURE_REGISTRY } from "@procedures/client";
-import { procedureModule } from "./module.js";
+import { registerProcedureProcedures } from "./module.js";
 
 export * from "./module.js";
 
-export function registerProcedureProcedures(): void {
-  // Override makes the registration idempotent. procedure.list and procedure.get are the core
-  // ones: this package does not replace them (docs review DOC-6).
-  PROCEDURE_REGISTRY.registerAll(procedureModule.procedures, { override: true });
-}
-
-// Auto-register
 registerProcedureProcedures();