v0.9.50-alpha — Node-RED Configurator configs survive updates

Updating your box no longer wipes the feeds you built in the Node-RED Configurator.

Configurator configs — your ArcGIS/TAK feeds, TextChat, PulsePoint, IPAWS, and TAK settings — live in Node-RED's in-memory state. A chain of flaws in the backup/restore path could erase them during an update or restart, and the emergency restore sometimes loaded nothing back. This release hardens that path end to end.

What's fixed

• Configs are backed up to disk the moment you save or delete one — not just at deploy time. A feed you create is durable immediately.
• The persistence setting is now written to the file Node-RED actually reads, and verified — so a class of boxes that were silently keeping configs only in memory (and losing them on every restart) now persist correctly.
• A restore can never replace your live feeds with an older, smaller backup. If a backup has fewer configs than what's live, the larger set is kept — older/smaller never silently wins.
• The restore screen now shows the real config counts instead of reporting success on an empty backup, so "the backup won't load" is visible instead of silent.
• CloudTAK /sw.js is served no-cache so your browser picks up new CloudTAK builds sooner. Stale "hard-refresh" guidance (which never bypassed the service worker) is replaced with the DevTools → Application → Clear site data steps that actually work.

Upgrade

Applied automatically. Configs already lost before this release can't be recovered, but anything you create or re-create now will persist through updates and restarts.