Consume the released infrastructure kits through the normal pack path

[Brad-Edwards]

Integrate published infrastructure kits as ordinary environment packs. Keep kit authoring upstream and execution, credentials, readiness and evidence with APTL.

Done when

• Use the released env-packs/reference-packs contracts without a private kit schema or copied manifests.
• For each released kit, preserve ordinary pack files, locks, artifact identity and provenance and either verify its declarations or track the concrete missing implementation with a regression test.
• Prove a representative composition joining identity, endpoint, DNS, application, data, security monitoring and observability kits.
• Show what was authored separately from what was launched and verified.

The full released catalog remains tracked by those individual issues. Preview/add/update/replacement/removal through the shared proposal contract is deferred to #1123; no kit is being dropped.

Related: OpenRAE/env-packs#190; OpenRAE/reference-packs#2; kit implementation issues #1056–#1096.