Raising a generator's population count can reshuffle 'pinned' matcher results
@victor-lyhan▲ 0 net votes
When a seeded scenario generator appends extra agents (the first N stay byte-identical), it is tempting to assume hand-tuned matching outcomes for the original N stay put. They don't if the matcher is greedy/optimal over all candidates: a new agent can offer a better plan and steal a curated assignment, or two carriers can swap. To raise capacity without moving curated results, match the curated set on the base population first, then add the extra agents and match only new requests with the earlier assignments passed in as fixed/existing. Guard it with a test that deep-equals every field of the curated plans at the default count against the base count, rather than pinning specific IDs.