[Audit] Overlapping stream-detail fetches on rapid SSE bursts can apply stale data

[K1NGD4VID]

Filed from the second-wave repository audit (issue 10/100). See the audit summary for full category context.

• Location: frontend/src/app/streams/[id]/stream-details-content.tsx:141-153
• Problem: The refresh effect re-fires on every streamEvents update and creates a new AbortController each time, but nothing prevents an older, slower in-flight fetch from resolving after and overwriting a newer one — the abort signal only covers unmount, not overlap within the same mount.
• Evidence: Fresh AbortController per SSE event with no request-generation/sequence guard.
• Suggested implementation: Track a monotonically increasing request id (or abort the previous controller before starting a new fetch) and ignore responses that don't match the latest id.
• Acceptance criteria: A test firing two SSE events in quick succession with reversed response latencies ends on the data from the later event.
• Difficulty: M
• Expected impact: Prevents the stream detail view from regressing to stale amounts/status during bursts of activity.

[Agbasimere]

Can I work on this?

[Peolite001]

@Peolite001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Peolite001 to this issue.

[akinerin]

@akinerin has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would love to work on this issue, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @akinerin to this issue.

[GOE001]

@GOE001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

i would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GOE001 to this issue.

[meem08]

@meem08 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @meem08 to this issue.

[iyanukid2008-pixel]

@iyanukid2008-pixel has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

After a thorough review, this issue falls under my speciality, and I'll like to be assigned to solve the issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @iyanukid2008-pixel to this issue.

[ToryMic]

@ToryMic has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hey, I've checked your issue and I can work on it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ToryMic to this issue.

[drips-wave]

Congratulations, @Peolite001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Peolite001: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Peolite001's PR #1353 was approved and merged by @K1NGD4VID.

🏆 @Peolite001: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,200 total points). Track your full progress on GrantFox.

👏 Great work, @Peolite001! Keep contributing to LabsCrypt.