[presentation-preset] generated output contract를 모든 지원 runtime profile에서 검증한다

[kang-heewon]

Problem

@croco/presentation-preset is beta, but production-ready promotion requires generated output contract validation for every supported runtime profile and no untested runtime capability claim in the package catalog.

Today the catalog can describe Node, Lambda, Workers, and Frontend support, but the runtime claims are not yet backed by a single generated-profile verification path that makes drift obvious to CI and reviewers.

Related: #922, #938

Scope

• Define the supported generated runtime profiles that @croco/presentation-preset claims.
• Add output contract fixtures or generated-app smoke coverage for each supported profile.
• Validate generated entries, artifacts, runtime target metadata, contract format, and unsupported runtime claims.
• Fail when docs/package-catalog.json claims a runtime that lacks generated contract evidence.
• Surface the result in package tests or generated-app smoke so CI catches drift.

Acceptance criteria

• Each supported runtime profile has a named output contract validation test or generated-app smoke.
• Untested runtime claims are removed from the package catalog or fail the verification step.
• @croco/presentation-preset README names the supported profiles and the command that proves them.
• pnpm --filter @croco/presentation-preset test passes.
• pnpm create-croco-app:smoke passes when generated profiles are touched.
• pnpm docs:catalog:check passes.

Verification

pnpm --filter @croco/presentation-preset test
pnpm create-croco-app:smoke
pnpm docs:catalog:check
pnpm check