Updates and rollback
Switch retained Framework package selections without overwriting product source, and recover controlled writes safely.
Retain the current version before updating
Work on an application branch with a reviewed package.json, bun.lock, and retained vendor selection. Keep release A's original source, archives, and notices in private storage. Back up application data separately. Run the commands from your project directory. Acquiring a release keeps previous downloads and does not update installed packages.
smoothie project context --format json
smoothie framework acquire --version <exact-release-tag>Replace the tag with the selected exact release. Read its compatibility and migration guidance first. The current mutator supports root Bun projects, not native workspaces or binary bun.lockb. Keep an independent copy of application source changes; package switching is not a source merge or a database migration.
Review and apply the package switch
smoothie framework use --dry-run --format json
smoothie framework use --expect-plan <data.planId>Review the first result and replace data.planId with its exact value before applying. Without --package, the CLI uses the current recorded roots and computes their closure. An explicit package list is a complete requested root selection, not an incremental add instruction. Inspect the resulting plan before changing it.
The switch retains verified package archives and updates Framework references in package.json. It preserves unrelated dependencies and your edited application source. Installation is separate by default.
bun install --ignore-scripts
smoothie project verify --task typecheck --task test --task build --runRegenerate and review the native lockfile deliberately; do not use a frozen install to resolve an intentional dependency switch. Inspect the diff, run relevant browser and service tests, then retain the new lock and archives. Package switching does not update installed coding-agent skills. Follow skill version alignment separately and resolve conflicts without overwriting your own edits.
Keep the selected release with the project
Acquisition keeps previous releases in the cache and updates selected.json; use changes the installed packages. Commit the selection, package files, lockfile and vendor records together after your checks pass. Your edited Starter source is preserved.
For a separately stored release, pass /path/to/release/bundle and --source /path/to/release/source to both use commands. The same plan review and installation steps apply.
Return to a retained selection
smoothie framework acquire --version <previous-exact-release-tag>
smoothie framework use --dry-run --format json
smoothie framework use --expect-plan <data.planId>
bun install --ignore-scriptsAcquire the earlier tag and review a new plan. The CLI reuses a verified cached copy when available. Changing the selected tag alone does not roll back installed packages. Inspect the lockfile diff and repeat checks. This returns Framework dependencies to the earlier release, not product source, node_modules bytes, databases, or remote effects. Restore compatible application changes and data only through their own reviewed recovery procedures.
Recover an interrupted managed write
smoothie framework recover <journal-id> --project . --action rollback --dry-run
smoothie framework recover <journal-id> --project . --action rollbackUse the journal id reported by the interrupted use operation, not a guessed id. Review recovery before applying; resume is a separate explicit alternative to rollback. The CLI refuses unrelated intervening file edits or unrecorded native lock changes instead of overwriting them. Recovery never implicitly reinstalls dependencies and is not a transaction over application data or external processes. Investigate unexplained state before authorizing another switch.