Separate consumer release names from validation profiles

[szmyty]

Outcome

Let consumers keep Relay's artifact-class profile as the validation authority while choosing a bounded product-facing name for the outer archive, annotated tag message, GitHub Release title, and release notes.

Context

OptiFlow correctly publishes through the binary profile, but Relay currently exposes that internal class as binary-v0.1.0.tar.gz and binary v0.1.0. The product-facing release should be named optiflow-v0.1.0.tar.gz / optiflow v0.1.0 without inventing an OptiFlow-specific validation profile.

The existing v0.1.0 tag and assets are immutable evidence and must remain unchanged. This contract applies to future releases.

Acceptance criteria

• release-artifact.yml accepts an optional safe product-facing release name.
• Omission remains backward-compatible by falling back to the selected profile.
• The resolved name is used consistently for the outer archive, annotated-tag message, Release title/notes, and identical-release resume checks.
• The validation profile remains separate and authoritative.
• semantic-release.yml, the workflow catalog, examples, and Relay dogfood propagate the new input.
• Static tests cover custom naming, fallback behavior, and unsafe-name rejection.
• Relay publishes the additive contract immutably before OptiFlow repins to it.