hermes-agent/tests/gateway/relay
Ben Barclay d8cd7ac2e7
fix(relay): declare explicit relevance policy when require_mention is configured false (#69816)
Companion to gateway-gateway#160 (connector absent-row default flips to
mention-gated / requireAddress=true).

relay_relevance_policy() previously returned None whenever the projected
policy was all-falsy, on the premise that 'the connector's quiet default
already matches'. Once the connector defaults requireAddress to true,
that premise inverts for one case: an agent EXPLICITLY configured with
require_mention: false would stay silent and get mention-gated anyway,
with no way out.

The nothing-to-declare check now keys on 'require_mention is unset'
rather than 'require_mention is falsy': an explicit false IS a
configured knob and is declared to the connector; a genuinely
unconfigured platform still declares nothing and inherits the
connector's default. No wire/contract change.
2026-07-23 13:57:57 +10:00
..
__init__.py
stub_connector.py
test_auth.py
test_channel_context_consume.py
test_contract_doc_conformance.py
test_descriptor.py
test_descriptor_from_entry.py
test_identity_token_resolver.py
test_no_stub_leak.py
test_relay_adapter.py
test_relay_follow_up.py
test_relay_going_idle.py
test_relay_interrupt.py
test_relay_multiplatform.py
test_relay_passthrough.py
test_relay_policy_send.py fix(relay): declare explicit relevance policy when require_mention is configured false (#69816) 2026-07-23 13:57:57 +10:00
test_relay_registration.py
test_relay_roundtrip.py
test_relay_roundtrip_telegram.py
test_relay_sheds_crypto.py
test_self_provision.py
test_ws_transport.py