Thomas Piacentini
← Workshop

Project brief

Dependency Upgrade Impact Map

Original text · English

Help a maintainer review an upgrade using supplied before/after API signatures and a bounded source parser. Map changed symbols to actual call sites, distinguish confirmed incompatibilities from unresolved uses, and emit a targeted test checklist. An optional model can explain evidence but cannot invent removed APIs.

Proposed milestones

  1. Read supplied old and new API contracts
  2. Index supported import and call-site forms
  3. Link changed signatures to affected code
  4. Export findings with unresolved cases visible

This is an upstream project brief; an implementation and completion tests are not supplied.

Code and artifacts 1
What you take away

Saved in your notebook on this device.

Sources and limits

Reading checkpoints are self-reported. Test results are recorded separately and apply to the executed cases.

AI Engineering from Scratch · 3f9715c · MIT

Download this file ↓