chore: improve SEO and release metadata

[amavashev]

Summary

• bump plugin, marketplace, npm, lockfile, README, and audit metadata to 0.1.1
• complete Claude marketplace and package discovery fields
• add audience guidance, verification steps, badges, canonical resources, and a changelog
• add a purpose-built 1280×640 GitHub social-preview asset
• align the live repository description, homepage, and 20 search topics

Why

Claude Code uses the manifest version as an update pin, so the merged enforcement work needs a version bump to reach existing installations. The repository also lacked the topic, catalog, package, and social metadata needed for strong discovery and evaluation.

Impact

No hook runtime behavior changes. Existing users can discover the next plugin update as v0.1.1, and new users get clearer search metadata, positioning, validation guidance, and release history.

Validation

• claude plugin validate . --strict
• npm run lint
• npm run test:coverage — 75 tests; 96.17% statements, 91.92% branches, 100% functions, 97.41% lines
• npm audit --audit-level=moderate — 0 vulnerabilities
• JSON/version/keyword consistency assertions
• git diff --check
• social preview verified at 1280×640 and 90,859 bytes
• all changed external links returned HTTP 200

Follow-up after merge

Create and publish the v0.1.1 tag/release. GitHub's social-preview image upload is UI-only; .github/assets/social-preview.jpg is ready for that repository setting.