Repository navigation
Test the dashboard's own profile in an unnamed pairing's gateway name - #855
Conversation
SummaryA test-only PR adding one test to Findings[severity: minor]
|
|
Review by DeepSeek V4.1 Flash. SummaryA test-only PR adding one test to Findings[severity: minor] The new test raises
|
Review by GLM-5.3-Flash.SummaryTest-only PR covering a dashboard scoped to FindingsThe previously raised minor finding ( VerdictAPPROVE |
|
Review by DeepSeek V4.1 Flash. SummaryA test-only PR adding one test to FindingsThe previously raised minor finding (the VerdictAPPROVE |




Summary
A test-only follow-up to #854, which both reviewers approved while noting this gap. Part of issue kaishi00/hermes-conduit#2540.
The new test covers a dashboard scoped to
profiles/workwhose bot has no name. It pairs with the profile missing, empty, orcurrent, and checks that the gateway gets<host> Hermes (work)from Conduit's Pair and fromclient.default_gateway_name. With no Hermes home it falls back to<host> Hermes.No version bump, because the plugin's shipped code doesn't change.
Siblings
No mapped feature: tests only.
Testing
tests/test_pairing.py: 39 pass.Generated by Claude Code