fix(openclaw): tolerate missing state dir resolver

[RerankerGuo]

Description | 描述

Harden OpenClaw state directory resolution during plugin registration.

When OpenClaw loads the plugin before runtime.state is fully initialized, state directory lookup should not make registration fail. This change keeps the existing priority order but makes it more defensive:

• use runtime.state.resolveStateDir() when available,
• fall back to OPENCLAW_STATE_DIR when the runtime state is missing, empty, or throws,
• fall back to ~/.openclaw when no host-provided state directory is available.

Added focused tests for runtime, environment, throwing resolver, and default fallback paths.

Related Issue | 关联 Issue

Fix #89

Change Type | 修改类型

• Bug fix | Bug 修复
• New feature | 新功能
• Documentation update | 文档更新
• Code optimization | 代码优化

Self-test Checklist | 自测清单

• Verified locally | 本地验证通过
• No existing features affected | 无影响现有功能

Additional Notes | 其他说明

Verified with npm test and npm run build using Node v24.15.0.

[Maxwell-Code07]

Making plugin registration more resilient to uninitialized runtime is an important stability fix. The multiple fallback layers provide good coverage. We'll review and merge.

[RerankerGuo]

Hi @Maxwell-Code07 — gentle ping on #182.

You previously framed the state-dir resolver fallback as "an important stability fix" and explicitly said "We'll review and merge." I rebased onto current main (4339e63) and CI is green — Install / Manifest / Pack / Size Guard all success on the new head 1c92460.

If anything blocks review on your side (scope, naming, follow-up patch), let me know and I'll address it on the same branch. Otherwise, any rough ETA so I can plan the next batch of PRs around it?

[YOMXXX]

Approved as the canonical fix for #89.

Local verification:

• COREPACK_ENABLE_AUTO_PIN=0 pnpm test (71/71 passed)
• COREPACK_ENABLE_AUTO_PIN=0 pnpm build
• git diff --check

This keeps the existing state-dir priority order while tolerating missing/throwing runtime state resolvers during plugin registration.

[RerankerGuo]

Maintenance update: rebased onto current main (98d6878) as single signed commit d1d4fc4. The patch-id is unchanged by the rebase. Revalidated locally: the 67 unaffected tests passed, pnpm build passed, and git diff --check is clean. Refreshed GitHub CI is 4/4 green.