fix(mosaico_integration): address Mosaico review feedback

- Replace git-clone+pin SDK install with mosaicolabs>=0.4.0 from PyPI.
  Release 0.4.0 (2026-04-21) is the first wheel shipping the futures
  subpackage correctly; the earlier packaging gap that forced the pin
  is resolved upstream. Bridge image drops ~100 MB.
- Store captured_at_seconds (float) alongside captured_at_iso so
  the timestamp is range-queryable via
  QuerySequence().with_user_metadata("captured_at_seconds", gt=X).
  Mosaico metadata filters only support numeric types for range
  predicates; the ISO string stays for human-readable listing.
- Update README SDK section and troubleshooting tip accordingly.

Author: Michał Fąferek

demos/mosaico_integration/README.md

@@ -63,9 +63,9 @@ License-safe: mosaicod runs as the unmodified upstream Docker image. The bridge
 - 24/7 recording of the same four topics: ~6 GB/robot/day.
 - At ~5 confirmed faults/robot/day the catalog holds ~10 MB/robot/day.
 
-## Mosaico SDK pin
+## Mosaico SDK
 
-PR #368 (ROS adapters for the `futures` ontology) merged on 2026-04-13 as commit `b3867be`. We validated end-to-end against the PR while it was in draft; post-merge no demo-side change was required. The subsequent `mosaicolabs==0.3.2` PyPI wheel is missing the `futures` subpackage from the distributed artifact, so the bridge `Dockerfile` installs directly from the repo at `b3867be` until a packaging-fixed release ships. The notebook still needs `import mosaicolabs.models.futures.laser` at the top to register the ontology on the read side.
+The bridge and notebook both use `mosaicolabs>=0.4.0` from PyPI. Release 0.4.0 (2026-04-21) is the first wheel that includes the `futures` subpackage (`LaserScan` ontology) required by this demo. The notebook still needs `import mosaicolabs.models.futures.laser` at the top to register the ontology on the read side; Mosaico team is looking into whether a shorter top-level import will suffice in a future SDK release.
 
 ## Integration notes
 
@@ -76,7 +76,7 @@ PR #368 (ROS adapters for the `futures` ontology) merged on 2026-04-13 as commit
 
 ## Troubleshooting
 
-- `docker compose build bridge` fails the LaserScan sanity import → the pinned Mosaico commit is no longer fetchable or the source layout has moved. Update `MOSAICO_PIN` in `bridge/Dockerfile` to a current `main` commit that still contains `mosaicolabs/models/futures/laser.py`.
+- `docker compose build bridge` fails the LaserScan sanity import → the installed `mosaicolabs` wheel no longer ships the `futures.laser` module. Check the version constraint in `bridge/requirements.txt` and pin back to a known-good release.
 - Bridge logs `No entity owns bulk-data for fault X (probed N candidates)` → the post-fault timer has not fired yet. Wait a few seconds and re-trigger.
 - Notebook raises `No ontology registered with tag 'laser_scan'` → the ontology import cell was skipped; re-run it.
 - `docker compose pull mosaicod` is slow on first run → the upstream image is ~110 MB, distroless.

demos/mosaico_integration/bridge/Dockerfile

@@ -7,38 +7,18 @@
 # License-safe pattern: bridge is a separate Python process that talks
 # the public Apache Arrow Flight protocol to an unmodified mosaicod
 # Docker image. We do not link or modify mosaicod or its Rust crates.
-#
-# SDK pinning: PR #368 (ROS adapters for futures ontology, including
-# LaserScan) merged on 2026-04-13 as commit b3867be. The subsequent
-# mosaicolabs==0.3.2 PyPI wheel (2026-04-15) ships with the
-# `futures` subpackage missing from the wheel despite being in source
-# on main, so `pip install mosaicolabs==0.3.2` cannot import LaserScan.
-# We therefore install from the upstream repo at the PR #368 merge
-# commit until a PyPI release with correct packaging ships.
 
 FROM python:3.11-slim
 
 ENV PYTHONUNBUFFERED=1
 ENV PIP_NO_CACHE_DIR=1
 ENV PIP_DISABLE_PIP_VERSION_CHECK=1
 
-RUN apt-get update \
-    && apt-get install -y --no-install-recommends git ca-certificates \
-    && rm -rf /var/lib/apt/lists/*
-
-ARG MOSAICO_REPO=https://github.com/mosaico-labs/mosaico.git
-ARG MOSAICO_PIN=b3867be
-RUN git clone "${MOSAICO_REPO}" /opt/mosaico \
-    && cd /opt/mosaico \
-    && git checkout "${MOSAICO_PIN}" \
-    && git rev-parse HEAD > /opt/mosaico/.pinned_sha
-
 COPY requirements.txt /tmp/requirements.txt
-RUN pip install -r /tmp/requirements.txt \
-    && pip install /opt/mosaico/mosaico-sdk-py
+RUN pip install -r /tmp/requirements.txt
 
 # Sanity check at build time: import the SDK and the LaserScan ontology
-# so we fail fast if a future pin regresses on what we need.
+# so we fail fast if the published wheel regresses on what we need.
 RUN python -c "from mosaicolabs import MosaicoClient; from mosaicolabs.ros_bridge import RosbagInjector, ROSInjectionConfig; from mosaicolabs.models.futures.laser import LaserScan; print('mosaicolabs SDK + LaserScan ontology import OK')"
 
 WORKDIR /app

demos/mosaico_integration/bridge/bridge.py

@@ -337,6 +337,10 @@ def ingest_to_mosaico(bag_path: Path, fault: FaultEvent) -> Optional[str]:
         f"{SOURCE_DEMO}_{ROBOT_ID}_{fault.fault_code}"
         f"_{int(fault.timestamp_sec)}_{fault.event_id}"
     )
+    # captured_at_seconds is stored as float so it can be used in Mosaico
+    # QuerySequence().with_user_metadata(key, gt=X, lt=Y) range filters.
+    # captured_at_iso is kept alongside it for human-readable inspection
+    # in list_sequences() output.
     metadata = {
         "robot_id": ROBOT_ID,
         "fault_code": fault.fault_code,
@@ -345,6 +349,7 @@ def ingest_to_mosaico(bag_path: Path, fault: FaultEvent) -> Optional[str]:
         "fault_description": fault.description or "",
         "fault_status": fault.status,
         "reporting_sources": ",".join(fault.reporting_sources),
+        "captured_at_seconds": float(fault.timestamp_sec),
         "captured_at_iso": datetime.fromtimestamp(
             fault.timestamp_sec, tz=timezone.utc
         ).isoformat(),

demos/mosaico_integration/bridge/requirements.txt

@@ -1 +1,2 @@
 httpx>=0.27,<0.30
+mosaicolabs>=0.4.0,<0.5