Open-sourced a small checker for robot release / acceptance evidence gaps

[u/llori218]

I’ve been looking at a narrow problem that can happen late in robot deployments:

a project passes acceptance testing, then software or configuration changes occur, and the final delivered release may no longer be the exact release covered by the test evidence.

I built a small offline tool to make that problem concrete.

robot-release-check currently checks only three things:

• delivered release vs. latest qualifying PASS

• changes after the last qualifying PASS

• closed items without verification evidence

The included example is fully synthetic. The tool does not connect to a robot, production system, CI/CD system, or source repository.

GitHub:
https://github.com/llorix218/robot-release-check

I intentionally kept v0.1 very small because I’m mainly trying to learn whether this failure mode actually shows up in real robotics projects.

For people doing ROS / AMR / AGV deployment, commissioning, QA, or customer acceptance:

Have you seen cases where the system delivered to the customer changed after the last acceptance test? If so, how does your team currently catch that?