Add release dry-run validation for compatibility publishing #28

Context

PR #27 adds the Angular compatibility harness that builds one tarball and tests that same artifact against generated Angular consumers before release publishing.

The release workflow now runs:

• pnpm run compat:release-parity
• pnpm run compat:pack
• pnpm run compat:artifact
• pnpm run compat:test
• npm publish "$TARBALL"

Follow-up

Add a dedicated release dry-run validation path that exercises the release workflow without publishing to npm.

Useful coverage would include:

• running the release workflow with dryRun=true
• confirming the release script keeps the expected package version semantics in dry-run mode
• confirming the packed artifact version check still passes
• confirming the dry-run path runs the same compatibility artifact checks as a real release

Why

CI now proves PR compatibility. This follow-up would prove the manual release workflow remains safe before a maintainer performs an actual publish.