Fix install commands and clone URL in docs, bump to 4.0.2

[pskoett]

Fixes the two copy-paste hazards reported in #24, plus one the issue missed —
and corrects the install command beyond what the issue asked for.

What was broken

1. clawdhub install is not a real command. The working path is
OpenClaw's built-in openclaw skills install, with the ClawHub CLI
(npm i -g clawhub) as a secondary option. There is no clawdhub.

2. The command needs the @pskoett/ scope. The issue reported the bare
slug self-improving-agent as working, and the first pass on this branch
took that at face value. It is wrong: the
ClawHub package page and
the OpenClaw docs both show @owner/slug, and a bare slug is only accepted
for already-installed or unambiguous skills. Documenting the bare form would
have reproduced the same class of bug this PR set out to fix.

3. The git clone URL used the wrong owner handle (peterskoett →
pskoett). That handle only resolves through GitHub's web redirect, which
git clone does not follow — so the manual install genuinely failed on a
fresh machine, exactly as reported.

Documented commands

openclaw skills install @pskoett/self-improving-agent   # -> active workspace
clawhub install @pskoett/self-improving-agent           # -> ./skills in cwd

The differing install targets are now called out in the docs, since
clawhub install does not write to the OpenClaw workspace.

Changes

File	Fix
README.md	Install section: scoped commands + targets; clone URL corrected
self-improving-agent/SKILL.md	Same, in the Installation block; version -> 4.0.2
self-improving-agent/references/openclaw-integration.md	Same, in Quick Setup step 1
self-improving-agent/CHANGELOG.md	Stale ClawdHub mention corrected; 4.0.2 release entry

references/openclaw-integration.md was not listed in the issue but
carried both original bugs.

Versioning

Docs-only — no skill behavior, hook, or .learnings/ changes — so this is a
patch. It targets 4.0.2 because the currently published ClawHub build is
v4.0.1 (confirmed on the package page); the changelog notes the skip so the
gap doesn't read as an error later.

One pre-existing bookkeeping detail worth a look while reviewing: the
[Unreleased] section already held an Added (CI workflow) and
Changed (repo restructure, frontmatter name correction) entry. Those
describe work that shipped inside the published 4.0.0 package but never got a
version heading. I folded them under 4.0.2 so nothing sits unreleased, which
slightly post-dates them. Reattributing them to 4.0.0 is a small edit if you
prefer.

Note on the commit history

Three commits, because a force-push to amend was blocked by a permission
classifier. Squash-merging collapses them and drops the superseded "4.0.1"
and bare-slug text from the intermediate commit messages.

Closes #24

🤖 Generated with Claude Code