add-oliphaunt-extension

To safely add a PostgreSQL extension, you must preserve accurate source pins, target compatibility, packaging, and release metadata. This prevents incomplete support claims by requiring explicit target evidence, carrier declarations, and artifact installation verification.

The best way to update external PostgreSQL extensions is to apply source pinning, validate the release graph, and ensure target compatibility across native, mobile, WASIX, npm, Maven, and Cargo distribution workflows. This maintains release and package integrity during updates.

Runtime availability does not equal extension support. You must declare supported and unsupported targets explicitly, attach evidence, and verify artifacts using a fail-closed compatibility approach to prevent runtime availability from being mistaken for official support.

To promote a deferred PostgreSQL extension, you update its support metadata, regenerate the extension model, and run all required verification checks. This includes legal-data closures, generated-model checks, and release-graph validation to ensure safe promotion.

Verifying artifact installation requires applying immutable source identities, validating checksums, and running installation and runtime verification checks. This fail-closed process ensures that PostgreSQL contrib extensions meet all packaging and release integrity requirements.

You should not use automated lifecycle management if you cannot provide explicit target evidence, immutable source identities, or legal-data closures. Without these required declarations and generated-model checks, the extension support claims remain unsafe and incomplete.