Fix generic derive output and document HexDebug secrecy

[HDauven]

Summary

• preserve generics and where clauses in Hex and HexDebug implementations
• use absolute ::core paths in generated code
• document that HexDebug exposes the complete serialized value

Closes #44

[Copilot]

Pull request overview

Updates derive-hex derives to support generic types safely, use hygienic absolute paths, and document HexDebug value exposure.

Changes:

• Preserve generics and where clauses.
• Use absolute ::core paths.
• Add generic derive tests and security documentation.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Summary
derive-hex/tests/hex_test.rs	Adds bounded generic derive coverage.
derive-hex/src/lib.rs	Updates generated implementations and documents HexDebug secrecy implications. Nit (4 votes): add the related [Unreleased] changelog entry linked to issue #44.

Suppressed comments (1)

derive-hex/src/lib.rs:61

• This warning is only in the proc-macro item's rustdoc, while the published derive-hex documentation is sourced from README.md and the dusk-bytes README also documents HexDebug without this warning. Please add the secrecy guidance to the user-facing README documentation so users following the package examples see it.

/// Do not derive `HexDebug` for types containing secrets. Formatting such a
/// value exposes its complete serialized representation.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.