Problem
woltspace update rebuilds the Docker image but never git pulls the host repo. The woltspace CLI script on the host stays at whatever version was originally cloned.
This causes drift: the container runs new code but the host CLI has stale logic. Real example: tunnel management moved to server/tunnel.py writing tunnel.json, but a user's host CLI still polls for the old tunnel-url file — _show_url() waits 30 seconds then gives up with "tunnel still digging."
Root cause
The update skill (/woltspace-update) calls woltspace rebuild --version <tag>, which:
- Builds a new Docker image (clones repo at build time inside Docker)
- Restarts the container
But step 0 is missing: update the host repo to the same tag so the woltspace script matches the container.
Proposed fix
In the rebuild subcommand (or the update skill), before building:
# Sync host repo to the target version
git fetch origin --tags --force --quiet
git checkout "v${VERSION}" 2>/dev/null || git checkout "${VERSION}" 2>/dev/null
Or more conservatively, just the CLI script:
# Pull latest woltspace script from the target tag
git show "${VERSION}:woltspace" > woltspace.tmp && mv woltspace.tmp woltspace
Files
woltspace — rebuild) subcommand (~line 482)
.claude/skills/woltspace-update/SKILL.md — update skill should include the git pull step
Problem
woltspace updaterebuilds the Docker image but nevergit pulls the host repo. ThewoltspaceCLI script on the host stays at whatever version was originally cloned.This causes drift: the container runs new code but the host CLI has stale logic. Real example: tunnel management moved to
server/tunnel.pywritingtunnel.json, but a user's host CLI still polls for the oldtunnel-urlfile —_show_url()waits 30 seconds then gives up with "tunnel still digging."Root cause
The update skill (
/woltspace-update) callswoltspace rebuild --version <tag>, which:But step 0 is missing: update the host repo to the same tag so the
woltspacescript matches the container.Proposed fix
In the
rebuildsubcommand (or the update skill), before building:Or more conservatively, just the CLI script:
Files
woltspace—rebuild)subcommand (~line 482).claude/skills/woltspace-update/SKILL.md— update skill should include the git pull step