TUI: endpoint tab UX improvements - remote filter, colors, layout

[davsclaus]

Summary

• Endpoint flow panel and mirrored sparkline now respect the remote on/off toggle: two parallel sliding window histories (all vs remote-only) are maintained and selected at render time; flow totals are filtered accordingly
• Replace dark Color.BLUE with Color.CYAN throughout the endpoints tab (DIR out arrow, flow panel, chart legend, MirroredSparkline) and in the routes diagram (to/toD/wireTap/enrich/pollEnrich nodes) for visibility on dark/black terminals
• Use bright green for in-traffic: throughput chart bars and legend, endpoint DIR in arrow, flow panel in-arrow and legend, MirroredSparkline top bars
• Integration name box in the flow diagram coloured yellow bold
• Flow diagram in/out direction arrows and labels always shown in their direction colour regardless of traffic level; only count numbers dim when zero
• in/out labels centred within their fixed-width slot so they no longer shift when counts change length or the remote toggle changes totals

Test plan

• Toggle remote on/off and verify flow panel counts and chart bars update to reflect only remote endpoints
• Verify in arrow and label are bright green, out arrow and label are cyan, always visible
• Verify in/out labels stay centred and do not shift when toggling remote or as message counts change
• Open Routes tab and verify to/toD nodes in the diagram are now cyan instead of dark blue
• Verify throughput chart bars are bright green on dark terminal

Claude Code on behalf of Claus Ibsen

🤖 Generated with Claude Code

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• dsl/camel-jbang/camel-jbang-plugin-tui

All tested modules (2 modules)

• Camel :: JBang :: Plugin :: TUI
• Camel :: Launcher :: Container

---

⚙️ View full build and test results