Preconditions

Robot turned on and connected

Steps

1. Start the container
2. Print of the live snapshot: aru config
3. Compare with the previews uid snape : aru config diff
4. Save the config : aru config save ## this will renamed/backed up the existing one _config.yaml.old

Expected

Every Elecstack and Top module present on the robot has its UID recorded for this run, so the hardware configuration under test is identifiable after the fact.

Notes

• Purpose: run at the start of every CIT so each campaign is traceable to the exact

modules fitted at the time. A later failure can then be tied to the hardware that was actually on the robot, and a module swapped between sprints becomes visible.

• Tagged preflight so it runs first and is picked up by the Sanity campaign.
• Automation approach (planned): TBD — the UIDs are read per module; whether they are

exposed over gRPC (which would make this a nio/SDK handle) is not yet established.

• Reason / caveat: Stays No for now. This is a data-capture step, not a pass/fail

check — the verdict is "were the UIDs recorded", which an operator confirms.

• if at step 4 aru config save; folder not present / not writable (save failed: [Errno 2] No such file or directory: '/etc/aru/host/_config/_config.yaml')

-do on the host, run as root: mkdir -p /data/aru_shared/_config chown 1000:1000 /data/aru_shared/_config