Summary

• Fix initPromise poisoning in both PlatformProvider and OSSProvider — a failed _init() permanently cached the rejected promise, making the provider broken with no retry possible. Now clears the promise on failure so subsequent calls retry.
• Add disableHistory passthrough — exposes oss.disableHistory in the plugin config so users can explicitly opt out of SQLite history storage (the underlying mem0ai/oss SDK already supports this via DummyHistoryManager).
• Graceful SQLite fallback — wraps new Memory(config) in a try-catch; if construction fails and history wasn't already disabled, automatically retries with disableHistory: true and logs a warning. This auto-recovers from native binding failures (jiti resolver regression in OpenClaw 2026.3.x) without losing core memory functionality.

Addresses the class of failures reported in openclaw/openclaw#31676, openclaw/openclaw#36377, and #4172.

Configuration

Users hitting SQLite binding issues can now explicitly disable history:

{
  "mode": "open-source",
  "oss": {
    "disableHistory": true,
    "vectorStore": { "provider": "qdrant", "config": {} }
  }
}

Or rely on the automatic fallback (no config change needed).

Tests

10 new tests added in openclaw/sqlite-resilience.test.ts (all passing):

Config passthrough (4 tests)

• disableHistory: true survives resolveEnvVarsDeep config parsing
• disableHistory: false is preserved, not coerced
• Field is undefined when omitted from config
• oss sub-object accepts disableHistory without unknown-key rejection

OSSProvider passthrough (2 tests)

• disableHistory: true reaches the Memory constructor when configured
• disableHistory is absent from Memory config when user doesn't set it

initPromise retry (2 tests)

• OSSProvider: after a transient failure (e.g. SQLITE_CANTOPEN), initPromise is cleared and the next call retries successfully instead of returning the cached rejection
• PlatformProvider: same fix verified — network timeout on first init allows retry on second call

Graceful SQLite fallback (2 tests)

• When Memory() throws a binding error, automatically retries with disableHistory: true and logs a console.warn; provider becomes functional
• When disableHistory is already true and init still fails (e.g. vector store issue), throws immediately — no infinite retry loop

Test plan

• All 24 existing unit tests pass
• All 10 new resilience tests pass (34 total)