The DGX Spark came up with a local model on it. The panel did not know. A collector on the box and a fetch on the PC were already writing the readings down, so I added a page and a tile that read those files. The panel does not call the box. If the file is stale, the page should say so, not invent a status.
Then I wanted the switches on that page, turn the collector on or off and change how often it samples from the panel, and a separate profile for the local box so a local run is not counted against a subscription. I ran the first real local sessions from the panel under that profile.
The add-session folder dialog had been opening behind the browser, I could not see it, and the log showed the dialog had started, which is the same class of bug as the quiet watcher. The thing ran. I could not see it. The dialog was fixed the same week.
I also added a log-only check for sensitive text in the harness. It records the kind of thing it saw, not the text. It does not block and it does not redact. I want a week of measurement before a week of blocking. Wiring it so the check actually runs on each session was still a manual step at the end of the week.