Manage a change that spans a primary code repo and a companion config/distro/data
repo as paired pull requests — keeping them backward-compatible, cross-linked, and
safe to merge independently. Use when a feature needs both a code change (new
field/loader/behavior) AND a configuration/catalog/deployment change that lives in
a separate repo, so neither PR is broken or confusing on its own.