chore(plugins): sync generated content mirrors

Regenerate plugins/*/skills/ from plugins/*/.apm/ after the previous
four commits, via scripts/sync-plugin-content.sh --all. The mirror is
generated output (ADR-0017) that check-plugin-content-sync's pre-push
hook diffs against .apm/; nothing here is hand-edited.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP

plugins/kyberforge/skills/skill-author/references/create.md

@@ -101,8 +101,10 @@ plain sentence and `disable-model-invocation: true` instead.
 - `license` — include when distributing the skill externally
 - `compatibility` — include if the skill requires specific tools, runtimes, or network access
   (max 500 characters)
-- `metadata` — key-value map; use `author`, `version`, `category`; add `source_keys` now (Step 6)
-  if research sources are in context
+- `metadata` — key-value map. `version` is **required** on every skill (ADR-0022), seeded at
+  `"1.0.0"` for a retrofitted skill with no prior version and at `"0.1.0"` for a newly created
+  skill; `author` and `category` stay optional; add `source_keys` now (Step 6) if research sources
+  are in context
 - `allowed-tools` — space-separated pre-approved tools; reduces permission prompts (experimental —
   support varies by client)
 - `disable-model-invocation` — hand-invoked skills only

plugins/kyberforge/skills/skill-author/references/retrofit.md

@@ -105,6 +105,16 @@ them for you. After every retrofit that adds, removes or renames a file:
       zero.
 - [ ] Re-run `/skill-audit` and confirm its `### Provenance` dimension does not report the new
       file as missing `source_keys`.
+- [ ] **Compression must not add authority the source text didn't have.** The bullet above is
+      about a `sources.md` entry going *stale* — Contributing files left uncited after content
+      moves. This is a distinct failure: a compression or rewrite pass that upgrades an honest
+      hedge in a Description into an unsupported confident claim, without the underlying source
+      having changed at all — "no forge-specific content drawn directly from it beyond that"
+      quietly becoming "Grounds Step 2's dispatch table." Nothing in `/skill-audit`'s structural
+      checks catches this; a bash script can verify an entry is internally consistent, never
+      whether the claim is *true*. If a retrofit strengthens or otherwise changes the wording of a
+      provenance claim, re-read the upstream research doc first and confirm the stronger wording
+      is actually still true before committing it.
 
 ## Worked example — a description retrofit