v0.1.19

Move history/job data off the USB boot device onto the storage pool

MOS boots from a USB drive into RAM and only writes back to that same USB
for things meant to persist across reboots - limited write endurance,
meant for occasional config writes, not history.json (rewritten on every
single analysis, and now holds full embedded results, making it bigger
than before) or the jobs/ directory (several small files per analysis,
pruned on every -start call).

All five scripts (ai-template-maker-analyze, -history, -analyze-start,
-analyze-status, -analyze-cancel) now resolve their data directory
against /boot/config/docker.json's .appdata - the same real storage-pool
location ai-template-maker-analyze's own remap_appdata_paths() already
resolves docker host paths against - falling back to the boot-resident
plugin directory only if no pool is configured yet. settings.json stays
on the boot device, since MOS's own plugin settings API controls that
path directly and it's only written on an explicit Save, not per
analysis.

Verified the resolution logic against three cases: pool configured, no
pool configured, and docker.json missing entirely (first boot) - all
resolve correctly, with the last two falling back safely rather than
erroring.

Note: existing history.json entries from before this change live at the
old boot-resident path and won't carry over - a clean cutover rather than
a migration, given this is still pre-1.0 with a small deployment.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>