feat: expose Q10 current cleaning room

[hCoureau]

Summary

• infer the currently cleaned room from the live robot position and segmented map grid
• use conservative exact-cell and nearby-cell matching with explicit boundary handling
• expose room state only during an active cleaning session and clear stale session state
• preserve custom room labels while keeping diagnostics redacted

Important

Depends on #938, #937 and #936; #933 has merged. This branch includes the updated read-only stack and current main, preserving the 30-second CLI timeout. Merge after #938.

Design against the #933 review priorities

• End-user API: map.current_room returns the existing typed Q10Room or None; it does not add a second room model or expose inference details to callers.
• Trait lifecycle: the value is available only in active/paused cleaning states with a fresh live trace. Inactive or docked updates clear freshness so a previous session cannot leak into a later one.
• Parser boundary: session validity remains in the trait, while the pure spatial resolver consumes typed map/trace models and returns a defensive room copy. No raw packet data crosses the boundary.
• Parser internals: the exact segmented grid cell wins; the bounded nearby-cell fallback returns None on room ambiguity or unusable calibration.

Validation

• 1051 passed, including 92 snapshot tests
• all pre-commit hooks passed
• package build passed

The behavior was also exercised against a physical Roborock Q10 S5. No private map captures, room labels, or account data are included.

Related work

• Depends on feat: render Q10 map obstacle markers #938, feat: expose Q10 map archives #937, feat: parse Q10 archived map packets #936
• Tracks the read-only map work in Add Missing Q10 Feature support #767

AI assistance disclosure

This contribution was prepared with OpenAI Codex assistance. I reviewed the submitted changes and test results and take responsibility for the contribution.

Latest maintenance validation

• Updated against upstream main at f58dfb2.
• uv run pytest -q: 1069 passed, including 92 snapshots.
• uv run pre-commit run --all-files: passed.
• uv build: sdist and wheel passed.
• Maintenance and review fixes prepared with OpenAI Codex assistance; no new physical-device validation was performed for this update.

[lboue]

Tested against a real device: Roborock Q10 S5+ (ss07 firmware family), on commit cd2621d (this PR's isolated commit, rebased onto its stacked dependencies).

Watched device.b01_q10_properties.map.current_room live via add_update_listener while running a targeted clean:

{"time": "13:16:10", "state": null,            "room_id": null, "room_name": null,        "position": null}
{"time": "13:16:11", "state": "SWEEP_AND_MOP",  "room_id": null, "room_name": null,        "position": {"x": -976, "y": -888}}
{"time": "13:16:11", "state": "SWEEP_AND_MOP",  "room_id": 3,    "room_name": "Salle d’eau","position": {"x": -976, "y": -888}}
...
{"time": "13:18:26", "state": "RETURNING_HOME", "room_id": null, "room_name": null,        "position": {"x": -412, "y": -508}}
{"time": "13:20:03", "state": "EMPTYING_THE_BIN","room_id": null,"room_name": null,        "position": null}

Observations:

• current_room correctly reflects a custom room label (Salle d’eau, French for "bathroom") rather than a raw firmware rr_... default - matches the "preserve custom room labels" goal.
• It's briefly None right after the position/state first arrive (before the first segmented-grid match resolves), then locks onto the right room.
• It correctly clears back to None as soon as the state moves to RETURNING_HOME / EMPTYING_THE_BIN, confirming stale session state doesn't leak into docking/post-clean states.

This was a single-room spot clean, so I didn't get to observe a room-to-room transition in this pass.