fix(ci): allow cargo package dry run

[RAprogramm]

Summary

• stop using path dependencies for masterror-derive/masterror-template, rely on their declared versions and override them locally via .cargo/config
• whitelist the workspace sources in include, add the config to the package payload, and bump the crate version to 0.10.4
• refresh README badges/snippets and CHANGELOG for the new release

Testing

• cargo +nightly fmt --
• cargo +1.90.0 clippy --workspace --all-targets --all-features -- -D warnings
• cargo +1.90.0 test --workspace --all-features --no-fail-fast
• cargo +1.90.0 doc --no-deps
• cargo deny check
• cargo audit --deny warnings

---

https://chatgpt.com/codex/tasks/task_e_68ce8478e99c832bbb42404d39139d0c

[chatgpt-codex-connector]

Codex Review: Here are some suggestions.

masterror/Cargo.toml

Lines 49 to 52 in 7297536

	[features]
	default = []

[P0] Switching to registry deps makes crate unparsable

The manifest now depends on masterror-derive and masterror-template solely by version, but both of those crates are still marked publish = false in their own manifests. Because .cargo/config.toml is not consulted when this package is consumed from crates.io, downstream builds will attempt to download masterror-derive 0.6.0/masterror-template 0.3.1 from the registry and fail with “no matching package found”. Unless these helper crates are actually published, this change makes masterror impossible to build for every external user.

---

Reply with @codex fix comments to fix any unresolved comments.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".