fix: respect per-skill version in Capacium sync, not force pyproject.toml version

build_bundle_capabilities() now reads each skill's own version from its
capability.yaml instead of blindly applying the pyproject.toml version.

normalize_manifest() preserves a skill's existing version instead of
overwriting it.

This fixes the bug where adding a new skill with a different version
(e.g. skillweave-council v0.8.0 when pyproject is 0.7.0) would cause
a permanent sync conflict.

Author: André Lange

src/skillweave/github_integration/capability_sync.py

@@ -85,11 +85,12 @@ def build_bundle_capabilities(self, version: str) -> list[dict[str, str]]:
         for path in self.skill_manifest_paths():
             manifest = self.load_manifest(path)
             name = manifest.get("name") or path.parent.name
+            own_version = manifest.get("version", version)
             capabilities.append(
                 {
                     "name": name,
                     "source": f"./skills/{path.parent.name}",
-                    "version": version,
+                    "version": own_version,
                 }
             )
         return capabilities
@@ -135,7 +136,7 @@ def normalize_manifest(self, path: Path, version: str) -> dict[str, Any]:
             normalized = {
                 "kind": "skill",
                 "name": current.get("name", path.parent.name),
-                "version": version,
+                "version": current.get("version", version),
                 "description": current.get("description", ""),
                 "author": DEFAULT_AUTHOR,
                 "license": DEFAULT_LICENSE,