Training plan sync

[jessephus]

Problem

Sync training plans from Runna or TrainingPeaks and optionally auto-edit external training plans

Why this was deferred from the MVP

The MVP should earn trust with suggestions first instead of writing back changes into third-party systems automatically.

Proposed future approach

• Revisit only if a richer supported or acceptable unofficial integration path appears.
• Support explicit approval workflows first, then carefully introduce low-risk automation once audit trails and rollback paths are mature.

Security and privacy considerations

• Be careful with any unofficial API path; review terms and token handling before implementation.
• Avoid storing brittle scraped credentials or sessions.
• Any write-back token must be encrypted and scoped as narrowly as possible.
• Every automated change should produce an auditable record and a user-visible explanation.

Acceptance criteria

• Imported planned workouts preserve enough detail to compare structure, intensity, and intent.
• The sync path survives normal plan edits without manual repair.
• Approved plan changes can be pushed to the target system safely.
• The athlete can review exactly what changed and revert when needed.

Open questions

• Which plan source should receive edits first?
• What guardrails define a low-risk plan change versus a human-review-only change?