A major version upgrade in May 2025, after thirteen months of a pin, and twelve months of nothing happening.
incidents attributable to the cache: 0
configuration changes since May: 0
the compatibility suite: retired
the fork: still in the
local stack,
still unused
the review scheduled for May 2026 concluded that the
fork profile can go. it has not been started once.
which is thirteen months of preparation and twelve
months of quiet, for a licence change that reverted.
Writing down that nothing happened is the only way the next licence panic has a reference point, and the reference is that the option cost about twenty minutes of runner time a year and was never exercised. That is cheap enough to do again and is not free, which is the whole finding.