chore(fleet-skill): internal-only skills are unversioned staging-dir singles — give them a repo home

[aarontrowbridge]

chore(fleet-skill): internal-only skills are unversioned staging-dir singles — give them a repo home

Important

Problem — The fleet skill (the multi-device coordination playbook: mount-stack mental model, health check, failure-mode catalog, chat-DB recovery, machine onboarding) exists only as the server's staging-dir copy — it ships in no VSIX (deliberately internal-only) and lives in no git repo (the staging dir is not a clone; the boot wrapper rsyncs VSIX skills in additively). One machine, one unversioned copy: a lost boot disk loses the playbook. A 2026-08-23 session also had to correct two stale entries in place (the canonical chat DB is opencode.db since the 2026-08-14 consolidation, not opencode-dev.db; a newly observed failure mode — a client kept the pre-rename personal-vault mount name and redirect remote URL after the 2026-08-21 vault rename) — corrections with nowhere durable to land. Ask: give internal-only skills a versioned home the wrapper deploys from, seeded with the corrected fleet card.

Acceptance Criteria

• The fleet skill's canonical source lives in a git repo (this repo or a private skills repo); the staging dir becomes a deployment target, not the only copy
• The boot wrapper picks up the internal tree alongside the VSIX skills (additive, never deletes — current behavior unchanged)
• The 2026-08-23 corrections (canonical DB pin; client pre-rename-mount failure mode) are present in the versioned copy