release-crates.yml has been failing since July - new crates can't be created via Trusted Publishing #2110

Summary

The release job in .github/workflows/release-crates.yml (release-plz release) has failed on about 97 of the last 100 pushes to master. No crates have been published to crates.io since 2026-07-10 (ironrdp 0.17.0 / ironrdp-core 0.2.1), while PR #2067 (chore(release): prepare for publishing) has been open since Oct 1.

Root cause

From the failed job log:

error: failed to publish ironrdp-rail v0.1.0 to registry at https://crates.io
Caused by:
  403 Forbidden: Trusted Publishing tokens do not support creating new crates.
  Publish the crate manually, first

The workflow authenticates via rust-lang/crates-io-auth-action (Trusted Publishing OIDC token). Per crates.io, a TP token can publish new versions of existing crates but cannot create a new crate. This release window introduces crates that don't exist on crates.io yet, so release-plz stops at the first one and the whole job exits 1 - nothing publishes, including version-only bumps.

New crates needing a one-time manual first publish

Verified 404 on crates.io, listed in dependency order:

1. ironrdp-rdpeudp 0.1.0
2. ironrdp-rdpemt 0.1.0
3. ironrdp-rail 0.1.0
4. ironrdp-rdpei 0.1.0
5. ironrdp-rdpel 0.0.0
6. ironrdp-rdpeudp-tokio 0.1.0 (depends on rdpemt + rdpeudp, so publish it after them)

ironrdp-agent and ironrdp-viewer already exist, so those are fine.

Fix

1. An owner runs a one-time cargo publish for each new crate above, in the order listed.
2. Merge PR chore(release): prepare for publishing #2067. The TP flow then publishes the remaining version bumps automatically on the next push to master.
3. Afterwards, consider documenting in the release docs / release-prep skill that any newly added crate must be manually published once before its first release window, so this doesn't recur.