Sync a pi extension to the latest pi SDK

Adapt an extension to the latest published pi version by default, or to an explicit target=<version>. Two layers:

• Compatibility layer (steps 2–4): fix breaking changes with zero behavior change — every behavior-affecting fix needs the user's sign-off.
• Adoption layer (step 5): survey APIs/features added since the installed version; present each as a candidate with benefit, scope, and risk; adopt only what the user picks, one item at a time.

Steps

1. Resolve the target version, locate the SDK, and read its changelog

Resolve target in this order: explicit target=<version> argument → else the latest published version (npm dist-tags.latest for @earendil-works/pi-coding-agent; cross-check GitHub releases). Never infer target from prior reports, prior syncs, GLOSSARY.md, ADRs, git history, or installed devDependencies — the report is write-only.

Record the resolved version. If it equals the installed version, skip the fix loop (steps 3–4) but still run step 2's typecheck — the seam catches pre-existing repo debt, not just SDK drift — and run the adoption survey (step 5).

Locate the installed package (for the baseline comparison) via: