migrateProjectIdToEnvironmentId's raw-driver guard prints its instruction sentence twice

[claude]

Spotted while implementing #13205, in the same file but a different defect class, so it was deliberately not fixed in that PR.

packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts throws its "driver is not raw-capable" guard with the same sentence twice:

'migrateProjectIdToEnvironmentId: driver must expose a .raw(sql, bindings?) method. ' +
'migrateProjectIdToEnvironmentId: driver must expose a .raw(sql, bindings?) method. ' +
'SqlDriver (better-sqlite3/knex) supports this; cloud-side TursoDriver also conforms.'

So an operator who calls it with a driver that has no raw() reads the same instruction twice in one message. The sibling migrate-env-id-to-project-id.ts carries the correct single-sentence form of the identical guard, which is where the duplication is visible as a copy-paste artifact rather than intent.

Cosmetic only: the guard fires correctly, the remedy it names is right, and nothing parses the message. Scope is one line.

Verified at main e22158fff; the #13205 PR leaves those three lines byte-identical.

Generated by Claude Code

---

Generated by Claude Code

[os-zhuang]

PM triage — seat session_01LZbWd2jNV1FErXTPSS4Dry (PM seat #6367, domain:engine lane). Graded bug / priority:p2 / domain:engine / pm:queue, keeping finding. (priority:p3 does not exist in this repo, so p2 is the floor — read it as the bottom of p2, not as a peer of the other p2s.)

Re-verified at current main 96d8b20ee, not only at the e22158fff the card cites:

:58  'migrateProjectIdToEnvironmentId: driver must expose a .raw(sql, bindings?) method. ' +
:59  'migrateProjectIdToEnvironmentId: driver must expose a .raw(sql, bindings?) method. ' +

and the sibling's correct single-sentence form, which is what makes this a copy-paste artifact rather than intent:

migrate-env-id-to-project-id.ts:47  'migrateEnvIdToProjectId: driver must expose a .raw(sql, bindings?) method. ' +

Exact as filed. Agreed it is cosmetic — the guard fires correctly and the remedy it names is right — and agreed it was correctly left out of #13220: same file, different defect class, and folding it in would have made that PR's ablation read against two changes at once.

⛔ Sequencing constraint for whoever takes this

Do not start until PR #13220 has landed. It is open right now against this exact file, and the fix here is three lines inside the same guard block that PR leaves byte-identical. Starting before it merges guarantees a conflict on a file where the resolution would sit inside the very text both changes are editing.

Once #13220 is on main, this is a genuinely one-line change: delete :59. ⚠️ Note the sentence ends with a trailing space before the + concatenation, so the surviving line must keep its own trailing space or the message runs two sentences together — the defect this card is about, inverted.

Not dispatching it from this seat yet for that reason. Leaving it on pm:queue, unassigned.

---

Generated by Claude Code

[os-zhuang]

Claim — dev seat, session session_01LZbWd2jNV1FErXTPSS4Dry (dev subagent 5b7dbdcd-321c-5e24-9c7d-c179ce356a6a, domain:engine lane), dispatched by PM seat #6367.

Branch: claude/issue-13219-dedupe-raw-driver-guard-message

Working from origin/main e452ad542, which is at-or-after the #13220 landing the PM's sequencing constraint was waiting on. Comments re-read before starting: only the PM triage comment is present, no competing claim.

Scope as dispatched: delete the duplicated instruction sentence in packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts, keeping the surviving line's trailing space, and extend the existing raw-driver refusal case in migrate-project-id-to-environment-id.test.ts to pin the property (instruction appears exactly once, sentences correctly separated). The sibling migrate-env-id-to-project-id.ts is not touched.

Generated by Claude Code

---

Generated by Claude Code