Remap Addresses
Preview a known conversion before applying it.
Follow ../../references/interaction-contract.md.
Process
- Require the source and target conventions.
- Require an explicit register area when notation does not prove it.
- Run
python3 <skill-dir>/scripts/run.py --input <map.json> --from <convention> --to <convention> --output <preview.json>. - Validate offsets, source/canonical agreement, and collisions across the whole map. A conflicting source token must not silently replace a canonical offset.
- When the requested conventions are explicit and the preview is collision-free, apply the conversion without another confirmation. Ask once only for ambiguity or a lossy/colliding result.
Output files
preview.json/ converted map - Review every old and new address, then use the applied map when the conversion is collision-free. The input map remains unchanged.
Completion requires a collision-free, hash-bound converted map before linting.
Stop
- Stop when source or target convention is unknown.
- Stop when register area is not proven by notation.
- Stop on collision or lossy conversion, or when a write is requested.
Handoff
- The converted map needs validation: suggest
check-map. - Source conventions remain mixed or unknown: suggest
normalize-map.
Keep the raw source token. Protocol offset zero is valid; offsets above 65535 are not.