[Marc-André Moreau (mamoreau-devolutions)]

Several crates added since the last release were marked publish = false or lack release metadata, so cargo publish cannot release them or the crates that depend on them, including ironrdp-agent, ironrdp-viewer, ironrdp-client, and ironrdp-server.

This makes all new crates publishable, except internal tooling and ironrdp-activex, ironrdp-rdpecam, and ironrdp-capture-replay, which stay internal:

• Drop publish = false from ironrdp-daemon, ironrdp-rpc, ironrdp-rdpeai, and ironrdp-rdpeusb. ironrdp-client, ironrdp-server, and ironrdp-rdpsnd-native depend on ironrdp-rdpeai, and ironrdp-server depends on ironrdp-rdpeusb; Cargo rejects these even as optional dependencies.
• Set rust-version = "1.94" on the newly published crates that lacked it.
• Give every not-yet-published crate a CHANGELOG.md that release-plz can extend: the git-cliff header followed by an empty ## [Unreleased] section. release-plz keeps the header through that line and inserts the generated release below it. Replace the placeholder ## [0.1.0] - YYYY-MM-DD heading in ironrdp-rdpei, which release-plz would otherwise duplicate.
• Make READMEs suitable for crates.io by linking sibling crates through docs.rs and no longer describing ironrdp-rpc as internal.
• Render the README as crate docs for ironrdp-rpc, ironrdp-daemon, and ironrdp-rdpeusb without repeating its first sentence.
• Update ARCHITECTURE.md: drop the "not published" note on ironrdp-daemon and add an ironrdp-rpc entry.

Crates.io Trusted Publishing cannot create new crates, which is why the Release crates workflow currently fails on ironrdp-rail. A crates.io owner must publish these manually once, in dependency order, after the bumped versions of their already-published dependencies: ironrdp-rail, ironrdp-rdpei, ironrdp-rpc, ironrdp-rdpeai, ironrdp-rdpel, ironrdp-rdpemt, ironrdp-rdpeudp, ironrdp-rdpeudp-tokio, ironrdp-usb, ironrdp-rdpeusb, ironrdp-rdpewa, ironrdp-rdpewa-native, ironrdp-vmconnect, and ironrdp-daemon (which needs the new ironrdp-client release first).

[Copilot]

🟢 Approval recommended

The focused publication metadata and documentation changes introduce no runtime changes, and no blocking issues were identified.

No open issues 🎉

What changed in this PR

Makes ironrdp-daemon and ironrdp-rpc publishable so dependent IronRDP applications can resolve them from crates.io.

Changes:

• Enables publication and declares Rust 1.94 as the minimum supported version.
• Adds initial changelogs and publication-ready documentation.
• Includes the RPC README in generated crate documentation.

File	Description
crates/​ironrdp-rpc/​src/​lib.rs	Includes README and logo in rustdoc.
crates/​ironrdp-rpc/​README.md	Removes internal-only wording.
crates/​ironrdp-rpc/​CHANGELOG.md	Adds initial release notes.
crates/​ironrdp-rpc/​Cargo.toml	Enables publication and declares minimum Rust version.
crates/​ironrdp-daemon/​README.md	Links RPC documentation through docs.rs.
crates/​ironrdp-daemon/​CHANGELOG.md	Adds initial release notes.
crates/​ironrdp-daemon/​Cargo.toml	Enables publication and declares minimum Rust version.
ARCHITECTURE.md	Updates daemon status and documents RPC.

_{Review effort: Balanced}

[Benoît Cortier (CBenoit)]

I’m updating the PR

[github-actions]

🟢 Release-metadata housekeeping PR that makes previously internal crates publishable. It removes publish = false from ironrdp-daemon, ironrdp-rpc, ironrdp-rdpeai, and ironrdp-rdpeusb (verified in head; their published dependents require this for cargo publish), adds rust-version = "1.94" consistent with the existing per-crate convention (ironrdp-rdpeai already had it), adds boilerplate CHANGELOG.md files matching the git-cliff/release-plz format and fixes the ironrdp-rdpei placeholder heading, converts sibling-crate links to docs.rs for crates.io rendering, applies the standard README-as-docs include pattern to ironrdp-rpc and ironrdp-daemon while removing the now-duplicated crate-level doc sentences, and updates ARCHITECTURE.md with an ironrdp-rpc entry. Independent inspection of all changed files in the head found no correctness, protocol, API, or maintainability issues; the manual first-publish ordering for crates.io Trusted Publishing is documented in the PR body. No findings to pub…