Regenerate: department VLANs tagged on all 42 field switch uplinks

Per user: Device.tenant dictates department. Set the one switch missing a
tenant (bs-cr13-sw01 -> AMI), then tagged each FS.com IES3110-8TFP-R
switch's SFP uplink(s) with its department VLAN, alongside the existing
214 (Switch Management) native VLAN:

  AMI -> 203, Security -> 209, Gas/Water/Waste Water -> 215 (Gas and
  Water, per user), Electric -> 217

63 interfaces updated, 0 skipped. Connector labels now show both, e.g.
'10 · V214+215T ↔ 2'.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NM3nivbufxEWiKKmatEtEe

README.md

@@ -44,9 +44,21 @@ Current convention (documented in NetBox, not hardcoded anywhere in these
 scripts): every FS.com `IES3110-8TFP-R` field switch trunks VLAN 214
 (Switch Management) as the native/untagged VLAN on both its SFP uplink
 ports (named `9`/`10` or `Gi1/9`/`Gi1/10` depending on the device), tagged
-alongside whatever department VLAN (AMI/Gas and Water/Electric/...) that
-switch belongs to. Department-VLAN tagging isn't populated yet -- it needs
-a real per-switch/site mapping, not a guess.
+alongside whatever department VLAN that switch belongs to -- derived from
+the device's NetBox **Tenant** (`AMI`/`Electric`/`Gas`/`Water`/`Waste
+Water`/`Security`), not stored on the interface directly:
+
+| Tenant | VLAN |
+| --- | --- |
+| AMI | 203 |
+| Security | 209 |
+| Gas, Water, Waste Water | 215 (Gas and Water) |
+| Electric | 217 |
+
+That mapping lives only in whoever ran the one-off assignment script, not
+in `export_topology.py` -- if a new switch's Tenant changes, its tagged
+VLAN has to be re-assigned in NetBox to match; the diagram just reads
+whatever `interface.tagged_vlans` already says.
 
 Connectors in the `.drawio` file are glued by shape id (draw.io's native
 `source`/`target` reference on each edge) -- drag a switch or panel in the