Release 0.7.0: changelogs, version bump (#644)

* docs: changelogs and package metadata for the 0.7.0 release

Fill the 0.7.0 section of every package changelog from the 459 commits since
0.6.0. Thirteen packages had no entry at all; four carried a Forthcoming
section whose bullets are kept and moved under the released heading.

ros2_medkit_graph_watchdog gains its first changelog and the include that
puts it in the aggregated docs page, so all nineteen packages are now
covered there.

ros2_medkit_fault_detection dated its initial release 0.6.0, a release it
was never part of. The section moves to 0.7.0.

Three entries are operator-visible and called out as breaking: the default
rosbag storage format is mcap again, so recordings land as .mcap and the
bulk-data download filename changes with them; the x-medkit-graph health
model is at schema_version 2.0.0 with three error_reason values gone; and
the lifecycle status operationId values were pluralized, which renames the
matching methods in a generated client.

The graph watchdog package description listed seven silent-fault classes.
Five detectors are registered - qos_mismatch, orphan, node_death,
param_drift and lifecycle_expectation - and the description now names
those. GRAPH_TF_STALE and GRAPH_LATENCY_BUDGET keep their reserved codes
and are described as undelivered in the changelog, as the package README
already described them.

Running the verification generator flips seven Scripts requirements to
verified, matching the tests that already carry their @verifies tags.

* chore: bump to 0.7.0 and fix the conf.py leg of the release script

release.sh matched docs/conf.py with a double-quoted pattern while the file
uses single quotes, so bump silently left it behind and verify reported the
file as 'unknown' on every run. Both legs now accept either quote style.
Checked by reverting conf.py to 0.6.0 and re-running bump: the patched
script rewrites it, the previous one reports 'unknown -> 0.7.0' and leaves
the file at 0.6.0.

The 0.6.0 changelog of ros2_medkit_fault_manager gains the entry it never
got: that release moved the default rosbag storage format back from mcap to
sqlite3. The 0.4.0 entries in the gateway and fault_manager changelogs are
accurate for the release they sit under - the default was mcap in 0.4.0 and
0.5.0 - and are left alone.

All 19 package.xml, version.hpp, docs/conf.py, docs/pyproject.toml,
docs/Doxyfile, QUALITY_DECLARATION.md and the REST examples read 0.7.0;
'release.sh verify 0.7.0' reports all versions consistent.

* docs: correct the 0.7.0 entries a review panel found wrong
* docs: scope the fault-trigger entry to what the code registers
The routes exist on Apps only - there is no component path - and the engine
is gated on a loaded plugin as well as on fault_triggers.enabled, so the
default of true is necessary rather than sufficient. The poll interval is
floored at 50 ms and a lower value is reported.

* docs: state when the peer credential is actually presented

On a forward it is the fallback: with forward_auth enabled and a caller
credential present, the caller's token wins, so the peer keeps being told the
end user. The entry claimed the gateway credential unconditionally.

* docs: the installation page said binary packages do not exist yet

They have since 0.3.0, and the README already tells the reader to apt install
the gateway. The page now leads with the apt path and names the three packages
that genuinely are not in the index: opcua, graph_watchdog and fault_detection.

* docs: cover the OpenAPI derivation work in the 0.7.0 notes

The release branch was cut before that work merged, so the largest change in
0.7.0 had no entry at all.

Two items are breaking for a caller. An action execution now belongs to the
entity it was started on, so an execution id no longer works as a global
handle and reaching one through another entity answers 404. And GET on a
scoped docs path is readable by viewer rather than admin, because the
permission table is now derived from the route registrations rather than kept
as a literal beside them.

The rest is what the derivation buys and what changed on the wire beside it:
corrected statuses on four paths, a Location that is sent and dereferenceable,
new advertised URIs on entity detail, two added operation ids with none
renamed and no route added or removed, and a status recorder whose sweep is
driven from the served document rather than a list.

The fault manager accepts the fault_code length it advertises, and a long code
keeps its recording instead of losing it to a filename limit.

Author: bburda

QUALITY_DECLARATION.md

@@ -33,7 +33,7 @@ All packages in the repository share the same version number.
 
 ### Version Stability [1.ii]
 
-The current version is **0.6.0**.
+The current version is **0.7.0**.
 The package follows semver; the pre-1.0 version reflects that the public API may still evolve
 based on early adopter feedback, not a lack of quality infrastructure.
 The 1.0.0 release is planned after the API has been validated through pilot deployments.
@@ -240,7 +240,7 @@ Security issues can be reported via GitHub Security Advisories on the
 
 | Requirement | Status | Notes |
 |---|---|---|
-| Version policy | Met | Semver, all packages at 0.6.0 |
+| Version policy | Met | Semver, all packages at 0.7.0 |
 | Stable version (>=1.0.0) | Caveat | Pre-1.0; API versioned, 1.0.0 planned post-pilot |
 | Change requests | Met | All changes via PR |
 | CI | Met | Build + test + coverage on every PR |
@@ -252,6 +252,6 @@ Security issues can be reported via GitHub Security Advisories on the
 | Platform support | Met | Ubuntu Noble / ROS 2 Jazzy + Ubuntu Jammy / ROS 2 Humble + Ubuntu Resolute / ROS 2 Lyrical |
 | Security policy | Met | REP-2006 compliant |
 
-**Caveat:** Version is 0.6.0 (pre-1.0.0, requirement 1.ii). The REST API is versioned (`/api/v1/`)
+**Caveat:** Version is 0.7.0 (pre-1.0.0, requirement 1.ii). The REST API is versioned (`/api/v1/`)
 and the package meets all other Level 3 requirements. The 1.0.0 release is planned after
 API validation through pilot deployments.

docs/Doxyfile

@@ -2,7 +2,7 @@
 # Used by Breathe extension to integrate with Sphinx
 
 PROJECT_NAME           = "ros2_medkit"
-PROJECT_NUMBER         = "0.6.0"
+PROJECT_NUMBER         = "0.7.0"
 PROJECT_BRIEF          = "SOVD Gateway for ROS 2"
 
 # Input settings

docs/api/rest.rst

@@ -72,7 +72,7 @@ Server Capabilities
 
       {
         "name": "ROS 2 Medkit Gateway",
-        "version": "0.6.0",
+        "version": "0.7.0",
         "api_base": "/api/v1",
         "endpoints": [
           "GET /api/v1/health",
@@ -126,7 +126,7 @@ Server Capabilities
             "version": "1.0.0",
             "base_uri": "/api/v1",
             "vendor_info": {
-              "version": "0.6.0",
+              "version": "0.7.0",
               "name": "ros2_medkit"
             }
           }

docs/changelog.rst

@@ -38,6 +38,8 @@ This page aggregates changelogs from all ros2_medkit packages.
 
 .. include:: ../src/ros2_medkit_plugins/ros2_medkit_graph_provider/CHANGELOG.rst
 
+.. include:: ../src/ros2_medkit_plugins/ros2_medkit_graph_watchdog/CHANGELOG.rst
+
 .. include:: ../src/ros2_medkit_plugins/ros2_medkit_opcua/CHANGELOG.rst
 
 .. include:: ../src/ros2_medkit_plugins/ros2_medkit_sovd_service_interface/CHANGELOG.rst

docs/conf.py

@@ -42,8 +42,8 @@
 project_copyright = f'{datetime.now().year}, selfpatch'
 author = 'selfpatch Team'
 
-version = '0.6.0'
-release = '0.6.0'
+version = '0.7.0'
+release = '0.7.0'
 
 # -- General configuration ---------------------------------------------------
 # https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration

docs/installation.rst

@@ -41,10 +41,24 @@ for your distribution:
    vendored copy as a fallback - no manual installation is needed. The build system
    automatically uses the vendored header when the system package is insufficient.
 
+Installation from Binary Packages
+---------------------------------
+
+ros2_medkit is in the ROS index, so most packages install with ``apt``:
+
+.. code-block:: bash
+
+   sudo apt install ros-jazzy-ros2-medkit-gateway   # or ros-humble- / ros-lyrical-
+   ros2 launch ros2_medkit_gateway bringup.launch.py
+
+``ros2_medkit_opcua`` is the one package not distributed this way; it is waiting
+on open62541pp being vendored and has to be built from source.
+
 Installation from Source
 ------------------------
 
-ros2_medkit is currently distributed as source code. Binary packages will be available in future releases.
+Build from source to get every package, to run against an unreleased version, or
+to develop against the tree.
 
 1. **Create a workspace**
 

docs/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ros2-medkit-docs"
-version = "0.6.0"
+version = "0.7.0"
 description = "Documentation for ROS 2 Medkit"
 authors = [{ name = "bburda", email = "bartoszburda93@gmail.com" }]
 requires-python = ">=3.12"

docs/requirements/specs/scripts.rst

@@ -3,49 +3,49 @@ Scripts
 
 .. req:: POST /{entity}/scripts
    :id: REQ_INTEROP_040
-   :status: open
+   :status: verified
    :tags: Scripts
 
    The endpoint shall upload a new diagnostic script or test script to the addressed entity.
 
 .. req:: GET /{entity}/scripts
    :id: REQ_INTEROP_041
-   :status: open
+   :status: verified
    :tags: Scripts
 
    The endpoint shall list all scripts stored on the addressed entity.
 
 .. req:: GET /{entity}/scripts/{id}
    :id: REQ_INTEROP_042
-   :status: open
+   :status: verified
    :tags: Scripts
 
    The endpoint shall return metadata and content information for the addressed script.
 
 .. req:: DELETE /{entity}/scripts/{id}
    :id: REQ_INTEROP_043
-   :status: open
+   :status: verified
    :tags: Scripts
 
    The endpoint shall delete the addressed script from the entity.
 
 .. req:: POST /{entity}/scripts/{id}/executions
    :id: REQ_INTEROP_044
-   :status: open
+   :status: verified
    :tags: Scripts
 
    The endpoint shall start an execution of the addressed script on the entity.
 
 .. req:: GET /{entity}/scripts/{id}/executions/{exec-id}
    :id: REQ_INTEROP_046
-   :status: open
+   :status: verified
    :tags: Scripts
 
    The endpoint shall return status and results for the addressed script execution.
 
 .. req:: PUT /{entity}/scripts/{id}/executions/{exec-id}
    :id: REQ_INTEROP_047
-   :status: open
+   :status: verified
    :tags: Scripts
 
    The endpoint shall control or modify the addressed script execution, if supported.

scripts/release.sh

@@ -37,6 +37,13 @@ DOXYFILE="${REPO_ROOT}/docs/Doxyfile"
 QUALITY_DECL="${REPO_ROOT}/QUALITY_DECLARATION.md"
 REST_RST="${REPO_ROOT}/docs/api/rest.rst"
 
+# Read one assignment out of docs/conf.py. Accepts either quote style and any
+# spacing around "="; the value is anchored to the closing quote so a suffixed
+# version is returned whole rather than truncated to its numeric prefix.
+conf_py_field() {
+    grep -oP "^[[:space:]]*$1[[:space:]]*=[[:space:]]*[\"']\\K[^\"']*(?=[\"'][[:space:]]*\$)" "$CONF_PY" | head -1
+}
+
 usage() {
     echo "Usage: $0 {bump <version>|verify [<version>]}"
     echo ""
@@ -98,9 +105,15 @@ cmd_bump() {
     # Update docs/conf.py version and release
     if [ -f "$CONF_PY" ]; then
         local old_conf
-        old_conf=$(grep -oP '^version = "\K[0-9]+\.[0-9]+\.[0-9]+' "$CONF_PY" || echo "unknown")
-        sed -i "s|^version = \"[0-9]\+\.[0-9]\+\.[0-9]\+\"|version = \"${target_version}\"|" "$CONF_PY"
-        sed -i "s|^release = \"[0-9]\+\.[0-9]\+\.[0-9]\+\"|release = \"${target_version}\"|" "$CONF_PY"
+        old_conf=$(conf_py_field version || echo "unknown")
+        sed -i -E "s|^([[:space:]]*version[[:space:]]*=[[:space:]]*)[\"'][^\"']*[\"']|\\1'${target_version}'|" "$CONF_PY"
+        sed -i -E "s|^([[:space:]]*release[[:space:]]*=[[:space:]]*)[\"'][^\"']*[\"']|\\1'${target_version}'|" "$CONF_PY"
+        # sed exits 0 whether or not it substituted, so confirm the rewrite landed
+        # rather than reporting a bump the file never received.
+        if [ "$(conf_py_field version)" != "${target_version}" ] || [ "$(conf_py_field release)" != "${target_version}" ]; then
+            echo "  ERROR: docs/conf.py was not rewritten to ${target_version}" >&2
+            return 1
+        fi
         echo "  docs/conf.py: ${old_conf} -> ${target_version}"
     fi
 
@@ -187,10 +200,14 @@ cmd_verify() {
 
     # Check docs/conf.py
     if [ -f "$CONF_PY" ]; then
-        local conf_version
-        conf_version=$(grep -oP '^version = "\K[0-9]+\.[0-9]+\.[0-9]+' "$CONF_PY" || echo "unknown")
+        local conf_version conf_release
+        conf_version=$(conf_py_field version || echo "unknown")
+        conf_release=$(conf_py_field release || echo "unknown")
         if [ -n "$expected_version" ] && [ "$conf_version" != "$expected_version" ]; then
-            echo "  MISMATCH: docs/conf.py is ${conf_version}, expected ${expected_version}"
+            echo "  MISMATCH: docs/conf.py version is ${conf_version}, expected ${expected_version}"
+            all_ok=false
+        elif [ "$conf_release" != "$conf_version" ]; then
+            echo "  MISMATCH: docs/conf.py release is ${conf_release}, version is ${conf_version}"
             all_ok=false
         else
             echo "  OK: docs/conf.py = ${conf_version}"

src/ros2_medkit_action_status_bridge/CHANGELOG.rst

@@ -2,6 +2,13 @@
 Changelog for package ros2_medkit_action_status_bridge
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
+0.7.0 (2026-08-27)
+------------------
+* A deferred fault report is retried instead of dropped, and delivered promptly through a fast retry timer rather than waiting for the next ordinary cycle (`#472 <https://github.com/selfpatch/ros2_medkit/pull/472>`_)
+* Silent parameter coercion is closed off, including a NaN that passed a ``FloatingPointRange`` descriptor and two integer narrowing paths where an out-of-range value wrapped back into the legal band before its own check ran. A value the node refuses or corrects is now reported rather than applied quietly (`#607 <https://github.com/selfpatch/ros2_medkit/pull/607>`_)
+* Build and test only: the package is instrumented for coverage (`#582 <https://github.com/selfpatch/ros2_medkit/pull/582>`_), every integration launch test runs on its own DDS domain taken at run time (`#551 <https://github.com/selfpatch/ros2_medkit/pull/551>`_, `#597 <https://github.com/selfpatch/ros2_medkit/pull/597>`_), and the suite synchronises on bridge discovery before raising a fault instead of assuming the graph has settled (`#504 <https://github.com/selfpatch/ros2_medkit/pull/504>`_)
+* Contributors: @bburda, @mfaferek93
+
 0.6.0 (2026-06-22)
 ------------------
 * Initial release: generic action-status bridge. Watches every