docs: remove stale Rust-pilot references from current source and docs

dc_bridge has been C++ since ADR-0007; comments and descriptions across the
package (headers, source files, tests, package.xml, README), dc_bringup's launch
file, ci.yaml's intro comment, and tools/e2e/Containerfile still referred to the
reverted Rust pilot ("Port of the Rust ...", "mirroring the Rust ... variants",
"dc_bridge (Rust)", rclrs/cargo/colcon-cargo/ros2_rust build-friction notes) —
noise at best, and in dc_bringup.launch.py's case actively wrong (still labeling
the C++ dc_bridge node "(Rust)" and citing "rclrs has no rclcpp_components
equivalent" as the reason it runs outside composition; replaced with the real,
current reason — dc_bridge isn't registered as an rclcpp_components plugin).

The architecture-decision history (why C++ was reverted from Rust) belongs in the
ADRs (docs/adr/0004, 0007), which already record it and are left untouched, along
with progress.txt (an append-only historical log — scrubbing "Rust" from entries
describing the Rust-to-C++ reversion would make the log describe something that
didn't happen) and the two doc/ mentions that are about unrelated things (cargo to
install the mdbook doc-site tool; a hypothetical answer about future plugin
languages in the FAQ).

Comment-only / doc-only changes; verified dc_bridge still builds clean and its 75
gtests still pass, and dc_bringup.launch.py still parses.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0155z4WEezE9gofR1zkHbMxK
Signed-off-by: David Bensoussan <d.bensoussan@proton.me>

Author: Minipada

.github/workflows/ci.yaml

@@ -1,6 +1,6 @@
 # DC 2.0 (Jazzy) CI (#249). This branch only builds the jazzy line (external Vector
-# shipper, C++ dc_bridge — the Rust pilot of ADR-0004 was reverted in ADR-0007). The
-# humble-line `industrial_ci`/Docker workflow this repo used to run doesn't apply here and
+# shipper, C++ dc_bridge). The humble-line `industrial_ci`/Docker workflow this repo used
+# to run doesn't apply here and
 # isn't carried over onto this branch (it still exists on `humble`, a separate branch/tree
 # — deleting it here doesn't touch that). This repo is moving off Docker in favor of
 # Podman (CLAUDE.md "Containers: Podman, not Docker").

dc_bridge/README.md

@@ -1,7 +1,7 @@
 # dc_bridge
 
-The Bridge (ADRs 0001/0003/0005/0006; ADR-0007 reverts the ADR-0004 Rust pilot): a C++
-(`rclcpp`) node that subscribes to `dc_interfaces/msg/StringStamped` Record topics and
+The Bridge (ADRs 0001/0003/0005/0006/0007): a C++ (`rclcpp`) node that subscribes to
+`dc_interfaces/msg/StringStamped` Record topics and
 forwards every Record to the [Vector](https://vector.dev) shipper over the Fluent Forward
 protocol. It renders Vector's configuration from ROS parameters for the blessed
 Destination set (`postgres`, `s3`, `file`, `console` — ADR-0003) and passes raw Vector
@@ -12,9 +12,8 @@ Records referencing Files get their Files uploaded to S3-compatible object stora
 `dc.files` Tag.
 
 `dc_bridge` is an ordinary `ament_cmake` C++ package. It builds with the same `rosdep
-install` + `colcon build` as every other `dc_*` package — no Rust toolchain, no
-`colcon-cargo`, no source-built message repos. See `docs/adr/0007-bridge-returns-to-cpp.md`
-for why the Rust pilot was reverted.
+install` + `colcon build` as every other `dc_*` package. See
+`docs/adr/0007-bridge-returns-to-cpp.md` for the architecture decision history.
 
 ## Layout
 

dc_bridge/include/dc_bridge/bridge_node.hpp

@@ -1,6 +1,6 @@
-// The dc_bridge ROS node (ADRs 0001/0003/0006, and ADR-0007 which reverts the Rust
-// pilot of ADR-0004): wires the ROS-independent core (Forwarder, Supervisor, Readiness,
-// ConfigRenderer) to topic subscriptions and a readiness service.
+// The dc_bridge ROS node (ADRs 0001/0003/0006/0007): wires the ROS-independent core
+// (Forwarder, Supervisor, Readiness, ConfigRenderer) to topic subscriptions and a
+// readiness service.
 //
 // Vector's own configuration is produced by dc_bridge::render (ADR-0003) from the
 // `shipper`/`destinations` parameters; this node declares those parameters, expands the

dc_bridge/include/dc_bridge/forwarder.hpp

@@ -1,7 +1,6 @@
 // Forwarder: send(record) hides Fluent Forward msgpack framing, socket lifecycle,
 // reconnection, and backpressure behind one call. The wire protocol is the interface;
-// nothing else about Vector or the transport leaks past this class. (Port of the Rust
-// dc_bridge_core::forwarder — ADR-0004 reversed by ADR-0007.)
+// nothing else about Vector or the transport leaks past this class.
 #ifndef DC_BRIDGE__FORWARDER_HPP_
 #define DC_BRIDGE__FORWARDER_HPP_
 
@@ -33,9 +32,9 @@ struct ForwarderConfig
   std::chrono::milliseconds write_timeout{ 200 };
 };
 
-/// Error categories a send() can fail with, mirroring the Rust ForwarderError variants
-/// so callers (and tests) can distinguish backpressure (retryable, connection kept)
-/// from a dropped connection / connect failure.
+/// Error categories a send() can fail with, so callers (and tests) can distinguish
+/// backpressure (retryable, connection kept) from a dropped connection / connect
+/// failure.
 enum class ForwarderErrorKind
 {
   Connect,       ///< could not establish the TCP connection

dc_bridge/include/dc_bridge/render.hpp

@@ -8,7 +8,7 @@
 // Two layers, both pure: destination_from_raw (+ the per-type from_raw builders) turns
 // the flat, stringly-typed values ROS parameters give into validated typed config (this
 // is where invalid-parameter rejection lives); render() turns already-validated typed
-// config into Vector TOML text. (Port of the Rust dc_bridge_core::render.)
+// config into Vector TOML text.
 #ifndef DC_BRIDGE__RENDER_HPP_
 #define DC_BRIDGE__RENDER_HPP_
 
@@ -112,8 +112,8 @@ struct RenderConfig
   std::vector<Destination> destinations;
 };
 
-/// Error categories mirroring the Rust RenderError variants; kind() lets tests assert
-/// the specific failure. Formatted message in what().
+/// Error categories a render() can fail with; kind() lets tests assert the specific
+/// failure. Formatted message in what().
 enum class RenderErrorKind
 {
   EmptyDataDir,

dc_bridge/include/dc_bridge/supervisor.hpp

@@ -61,8 +61,7 @@ class Supervisor
   /// Checks whether the supervised process has exited and, if so, restarts it (subject
   /// to restart_backoff). Returns true if a restart happened. A no-op returning false
   /// once stop() has been called — prevents the respawn-after-stop race a background
-  /// poll loop would otherwise hit against a concurrent stop() (see the Rust
-  /// supervisor's `stopped` field doc / regression tests).
+  /// poll loop would otherwise hit against a concurrent stop().
   bool poll_restart();
 
   /// Stops the supervised process and permanently disables future respawns from

dc_bridge/include/dc_bridge/uploader/object_store.hpp

@@ -3,8 +3,7 @@
 // low-level multipart primitives whose persistent upload id makes interrupted transfers
 // resumable. The real S3 implementation (aws-sdk-cpp) lives in src/uploader/
 // s3_object_store.cpp; an in-memory fake in the tests exercises the logic without any
-// cloud dependency — the same split the Rust design had with object_store's InMemory
-// backend, keeping the upload logic testable and aws-free.
+// cloud dependency, keeping the upload logic testable and aws-free.
 #ifndef DC_BRIDGE__UPLOADER__OBJECT_STORE_HPP_
 #define DC_BRIDGE__UPLOADER__OBJECT_STORE_HPP_
 

dc_bridge/package.xml

@@ -6,9 +6,8 @@
   <description>
     Bridge node (C++): subscribes to StringStamped Record topics and forwards them to the
     Vector shipper over the Fluent Forward protocol, rendering Vector's config from ROS
-    parameters for the blessed Destination set (ADRs 0001/0003/0006). ADR-0007 reverts
-    the ADR-0004 Rust pilot: the Bridge is plain ament_cmake C++, so it builds with
-    rosdep + colcon like every other dc_* package.
+    parameters for the blessed Destination set (ADRs 0001/0003/0006/0007). Plain
+    ament_cmake C++, so it builds with rosdep + colcon like every other dc_* package.
   </description>
   <maintainer email="d.bensoussan@proton.me">David Bensoussan</maintainer>
   <license>MPL-2.0</license>

dc_bridge/src/forwarder.cpp

@@ -20,9 +20,9 @@ namespace dc_bridge
 namespace
 {
 
-// Packs a nlohmann::json value onto a msgpack packer, mirroring the Rust
-// json_to_value: numbers keep integer/unsigned/float distinctions, everything else maps
-// 1:1. (msgpack-cxx has no built-in nlohmann::json adaptor, so we walk the tree.)
+// Packs a nlohmann::json value onto a msgpack packer: numbers keep
+// integer/unsigned/float distinctions, everything else maps 1:1. (msgpack-cxx has no
+// built-in nlohmann::json adaptor, so we walk the tree.)
 template <typename Packer>
 void pack_json(Packer& pk, const nlohmann::json& value)
 {
@@ -69,7 +69,7 @@ void pack_json(Packer& pk, const nlohmann::json& value)
 
 // The Fluent Forward wire record must be a map. A Record's JSON payload usually is one;
 // anything else (bare string/number/array) is wrapped in {"message": ...} rather than
-// dropped — matching the Rust record_to_msgpack_map.
+// dropped.
 template <typename Packer>
 void pack_record_map(Packer& pk, const nlohmann::json& payload)
 {
@@ -209,7 +209,7 @@ void Forwarder::send(const Record& record)
     if (n < 0 && (errno == EAGAIN || errno == EWOULDBLOCK))
     {
       // Peer stalled: keep the connection (it may just be slow to drain), report
-      // backpressure. Matches the Rust WouldBlock/TimedOut arm.
+      // backpressure.
       throw ForwarderError(ForwarderErrorKind::Backpressure,
                            "peer stalled: write did not complete within the configured timeout");
     }

dc_bridge/src/main.cpp

@@ -1,6 +1,5 @@
 // dc_bridge node entry point. rclcpp handles SIGINT/SIGTERM and returns from spin();
-// on_shutdown stops the supervised Vector before exit so it's never orphaned (the same
-// guarantee the Rust node's ctrlc handler provided, but native to rclcpp here).
+// on_shutdown stops the supervised Vector before exit so it's never orphaned.
 #include <memory>
 #include <rclcpp/rclcpp.hpp>