feat(hosted-teleop): auto-select operator view via robot_type broker config

[ruthwikdasyam]

Contribution path

• Small, safe change that does not need a tracking issue
• Linked issue or discussion: DIM-XXX / #XXX / URL

Closes DIM-1264

Problem

• hosted-teleop operator manually picks the right view every session.
  The robot already knows its kind - the broker session should carry it so the UI opens the correct view automatically.

Solution

• Add a robot_type field to BrokerConfig, sent in the session-create POST.
• It's pinned per-blueprint on the broker transport spec so the kind is declared where the blueprint is defined
• Unset (standalone callers) omits it from the POST and the operator picks.

How to Test

dimos run teleop-hosted-go2-transport   # dashboard opens the Go2 view, no manual pick

AI assistance

Claude Code with Opus 4.8 — (design exploration, implementation). Reviewed and understood all changes
design decisions were mine

Checklist

• I have read and approved the CLA.

[codecov]

Codecov Report

❌ Patch coverage is 77.27273% with 5 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...os/protocol/pubsub/impl/webrtc/providers/broker.py	44.44%	5 Missing ⚠️

@@            Coverage Diff             @@
##             main    #3144      +/-   ##
==========================================
+ Coverage   73.33%   73.43%   +0.10%     
==========================================
  Files        1038     1050      +12     
  Lines       94300    94939     +639     
  Branches     8546     8649     +103     
==========================================
+ Hits        69154    69721     +567     
- Misses      22799    22839      +40     
- Partials     2347     2379      +32     

Flag	Coverage Δ
OS-ubuntu-24.04-arm	66.34% <70.58%> (+0.17%)	⬆️
OS-ubuntu-latest	68.89% <70.58%> (+0.15%)	⬆️
Py-3.10	68.88% <70.58%> (+0.13%)	⬆️
Py-3.11	68.88% <70.58%> (+0.15%)	⬆️
Py-3.12	68.88% <70.58%> (+0.14%)	⬆️
Py-3.13	68.87% <70.58%> (+0.13%)	⬆️
Py-3.14	68.89% <70.58%> (+0.15%)	⬆️
Py-3.14t	68.88% <70.58%> (+0.15%)	⬆️
SelfHosted-Large	30.08% <35.29%> (+0.03%)	⬆️
SelfHosted-Linux	37.03% <50.00%> (-0.05%)	⬇️
SelfHosted-macOS	35.94% <50.00%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
dimos/core/coordination/module_coordinator.py	84.42% <100.00%> (+0.02%)	⬆️
dimos/core/coordination/test_module_coordinator.py	99.55% <100.00%> (+<0.01%)	⬆️
dimos/teleop/hosted/blueprints/cloudflare.py	100.00% <100.00%> (ø)
dimos/teleop/hosted/robot_type.py	100.00% <100.00%> (ø)
...os/protocol/pubsub/impl/webrtc/providers/broker.py	36.07% <44.44%> (+0.22%)	⬆️

... and 34 files with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[greptile-apps]

Greptile Summary

This PR adds a robot_type field to BrokerConfig that is sent in the broker session-create POST, allowing the hosted-teleop UI to auto-select the correct operator view without manual intervention. It also fixes a pre-existing bug where config-field kwargs pinned on a TransportSpec were silently dropped during coordinator materialization.

• module_coordinator.py: Extracts config-field kwargs from spec.kwargs and merges them ahead of CLI/env overrides when constructing the provider config, so spec-pinned fields survive materialization.
• broker.py: Adds robot_type: str | None to BrokerConfig with custom __eq__/__hash__ (backed by model_dump()) that exclude robot_type from identity, preventing a second PeerConnection fork for blueprint transports that omit it.
• cloudflare.py / robot_type.py: Pins RobotType.GO2 / RobotType.ARM on the state_reliable spec in each hosted blueprint via a new str-mixin enum for wire-safe JSON serialization.

Confidence Score: 3/5

The core coordinator fix and RobotType enum are solid, but the broker provider-creation path has a non-deterministic ordering issue that can silently drop robot_type from the session-create POST.

If CameraMuxModule subscribes before Go2CommandModule in the same process, the provider is created without robot_type and no error is raised — the auto-select feature silently never activates.

dimos/protocol/pubsub/impl/webrtc/providers/broker.py — the provider() lookup and _create() call path needs to guarantee that a config with robot_type set wins over one without it when both compete for the same provider slot.

Important Files Changed

Filename	Overview
dimos/protocol/pubsub/impl/webrtc/providers/broker.py	Adds robot_type field to BrokerConfig and custom __eq__/__hash__ that exclude it from identity; sends field in session-create POST. The identity exclusion correctly prevents a second PeerConnection fork, but leaves which config's robot_type wins at first-call time non-deterministic.
dimos/core/coordination/module_coordinator.py	Extracts config-field kwargs from spec.kwargs and merges them (with CLI overrides winning) into the provider config at materialization time, so robot_type pinned on a spec survives the coordinator build step.
dimos/core/coordination/test_module_coordinator.py	Adds a regression test verifying that a config-field kwarg on a TransportSpec reaches the materialized transport's _config, covering the previous silent-drop bug.
dimos/teleop/hosted/blueprints/cloudflare.py	Pins robot_type=RobotType.GO2 / RobotType.ARM on the state_reliable spec in each hosted blueprint; straightforward and consistent across all four affected blueprints.
dimos/teleop/hosted/robot_type.py	New RobotType(str, Enum) with GO2 and ARM members; str mixin ensures JSON-serializable wire values and Python 3.10 compatibility.

Comments Outside Diff (1)

1. dimos/protocol/pubsub/impl/webrtc/providers/broker.py, line 86-103 (link)

   Race between no-robot_type transport and robot_type-bearing transport at provider creation

   _providers is keyed by config identity (which excludes robot_type), so the two transports for state_reliable in every Go2 blueprint — one with robot_type=RobotType.GO2 and one without — are considered equal and share a single provider. The provider is created by whichever config's .provider() is called first. If CameraMuxModule subscribes to camera_select before Go2CommandModule subscribes to state_json, BrokerConfig(robot_type=None) triggers _create(), and _connect() POSTs without robot_type. The state_json transport then retrieves the already-existing provider via the matching hash/eq, but that provider's _config.robot_type is None for the lifetime of the session — silently disabling the auto-select feature with no error.

   A concrete fix: override provider() in BrokerConfig so that if a provider already exists in the registry for this identity but was created with robot_type=None, and the incoming config has robot_type set, reassign provider._config before _connect() runs.

_{Reviews (3): Last reviewed commit: "test(hosted-teleop): drop redundant prec..." | Re-trigger Greptile}