Plan sync — keep a saved plan up to date from a URL

[jojobird6]

tl;dr - Sync plans into liftlog, mirrors backup process

I self-host my training plan on my own server. The plan changes most weeks, and right now getting each update
onto my phone is a manual loop: tap a bookmark, open the downloaded .liftlogplan, save
it, then delete the old copy so I don't end up with duplicates. It works, but it's fiddly
to do every week.

Would you be open to an optional Plan sync setting? The idea, mirroring the Automatic
Remote Backup screen: you give it a URL (plus an optional API key). When you open the app,
LiftLog checks the URL, and if the served plan file has changed it updates that one saved
plan in place instead of importing a new duplicate. If nothing changed, it does nothing.

It feels like the natural mirror of the remote backup webhook (#243): that solved getting
data out to a self-hosted server, and this is the same audience getting a plan in. Same
settings pattern, no server-side changes.

A few design choices I made:

• If the file hasn't changed, opening the app costs a single GET and nothing else happens.
• Background checks fail silently — Only an explicit "Sync now" surfaces a failure reason.
• The subscription owns one saved plan slot; your active plan and other saved plans
  are left alone.
• Deleting the synced plan gives up the subscription, so it can't silently reappear later.

I've already built a working version on my fork and I'm happy to adapt it to whatever shape
you'd want, or to trim/split it. Rough size is ~590 lines across 11 files, but ~225 of that
is tests and the rest is mostly the cloned settings screen and i18n — the core sync logic is
small, and the effect + store wiring stands alone if you'd rather review that separately
from the settings screen. It reuses the existing plan parser and save path, so there's no
new storage or schema change. Happy to share screenshots or a diff if that's helpful.

Does this sound like something you'd accept a PR for?

My fork: https://github.com/jojobird6/LiftLog

[github-actions[bot]]

Thanks for starting a discussion!

Please write in your own words. AI-generated summaries tend to be more verbose than necessary and frustrating to read.

A few things that help:

• Written in your own words, describing the problem or idea clearly.
• Written in your original language. If you're not comfortable in English, write in your own language and it can be translated if needed.
• Search existing discussions to check this hasn't already been raised.

See the Contributing guide for more.