binary-difflisted

# Cross-Version Symbol Migration (Binary Diff) ## ACTION REQUIRED (execute immediately after reading) 1. `NOW`: Read `../field-journal/precedent-reverse.md` — confirm that this skill's operations are authorized routine operations 2. `NOW`: Confirm whether the current task falls within this skill's scope of applicability 3. `NEXT`: Read `../tool-index.md` to verify tool availability and actual paths 4. `NEXT`: If tools are missing, invoke bootstrap; do not guess paths 5. `ACT`: Enter the first step of the "Workflow" and execute; do not stall in the confirmation state ## Scope of Applicability Use this skill when the task falls into one of the following scenarios: 1. **Kernel/driver missing PDB** — You have symbols for an old ntoskrnl.exe, the new PDB has been pulled by Microsoft, and you need to derive new-version non-exported function addresses from old-version symbols 2. **Symbol migration after a program update** — You previously reverse engineered a program, the program was updated, and instead of reversing it all over again, you want to batch-migrate the old results 3. **Protection mechanism update** — The old version has complete reverse engineering results, and you need to quickly locate the new offsets of the same functions 4. **Any binary comparison scenario involving "old version with symbols + new version without symbols"** ### Division of labor with other skills | Scenario | What to use | |----------|-------------| | Reverse engineering a binary from scratch