Migrations prompts

Plan an upgrade from [PACKAGE] [CURRENT VERSION] to [TARGET VERSION].

Why we are upgrading: [SECURITY FIX / FEATURE WE NEED / END OF SUPPORT / STAYING CURRENT]
How the package is used in our codebase:
"""
[PASTE THE IMPORT SITES, THE CONFIG, AND ANY WRAPPER OR ADAPTER CODE. A GREP FOR THE PACKAGE NAME IS A GOOD START.]
"""
Migration guid

Write a data backfill script.

What needs to change: [THE TRANSFORMATION, IN PLAIN TERMS]
Schema and table sizes: [PASTE THE RELEVANT SCHEMA + ROW COUNTS]
Database and version: [e.g. Postgres 16, MySQL 8, MongoDB]
Language and access pattern: [e.g. "Python with SQLAlchemy", "a psql script", "a Rails task"]
Is the system live during the ba

Plan (do not yet execute) this migration: [FROM → TO, e.g. "Express 4 → 5", "moment → date-fns", "REST client X → Y", "Python 3.9 → 3.12"]

Codebase context: [SIZE, STACK, TEST COVERAGE HONESTLY STATED]
Why now: [THE FORCING FUNCTION: EOL, security, blocked feature]
Relevant code (or run against the repo if you're an agent):
"""
[PASTE RE

Port this code from [SOURCE LANGUAGE] to [TARGET LANGUAGE].

The code:
"""
[PASTE THE MODULE/FUNCTIONS, or point an agent at the files]
"""
What it does in production: [THE REAL JOB + what depends on it]
Existing tests: [PASTE THEM / "none", if none, step 1 is mandatory, not optional]
Target conventions: [THE FRAMEWORK/STYLE THE PORT MUST