pokeswift-extractor-contract-change

# PokeSwift Extractor Contract Change Read [AGENTS.md](../../../AGENTS.md) and [SWIFT_PORT.md](../../../SWIFT_PORT.md) before changing milestone-sensitive behavior. Treat generated content as evidence, not authoring surface. Prefer fixing the first broken contract layer instead of compensating in runtime code. ## Workflow 1. Define the failing contract. Capture the exact value or shape that is wrong: missing dialogue ID, wrong warp/checkpoint, broken map script, bad trainer manifest, missing audio cue metadata, stale item/species/move field, or loader decode mismatch. 2. Trace the first diverging layer. Use this order: `pret/pokered asm/data -> PokeExtractCLI -> Content/Red -> PokeDataModel/PokeContent -> PokeCore/PokeUI`. Fix the first layer that differs from the expected source-driven result. 3. Pick the right ownership boundary. If the extracted value is wrong, change `PokeExtractCLI`. If the extracted value is right but the shared model cannot represent it, change `PokeDataModel` first. If the model is right but loading or validation is wrong, change `PokeContent`. Only change `PokeCore` or `PokeUI` after the upstream contract is correct. 4. Regenerate instead of patching artifacts. After extractor changes, run `./scripts/extract_red.sh`. Never hand-edit `Content/Red/**` as the fix. 5. Validate upstream first, then downstream. Run focused `PokeExtractCLITests` and `PokeContentTests`. Then run the smallest runtime or UI tests tha...