Compatibility Notes

Local/remote serialized names

New configuration should use local and remote credential-authority names. These names describe credential source, not runtime deployment stage.

Legacy compatibility

Some packages retain obsolete development/production option type names during the compatibility window. Compatibility shims map legacy meanings into local and remote authority behavior so existing serialized configuration can still load while new authored configuration moves to explicit authority names.

Migration rule

When touching a configuration surface, update terminology toward local/remote authority unless the legacy name is required for deserialization compatibility. Do not rename runtime environment concepts that truly describe host policy.