tui: Make verdict colors and badges more consistent across operator screens

[KaayanatSally]

Summary

This PR improves verdict consistency across the TUI operator screens.

Changes made:

Added shared render_decision_badge() helper for centralized verdict rendering
Reused shared verdict badge rendering in Events and Audit screens
Updated AI screen verdict terminology for consistency
Improved visual distinction for throttle using the purple palette color
Reduced duplicated verdict formatting logic across screens

Why

Verdict categories such as allow, flag, throttle, and block
were rendered inconsistently across different TUI views.

This change improves operator readability by ensuring verdicts use a
consistent visual language across Monitor, Events, Audit, and AI screens
without changing scoring or decision semantics.

Scope

What kind of change is this?
[ ] TUI / CLI improvement

Verification

How did you verify the change?

Commands run:

TUI verified manually during development

Notes:

• I updated screenshots if the TUI changed materially

Signal-specific notes

If this PR adds or changes a signal or a meaningful detection pattern, fill this in.

Signal type:

• not applicable

Source, reproducer, or proof:

Benign case checked:

Performance note:

TUI notes

• before/after screenshots attached

Local-only file check

I did not accidentally stage local-only files such as adiuvare.yaml or local conftest.py changes

Related issue

Closes #20
Attached screenshots show the verdict rendering consistency updates across the affected TUI screens.

[0-Shimanshu]

The idea looks good, but the PR is not ready yet because Ruff is failing.

After adding render_decision_badge(), some old variables are still left in the code but are no longer used.

Please remove the unused variables Ruff is pointing to:

• icon in adiuvare/tui/screens/ai.py
• icon, color, verdict_color in adiuvare/tui/screens/audit.py
• icon, color, verdict_color in adiuvare/tui/screens/events.py

Also add a blank line between decision_icon() and decision_label() in adiuvare/tui/workspace.py.

Once the lint check is green, this should be good to review again.

and add ss of the tui before and after since its a tui pr

[0-Shimanshu]

@KaayanatSally

[0-Shimanshu]

@KaayanatSally

[0-Shimanshu]

@KaayanatSally i wouls need to see ss of the tui screen where the changes are made not the code area that i can already see in the commit changes

[0-Shimanshu]

@KaayanatSally update?

[KaayanatSally]

Thanks for the review. I was away for a few days and just got back to this PR.
I've addressed the Ruff issues and test failures. The remaining failing check is the repository hygiene test-update requirement.
Regarding the screenshots, I currently don't have a local environment set up to capture the TUI screens. Would code-diff screenshots be sufficient for this visual-consistency change, or would you prefer that I set up the TUI locally and provide actual before/after screen captures?

[0-Shimanshu]

@KaayanatSally tui ss are required too see what changed
i suppose u would have cloned the repo offline and runned it to make those changes so you should be able to run it locally.

[KaayanatSally]

I actually made the changes through GitHub Web and didn't have a local environment set up for running the TUI, which is why I attached the code diff screenshots instead of TUI screenshots. I'll set up the project locally and capture the required TUI screenshots showing the affected screens, then update the PR.

…

On Thu, Jun 11, 2026 at 1:04 AM Shimanshu Chouhan ***@***.***> wrote: *0-Shimanshu* left a comment (0-Shimanshu/ADIUVARE#78) <#78 (comment)> @KaayanatSally <https://github.com/KaayanatSally> tui ss are required too see what changed i suppose u would have cloned the repo offline and runned it to make those changes so you should be able to run it locally. — Reply to this email directly, view it on GitHub <#78?email_source=notifications&email_token=BT6KM3HZWPRSY6XFUG76RVL47GZ53A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRXGM3TKMBVG422M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4673750575>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BT6KM3GF6LA4TYX3OQICSZL47GZ53AVCNFSNUABGKJSXA33TNF2G64TZHMYTCOJUGM4DANRSHE5US43TOVSTWNBUGYYDMMRSGMZTNILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BT6KM3D2ZUSJQDPTP4XE7O347GZ53A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRXGM3TKMBVG422M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BT6KM3F4NICJNVMAXAJLV4L47GZ53A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRXGM3TKMBVG422M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>