Require end-to-end compatibility for workspace release changes

Treat workspace-aware release behavior as an end-to-end, cross-repository contract. Propagate selected workspaces losslessly through configuration resolution, CLI parsing, actions, input forwarding, title/issue identity, CI-label assumptions, target selection, publish-state keys, documentation, and tests; update all producers and consumers together. Validate untrusted workspace values before side effects and fail closed for empty, option-like, ambiguous, control-character, Unicode-control, separator, or otherwise unsafe input. Preserve unscoped paths byte-for-byte, prevent workspace/version collisions, use authoritative identity/state algorithms, and do not ship producer changes before acceptance-side support. Test scoped and unscoped paths, defaults, invalid inputs, and security/correctness boundaries; require adversarial evidence-based review and use pnpm for project dependency and test commands.