@blockrun/clawrouter@0.10.12 appears to use async plugin registration incompatible with OpenClaw 2026.2.25 (0.10.10 works)

[KevinkeVarson]

After updating @blockrun/clawrouter from 0.10.10 to 0.10.12, OpenClaw logs:

[gateway] [plugins] plugin register returned a promise; async registration is ignored (plugin=clawrouter, source=~/.openclaw/extensions/clawrouter/dist/index.js)

0.10.10 works in the same environment, rollback restores expected behavior.

Likely cause: 0.10.12 plugin registration became async (returns Promise), while the current OpenClaw plugin loader expects sync registration.

Environment

• OpenClaw: 2026.2.25
• ClawRouter: 0.10.10 (good) / 0.10.12 (bad)
• OS: macOS 26.3 (arm64)
• Node: v24.13.0
• Install style: npm global OpenClaw, plugin installed via openclaw plugins (registry npm spec)

User-facing impact

After upgrading to 0.10.12, OpenClaw logs plugin register returned a promise; async registration is ignored for ClawRouter; routing doesn’t initialize, rollback back to 0.10.10 fixes immediately.

Reproduction (copy/paste)

# 1) Confirm baseline
openclaw --version
openclaw plugins list

# 2) Ensure known-good
openclaw plugins install @blockrun/clawrouter@0.10.10
openclaw plugins list

# 3) Update to failing target
openclaw plugins update clawrouter
# or
openclaw plugins install @blockrun/clawrouter@0.10.12

# 4) Restart or reload the gateway, then inspect
openclaw status
openclaw plugins doctor
openclaw plugins list

Evidence (sanitized)

[gateway] [plugins] plugin register returned a promise; async registration is ignored (plugin=clawrouter, source=~/.openclaw/extensions/clawrouter/dist/index.js)

openclaw plugins list
ClawRouter | id=clawrouter | status=loaded | version=0.10.10

// @blockrun/clawrouter@0.10.12 package.json (published)
{
  "openclaw": {
    "extensions": ["./dist/index.js"]
  }
}

Validation performed

• Confirmed plugin entry exists: ~/.openclaw/extensions/clawrouter/dist/index.js
• Confirmed metadata entry path: package.json -> openclaw.extensions[0] = "./dist/index.js"
• Confirmed issue is version-specific (0.10.10 good, 0.10.12 problematic)

Request to maintainers

Can you confirm whether:

1. ClawRouter 0.10.12 intentionally moved to async registration, and
2. OpenClaw 2026.2.25 supports, or does not support, awaited async plugin registration?

If async registration is unsupported by design, should ClawRouter revert to sync register for compatibility?

If it is supported, is this a loader regression in OpenClaw?