plastic-rollback

# Plastic Rollback: local version time-machine ## When to Use - "show plastic versions", "version history", "what versions have I run" - "roll back plastic", "downgrade", "go back to the version that worked", "revert plastic" - A new version broke something and the user wants their last known-good build For upgrading to a **new** release, use `plastic-update`. This skill only navigates versions you have **already installed**, the ones recorded in the ledger. ## Read-only by default A flagless run only prints the version history table. It never switches, never prompts, and never offers to keep going further back. Switching a version always needs an explicit target, named with `--version`. ## Channel rule `rollback` restores whichever build you name from the ledger, it does not take a channel flag for the target. The pinned `<channel>` below is only the npx invocation itself: derive it from `~/.plastic/VERSION` the same way as the other lifecycle skills, `-alpha` to `@alpha`, `-beta` to `@beta`, otherwise `@latest`. ## The ledger `~/.plastic/versions.json` is an **append-only JSONL** ledger, one line per version change, never modified or deleted: ```json {"version":"1.0.0-alpha.17","action":"install","at":"..."} {"version":"1.0.0-alpha.18","action":"update","at":"..."} ``` `action` is one of `install`, `reinstall`, `update`, `downgrade` (derived from version direction; the channel is derived from the version string, never stored). It is a troubleshooting record. ## P...