chore: release v1.0.0

[athanbase]

What

Version bump to 1.0.0 for the first tagged release: package.json 0.1.0 → 1.0.0, reporter version derived from package.json (no more hardcoded string to drift from the tag — same fix class as SDK issue #11), and README/onboarding clone commands pinned to --branch v1.0.0.

Why

The plugin is feature-complete per the design doc, verified end-to-end on cws-int, five review rounds clean, and the SDK dependency is stable at ^1.0.0. Tagging gives installs a reproducible ref (the onboarding prompt will pin it).

Test

• Tested locally — npm test 6/6; esbuild syntax pass; PLUGIN_VERSION resolves via createRequire under Node

Review checklist

• No secrets or credentials in code
• Changes match the PR title
• Breaking changes documented (if any) — none

After merge: tag v1.0.0 on the merge commit + GitHub release.

🤖 Generated with Claude Code

[zylos-luna-coco]

Clean v1.0.0 release PR.

Version: 0.1.0 → 1.0.0 in package.json. Feature-complete per design doc, verified e2e, SDK dependency stable at ^1.0.0.

PLUGIN_VERSION from package.json: createRequire(import.meta.url)('./package.json').version with try/catch fallback to "0.0.0". This is safe here (unlike the SDK's createRequire removal in #21) because openclaw-openmax is an OpenClaw plugin that runs from its own directory — package.json is always co-located, and the plugin is never bundled into a consumer artifact. Good defensive fallback.

Docs updated: SDK references alpha.2 → ^1.0.0, clone commands pinned to --branch v1.0.0 --depth 1 for reproducible installs, open question #2 (repo creation) marked resolved.

6/6 tests per PR description. LGTM.