Keep compiled specifications out of runtime package artifacts #40

Observation

Registry verification of @cratis/scene.components@3.4.0 found compiled specification modules in the published runtime archive, for example:

package/dist/esm/data/for_SceneDataTable/when_forwarding_query_arguments.js

This is a packaging-boundary follow-up, not a claim that the module is imported by the normal runtime entrypoint or that it breaks the verified query-argument behavior.

Scope

• Inspect the current TypeScript/Rollup/package-files boundary and separate runtime outputs from co-located specifications.
• Preserve native test discovery/typechecking and normal package exports.
• Apply the same reviewed policy to other Scene packages only where the same issue is confirmed.

Acceptance

• A packed runtime archive contains no for_* / specification modules or test-runner imports in its supported runtime surface.
• Native package tests/type checks still run and pass; tests are not simply excluded from verification.
• Runtime entrypoints, declarations and documented subpath exports remain compatible.
• A real packed-package assertion detects future test-output leakage.

Observed during v3.4.0 release verification; independent from optional-single query UI (#39) and standalone frontend composition (Cratis/Stage#100).