Blueprint outputs and automatic redeploys

Blueprints can now expose outputs like database endpoints, connection strings, and API URLs that other installations consume through valueFromOutput. When a blueprint's Terraform installation produces outputs, they're surfaced as named values that any downstream installation can reference:

The same syntax works for referencing outputs from service installations. Replace blueprintInstallation with serviceInstallation.

Automatic redeploys on output changes

Previously, if an upstream installation hadn't been deployed yet, the downstream would deploy with empty values. And if the upstream's outputs changed later, like a database endpoint rotating or a new Terraform apply, downstream installations kept running with stale config until someone manually redeployed them.

Both of these are now handled automatically. If an installation references outputs that don't exist yet, it's blocked with an Outputs unavailable status until the dependency completes, then deploys with the correct values.

When upstream outputs change, every downstream installation that references them is redeployed automatically. This also applies to environment config changes. Provider updates, registry credential rotations, release channel changes, and provisioning output changes all trigger redeployment of affected installations. Variable groups, output references, and environment config are tracked through a single unified mechanism, so all external inputs to an installation are covered.