Practical use
- If you skip a fusion in the current public build, do not assume there is an in-run restore button for that exact offer.
- The live 1.1 rollout confirms Splicing 2.0 is part of the shipped update and that Splicing stays available in Pressure runs once unlocked, but current route advice should still be based on tested live behavior rather than teaser phrasing alone.
- Treat restore-fusion searches as three separate checks: whether you only skipped one offer, whether Splicing is unlocked on the profile, and whether you are asking about current live-build behavior or older pre-1.1 notes.
- If a run depends on one exact fusion branch, preserve mutagen and route stability first; do not click skip expecting a safe undo.
- After 1.1, retest Splicing availability, pause-menu screenshot flow, and Codex access in live runs before turning any preview wording into hard route rules.