How to use
- Start after Token Impact Simulator already gives you a believable blast-radius estimate.
- Enter the rollout stage, affected branches, diff coverage, tests, docs status, and target token.
- Read the result as a compact pre-merge or pre-release checklist, not as a substitute for the repository release policy.
Convert impact into release-ready checks
This page fills the gap between “I know what changes first” and “I know what must be checked before I ship the change.”
How to choose between nearby pages
Use Token Impact Simulator when the open question is still what changes first. Use Token Deprecation Plan when the blast radius already looks believable but the next question is alias grace, warning timing, freeze timing, and hard removal order. Use this page after that, when the next question is what must be checked before merge or rollout.
FAQ
What does this page organize?
It turns change type, rollout stage, visual diff coverage, tests, and docs readiness into a compact pre-merge or pre-release checklist for token changes.
When should I use this instead of Token Impact Simulator?
Use Token Impact Simulator when the question is still what changes first. Use this page after that, when the next question is what must be checked before merge or rollout.
Does this replace repository-specific release policy?
No. It is a general checklist for token work and should be combined with the actual repository release gate and QA flow.
What is stored in the share URL?
The share URL stores change type, release stage, component scope, affected branches, affected components, visual diff coverage, test coverage, docs readiness, and target token.