v0.3.2 — Default workdir shortened from ~/.spectator-workdir to ~/.spectator

What changed

Default \$workdir is now ~/.spectator/ (was ~/.spectator-workdir/ in v0.3.0 and v0.3.1). The inner-tree dir is unchanged: \$workdir/Spectator/.

Single source of truth: config.DEFAULT_REMOTE_WORKDIR = \"~/.spectator\".

Migration

Coming from	Outer dir	Inner-tree dir	One-shot mv
v0.2.x	`~/spectator/`	`spectator-tool/`	`mv ~/spectator/spectator-tool ~/spectator/Spectator && mv ~/spectator ~/.spectator`
v0.3.0 / v0.3.1	`~/.spectator-workdir/`	`Spectator/`	`mv ~/.spectator-workdir ~/.spectator`

After the mv, redeploy from your laptop so v0.3.2 lands on the host:

```bash
ssh ''
./spectator deploy --target
```

Rsync excludes .venv/, so the audio venv and other cached state under the renamed tree survive the move. New installs need no migration — the v0.3.2 default just works.

Tests

39 / 39 pytest passes. The pin test that asserts the default value (test_default_remote_workdir_is_dotted) was updated; its docstring now records both the v0.3.0 (~/.spectator-workdir) and v0.3.2 (~/.spectator) names so the rename's history isn't lost.

Why patch and not minor?

Pre-1.0 semver doesn't strictly require a minor bump for breaking defaults; the .spectator-workdir layout existed for under 24 hours and never had material outside-deployment use, so the rename is functionally a private detail of the v0.3 release line. v0.3.0 took a minor bump because it broke from v0.2.x's long-standing ~/spectator/ layout. The maintainer's call.