v0.5.5

fix: honor per-loop sandboxEnabled=false in workspace adapter

The remote launch config flag (remotes[].sandbox=false) was only consulted at session-attach time, but forge-adapter.create() unconditionally provisioned a sandbox container when a sandbox manager existed. On remotes without Docker, this caused "Docker is not available" before the per-loop flag was ever read.

Guard sandbox provisioning on info.extra.forgeLoop.sandboxEnabled !== false so an explicit opt-out skips the Docker start entirely.

Upgrade: update the forge plugin on any remote server that runs sandboxed loops (or that is launched into by a client with remote targets).