+ Step 5 shrinks to one sentence. The "one concern per PR" rule already exists + in the repo guidelines and + #221 + ignored it, so a new rule would not have helped there. What is worth adding is a + single line in AGENTS.md saying that migrations touching existing rows must be timed + against a big database before merge. +
++ So the plan becomes: PR one is the migration fix. PR two is "desktop waits while + migrating" plus the per-migration timing log. And one sentence in the guidelines. + Nothing else. +
++ Starting with PR 1: adding the one-line guideline, committing the migration fix on a + descriptively named branch, pushing, and opening the PR. +
+