# Changelog All notable changes are documented here. ## [Unreleased] ## [0.1.14] - 2026-09-21 ### Fixed - `ros_launch_analyze`/`ros_launch_validate` now extract the include path from `PythonLaunchDescriptionSource('…')` and the other `*LaunchDescriptionSource` wrappers. The common `IncludeLaunchDescription(PythonLaunchDescriptionSource('child.launch.py'))` nests the path one call deeper than `IncludeLaunchDescription('…')`, so it was reported as `includes: []` and a missing included launch file went undetected. A path computed with `PathJoinSubstitution`/`FindPackageShare` is still not a string literal and stays unextracted rather than being guessed. ## [0.1.13] - 2026-09-21 ### Fixed - `ros_build`, `ros_test`, `ros_validation_bundle`, `ros_environment`, and `ros_tdd_checkpoint` now accept an optional `path` and resolve the workspace / git repository from it instead of only from `ctx.cwd`. Without it, a workspace reached through `path` while the session ran elsewhere reported `WORKSPACE_NOT_FOUND` or discovered the wrong tree. ## [0.1.12] - 2026-09-21 ### Changed - Adopt `pi-helper-core` (`^0.1.1`) for the shared response envelope, bounded command runner, TDD checkpoint, and completion-evidence gate. `src/core/result.ts` and `src/core/runner.ts` are now thin shims and the gates supply only ROS signals and labels. - **Breaking:** every tool response now carries `attention` (`true` when the caller must act), matching the other helpers. The unused `metadata.rosDistro` field is removed. ### Added - `test/core-dependency.test.ts` pins the `pi-helper-core` dependency and the shared behaviours the ROS gates delegate to. ## [0.1.11] - 2026-09-20 ### Changed - Modularized `extensions/index.ts` by extracting all 34 tools into domain-specific modules under `src/tools/` and `src/commands/`. - Created `src/tools/index.ts` central tool aggregator providing `registerAllTools` and individual module registrars for independent testing and reuse. ## [0.1.10] - 2026-09-20 ### Fixed - `ros_test`: Scope JUnit test result collection to specified `testTargets`, preventing unrelated test binary results from polluting the failure summary. ### Added - `ros_validation_bundle`: Support `testTargets` parameter for focused CTest execution and target-scoped JUnit test result collection. ## [0.1.9] - 2026-09-20 ### Improved - `ros_test` accepts selected test targets and passes a safely escaped CTest filter for focused execution. - Colcon diagnostics recognize common gtest matcher errors as test-tooling failures with more relevant suggestions. - Dependency planning ignores generated/system/gtest/gRPC includes and package-local/ament build references to reduce false positives. ## [0.1.8] - 2026-09-20 ### Added - `ros_parameter_validate` compares declared parameter types with configuration values without mutating a running node. - `ros_launch_validate` validates included files and static launch node discovery without starting nodes. - `ros_graph_assert` checks expected versus actual nodes, topics, and services. - `ros_tdd_checkpoint` and `ros_completion_evidence` provide conservative development and completion gates. - Safety regression coverage for namespaced actuator topics, QoS semantics, and missing subprocesses. ### Fixed - Runtime graph snapshots no longer report partial command results as a complete graph. - TF diagnostics honor the requested bounded timeout. - QoS diagnostics distinguish actual incompatibilities from harmless policy differences. ## [0.1.7] - 2026-09-20 ### Added - `ros_failure_diagnose` classifies the first actionable colcon/compiler/CMake/rosidl/test failure and returns bounded suggestions. - `ros_test_select` selects likely focused test targets from changed paths without running ROS commands. - `ros_dependency_plan` compares C++ includes and CMake references with package.xml and previews dependency actions without editing files. - `ros_validation_bundle` previews or executes a bounded build-then-test sequence and returns one evidence-oriented result; previews are never reported as passes and stale artifacts fail the gate. - Unit tests covering failure diagnosis, focused test selection, dependency planning, and validation gating. ## [0.1.6] - 2026-09-20 ### Fixed - `ros_test` no longer reports a stale pass silently. `colcon test` does not rebuild, so a run could succeed against a test binary that predates the current sources. The tool now compares the compiled test binaries under `build/` with source and build files, and raises a `STALE_TEST_ARTIFACTS` warning with `staleArtifacts` details when the sources are newer. Documentation and log changes do not trigger the warning, and Python-only workspaces without compiled test binaries are left alone. ### Added - `detectStaleTestArtifacts`, a pure helper that reports the newest source and test binary when a compiled test binary is out of date. - `ros_test` now states in its description and prompt guidelines that `ros_build` must run before `ros_test` after editing sources, and the bundled `ros2-development` skill lists the same rule in its investigation order. - Regression tests for stale, fresh, Python-only, documentation-only, build-file, and build-tree staleness cases. ## [0.1.5] - 2026-09-20 ### Fixed - `ros_test` no longer labels every JUnit suite `AllTests`. It derives the test binary from the result file name, keeps the real `testsuite` name, and reports each failed case with its suite, test name, source file, and line so `ros_test` can name the failing assertion instead of returning only a generic CTest hint. - `ros_log_analyze` classifies test and build framework failures (`ctest` `***Failed`, gtest `[ FAILED ]`, pytest node ids, `CMake Error`, `AssertionError`, and `N tests failed`) as errors, and lists the failing test lines in a new `testFailures` field. A log full of gtest failures no longer reports zero errors. - `ros_build` classifies generated `.cc` and `.c++` sources and location-only diagnostics (`file:line:col: error:`) as compiler failures. - `ros_build` collapses repeated compiler warnings into the top offending file/message/flag sites with counts instead of returning the raw warning stream. ### Added - `summarizeTestResults`, `summarizeBuildWarnings`, and structured `TestCaseFailure` records in the colcon analysis module. - `ros_test` reports `testSummary` (suite, test, failure, and skipped totals) and a `failingTests` list. - `ros_scaffold_preview` accepts `kind: "node"` and emits a node that declares a parameter and drives a timer for both C++ and Python. - Regression tests for JUnit failure attribution, skipped totals, generated-source compiler classification, build warning grouping and capping, test framework log classification, the node scaffold, and extension tool registration. ## [0.1.4] - 2026-09-20 ### Fixed - `ros_workspace_inspect` now discovers a package whose `package.xml` sits at the workspace root, so single-package repositories no longer report zero packages. - `findWorkspace` treats a directory containing `package.xml` as a workspace root in addition to one containing `src`. - `ros_package_analyze` resolves an absolute path, a relative path, a `package.xml` file, or a package name, and no longer fails with `PACKAGE_NOT_FOUND` when the manifest is at the repository root. - `ros_launch_analyze` detects Python `Node(...)` actions that span multiple lines and reads XML `` attributes instead of relying on single-line matches. - `ros_scaffold_preview` now emits real ROS 2 publisher and subscriber code; previously `kind` was accepted but ignored and both kinds produced an empty node. - `ros_log_analyze` classifies a line by its ROS severity tag first, so a `[WARN]` line that merely mentions "error" is no longer counted as an error. - `ros_param_diff` reports `ok: true` when the comparison succeeds; differences are returned as data rather than as a failure. - `ros_interface_scaffold_preview` no longer copies the supplied fields into the result and feedback sections of an action definition. - Tool metadata reports the real `package.json` version instead of a hardcoded `0.1.0`. ### Added - Regression tests for single-package workspace discovery, path-based package resolution, multi-line and XML launch node detection, publisher/subscriber scaffold output, ROS severity classification, action interface sections, and tool version reporting. ## [0.1.3] - 2026-09-20 ### Fixed - `skills/ros2-development/SKILL.md` now declares the required `name` and `description` frontmatter, so pi loads the skill instead of warning `description is required` under `[Skill conflicts]`. ### Added - Regression test asserting every bundled skill declares valid frontmatter that pi can load. ## [0.1.1] - 2026-09-20 ### Added - Unit-test coverage for graph diffing, parameter diffing, colcon classification, scaffold validation, and safety rules. - Repository development guide in `AGENTS.md`. - ROS interface scaffold preview for msg, srv, and action definitions. - Prettier formatting checks. ### Changed - Test command now runs TypeScript tests through `tsx`. - CI now tests ROS 2 Humble and Jazzy container smoke cases. ## [0.1.0] - 2026-09-12 ### Added - ROS environment, workspace, package, build, and test diagnostics. - ROS graph, QoS, TF, parameter, and log diagnostics. - Launch and rosbag inspection/query tools. - Confirmed topic, service, action, and lifecycle controls. - Preview and safe-write ROS 2 package scaffolds.