State manifest renamed from slice.toml to thinslice.toml. On first run after upgrading, slice automatically migrates any existing slice.toml to the new filename. No manual action required.
The old slice.toml filename is no longer read; worktrees that skipped the automatic migration must rename the file manually.
Improved
Migration is idempotent — re-running slice reconcile after a partial upgrade is safe.
Error messages now cite thinslice.toml everywhere, eliminating the old mixed references to both filenames.
Reporting output updated to use the new manifest name throughout (befec97).
slice tmp --from current creates a disposable agent worktree that inherits a full clone of the current slice's state — its own Postgres database, Redis instance, and port assignments — so coding agents can work in isolation without polluting your main branch's environment.
Temporary worktrees created with slice tmp are automatically cleaned up (services torn down, ports released) when the worktree is removed.
State cloning is incremental: only tables and keys modified since the last snapshot are copied, keeping spin-up time fast on large datasets.
Improved
Global port allocation now tracks reservations across all active worktrees in a shared registry, eliminating the port collisions that occurred when spinning up multiple agents concurrently.
give-me-a-port command updated to consult the global registry before handing out a port, with an atomic reserve-and-write step to prevent races (e0c5377).
Port ranges are now configurable per project in thinslice.toml; the default range widens to 20 000–29 999 to accommodate larger agent fleets.
Fixed
slice reconcile no longer leaves orphaned Postgres roles when a worktree is deleted mid-migration.
Redis key namespacing is applied consistently so worktrees with identical key names no longer bleed state into each other.