Our Foundations file is published as a library, consumed by other design files and by developers via the Variables REST API. We need to test changes — including adding/removing variables, not just editing values — without those changes reaching devs or other files until we're ready.
Current gaps:
- Branches can't be referenced as a library from another file, so we can't test a branched foundations file in a separate screens file.
- Extended Collections only allow overriding existing values, not adding/removing variables.
- Our only workaround is manually duplicating the whole file into a "sandbox" library and re-syncing it by hand whenever production changes — error-prone, with no diffing.
Ask: A way to stage variable changes (ideally via branching) and reference that staged version as a library in a separate file for testing, while production and the REST API stay untouched until we merge and publish. A diff view between staged and production would also help avoid drift.