@engramx/idl 0.16.0-rc.20 → 0.16.0-rc.21

package/dist/engram.did

@@ -2091,6 +2091,9 @@ type Engram =
    /// Owner-only, Billing-class: the signing floor, the balance, one signature's price, and how many
    /// payment signatures the balance carries above the floor before `signX402Payment` is refused by
    /// name. The same numbers the check uses, so Billing can say only what the engram enforces.
+   /// ⟨2026-11-01, "6 fix"⟩ Refused by name (`#Unavailable`) while this engram has not read its own
+   /// freezing setting: there is no floor to serve then, and a 30-day figure would be a made-up one
+   /// (ADR-0002) — the signers refuse in that state too, so the refusal is the truth on Billing.
    getSigningFloor: () -> (Result_62) query;
    /// The registry that spawned this engram, if it recorded one.
    /// 

package/dist/engram.idl.d.ts

@@ -1259,6 +1259,9 @@ export interface Engram {
    * / Owner-only, Billing-class: the signing floor, the balance, one signature's price, and how many
    * / payment signatures the balance carries above the floor before `signX402Payment` is refused by
    * / name. The same numbers the check uses, so Billing can say only what the engram enforces.
+   * / ⟨2026-11-01, "6 fix"⟩ Refused by name (`#Unavailable`) while this engram has not read its own
+   * / freezing setting: there is no floor to serve then, and a 30-day figure would be a made-up one
+   * / (ADR-0002) — the signers refuse in that state too, so the refusal is the truth on Billing.
    */
   getSigningFloor: ActorMethod<[], Result_62>;
   /**

package/dist/registry.did

@@ -1549,6 +1549,33 @@ service : {
          invite: opt text;
          walletProof: opt blob;
        }) -> (Result);
+  /// Admin (the wasm admin): give one grown engram's working memory back, in place. The engram's
+  /// stable graph is copied into its stable memory and the SAME module is reinstalled with
+  /// `wasm_memory_persistence = ?#replace`, so the engram restarts in a fresh, small wasm memory with
+  /// every file, version, record entry, setting and key it had (MemoryReset.mo).
+  /// 
+  /// REFUSES, and changes nothing, when: the caller is not the wasm admin; the registry does not know
+  /// the engram; a change of owner or a restart is open; its status cannot be read (a sovereign engram);
+  /// it is not running; it is not on the current template; its wasm memory is under
+  /// `MemoryReset.WASM_FLOOR_BYTES` (nothing to give back — and so a second reset straight after a
+  /// first); its balance is short of the install hold above its own freezing line (no dip, no deposit);
+  /// or one of its own calls is in flight ("Busy, try again").
+  /// 
+  /// WHO PAYS: the engram, as for any install — `install_code` is charged to the canister it installs
+  /// on, and the stabilise / rebuild steps are the engram's own messages. The registry deposits
+  /// nothing; it pays only for its own calls. Two installs run: an ordinary one of the same module
+  /// first, which is the network's test for a call in flight while nothing is yet at stake, then the
+  /// replace.
+  /// 
+  /// ONCE STARTED it finishes or says the engram is HELD: between the stabilise call and the replace
+  /// install the engram refuses every message, so a failure there answers `#Unavailable` naming the
+  /// step, and running this method again picks up where it stopped (it reads the held state from the
+  /// engram itself). Do not publish a new template while a reset is held.
+  /// 
+  /// Never run on production engrams (the owner's ruling). On the staging network, as the wasm admin,
+  /// with the engram's canister id in ENGRAM:
+  ///     icp canister call registry-staging resetEngramMemory "(principal \"$ENGRAM\")" -e ic
+  resetEngramMemory: (canisterId: principal) -> (Result);
   /// Restart YOUR OWN stopped engram.
   /// 
   /// CALLER: the owner, from the app's restart sheet (ADR-0020). Afterwards the app runs the engram's

package/dist/registry.idl.d.ts

@@ -1497,6 +1497,35 @@ export interface _SERVICE {
     ],
     Result
   >;
+  /**
+   * / Admin (the wasm admin): give one grown engram's working memory back, in place. The engram's
+   * / stable graph is copied into its stable memory and the SAME module is reinstalled with
+   * / `wasm_memory_persistence = ?#replace`, so the engram restarts in a fresh, small wasm memory with
+   * / every file, version, record entry, setting and key it had (MemoryReset.mo).
+   * /
+   * / REFUSES, and changes nothing, when: the caller is not the wasm admin; the registry does not know
+   * / the engram; a change of owner or a restart is open; its status cannot be read (a sovereign engram);
+   * / it is not running; it is not on the current template; its wasm memory is under
+   * / `MemoryReset.WASM_FLOOR_BYTES` (nothing to give back — and so a second reset straight after a
+   * / first); its balance is short of the install hold above its own freezing line (no dip, no deposit);
+   * / or one of its own calls is in flight ("Busy, try again").
+   * /
+   * / WHO PAYS: the engram, as for any install — `install_code` is charged to the canister it installs
+   * / on, and the stabilise / rebuild steps are the engram's own messages. The registry deposits
+   * / nothing; it pays only for its own calls. Two installs run: an ordinary one of the same module
+   * / first, which is the network's test for a call in flight while nothing is yet at stake, then the
+   * / replace.
+   * /
+   * / ONCE STARTED it finishes or says the engram is HELD: between the stabilise call and the replace
+   * / install the engram refuses every message, so a failure there answers `#Unavailable` naming the
+   * / step, and running this method again picks up where it stopped (it reads the held state from the
+   * / engram itself). Do not publish a new template while a reset is held.
+   * /
+   * / Never run on production engrams (the owner's ruling). On the staging network, as the wasm admin,
+   * / with the engram's canister id in ENGRAM:
+   * /     icp canister call registry-staging resetEngramMemory "(principal \"$ENGRAM\")" -e ic
+   */
+  resetEngramMemory: ActorMethod<[Principal], Result>;
   /**
    * / Restart YOUR OWN stopped engram.
    * /

package/dist/registry.idl.js

@@ -558,6 +558,7 @@ export const idlFactory = ({ IDL }) => {
       [Result],
       [],
     ),
+    resetEngramMemory: IDL.Func([IDL.Principal], [Result], []),
     restartMyStoppedEngram: IDL.Func([], [Result_8], []),
     returnToManaged: IDL.Func([], [Result], []),
     setAdmin: IDL.Func([IDL.Principal], [Result], []),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@engramx/idl",
-  "version": "0.16.0-rc.20",
+  "version": "0.16.0-rc.21",
   "description": "The Candid interfaces of the EngramX canisters (engram, registry, market) — the .did files and the JS/TS IDL factories generated from them, published with every release so code that calls them pins the interface by version.",
   "license": "Apache-2.0",
   "author": "EngramX <developer@engramx.ai>",