Advice to delay non-critical updates

Quote-posts the Bitcoin Red Team's Situation Report No. 1, whose figures are 4,962 findings across 390 of 391 projects reviewed, 85 critical and 635 high severity in 29.8 hours, and draws an unusual conclusion from them: because much of the ecosystem is about to ship fixes, owners should wait two or more weeks before applying any update that is not mission critical, so that other users encounter and report the new bugs first. Held because it is a distinct argument in the post-incident software debate, running against the migrate-and-update-now advice held elsewhere in this record, and because it treats the audit wave itself as a source of risk. The primary post for the quoted figures is held at callebtc-2085024458012586286. The underlying findings are not public, and both the counts and the update advice are the posters' own and are not verified here.