chore: remove dead StatusMessage component

[tech-adrian]

Area
frontend/src/components/ui/StatusMessage.tsx, frontend/src/components/ui/index.ts

Problem
StatusMessage (and its inferTone helper) is exported from the ui barrel but has zero usages anywhere in frontend/src/app/** — it appears to be a superseded precursor to the current toast-based status pattern (Toast.tsx, which duplicates the same inferTone-style logic at lines 26-37). Dead, unused code with a duplicated helper is easy to accidentally diverge from the real (toast) implementation if someone edits one copy and not the other.

Proposed change
Delete StatusMessage.tsx and its barrel export if truly unused (double-check with a repo-wide search first), and consolidate inferTone-style logic into a single shared helper used by Toast.tsx.

Acceptance Criteria

• Confirmed no usages of StatusMessage anywhere in the app before deleting
• Dead component and its export removed
• Any duplicated tone-inference logic consolidated into one shared helper
• Relevant tests (just test, pnpm test, cargo test, or nargo test as applicable) pass locally and in CI
• A screenshot or short screen recording is attached to the PR showing the change working (pnpm build succeeding with the component removed) — required before this can be merged.

Open your PR against the dev branch, not main. All active development merges into dev.

Discuss this issue / coordinate work: join the DShield contributor Telegram group: https://t.me/+SiGHH24No9U2MDJk

[ebubeb683-ship-it]

Hello boss, Please assign this issue to me. i checked it out and im confident i will solve it
my eta is 4 hours

[ebubeb683-ship-it]

I have gone through the issue details and already have an approach in mind. I would appreciate being assigned to this task.

[Diggardson270]

Let me lift this burden off of you,
Looked through our UI components and noticed we are carrying unnecessary technical debt in frontend/src/components/ui/.Right now, StatusMessage.tsx is completely dead code. It has zero usages across the frontend/src/app/** directory, yet it is still being exposed through the ui barrel file.Worse, it duplicates the exact inferTone logic that our active Toast.tsx component relies on. Leaving duplicated helper logic in a dead component creates a maintenance trap where someone could easily update one copy and diverge from the actual production implementation.

Let me fight for you
ETA: 3hrs

[young-wallace]

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

[grantfox-oss]

🦊 GrantFox — @Diggardson270 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.