Declare compatibility and requirements

List only the MSFS versions in which your add-on works. I tested it means you actually checked it in that simulator; it is separate from declaring compatibility.

1. Check the destinations and simulators configured in Architect.
2. In the Compatibility step, record the tests you performed and any version restrictions.
3. Use Architect’s settings to specify required add-ons, known conflicts and other requirements.
4. Explain any important limitations in the description.

Once a plan exists, its simulators and destinations are the reference. To change them, use the plan settings in Architect, then check compatibility again. They must match before submission.

Declaring a companion application or an external setting is informational: it does not install anything, automatically check its presence or block installation on its own. Hub installation tests do not replace trying the add-on in flight or in the scenery.