[Existing app][Changelog Panel] Trim render work and loading latency

[kryputh]

Summary

Improve the existing Changelog Panel surface. This issue is intentionally scoped to existing app code and should not introduce a new standalone tool or unrelated feature.

Current area

changelog entries, panel visibility, read state, release grouping, and user-facing change summaries

Relevant paths

• src/features/changelog/ChangelogPanel.tsx
• src/features/changelog/useChangelog.ts
• src/features/changelog/data.ts

Goal

make the existing changelog panel useful for release comprehension and contributor handoff.

Work focus

Reduce unnecessary render work and perceived latency in the current implementation. Prefer memoization, derived data cleanup, smaller loops, and loading skeleton improvements over broad rewrites.

Acceptance criteria

• Identify the current render or data-flow hotspot before changing code.
• Avoid broad refactors; keep the optimization scoped to the listed paths.
• No visible regression in empty, loading, populated, and error states.
• Add a short PR note describing the measured or reasoned performance win.

Scope guardrails

• Keep the work inside the relevant existing app/module paths above unless a small shared helper is clearly justified.
• Do not add a new V1/V2 tool folder for this issue.
• Do not use real user data, secrets, private keys, or live customer mail.
• Keep copy and UI aligned with the Stealth Mail safety, speed, and sender-control positioning.

Suggested validation

• Run the most relevant unit or e2e tests for the touched area.
• Run �un x tsc --noEmit and �un run lint when the local environment supports the project dependency install.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.

[Johnsource-hub]

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

[nelly439]

I’ll take this on. I’ll first identify the current render/data-flow hotspots in ChangelogPanel.tsx and useChangelog.ts, then apply tightly scoped optimizations (memoization, derived state cleanup, and reduced re-computation in grouping/read-state logic). I’ll also improve loading skeleton behavior where needed to reduce perceived latency, without changing the existing UI contract. All changes will stay within the src/features/changelog/* boundary, with no architectural or feature expansion. A short PR note will be included summarizing the measured or reasoned performance improvement.

[grantfox-oss]

🦊 GrantFox — @Johnsource-hub has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #998)
2. Your PR will be reviewed by the Stellar-Mail maintainers

Good luck! Track your progress on GrantFox.