chore: bump the dev version to 0.2.0.dev202609211315

[potiuk]

Summary

• Moves the dev stamp to 0.2.0.dev202609211315 so adopters running claude plugin update pick up the work merged since .dev202609210104.
• The marketplace is served from main and the client compares version strings, so a frozen suffix answers "already at the latest version" however far behind an installed copy has fallen.
• The three documented steps, by hand: bump-dev-version.py, then check-family-plugins.py --fix, then uv lock.

Type of change

• Skill change (.claude/skills/<name>/) — eval fixtures updated below
• Tool / bridge contract (tools/<system>/*.md)
• Python package (tools/*/ with pyproject.toml)
• Groovy reference impl
• Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
• Documentation (docs/, README.md, CONTRIBUTING.md)
• Project template (projects/_template/)
• CI / dev loop (prek, workflows, validators)
• Other: release plumbing — dev-version stamp

Test plan

• prek run --all-files passes (32 hooks, exit 0), including check-family-plugins in --fix mode with nothing left to regenerate.
• Every changed line is a version string — git diff -U0 filtered for anything other than the old and new stamps comes back empty across all 20 files.
• bump-dev-version.py --print reports 0.2.0.dev202609211315.

RFC-AI-0004 compliance

• Sandbox — no new host access; the change is a version string and the manifests generated from it.

Linked issues

None.

Notes for reviewers (optional)

• Done by hand rather than through the bump dev version workflow, so this is a normal PR rather than the workflow's draft. The three steps are the same ones bump-dev-version.yml runs; the commit is locally signed rather than GitHub-signed.

🤖 Generated with Claude Code