feat: rename skill to cowork-repository-update, bump to v1.1

skills/cowork-project/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: cowork-project
+name: cowork-repository-update
 description: >
   Manages the full lifecycle of CoWork skill and plugin projects at MPM. Use this skill
   whenever: starting a NEW skill, plugin, or tool concept that doesn't exist yet ("new skill idea",
@@ -8,12 +8,12 @@ description: >
   created or refreshed ("create the entry for this", "document this plugin", "update the wiki",
   "add to the coordination folder", "set up the project folder", "package the plugin",
   "we just finished building", "update the registry for"). This skill handles folder creation,
-  README writing, Git repo creation, .plugin packaging, Wiki V2 docs, and registry updates —
+  README writing, Git repo creation, .skill packaging, Wiki V2 docs, and registry updates —
   everything needed to keep the CoWork coordination system current. Always use this skill rather
   than doing coordination steps manually.
 ---
 
-# CoWork Project Coordination Skill
+# CoWork Repository Update Skill
 
 You manage the CoWork project coordination system for MPM. Every skill, plugin, and tool gets
 tracked in the registry, documented in a wiki, and stored in the Coordination folder. This skill
@@ -177,7 +177,7 @@ Tell them to load the Concept.md file at the start of the build session.
 
 Read `references/mode-document.md` for the full step-by-step process. That file covers:
 metadata extraction, version checking, repo creation, README generation, Git push,
-.plugin packaging, Wiki V2 creation, and registry write.
+.skill packaging, Wiki V2 creation, and registry write.
 
 Before reading that file, note:
 - If no registry row exists yet for this project: full new entry needed