0.8.0-dev6: sanitize whitespace in NATS subject target parts

[stevenca]

Summary

Hot-fix to dev5. Caught within ~30 seconds of the dev5 deploy on cpn-ful-netcortex1:

snmp.link_state.publish_failed device=cpn-arlington-ms1 interface=Port 3
  error=sensory subject target part 0='cpn-arlington-ms1|Port 3'
  contains whitespace; NATS subjects must be whitespace-free

Meraki MS switches expose interface names like `"Port 3"`, `"Port 4"` with literal spaces. NATS subjects forbid whitespace, so the publisher's validator (correctly) rejected every such event — dropping link-state events for every Meraki MS port on every poll cycle.

Fix

Collapse any whitespace run in each target part to a single `_` at the `SensoryPublisher` boundary. Every future publisher (Meraki webhook in next dev cycle, SNMP traps, gNMI dial-out) inherits the behavior automatically.

• Subject token: `Port_3`
• Payload `interface` field: `"Port 3"` (original preserved)

Dots in target parts remain a hard error — they are the NATS token separator and silently splitting would mask a programmer bug.

Test plan

• CI: all 8 jobs pass
• Deploy to cpn-ful-netcortex1
• Within one SNMP poll cycle, verify `snmp.link_state.publish_failed` warnings stop and (if any Meraki MS ports are down) `:ReflexEvent` nodes appear in Neo4j with subjects like `sensory.link_down.snmp_poll.cpn-arlington-ms1|Port_3`

Made with Cursor