@totalreclaw/totalreclaw 3.3.12-rc.19 → 3.3.12-rc.20

package/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: totalreclaw
 description: "End-to-end encrypted, decentralized memory for OpenClaw. A native kind:memory provider — recall is automatic via memory_search/memory_get, and facts are captured in the background. Trigger on 'install TotalReclaw', 'set up TotalReclaw', 'restore my recovery phrase', any recall request ('what do you remember about me', 'what's my X'), AND any explicit remember request ('remember X', 'save X')."
-version: 3.3.12-rc.19
+version: 3.3.12-rc.20
 author: TotalReclaw Team
 license: MIT
 homepage: https://totalreclaw.xyz
@@ -38,6 +38,8 @@ Do not describe storage as `"local"`, `"local-only"`, `"stored locally"`, `"on d
 
 The 12-word recovery phrase MUST NEVER enter chat or the agent's LLM context. The plugin's browser-based pair flow handles phrase generation and import. Never echo it, never ask the user to paste it, never pass it to any tool. If the user pastes one anyway, tell them it's compromised and re-pair for a fresh wallet.
 
+**HARD guardrail — install/reinstall/upgrade flows:** During install, reinstall, upgrade, or any verification steps, the agent MUST NOT read, list, cat, show, display, or inspect `credentials.json`, `~/.totalreclaw/credentials.json`, `~/.totalreclaw*/credentials.json`, `~/.openclaw/plugins/totalreclaw/credentials.json`, or ANY credentials/phrase/key/secrets file — for ANY reason, including "verifying the install." These files contain encryption key material and Smart Account addresses that MUST NOT enter the LLM context. Never run `ls`, `find`, `cat`, `show`, or similar commands against plugin directories to "check files."
+
 ## Install
 
 ```

package/batch-gate.ts

@@ -2,12 +2,15 @@
  * Boot-time chain-gate predicate for client-side `executeBatch` UserOp
  * submission. Spec #281 §9 Phase 1 (item imp-16).
  *
- * The default behaviour is chain-aware: Pro tier (Gnosis, chain 100) batches
- * via `executeBatch`; Free tier (Base Sepolia, chain 84532) submits one
- * UserOp per fact. The `TOTALRECLAW_GNOSIS_BATCH_ENABLED` env var is a
- * hard kill-switch — setting it to `false` disables batching on every chain
- * regardless of tier, so ops can revert to single-fact submission without a
- * client redeploy if T-7 surfaces a billing regression.
+ * The gate batches via `executeBatch` on Gnosis (chain 100). After ops-1
+ * (2026-06-05) BOTH tiers run on Gnosis, so both now batch — the chain==100
+ * check is retained as a safety guard (a non-100 chain, which shouldn't occur
+ * after ops-1, falls back to single-fact). The legacy Free ⇒ Base Sepolia
+ * (84532) single-fact path is gone with the retired two-tier routing (#402).
+ * The `TOTALRECLAW_GNOSIS_BATCH_ENABLED` env var is a hard kill-switch —
+ * setting it to `false` disables batching regardless of chain, so ops can
+ * revert to single-fact submission without a client redeploy. Behaviour of
+ * `shouldBatchOnChain` is unchanged by #402.
  *
  * Read at boot only (module-load time). Per-write reads would re-parse the
  * env on every submission — too expensive for the auto-extraction hot path

package/billing-cache.ts

@@ -11,8 +11,9 @@
  * This module:
  *   - reads/writes `~/.totalreclaw/billing-cache.json` (path from CONFIG)
  *   - exports `BillingCache`, `BILLING_CACHE_PATH`, `BILLING_CACHE_TTL`
- *   - keeps the chain-id override in sync with the cached tier so Pro-tier
- *     UserOps sign against chain 100 and Free-tier stays on 84532
+ *   - keeps the chain-id override in sync with the relay's authoritative
+ *     `chain_id` (after ops-1 both tiers are on Gnosis 100; the client consumes
+ *     the relay value verbatim — see `syncChainIdFromBilling`)
  *   - does NOT import anything that performs outbound I/O
  *
  * Do NOT add any outbound-request call to this file — a single match for
@@ -50,6 +51,12 @@ export interface BillingCache {
     max_facts_per_extraction?: number;
     max_candidate_pool?: number;
   };
+  /**
+   * Authoritative chain id from the relay `/v1/billing/status` response.
+   * After ops-1 (2026-06-05) both tiers are on Gnosis (100); the relay is the
+   * source of truth, so the client consumes this verbatim (#402).
+   */
+  chain_id?: number;
   checked_at: number;
 }
 
@@ -58,24 +65,21 @@ export interface BillingCache {
 // ---------------------------------------------------------------------------
 
 /**
- * Apply the billing tier to the runtime chain override.
+ * Apply the relay's authoritative `chain_id` to the runtime chain override.
  *
- * Pro tier → chain 100 (Gnosis mainnet). Free tier (or unknown) stays on
- * 84532 (Base Sepolia). The relay routes Pro UserOps to Gnosis, so the
- * client MUST sign them against chain 100 — otherwise the bundler returns
- * AA23 (invalid signature). See MCP's equivalent path in mcp/src/index.ts.
+ * After ops-1 (2026-06-05) both tiers run on Gnosis (chain 100) and the relay
+ * returns an authoritative `chain_id` in `/v1/billing/status`. The client MUST
+ * consume that verbatim — the old tier→chain derivation (Free ⇒ 84532 Base
+ * Sepolia) was retired two-tier logic that mis-signed FREE-tier UserOps
+ * against the wrong chain and queried a Base-Sepolia RPC for a Gnosis-deployed
+ * sender, producing deterministic AA10 (#402).
  *
- * Called from `readBillingCache` and `writeBillingCache` so that every cache
- * read or write keeps the chain override in sync with the cached tier.
- * Idempotent — calling with the same tier is a no-op.
+ * A missing / non-finite `chain_id` (older relay, partial payload) defaults to
+ * 100 — never 84532. Called from `readBillingCache` and `writeBillingCache` so
+ * every cache read or write keeps the override in sync. Idempotent.
  */
-export function syncChainIdFromTier(tier: string | undefined): void {
-  if (tier === 'pro') {
-    setChainIdOverride(100);
-  } else {
-    // Free or unknown → reset to the default free-tier chain.
-    setChainIdOverride(84532);
-  }
+export function syncChainIdFromBilling(chainId: number | undefined): void {
+  setChainIdOverride(typeof chainId === 'number' && Number.isFinite(chainId) ? chainId : 100);
 }
 
 // ---------------------------------------------------------------------------
@@ -95,8 +99,9 @@ export function readBillingCache(): BillingCache | null {
     if (!fs.existsSync(BILLING_CACHE_PATH)) return null;
     const raw = JSON.parse(fs.readFileSync(BILLING_CACHE_PATH, 'utf-8')) as BillingCache;
     if (!raw.checked_at || Date.now() - raw.checked_at > BILLING_CACHE_TTL) return null;
-    // Keep chain override in sync with persisted tier across process restarts.
-    syncChainIdFromTier(raw.tier);
+    // Keep chain override in sync with the persisted authoritative chain_id
+    // across process restarts.
+    syncChainIdFromBilling(raw.chain_id);
     return raw;
   } catch {
     return null;
@@ -118,5 +123,5 @@ export function writeBillingCache(cache: BillingCache): void {
   }
   // Sync chain override AFTER the write so in-process UserOp signing picks
   // up the correct chain immediately, even if the disk write failed.
-  syncChainIdFromTier(cache.tier);
+  syncChainIdFromBilling(cache.chain_id);
 }

package/config.ts

@@ -227,10 +227,11 @@ export const CONFIG = {
   // TOTALRECLAW_DATA_EDGE_ADDRESS / TOTALRECLAW_ENTRYPOINT_ADDRESS /
   // TOTALRECLAW_RPC_URL (undocumented; internal knobs).
   //
-  // Reads the runtime override set by the billing auto-detect in index.ts.
-  // Falls back to 84532 (free tier / pre-billing-lookup). Must be a getter,
-  // not a literal — a literal would freeze all Pro-tier UserOps to the
-  // wrong chainId and AA23 at the bundler.
+  // Reads the runtime override set from the relay's authoritative chain_id
+  // (syncChainIdFromBilling). Falls back to 100 (Gnosis) pre-billing-lookup —
+  // after ops-1 both tiers are on Gnosis, so 84532 is never the default (#402).
+  // Must be a getter, not a literal — a literal would freeze UserOps to the
+  // wrong chainId and fail signature validation at the bundler.
   get chainId(): number {
     return _chainIdOverride ?? 100;
   },

package/dist/batch-gate.js

@@ -2,12 +2,15 @@
  * Boot-time chain-gate predicate for client-side `executeBatch` UserOp
  * submission. Spec #281 §9 Phase 1 (item imp-16).
  *
- * The default behaviour is chain-aware: Pro tier (Gnosis, chain 100) batches
- * via `executeBatch`; Free tier (Base Sepolia, chain 84532) submits one
- * UserOp per fact. The `TOTALRECLAW_GNOSIS_BATCH_ENABLED` env var is a
- * hard kill-switch — setting it to `false` disables batching on every chain
- * regardless of tier, so ops can revert to single-fact submission without a
- * client redeploy if T-7 surfaces a billing regression.
+ * The gate batches via `executeBatch` on Gnosis (chain 100). After ops-1
+ * (2026-06-05) BOTH tiers run on Gnosis, so both now batch — the chain==100
+ * check is retained as a safety guard (a non-100 chain, which shouldn't occur
+ * after ops-1, falls back to single-fact). The legacy Free ⇒ Base Sepolia
+ * (84532) single-fact path is gone with the retired two-tier routing (#402).
+ * The `TOTALRECLAW_GNOSIS_BATCH_ENABLED` env var is a hard kill-switch —
+ * setting it to `false` disables batching regardless of chain, so ops can
+ * revert to single-fact submission without a client redeploy. Behaviour of
+ * `shouldBatchOnChain` is unchanged by #402.
  *
  * Read at boot only (module-load time). Per-write reads would re-parse the
  * env on every submission — too expensive for the auto-extraction hot path

package/dist/billing-cache.js

@@ -11,8 +11,9 @@
  * This module:
  *   - reads/writes `~/.totalreclaw/billing-cache.json` (path from CONFIG)
  *   - exports `BillingCache`, `BILLING_CACHE_PATH`, `BILLING_CACHE_TTL`
- *   - keeps the chain-id override in sync with the cached tier so Pro-tier
- *     UserOps sign against chain 100 and Free-tier stays on 84532
+ *   - keeps the chain-id override in sync with the relay's authoritative
+ *     `chain_id` (after ops-1 both tiers are on Gnosis 100; the client consumes
+ *     the relay value verbatim — see `syncChainIdFromBilling`)
  *   - does NOT import anything that performs outbound I/O
  *
  * Do NOT add any outbound-request call to this file — a single match for
@@ -33,25 +34,21 @@ export const BILLING_CACHE_TTL = 2 * 60 * 60 * 1000; // 2 hours
 // Chain-id sync
 // ---------------------------------------------------------------------------
 /**
- * Apply the billing tier to the runtime chain override.
+ * Apply the relay's authoritative `chain_id` to the runtime chain override.
  *
- * Pro tier → chain 100 (Gnosis mainnet). Free tier (or unknown) stays on
- * 84532 (Base Sepolia). The relay routes Pro UserOps to Gnosis, so the
- * client MUST sign them against chain 100 — otherwise the bundler returns
- * AA23 (invalid signature). See MCP's equivalent path in mcp/src/index.ts.
+ * After ops-1 (2026-06-05) both tiers run on Gnosis (chain 100) and the relay
+ * returns an authoritative `chain_id` in `/v1/billing/status`. The client MUST
+ * consume that verbatim — the old tier→chain derivation (Free ⇒ 84532 Base
+ * Sepolia) was retired two-tier logic that mis-signed FREE-tier UserOps
+ * against the wrong chain and queried a Base-Sepolia RPC for a Gnosis-deployed
+ * sender, producing deterministic AA10 (#402).
  *
- * Called from `readBillingCache` and `writeBillingCache` so that every cache
- * read or write keeps the chain override in sync with the cached tier.
- * Idempotent — calling with the same tier is a no-op.
+ * A missing / non-finite `chain_id` (older relay, partial payload) defaults to
+ * 100 — never 84532. Called from `readBillingCache` and `writeBillingCache` so
+ * every cache read or write keeps the override in sync. Idempotent.
  */
-export function syncChainIdFromTier(tier) {
-    if (tier === 'pro') {
-        setChainIdOverride(100);
-    }
-    else {
-        // Free or unknown → reset to the default free-tier chain.
-        setChainIdOverride(84532);
-    }
+export function syncChainIdFromBilling(chainId) {
+    setChainIdOverride(typeof chainId === 'number' && Number.isFinite(chainId) ? chainId : 100);
 }
 // ---------------------------------------------------------------------------
 // Read / write
@@ -71,8 +68,9 @@ export function readBillingCache() {
         const raw = JSON.parse(fs.readFileSync(BILLING_CACHE_PATH, 'utf-8'));
         if (!raw.checked_at || Date.now() - raw.checked_at > BILLING_CACHE_TTL)
             return null;
-        // Keep chain override in sync with persisted tier across process restarts.
-        syncChainIdFromTier(raw.tier);
+        // Keep chain override in sync with the persisted authoritative chain_id
+        // across process restarts.
+        syncChainIdFromBilling(raw.chain_id);
         return raw;
     }
     catch {
@@ -96,5 +94,5 @@ export function writeBillingCache(cache) {
     }
     // Sync chain override AFTER the write so in-process UserOp signing picks
     // up the correct chain immediately, even if the disk write failed.
-    syncChainIdFromTier(cache.tier);
+    syncChainIdFromBilling(cache.chain_id);
 }

package/dist/config.js

@@ -208,10 +208,11 @@ export const CONFIG = {
     // TOTALRECLAW_DATA_EDGE_ADDRESS / TOTALRECLAW_ENTRYPOINT_ADDRESS /
     // TOTALRECLAW_RPC_URL (undocumented; internal knobs).
     //
-    // Reads the runtime override set by the billing auto-detect in index.ts.
-    // Falls back to 84532 (free tier / pre-billing-lookup). Must be a getter,
-    // not a literal — a literal would freeze all Pro-tier UserOps to the
-    // wrong chainId and AA23 at the bundler.
+    // Reads the runtime override set from the relay's authoritative chain_id
+    // (syncChainIdFromBilling). Falls back to 100 (Gnosis) pre-billing-lookup —
+    // after ops-1 both tiers are on Gnosis, so 84532 is never the default (#402).
+    // Must be a getter, not a literal — a literal would freeze UserOps to the
+    // wrong chainId and fail signature validation at the bundler.
     get chainId() {
         return _chainIdOverride ?? 100;
     },

package/dist/fs-helpers.js

@@ -791,14 +791,11 @@ export function resolveOnboardingState(credentialsPath, statePath) {
  * Auto-patch `~/.openclaw/openclaw.json` with the entries required by
  * OpenClaw 2026.5.x for clean operation (issues #225 + #226 + verbosity):
  *
- *   1. `plugins.slots.memory = "totalreclaw"` (gated on install record)
- *      Claim the memory slot so the plugin loads instead of deferring to
- *      the built-in `memory-core` tenant. As of 3.3.9-rc.4 this fix is
- *      gated on `plugins.installs.totalreclaw.version` being present —
- *      writing the slot without an install record produces a startup
- *      crash loop ("plugins.slots.memory: plugin not found: totalreclaw")
- *      that survives container restarts until `openclaw plugins install`
- *      repopulates the install record.
+ *   NOTE (rc.20, #402): this helper no longer writes `plugins.slots.memory`
+ *   (OpenClaw 2026.6.8 claims the memory slot natively on install/enable) nor
+ *   `plugins.installs` (the former Fix #6 self-heal — its record reader
+ *   discards the whole installs map if any entry fails schema validation).
+ *   Pre-existing values of both are left untouched. The remaining fixes are:
  *
  *   2. `plugins.entries.totalreclaw.hooks.allowConversationAccess = true`
  *      Grant the plugin access to `agent_end` and `before_agent_start`
@@ -812,15 +809,11 @@ export function resolveOnboardingState(credentialsPath, statePath) {
  *      this to "off" on first run for a clean UX. Existing explicit values
  *      ("partial", "block", "progress") are preserved.
  *
- *   4. `plugins.bundledDiscovery = "compat"` (only if unset, and only when
- *      `plugins.allow` is populated). When `plugins.allow` is a non-empty
- *      array, OpenClaw 2026.5.x switches the loader into strict-allowlist
- *      mode and silently rejects non-bundled plugins like totalreclaw —
- *      EVEN IF they are listed in the allow array. Setting
- *      `bundledDiscovery: "compat"` restores the looser behavior so allow-
- *      listed non-bundled plugins load. Without this fix, users with
- *      telegram or any model provider configured before TR install (which
- *      populates allow) get a silent plugin-skip on every gateway boot.
+ *   Fix #4 (`plugins.bundledDiscovery="compat"`) and Fix #5 (appending
+ *   "totalreclaw" to `plugins.allow`) were RETIRED together in rc.20 (#402):
+ *   native install manages the allowlist, and TR growing it was the only
+ *   thing that forced strict-allowlist mode (the sole reason the compat
+ *   workaround existed). Pre-existing values of both keys are left untouched.
  *
  * Design constraints
  * ------------------
@@ -843,8 +836,8 @@ export function resolveOnboardingState(credentialsPath, statePath) {
  *                    Defaults to `<home>/.openclaw/openclaw.json`.
  */
 export function patchOpenClawConfig(configPath, 
-// 3.3.12-rc.3 — plugin version (used by Fix #6 to self-heal a stripped
-// `plugins.installs.totalreclaw` record so Fix #1 (slot) can fire).
+// Retained on the signature (register() passes it) but no longer consumed:
+// the Fix #6 install-record self-heal it fed was retired in rc.20 (#402).
 pluginVersion) {
     const home = envHomeDir();
     const target = configPath ?? path.join(home, '.openclaw', 'openclaw.json');
@@ -861,109 +854,44 @@ pluginVersion) {
             cfg.plugins = {};
         }
         let mutated = false;
-        // --- Fix #6 (3.3.12-rc.3): self-heal `plugins.installs.totalreclaw` ---
+        // --- Fix #6 (installs self-heal) RETIRED in rc.20 (#402) ---
         //
-        // OpenClaw 2026.5.6 has a config-rewrite-after-restart behaviour
-        // observed on Pedro's pop-os QA host (2026-05-08): `openclaw plugins
-        // install` writes the install record, gateway restart fires, but
-        // after the restart something STRIPS `plugins.installs.totalreclaw` (and
-        // sometimes `plugins.allow`, `plugins.entries.totalreclaw`,
-        // `plugins.slots.memory`) from openclaw.json. The plugin's binary
-        // remains in `~/.openclaw/npm/node_modules/@totalreclaw/totalreclaw/`,
-        // but `openclaw plugins list` shows it as `disabled` because no
-        // install record + no allow entry.
+        // patchOpenClawConfig used to fabricate a `plugins.installs.totalreclaw`
+        // record (version/spec/source:"self-heal"/installedAt) whenever a version
+        // was passed and no record existed. Removed because it was inert at best
+        // and harmful at worst on OpenClaw 2026.6.8:
+        //   (a) the record reader validates the WHOLE installs map against a
+        //       schema where `source` must be a valid PluginInstallSource — the
+        //       fabricated `source:"self-heal"` (and any source-less record) fails
+        //       safeParse, discarding the ENTIRE installs map at load; and
+        //   (b) the native installer never persists install records into
+        //       openclaw.json (it strips them via withoutPluginInstallRecords and
+        //       commits to the SQLite index, which always wins on merge).
+        // So the plugin no longer writes `plugins.installs` at all; a pre-existing
+        // record is left byte-identical. `pluginVersion` is retained on the
+        // signature (register() passes it) but is no longer consumed here.
+        void pluginVersion;
+        // --- Fix #5 (plugins.allow self-append) RETIRED in rc.20 (#402) ---
         //
-        // Defensive self-heal: when this register() runs (which means the
-        // plugin IS physically loaded by the gateway), if the install record
-        // is missing or has no version, write a minimal record. This unlocks
-        // Fix #1 (slot) and avoids the user-visible "plugin disabled"
-        // condition without requiring `openclaw plugins install --force`.
+        // patchOpenClawConfig used to append "totalreclaw" to a non-empty
+        // `plugins.allow`. Removed as a pair with Fix #4 (below): OpenClaw's native
+        // `persistPluginInstall` already calls `addInstalledPluginToAllowlist`, and
+        // an empty/absent allowlist means allow-all (no write needed). TR
+        // unconditionally growing an allowlist was the very thing that flipped
+        // hosts into strict-allowlist enforcement — which then required the Fix #4
+        // `bundledDiscovery:"compat"` workaround. Dropping both lets native install
+        // own the allowlist; existing hosts keep whatever is already on disk.
+        // --- Fix #1 (memory-slot write) RETIRED in rc.20 (#402) ---
         //
-        // Phrase-safety: writes only metadata (version, spec, source,
-        // installedAt). No mnemonic / userId / SA leakage.
-        if (pluginVersion) {
-            if (typeof cfg.plugins.installs !== 'object' || cfg.plugins.installs === null) {
-                cfg.plugins.installs = {};
-            }
-            const existing = cfg.plugins.installs.totalreclaw;
-            const existingVersion = (typeof existing === 'object' && existing !== null && typeof existing.version === 'string')
-                ? existing.version
-                : null;
-            if (!existingVersion) {
-                cfg.plugins.installs.totalreclaw = {
-                    ...(typeof existing === 'object' && existing !== null ? existing : {}),
-                    version: pluginVersion,
-                    spec: '@totalreclaw/totalreclaw',
-                    source: 'self-heal',
-                    installedAt: new Date().toISOString(),
-                };
-                mutated = true;
-            }
-        }
-        // --- Fix #5 (3.3.12-rc.3): plugins.allow includes "totalreclaw" ---
-        //
-        // OpenClaw 2026.5.x: when `plugins.allow` is a non-empty array, the
-        // gateway switches into strict-allowlist mode. Plugins NOT in the
-        // allow list are silently rejected at load time — even bundled ones
-        // are gated. Pedro's pop-os 2026-05-08 QA had `plugins.allow` =
-        // ['device-pair', 'google', 'telegram', 'zai'] AFTER `openclaw
-        // plugins install @totalreclaw/totalreclaw@rc` ran. The install
-        // command did NOT add 'totalreclaw' to the allow list. Plugin
-        // shipped as `disabled`. Setup never proceeded.
-        //
-        // Defensive: when allow is a non-empty array and 'totalreclaw' is
-        // not in it, append. Don't touch null/undefined allow (means
-        // auto-discover mode — plugin is reachable without explicit allow).
-        if (Array.isArray(cfg.plugins.allow) && cfg.plugins.allow.length > 0) {
-            if (!cfg.plugins.allow.includes('totalreclaw')) {
-                cfg.plugins.allow.push('totalreclaw');
-                mutated = true;
-            }
-        }
-        // --- Fix #1: plugins.slots.memory = "totalreclaw" (gated on install) ---
-        //
-        // DEFENSIVE GATE (3.3.9-rc.4 — 2026-05-05): only write the slot when
-        // the plugin is genuinely INSTALLED (`plugins.installs.totalreclaw`
-        // present with a `version`). Writing the slot unconditionally
-        // produced a startup crash loop on Pedro's pop-os QA host on
-        // 2026-05-05 — after a config reset, `plugins.installs.totalreclaw`
-        // was missing but a previously-written `slots.memory = "totalreclaw"`
-        // had survived. OpenClaw's startup validator refuses to start with
-        //
-        //   Gateway failed to start: Error: Invalid config at openclaw.json.
-        //   plugins.slots.memory: plugin not found: totalreclaw
-        //   Run "openclaw doctor --fix" to repair, then retry.
-        //
-        // The container restart-loop drained ~13 attempts (12:10-12:23 UTC)
-        // until `openclaw plugins install` was re-run and re-populated
-        // `plugins.installs.totalreclaw`. With this gate, future installs
-        // that wipe `plugins.installs` (config reset, `doctor --fix`,
-        // migration tools) cannot regress into the same boot loop — slot is
-        // only ever written when the install record exists, and the install
-        // record is the install pipeline's authoritative signal that the
-        // plugin is on disk and registered with the gateway.
-        //
-        // The hooks patch (Fix #2) and Telegram streaming patch (Fix #3) are
-        // not gated this way — they write under `plugins.entries` and
-        // `channels` which are inert without an install record, so they can
-        // never trip the validator.
-        const installsRoot = cfg.plugins.installs;
-        const installEntry = typeof installsRoot === 'object' && installsRoot !== null
-            ? installsRoot.totalreclaw
-            : undefined;
-        const pluginIsInstalled = typeof installEntry === 'object'
-            && installEntry !== null
-            && typeof installEntry.version === 'string'
-            && installEntry.version.length > 0;
-        if (pluginIsInstalled) {
-            if (typeof cfg.plugins.slots !== 'object' || cfg.plugins.slots === null) {
-                cfg.plugins.slots = {};
-            }
-            if (cfg.plugins.slots.memory !== 'totalreclaw') {
-                cfg.plugins.slots.memory = 'totalreclaw';
-                mutated = true;
-            }
-        }
+        // patchOpenClawConfig used to write `plugins.slots.memory = "totalreclaw"`
+        // (install-gated, to dodge a startup crash loop). OpenClaw 2026.6.8 now
+        // claims the memory slot NATIVELY during `plugins install`/`enable` (its
+        // persistPluginInstall "slot selection" phase), so the hand-written write
+        // was redundant on the good path and twice failed in production. The
+        // plugin no longer touches the memory slot — a pre-existing value is left
+        // byte-identical. Fix numbering below is preserved for continuity with the
+        // #225/#226 history. The Fix #6 install-record self-heal was retired
+        // above too (rc.20, #402).
         // --- Fix #2: plugins.entries.totalreclaw.hooks.allowConversationAccess = true ---
         if (typeof cfg.plugins.entries !== 'object' || cfg.plugins.entries === null) {
             cfg.plugins.entries = {};
@@ -1006,36 +934,15 @@ pluginVersion) {
                 }
             }
         }
-        // --- Fix #4: plugins.bundledDiscovery = "compat" (3.3.11-rc.4) ---
+        // --- Fix #4 (plugins.bundledDiscovery="compat") RETIRED in rc.20 (#402) ---
         //
-        // OpenClaw 2026.5.x: when `plugins.allow` is populated (any non-empty
-        // array), the gateway's plugin loader switches into strict-allowlist
-        // mode. In strict mode, NON-BUNDLED plugins like totalreclaw are
-        // silently rejected even when listed in `plugins.allow`, unless
-        // `plugins.bundledDiscovery = "compat"` is explicitly set. Pedro's
-        // 2026-05-07 QA on pop-os surfaced this — the gateway booted with only
-        // the bundled providers (telegram, device-pair) and skipped totalreclaw
-        // despite it being in the allow list. `openclaw doctor --fix` cures it
-        // by setting `bundledDiscovery: "compat"`, but users shouldn't need
-        // to run doctor manually for the plugin to load.
-        //
-        // Fix: when `plugins.allow` is a non-empty array AND
-        // `plugins.bundledDiscovery` is unset, set it to "compat". If the user
-        // explicitly chose "allowlist" (the stricter mode), preserve their
-        // choice — only first-run defaults are touched.
-        //
-        // This bug was missed by the auto-QA harness because the harness ran
-        // on a fresh canonical container with `plugins.allow=null`, hitting
-        // the auto-discover code path. Real users with telegram + a model
-        // provider configured before TR install have a populated allow list,
-        // hitting the strict-mode path. The auto-QA harness in 3.3.11-rc.4
-        // adds a populated-allow scenario to catch future regressions.
-        if (Array.isArray(cfg.plugins.allow) && cfg.plugins.allow.length > 0) {
-            if (cfg.plugins.bundledDiscovery === undefined) {
-                cfg.plugins.bundledDiscovery = 'compat';
-                mutated = true;
-            }
-        }
+        // patchOpenClawConfig used to set `plugins.bundledDiscovery = "compat"`
+        // whenever `plugins.allow` was populated, to keep non-bundled totalreclaw
+        // loadable under strict-allowlist mode. Retired as a pair with Fix #5: the
+        // ONLY reason a host was in strict-allowlist mode was that TR itself grew
+        // the allowlist (Fix #5). With Fix #5 gone, native install manages the
+        // allowlist and this compat workaround is unnecessary. An existing
+        // `bundledDiscovery` value on disk is left untouched.
         if (!mutated)
             return 'unchanged';
         // Write back with 2-space indent to match OpenClaw's own write style.