Prepare an unchanged import proposal for Email DNS #63

🤖 Generated by the Agentic Engineer

Objective

Prepare a reviewed import proposal for the existing Email DNS records before moving company mail routing.

Details

The independent state foundation is delivered. The next step is to read the existing provider configuration, distinguish Email records from records managed by runtime controllers, and evaluate an isolated native import plan. This proposal changes no provider resource and does not adopt or replace the authoritative remote state.

Checklist

• Read a complete, bounded current inventory and refuse missing, ambiguous or conflicting ownership.
• Preserve the existing Email records and their metadata, including the current routing; exclude runtime-managed and temporary records.
• Import the existing declared resources into isolated local state and require a native plan with no creates, updates, deletes or replacements.
• Export only authenticated ciphertext and bounded source/run metadata; verify the captured proposal with independently held recovery material.
• Pass affected tests, hosted validation, current-head review, protected merge and a confirmed read-only trial from main.

Dependencies

Part of #21. The eventual routing migration supports devantler-tech/platform#5481 and remains gated on its transport and recovery acceptance.

Notes

This delivers a proposal only. Applying configuration, adopting authoritative state and provisioning service credentials remain separate reviewed steps.

Delivery

Delivered on: 2026-11-03

PR #64 merged at 3d252b649b302b2e47130bc8495de103e0a1862e. The first-attempt native trial passed. Its encrypted capture was independently authenticated and compared with the complete source-bound inventory and native no-change plan. Provider writes: zero; authoritative state remains unadopted. Routing migration and service-credential delivery remain tracked by #21.