diff --git a/.wiki/concepts/skill-versioning.md b/.wiki/concepts/skill-versioning.md
index ee7f050..a98113b 100644
--- a/.wiki/concepts/skill-versioning.md
+++ b/.wiki/concepts/skill-versioning.md
@@ -1,7 +1,7 @@
 ---
 title: Skill versioning + bootstrap manifest
 type: concept
-updated: 2026-04-28
+updated: 2026-05-01
 ---
 
 # Skill versioning + bootstrap manifest
@@ -33,9 +33,11 @@ Bumped manually when `SKILL.md` is edited. No CI gate — discipline-based.
 
 ## What skills are versioned
 
-Currently only the **infrastructure** skills (the ones bootstrap touches and that govern project layout). Communication-mode skills (`caveman`, family) and discovery skills (`find-skills`, `active-platform`) aren't versioned — their content is "good copy-paste" and a snapshot mismatch isn't a layout problem.
+**Originally** only the **infrastructure** skills (the ones bootstrap touches and that govern project layout). Communication-mode skills (`caveman`, family) and discovery skills (`find-skills`, `active-platform`) were left unversioned — their content was "good copy-paste" and a snapshot mismatch wasn't a layout problem.
 
-If we ever start packaging or marketplace-publishing the rest, we'll version them too.
+**As of `project-discipline` v0.1.0** (Rule 3), the requirement extends to **all** skills in this repo, regardless of category. Communication-mode and discovery skills also need `version:` in frontmatter; the migration is a separate one-time task tracked in `.tasks/`. Rationale: discipline-by-default is simpler than maintaining a list of "exempt" skills, and it costs nothing — `version: 0.1.0` is added on the next edit per the Rule 3 first-edit-unversioned clause.
+
+If we ever start packaging or marketplace-publishing skills outside this repo, the same rule still applies.
 
 ## The manifest