resilio-app: Skill for Codex

Synchronize approved running workouts

Operate non-interactively on exact applied-week authority. Never generate, revise, approve, or repair workout content. Weekly application is run-only by contract; if non-running content reaches this boundary, stop on invalid upstream state instead of filtering it. The athlete chooses a workout from the watch list; this procedure never schedules or starts a workout on the watch.

Preconditions

Read the athlete-confirmed automation policy and current provider capability:

poetry run resilio workout config
poetry run resilio workout capabilities --sport run
poetry run resilio plan week --week <WEEK_NUMBER>
poetry run resilio approvals status

Require an approved plan, a consumed exact weekly approval, and an active applied-week audit. Every future run must contain a typed structured_workout. Date-only runs are valid and use provider local midnight without claiming that midnight was athlete-approved.

Interpret capabilities precisely:

• targetless runs need no threshold pace;
• percent-LTHR targets require Run LTHR;
• percent-max-heart-rate targets require Run maximum heart rate;
• pace targets require both Run threshold pace and pace zones;
• one published run may use at most one target mode;
• missing Garmin connection, forwarding, or Run filter affects Garmin status, not Intervals calendar ownership;
• Wahoo state is outside this procedure and never blocks it.

Do not calculate or change threshold pace. A five-kilometre benchmark alone does not authorize that setting. The coach reassesses whether threshold-specific evidence is needed before the first pace-targeted phase.

Inspect desired state

poetry run resilio workout status --week-number <WEEK_NUMBER>
poetry run resilio workout fulfillment-status --week-number <WEEK_NUMBER>

Status performs no mutation. Require reconciliation_safe: true before an ordinary reconcile. Report every blocker exactly; do not silently remove targets, invent a start time, or synchronize only the runs that happen to pass. For any exact fulfillment, status also inspects the native Intervals activity/event pair and blocks publication reconciliation when that pair is conflicted, unsupported, or drifted. Exact provider-observed pairs do not require a redundant athlete confirmation.