Not every change deserves the same repair speed.

Release triage ranks doc repairs by answer risk. A spelling fix can wait. A changed default, a removed safety note, a model limitation, or a new authentication flow cannot. The triage wall asks whether an old answer would cause a failed implementation, a misleading comparison, a privacy mistake, or a support burden.

High-risk changes move directly to example review and instruction review. Medium-risk changes get source anchors and visible caveats. Low-risk changes are batched so the public page stays tidy without turning every release into an emergency. This simple separation keeps a documentation team from treating all change as noise.