Add a wallet rotation dry-run report artifact

[robertocarlous]

Why
The repo already has wallet rotation scripts, but operators benefit from a durable report that shows what would change before a real rotation is executed.

Acceptance criteria

• Generate a human-readable dry-run summary.
• Include impacted wallets, validation status, and next-step instructions.
• Keep the report safe to store in logs or CI artifacts.

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Tobi-8]

Hey maintainer, i have looked through your description, and i have had experience in this type of issue.
kindly assign

[femiolutayo]

I want to apply for this issue because operational safety and transparency are critical when managing wallet rotations in production systems. With my experience working on backend tooling, automation, and system reliability, I can implement a clear dry-run reporting mechanism that summarizes impacted wallets, validates rotation readiness, provides actionable next steps, and ensures no sensitive information is exposed so the report can be safely stored in logs, CI artifacts, and operational records.

[Ebenezer199914]

can i work on this

[Elizabeth-dev270]

I enjoy solving software problems and have experience in backend development, APIs, OOP, and scalable application design.