Replace legacy presets with trusted definitions

[YKDZ]

What changed

• Replaced the legacy Preset Source/Projection runtime with trusted TypeScript Built-in Preset Definitions and one explicit registry.
• Cut catalog, init, dry-run, Package Addition, Blueprint v2, linking, checks, and publication over to the registry.
• Moved generated file bodies into Self-Checking Template Source and removed the old manifest/schema/interpreter/adapters.
• Added registry-derived init, addition, focused-link, packed-publication, boundary, deployment, and zero-legacy checks.

Why

Preset names and behavior were repeated across core, CLI, checks, and template manifests. This made removed entries such as hono-api difficult to delete cleanly and coupled generic generation code to built-in frameworks.

The new model keeps Preset-specific planning and file behavior with each trusted Definition while the shared core handles generic composition and execution.

Validation

• pnpm check — 24/24 tasks
• Registry init matrix — 5/5
• Package Addition matrix — 15/15
• Focused Project Link scenarios — 5/5
• Packed CLI consumer/import/init/all-addable verification
• Packed Legacy Architecture Removal Check
• Cargo tests and Turbo boundaries

Docker is unavailable in the local environment. The deployment gate therefore hard-fails locally with an explicit message and is wired into GitHub Actions on a Docker-capable runner.