version-updates

# Version Update Workflow ## When To Use Use this skill when preparing a release or bumping the project version. Run `Skill(sanctum:git-workspace-review)` first to capture current changes. ## When NOT To Use - Just documentation updates - use doc-updates - Full PR preparation - use pr-prep ## Required TodoWrite Items 1. `version-update:context-collected` 2. `version-update:target-files` 3. `version-update:version-set` 4. `version-update:docs-updated` 5. `version-update:verification` ## Step 1: Collect Context (`context-collected`) - Confirm which version to apply (default: bump patch). - If the prompt provides an explicit version, note it. - validate `Skill(sanctum:git-workspace-review)` has already captured the repository status. ## Step 2: Identify Targets (`target-files`) - Find ALL configuration files that store versions using recursive search: - Root level: `Cargo.toml`, `package.json`, `pyproject.toml` - **Nested directories**: Use glob to find `*/pyproject.toml`, `*/Cargo.toml`, `*/package.json` - **Example**: `plugins/memory-palace/hooks/pyproject.toml` must be included - Exclude virtual environments (`.venv`, `node_modules`, `target/`) using grep -v - Include changelog and README references that mention the version. - Use: `find plugins -name "pyproject.toml" -o -name "Cargo.toml" | grep -v ".venv"` ## Step 3: Update Versions (`version-set`) - **Automated approach**: Use `plugins/sanctum/scripts/update_versions.py <version>` to update all version files...