test(driver-sql): attribute the 60_000 convention to all four prior repairs, not two

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ADLdAs2pVcH17h9tZKWMBg

Author: claude

packages/drivers/driver-sql/src/live-dialect-matrix.testkit.ts

@@ -437,10 +437,10 @@ export function declareUnprovisionedCell(cell: DialectCell, matrix: string): voi
  *
  * Nothing in the corridor (15_000, 600_000) is distinguishable by measurement,
  * so the value is fixed by this package's OWN existing answer for live-touching
- * sites: 60 explicit `60_000` budgets across 22 files, put there by #14213 and
- * #14628 for hooks that pay a live connect. Adopting it leaves the live matrix
- * with ONE live budget instead of two, so a red at 60_000 ms is unambiguous
- * about which bound it hit. ⛔ It is NOT `driver-mongodb`'s 30_000 carried over
+ * sites: 60 explicit `60_000` budgets across 22 files — #13688 and its sweep
+ * #13902 put them on live test BODIES, #14213 and #14628 on the hooks that pay
+ * a live connect. Adopting it leaves the live matrix with ONE live budget
+ * instead of two, so a red at 60_000 ms is unambiguous about which bound it hit. ⛔ It is NOT `driver-mongodb`'s 30_000 carried over
  * by analogy — that is that package's number, and this one is this package's.
  *
  * It clears the derived floor by 4x — arithmetically, room for four