[WIP] Fix inconsistent terminology for the TUI - #528
Conversation
Agent-Logs-Url: https://github.com/AISecurityLab/hackagent/sessions/a9d77e06-8cce-42c6-855d-c2a2e49a9036 Co-authored-by: franconicola <51865029+franconicola@users.noreply.github.com>
Agent-Logs-Url: https://github.com/AISecurityLab/hackagent/sessions/a9d77e06-8cce-42c6-855d-c2a2e49a9036 Co-authored-by: franconicola <51865029+franconicola@users.noreply.github.com>
Agent-Logs-Url: https://github.com/AISecurityLab/hackagent/sessions/a9d77e06-8cce-42c6-855d-c2a2e49a9036 Co-authored-by: franconicola <51865029+franconicola@users.noreply.github.com>
AttacksTab's stylesheet now references $brand-* variables that are only registered via HackAgentTUI.get_css_variables(). The integration tests mounted AttacksTab under a bare textual.app.App, which left those variables unresolved and crashed every test in this file.
800cb5b to
755750d
Compare
|
@claude[agent] resolve the merge conflicts in this pull request |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
main split hackagent/cli/tui/views/attacks.py and views/results.py into
packages while this branch modified the monolithic modules. The branch's
terminology, colour and attack-config changes are re-applied to the new
layout: theme-driven outcome/run-state vocabulary in results/{table,tab,
details}.py and results/formatters/{summaries,traces,run_report}.py, and
the attack config wording plus escalate default in attacks/{layout,runner,
tab}.py. The new snapshot host apps now expose the brand CSS variables.
Co-authored-by: franconicola <51865029+franconicola@users.noreply.github.com>
Resolved in c74d7c6.
The new snapshot host apps also needed Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.