chore: update project skills

[github-actions]

Summary

• refresh all project skills tracked by skills-lock.json
• update committed skill content and lockfile hashes

Generated by the daily project skill updater.

[steipete]

Closing this generated snapshot because it is not safe to land as generated.

The refreshed router now tells product-UI tasks to use openclaw-carapace, but the pinned updater still selects only the five legacy skill IDs, so that referenced skill is absent. Installing the intended sixth skill from current canonical source (openclaw/carapace@6897669b84a0461ea6f31e43c157f738cd2266dc) also exposed an upstream guidance bug: both consumer-adapter references describe html[data-theme="light"|"dark"] as a canonical CSS selector. That selector is invalid and the rule is discarded; the data-theme-resolved="light"|"dark" notation is ambiguous for the same reason.

Proof:

• daily updater run https://github.com/openclaw/docs/actions/runs/29757455549 succeeded but logged 7 discovered skills and only 5 selected
• generated legacy skill directories match the canonical source byte-for-byte
• npm run skills:install with the canonical repository plus openclaw-carapace was idempotent
• npm test: 4/4 passed
• full docs build produced 30,028 pages; search indexed 15,382 pages across 21 languages; docs smoke passed
• canonical AutoReview rejected the added guidance at openclaw-carapace/references/consumer-adapters.md:14 with P2/high confidence

Please let the updater create a fresh PR after the canonical Carapace guidance is corrected and this repository's pinned skill selection includes openclaw-carapace. The downstream mirror should not carry a hand-edited divergence from canonical source.