Add OpenClaw remediation and extensibility plan (OPENCLAW_REMEDIATION_PLAN.md)

[G9Pedro]

Motivation

• Capture and operationalize findings about an OpenClaw plugin compatibility bug where registration was declared async and should be synchronous.
• Document related compatibility and documentation drift, including a manifest path mismatch between package.json and src/commands/compat.ts and tests that currently codify the wrong async contract.
• Propose an actionable, phased remediation and extensibility roadmap to restore compatibility, harden validation, and evolve ClawVault into a typed-memory, capability-driven platform.
• Provide concrete release, validation, and testing steps to make a hotfix and follow-on architecture and product improvements.

Description

• Add OPENCLAW_REMEDIATION_PLAN.md containing a detailed, phased plan that includes an immediate hotfix to make registerOpenClawPlugin(...) and register(...) synchronous and test updates to assert a synchronous registration contract.
• Call out and prescribe a fix for the manifest path validation in src/commands/compat.ts so it resolves the actual openclaw.plugin.json declared in package.json.
• Recommend documentation updates (README.md, SKILL.md, docs/openclaw-plugin-usage.md) to align with current OpenClaw installation flows and add a release checklist for packaging/manifest validation.
• Define a mid/long-term architecture: separate registration, orchestration, and memory engine layers; introduce capability modules and a MemoryBackend abstraction; formalize typed memory record schemas and policy-driven behavior; and outline an eval harness and background maintenance jobs.

Testing

• This change is documentation-only and does not modify source code or automated tests.
• No automated tests were run or modified as part of this PR.
• The plan includes explicit test guidance to update src/openclaw-plugin.test.ts and add regressions that verify synchronous registration, hook wiring, legacy slot behavior, and manifest-path resolution, which are recommended to be implemented and validated in follow-up changes.

---

Codex Task