Mifal 0.2.1

A small release: the doctor stops failing on your own skills, the release check runs on every pull request, and the agent install page ships.

• mifal doctor no longer fails an install because you keep skills of your own in ~/.agents/skills. It warns that Claude Code cannot see the ones that are not linked into ~/.claude/skills, and prints the link command; a Mifal skill that is unlinked is still a failure.
• The release check runs on every pull request, finishing in seconds unless VERSION changed, so it can be required on main. When VERSION does change it still runs the full suite and the upgrade rehearsal.
• AGENTS.md and CLAUDE.md: give a coding agent this repository's link and it checks the machine, installs the newest release, shows you the dry run and waits for your yes, then runs mifal doctor. MAINTAINING.md gains the routine for changes and releases. The 0.2.0 notes described this page, but the v0.2.0 tag does not contain it; it first appears here.
• maint/rehearse-upgrade.sh now rehearses the revision you hand it, tagged as the release it would be, instead of the repository's local main, which can be stale. Without this a release candidate could not be rehearsed from a tag-following release.

Upgrading from 0.2.0: mifal update finds v0.2.1 and shows you the incoming commits before it installs. From 0.1.x, your first update still lands on the tip of main.

Tested: full suite under Python 3.9 and 3.13 (188 + 348 + 9 + 18 + 369 tests); the upgrade rehearsal from v0.2.0 and from v0.1.2; a real mifal update from the public v0.2.0 clone to 0.2.1 in a disposable home folder, followed by mifal doctor with 0 failures.

Not signed. macOS only. Alpha.