v0.2.0 — Sites, Projects, and Per-Wolt Isolation

What's new

Wolt sites with livereload

Every rodent wolt's wolt/site/ directory is now served at /wolt/<name>/site/ with automatic livereload. Edit files and see changes instantly in the viewport. New wolts get a wakeup template on creation.

Projects system

wolts/projects/ is a new shared directory for apps that need their own server, dependencies, or public routes. Each project has a woltspace.json manifest and gets served at /project/<name>/.

• /projects/ API — list, detail, start, stop
• Auto port allocation (4001-4999), max 2 concurrent
• Lodge shows project cards with start/stop controls
• Off-state placeholder pages in the forest theme

Create-wolt modal

The lodge has a proper create dialog — name input + type picker (otter/beaver/raccoon). Replaces the old blank-session flow.

Per-wolt .claude/ isolation

New wolts get their own .claude/ directory with isolated settings, skills, and credentials. The wclaude wrapper sets HOME per-wolt automatically. Existing wolts are unaffected — opt-in migration available.

Session routing

Unified start_session() entry point for all adapters (lodge, telegram, slack). /start-chat skill with mode files controls per-adapter behavior.

Type system

Wolt types now map to specific tiers: raccoon (Opus), beaver (Sonnet), otter (Haiku). Legacy "rodent" type still works.

Migration

See docs/migrations/v0.2.0.md. No breaking changes — existing wolts work as-is. All new features are additive.

Stats

• 16 commits, 36 files changed, +2885 / -1200 lines
• 115 tests passing

Known issues

• Project proxy doesn't rewrite internal links (#212) — multi-page apps need base path config
• litellm not in test env — 3 pre-existing bot test failures