fix: rename plugin package to clawmetry-plugin for ClawHub

[vivekchand]

Summary

• Rename @clawmetry/openclaw-plugin to clawmetry-plugin in package.json
• ClawHub rejects package names that collide with existing skill slugs — the skill is clawmetry, so the plugin package must be clawmetry-plugin

Already published to ClawHub as clawmetry-plugin@1.0.0.

Generated with Claude Code

[vivekchand]

Test plan & review notes

What changed

• Single-line rename in clawhub-plugin/package.json: @clawmetry/openclaw-plugin → clawmetry-plugin to satisfy ClawHub's slug collision rule.

Smoke commands

• make test or make test-api
• cd clawhub-plugin && npm install && npm pack — verify the published package name resolves correctly under the new name
• Confirm the ClawHub-published clawmetry-plugin@1.0.0 matches this package.json exactly
• Confirm old clawmetry CLI entry point still works: clawmetry --help

Likely failure modes from the diff

• Any CI workflow, docs, or README that references @clawmetry/openclaw-plugin (the old scoped name) will now be stale — worth a quick grep across the repo to catch lingering references.
• If downstream consumers npm install @clawmetry/openclaw-plugin they will silently get nothing; consider adding a deprecation notice or npm deprecate on the old name if it was ever published.
• No Python import paths are affected (change is JS-only, inside clawhub-plugin/), so the core clawmetry package is unaffected.

Issue link

• No linked issue found in the PR body — consider adding Closes #N if there is a tracking issue for the ClawHub slug conflict.

---

Generated by Claude Code

[vivekchand]

Test plan & review notes

What changed

• Single-line rename of the npm package in clawhub-plugin/package.json from @clawmetry/openclaw-plugin to clawmetry-plugin so the package name does not collide with the existing clawmetry skill slug on ClawHub.

Smoke commands

• make test-api
• python3 dashboard.py --port 8900

What to look at

• Verify openclaw plugins install clawmetry-plugin resolves the correct package from ClawHub (i.e. the registry entry at clawmetry-plugin@1.0.0 that was already published).
• Check that no other file in the repo still references @clawmetry/openclaw-plugin as an install target, peer dependency, or in docs — a grep for @clawmetry/openclaw-plugin across *.md, *.json, and *.sh files would confirm the rename is complete.
• Note that PR #819 (fix/plugin-security-scanner) also touches package.json and bumps the version to 1.2.0 while setting the name to clawmetry-plugin. If #818 merges into main first, #819 will merge cleanly since both set the same name; but if the merge order is reversed the rename here becomes a no-op. Worth confirming the intended merge order.

Likely failure modes

• If any install.sh or CI step still does npm install @clawmetry/openclaw-plugin it will 404 after this merges.
• ClawHub may have cached the old scoped package name and could serve the wrong package until cache invalidation; worth testing the install end-to-end against the live registry after merging.

Issue link

• No issue linked — consider adding one.

---

Generated by Claude Code

[vivekchand]

Test plan & review notes

Repo: vivekchand/clawmetry

What changed

• package.json name changed from @clawmetry/openclaw-plugin → clawmetry-plugin

Smoke commands

• cat package.json | python3 -c "import sys,json; d=json.load(sys.stdin); assert d['name']=='clawmetry-plugin', d['name']; print('OK')" — verify name
• grep -rn '@clawmetry/openclaw-plugin' . — should return nothing (any stale references in docs/README/CHANGELOG need updating)

Likely failure modes from the diff

• package-lock.json or yarn.lock may still reference the old scoped name — regenerate the lock file after the rename if it exists
• Version in package.json should match the already-published clawmetry-plugin@1.0.0; a mismatch would cause confusion on the next publish

Issue link

• No linked issue found

---

Generated by Claude Code

[vivekchand]

Test plan & review notes

Repo: vivekchand/clawmetry

What changed

• clawhub-plugin/package.json: name renamed from @clawmetry/openclaw-plugin to clawmetry-plugin (1-line change, no logic touched)

Smoke commands

• make lint
• pip install -e . && clawmetry --version to confirm the Python CLI is unaffected
• If there's a ClawHub publish step: cd clawhub-plugin && npm publish --dry-run to validate the new package name resolves cleanly before a real push

Likely failure modes from the diff

• Any other file that still references the old scoped name @clawmetry/openclaw-plugin (README, install docs, CI publish workflow, or clawhub-plugin/ source imports) will be silently stale — worth a quick grep -r "@clawmetry/openclaw-plugin" . to catch stragglers
• If a CI step does npm install @clawmetry/openclaw-plugin or pins the old name in a lockfile, it will start failing after merge
• The PR body says it's already published to ClawHub as clawmetry-plugin@1.0.0 — make sure version in package.json stays in sync if a re-publish is ever needed

Issue link

• No linked issue found — consider opening one (or adding Closes #N to the PR body) so the ClawHub rejection is tracked for posterity

---

Generated by Claude Code

[vivekchand]

Test plan & review notes

Repo: vivekchand/clawmetry

What changed

• package.json: renames @clawmetry/openclaw-plugin → clawmetry-plugin to pass ClawHub's package-name validator (1 file, +1/-1); already published to ClawHub as clawmetry-plugin@1.0.0

Smoke commands

• npm install && npm run build in the plugin directory
• openclaw plugins install clawmetry-plugin → should install without name-collision errors

Likely failure modes from the diff

• If anything else in the repo references the old package name @clawmetry/openclaw-plugin (docs, CI, install.sh), those will be stale after merge — worth a quick grep -r '@clawmetry/openclaw-plugin' . before landing

Issue link

• No Closes #N found. PR notes it's already published to ClawHub as clawmetry-plugin@1.0.0 — this just syncs the source to match.

---

Generated by Claude Code