Record MIT-0 as ClawHub's platform constant, not a listing error

The listing's MIT-0 next to the repository's Apache-2.0 was documented as a
drift to repair in the ClawHub listing itself. It is not repairable and not
drift: ClawHub's own client pins the platform skill license
(dist/schema/license.js sets PLATFORM_SKILL_LICENSE = "MIT-0", and the
version schema accepts only "MIT-0" or null), so every skill published there
is offered under MIT No Attribution. Publishing to ClawHub means offering
this skill on those terms in addition to Apache-2.0; the field is not
editable and the mismatch must not be read as drift.

pre-commit: 1) maintain.sh - exit 2 at the uv-secure gate, the three triaged
no-fix advisories in docs/development.md (rechecked 2026-09-09 against PyPI);
ruff check+format clean, pyright src/ 0 errors, 2368 passed 3 skipped run
separately; 2) /simplify - single pass, no fan-out available, prose-only
change, no findings; 3) docs sync - MIT-0/ClawHub grepped across docs/,
README, .claude/rules/, skills/: only release-and-distribution.md describes
the publish flow and stays accurate, the audit doc row is a dated snapshot,
no refs to update; 4) CLAUDE.md - audited against the structure rule, no
additions, revise-claude-md: no additions

docs/agent-skill.md

@@ -86,8 +86,13 @@ Do these in order after the skill is on the default branch.
    fires only on a published GitHub Release: a skill version bumped after a
    release, as 1.0.6 was, reaches ClawHub with the next one. Do not publish by
    hand to close that gap. The listing records the license as MIT-0 while
-   `SKILL.md` declares Apache-2.0; `clawhub skill publish` has no license
-   flag, so correct it in the ClawHub listing itself. The public catalog
+   `SKILL.md` declares Apache-2.0, and that is not a listing error to repair:
+   MIT-0 is a platform-wide constant in ClawHub's own client
+   (`dist/schema/license.js`, and its version schema accepts only `"MIT-0"`
+   or null), so every skill published there is offered under MIT No
+   Attribution. Publishing to ClawHub means offering this skill on those
+   terms in addition to the repository's Apache-2.0; do not try to edit the
+   field, and do not read the mismatch as drift. The public catalog
    already has an add-watermark skill; this is the removal counterpart, framed
    as the user's own content. ClawHub disallows deception, impersonation, and
    fake-engagement install loops.