update-templates

Update upstream templates

This plugin is a thin orchestrator. The actual simulator code lives in the upstream template repos and is cloned fresh by scaffold-simulation. This skill pulls the latest into existing workspace clones (and into a shared template-cache dir if used).

Steps

1. Read the registry. Load templates/registry.json.
2. For each template, find existing clones. Two places to check:
   • Workspaces — read $CLAUDE_USER_DATA/geopol-sim/config.json's registered-workspaces list (if a runstore is configured). For each workspace, check .template-id and pull only if it matches the template under consideration.
   • Template cache — if the plugin maintains a shared cache (default $CLAUDE_USER_DATA/geopol-sim/template-cache/<template-id>/), pull there too.
3. Pull each clone:

   cd <clone-path>
   git fetch origin <default_branch>
   git log --oneline HEAD..origin/<default_branch>   # show new commits
   git pull --ff-only origin <default_branch>
   

   If the workspace has uncommitted local changes (the user edited persona briefs, for example), fall back to git stash && git pull --ff-only && git stash pop and warn the user. If the merge isn't fast-forwardable, stop for that workspace and report — don't force.
4. Report per-template summary:
   • Number of new commits pulled
   • One-line subject of each new commit
   • Workspaces that were updated vs skipped (and why)
5. If install_commands changed (e.g. pyproject.toml touched), suggest re-running them in each affected workspace. Don't auto-run — the user might want to inspect first.

Notes

• Never rewrite git history in user workspaces. Fast-forward only.
• If a workspace has gone divergent (the user committed local changes on top), report and let the user decide.
• This skill does NOT update the plugin itself — that's claude plugins update geopol-sim or via Daniel's publish-plugin-update.