Retire provider-target compatibility aliases and projection fallback

[cbusillo]

Intent

Remove or demote compatibility surfaces after provider-target authority is proven in production.

Current Status

Waiting for live evidence slice #1105. Parent: #1100.

Finish Line

Legacy dokploy_targets manifest aliases, duplicate Dokploy-named response keys, flat target fields that duplicate target_reference, and read-through projection fallback are removed or demoted according to compatibility-retirement policy.

Acceptance Criteria

• Compatibility inputs fail with clear validation errors or are explicitly local/import-only.
• Provider-target reads no longer synthesize live authority from Dokploy records.
• Product workflows and service routes use neutral names.
• Dokploy execution records/adapters remain where still needed for provider-specific config.
• Docs updated in records, service-boundary, new-product-repo, driver-descriptors, and compatibility-retirement.
• Tests prove old aliases no longer mutate production authority and missing provider-target rows fail closed.

Quality Gates

Full targeted compatibility tests, default unittest, full ruff, mypy, docs updates, and post-merge CI/deploy/health.