Program templates

A program template is a reusable plan in the studio’s library. Assigning a template copies it into a program for one trainee. Later edits to the template do not change programs that were already assigned. The Prisma model is ProgramTemplate.


Source	`backend/apps/core-api/src/modules/program-templates/`
Lane	Web gateway only
Base path	`/v1/web/program-templates`
Guards	Service auth plus web user context. No `requireRole` guard, so every studio role can call every route.

Besides the five standard files the module holds the plan content contracts, which the rest of the backend imports:

File	Purpose
`training-schema.ts`	`TrainingContent` type, `normalizeTrainingContent`, `summarizeTraining`, movement requirement helpers, technique video rules
`nutrition-schema.ts`	`NutritionContent` type, `normalizeNutritionContent`, `summarizeNutrition`, day rotation and water helpers
`autofit-meta.ts`	The `content.meta` keys the AutoFit import stamps, and the helpers that keep them through a save

The router wires the service with createProgramGenerator (ai/program-generator.ts, configured from OPENAI_API_KEY and OPENAI_NUTRITION_MODEL), a trainee notifier, and a plan-activated hook that calls the subscription starter with the FIRST_PLAN trigger.

The template object

Every route that returns a template passes the Prisma row through enrich() and adds assignedCount. The extra fields depend on the kind of template. Base fields from the ProgramTemplate row:

Field	Type	Notes
`id`	string	cuid
`studioId`	string
`folderId`	string or null	See Program folders
`type`	`TRAINING`, `NUTRITION` or `COMBINED`	Set on create, not editable
`name`	string
`displayName`	string or null	Name shown to the trainee
`description`	string or null
`level`	string or null
`content`	object	Plan JSON, see Content contracts
`version`	integer	Defaults to 1. This module never increments it
`pdfUrl`	string or null	Set means a file template
`createdAt`, `updatedAt`	datetime

Added by the service:

Field	When	Meaning
`assignedCount`	always	Number of `Program` rows in the studio whose `sourceTemplateId` is this template, in any status
`discipline`, `dayCount`, `exerciseCount`, `workoutsPerWeek`	`TRAINING`	From `summarizeTraining`
`goal`, `dayCount`, `mealCount`, `kcalTarget`, `kcalTargetMax`	`NUTRITION`	From `summarizeNutrition`. The two kcal values are the lowest and highest day target
`imported`, `draft`	`TRAINING` or `NUTRITION`, only when true	Import badges
`goalSet`	`NUTRITION`, only when `false`	The imported document carried no goal
`kcalMissing`	`NUTRITION`, only when true	An imported plan has a day with a 0 kcal target
`kind: "pdf"`	file template	With `discipline`, `goal`, `dayCount`, `exerciseCount`, `mealCount`, `kcalTarget`, `kcalTargetMax` all `null`, and `workoutsPerWeek` read from `content.meta` or `null`
`discipline: null`, `dayCount: 0`, `exerciseCount: 0`	`COMBINED`	Combined templates get no computed stats

{
  "id": "cmtpl000010qz8h1a2b3c4d",
  "studioId": "cmstudio0001qz8h7w8x9y0z",
  "folderId": "cmf4p1q2r0001qz8h3s4t5u6v",
  "type": "TRAINING",
  "name": "Push pull legs",
  "displayName": null,
  "description": "Three day split for intermediates.",
  "level": "intermediate",
  "content": { "schemaVersion": 2, "meta": {}, "days": [] },
  "version": 1,
  "pdfUrl": null,
  "createdAt": "2026-09-10T08:00:00.000Z",
  "updatedAt": "2026-09-22T14:05:00.000Z",
  "discipline": "strength",
  "dayCount": 3,
  "exerciseCount": 18,
  "workoutsPerWeek": 3,
  "assignedCount": 7
}

The content value in the example is shortened. A full example is under Training content.

Endpoints

`GET /v1/web/program-templates`

Lists the studio’s templates, most recently updated first. Auth: web lane, any role.

string

TRAINING, NUTRITION or COMBINED.

string

Limit to one folder.

string

Case-insensitive contains on name.

integer

default:"1"

Page number, positive.

integer

default:"20"

Positive, maximum 500.

The assigned counts for the whole page are loaded with one groupBy on Program.sourceTemplateId. Response:

{
  "ok": true,
  "data": {
    "items": [
      {
        "id": "cmtpl000020qz8h5e6f7g8h",
        "studioId": "cmstudio0001qz8h7w8x9y0z",
        "folderId": null,
        "type": "NUTRITION",
        "name": "Cutting 1800",
        "displayName": "Your nutrition plan",
        "description": null,
        "level": null,
        "content": { "schemaVersion": 1, "meta": { "goal": "deficit", "autoAlts": false }, "days": [] },
        "version": 1,
        "pdfUrl": null,
        "createdAt": "2026-09-11T08:00:00.000Z",
        "updatedAt": "2026-09-30T10:00:00.000Z",
        "goal": "deficit",
        "dayCount": 2,
        "mealCount": 9,
        "kcalTarget": 1800,
        "kcalTargetMax": 2000,
        "assignedCount": 3
      }
    ],
    "total": 24,
    "page": 1,
    "pageSize": 20
  }
}

Errors: VALIDATION, UNAUTHORIZED.

`POST /v1/web/program-templates`

Creates a template. Returns 201. Auth: web lane, any role.

string

required

TRAINING, NUTRITION or COMBINED.

string

required

Minimum length 1.

string | null

Name shown to the trainee.

string

Free text.

string

Free text.

string | null

Folder to file the template in. The service does not check that the folder exists or matches the type. A bad id fails at the database with CONFLICT.

object

required

Plan JSON. Normalized before it is stored.

string | null

An http(s) URL. Setting it makes a file template.

Content handling depends on the kind:

File template (pdfUrl set): content must be {} or { "meta": { "workoutsPerWeek": n } }. Anything else is BAD_REQUEST. The normalizers are skipped, because they would fabricate a day.
TRAINING: stored as normalizeTrainingContent(content).
NUTRITION: stored as normalizeNutritionContent(content).
COMBINED: stored as sent.

Response: the created template object with assignedCount: 0. Errors: BAD_REQUEST (a file plan carries no content beyond meta.workoutsPerWeek). VALIDATION for a bad body. UNAUTHORIZED.

`POST /v1/web/program-templates/generate-ai`

Generates a template from a free-text description with OpenAI and saves it. Returns 201. Auth: web lane, any role.

string

required

TRAINING, NUTRITION or COMBINED. The generator only has two branches: TRAINING produces a training plan, and every other value goes down the nutrition branch. Sending COMBINED therefore stores nutrition-shaped content on a COMBINED template, without normalizing it. Send TRAINING or NUTRITION.

string

required

Between 1 and 2000 characters. A prompt that is blank after trimming is refused.

string | null

Folder for the new template.

The generator calls generateObject from the Vercel AI SDK with a fixed system prompt and a Zod output schema, then maps the result into builder content. The service normalizes that content and creates the template with the generated name and level. What the generated content looks like:

Training. Days with Hebrew labels, each with strength rows (muscle, sets, reps, rest, weight, rir, tempo, notes) and aerobic rows. Every row has exerciseId: null, so the coach still has to link rows to library exercises. The generator emits the v1 shape with an aerobic array per day. The normalizer converts those minutes into the cardio requirement.
Nutrition. One targets block applied to every day, meals typed as breakfast, snack_am, lunch, pre, post or dinner, and items with foodId: null. The food name the model produced is kept only in the item note (item.note || item.name), because the stored item shape has no name field.

Response: the created template object with assignedCount: 0. Errors:

Code	When
`INTERNAL`	`program AI is not configured` when `OPENAI_API_KEY` is empty. `failed to generate training program` or `failed to generate nutrition program` when the model call fails.
`BAD_REQUEST`	`provide a program description` for a blank prompt.
`VALIDATION`	Bad body.

`GET /v1/web/program-templates/:id`

Returns one template. Auth: web lane, any role.

string

required

The template id.

Response: one template object. Errors: NOT_FOUND (program template not found).

`PATCH /v1/web/program-templates/:id`

Edits a template. Only the fields sent are written. type cannot be changed. Auth: web lane, any role.

string

required

The template id.

string

Minimum length 1.

string | null

Send null to clear.

string | null

Send null to clear.

string | null

Send null to clear.

string | null

Send null to unfile.

object

New plan JSON.

string | null

An http(s) URL, or null to remove the file.

The kind after the patch decides how content is stored. If the template is, or becomes, a file template, the content must pass the file plan rule. Otherwise the content is normalized for the template’s existing type and passed through keepAutofitMeta, which restores the AutoFit keys of the stored row. A save from a builder that does not echo those keys keeps the template findable by a later AutoFit sync. Programs already assigned from the template are not touched. There is no notification or activity record. Response: the updated template object. Errors: NOT_FOUND, BAD_REQUEST (file plan content), VALIDATION.

`DELETE /v1/web/program-templates/:id`

Deletes a template. Returns 204 with no body. Auth: web lane, any role.

string

required

The template id.

The row is hard deleted. Program.sourceTemplateId is a plain column with no relation, so assigned programs keep the stale id and are otherwise unaffected. Errors: NOT_FOUND (program template not found).

`POST /v1/web/program-templates/:id/duplicate`

Copies a template inside the library. Returns 201. Auth: web lane, any role.

string

required

The template id.

No body. The copy keeps type, content, displayName, description, level, folderId and pdfUrl. Its name is the original name followed by a Hebrew suffix meaning “(copy)”. The content is copied as stored, AutoFit keys included. Response: the new template object with assignedCount: 0. Errors: NOT_FOUND.

`GET /v1/web/program-templates/:id/assignments`

Lists the trainees that currently hold a plan made from this template. Auth: web lane, any role.

string

required

The template id.

Only programs with status ACTIVE or PAUSED are listed, oldest first. A trainee with two such programs appears twice. Note the difference from assignedCount, which counts programs in every status. Response:

{
  "ok": true,
  "data": {
    "items": [
      {
        "clientId": "cmf1a7b2c0003qz8h9k1l2m3n",
        "clientName": "Dana Levi",
        "programId": "cmf7p1q2r0001qz8h3s4t5u6v"
      }
    ]
  }
}

Errors: NOT_FOUND.

`POST /v1/web/program-templates/:id/assign`

Assigns the template to one trainee by creating a program. Returns 201. Auth: web lane, any role.

string

required

The template id.

string

required

The trainee. Must be in the caller’s studio.

date

Stored on the program. Parsed with z.coerce.date().

string

Hold mode. The id of an intake FormResponse for this same trainee. The plan is created hidden from the trainee until the coach sends it.

The program is always a fresh copy. An earlier or parallel plan from the same template does not block the assignment. The copy takes type, name, displayName, content and pdfUrl from the template, sets sourceTemplateId, and is created with status: ACTIVE. Normal assign side effects:

A ClientActivity row (actorType: TRAINER, action: ASSIGNED, entityType: PROGRAM, entityId the program id, entityName the template name, type one of TRAINING_PLAN, NUTRITION_PLAN, TRAINING_AND_NUTRITION_PLAN).
A push of type TRAINING_PLAN_ASSIGNED, NUTRITION_PLAN_ASSIGNED, or both for a combined template. The plan variable is the display name, falling back to the name.
The plan-activated hook, which starts a subscription that waits on the FIRST_PLAN trigger.

Hold mode (holdForResponseId set): the response must exist in the studio, belong to this trainee, and be of a form whose type is INTAKE. The program is created with status: PAUSED, releasePending: true and releaseResponseId set. The activity row is still written. The push and the hook are skipped. They fire when the plan is released, see Programs. Response: the created Program row.

{
  "ok": true,
  "data": {
    "id": "cmf7p1q2r0001qz8h3s4t5u6v",
    "studioId": "cmstudio0001qz8h7w8x9y0z",
    "clientId": "cmf1a7b2c0003qz8h9k1l2m3n",
    "sourceTemplateId": "cmtpl000010qz8h1a2b3c4d",
    "type": "TRAINING",
    "name": "Push pull legs",
    "displayName": null,
    "content": { "schemaVersion": 2, "meta": {}, "days": [] },
    "version": 1,
    "status": "PAUSED",
    "pdfUrl": null,
    "startsOn": null,
    "endsOn": null,
    "lastPlanNotifiedAt": null,
    "releasePending": true,
    "releaseAt": null,
    "releaseResponseId": "cmresp00010qz8h1a2b3c4d",
    "createdAt": "2026-10-06T09:00:00.000Z",
    "updatedAt": "2026-10-06T09:00:00.000Z"
  }
}

Errors:

Code	When
`NOT_FOUND`	`program template not found`, `client not found`, or `form response not found`.
`BAD_REQUEST`	`the review belongs to another trainee`, or `plans are held only from an intake review`.
`VALIDATION`	Bad body.

`POST /v1/web/program-templates/:id/assign-bulk`

Assigns the template to many trainees. Returns 201. Auth: web lane, any role.

string

required

The template id.

string[]

required

Between 1 and 500 trainee ids. Duplicates are removed.

date

Stored on every new program.

Bulk assign only adds. It behaves differently from the single assign in two ways:

All ids are checked first. If any id is not in the studio, the whole request fails with NOT_FOUND and nothing is created.
Existing assignments are skipped. A trainee who already has an ACTIVE or PAUSED program from this template gets no second copy. Their existing program id is returned instead.

New programs are inserted with one createManyAndReturn, all ACTIVE. Then one batch of ClientActivity rows is written, the assigned push goes to all new recipients, and the plan-activated hook runs once per new program. Hold mode is not available in bulk. Response: one entry per trainee that now holds a plan from this template. This includes trainees who already had one and were not in the request.

{
  "ok": true,
  "data": {
    "items": [
      { "clientId": "cmf1a7b2c0003qz8h9k1l2m3n", "programId": "cmf7p1q2r0001qz8h3s4t5u6v" },
      { "clientId": "cmf1b8c3d0004qz8h0l2m3n4o", "programId": "cmf7p2a3b0002qz8h4c5d6e7f" }
    ]
  }
}

Errors: NOT_FOUND (program template not found or client not found). VALIDATION for a bad body.

Content contracts

The request schemas accept any object for content. The shape is enforced by normalizers, not by Zod. A normalizer never throws. It reads what it recognizes, fills defaults, and drops everything else. Unknown keys do not survive a template save. Two rules follow from that:

Add a field to the normalizer, or it will be stripped the next time a coach saves.
Both normalizers mirror the frontend builder shape, so a change has to land in both places.

Training content

Type TrainingContent in training-schema.ts. Current schemaVersion is 2.

{
  "schemaVersion": 2,
  "meta": {
    "discipline": "mixed",
    "level": "intermediate",
    "split": "push-pull-legs",
    "workoutsPerWeek": 3,
    "requirement": {
      "on": true,
      "mode": "both",
      "cardio": { "scope": "perWorkout", "minutes": "30", "activities": ["walking", "cycling"] },
      "steps": { "daily": "8000" }
    },
    "columns": { "tempo": false, "rir": true }
  },
  "days": [
    {
      "id": "d1",
      "label": "Day A",
      "cardioMinutes": "",
      "stepsDaily": "",
      "strength": [
        {
          "id": "s_k3j9x2a",
          "exerciseId": "cmexr8s9t0004qz8h2u3v4w5x",
          "muscle": "centralChest",
          "sets": "3",
          "reps": "8",
          "repType": "range",
          "repsHigh": "12",
          "rest": "01:30",
          "weight": "",
          "rir": "2",
          "tempo": "",
          "notes": "",
          "setRows": [
            { "id": "set_a1b2c3d", "type": "warmup", "reps": "12", "repType": null, "repsHigh": "", "weight": "", "rest": "", "note": "" },
            { "id": "set_e4f5g6h", "type": "working", "reps": "", "repType": null, "repsHigh": "", "weight": "", "rest": "", "note": "" },
            { "id": "set_i7j8k9l", "type": "working", "reps": "", "repType": null, "repsHigh": "", "weight": "", "rest": "", "note": "" }
          ],
          "alternatives": ["cmexr9t0u0005qz8h3v4w5x6y"],
          "supersetParentId": null,
          "techniqueVideo": { "mode": "coachDemand", "firstTime": true, "everyN": "" }
        }
      ]
    }
  ]
}

`meta`

Key	Type	Rule
`discipline`	`strength`, `aerobic` or `mixed`	Always derived, never read from input. `mixed` when there are strength rows and the requirement includes cardio, `aerobic` when there is cardio and no strength rows, otherwise `strength`
`level`, `split`	string	Kept only when non-empty
`workoutsPerWeek`	integer	Clamped to 1 through 7. Default 3
`requirement`	object	The movement requirement, see below
`columns`	`{ tempo, rir }`	Each is `true` only when the input is exactly `true`. Controls which optional columns the builder and the app show
`autoAlts`	`true`	Written only when on. Offers the trainee the automatic top alternatives on every strength row, in place of the coach’s own `alternatives`
`imported`, `source`, `draft`	plan import keys	Written only when set. See Plan import
AutoFit keys	string or number	`autofitTrainingId`, `autofitMenuId`, `autofitTemplateId`, `autofitProgramId`, `autofitWeek`, `autofitNutritionTemplateId`, passed through verbatim

Movement requirement

meta.requirement describes cardio and daily steps for the whole plan.

Key	Values	Default
`on`	boolean	`false`
`mode`	`cardioOnly`, `stepsOnly`, `both`, `bothCompensated`	`both`
`cardio.scope`	`perWorkout`, `weekly`	`perWorkout`
`cardio.minutes`	positive integer as a string	`"30"`
`cardio.activities`	subset of `walking`, `running`, `stairs`, `cycling`, de-duplicated	`[]`
`steps.daily`	positive integer as a string	`"8000"`

Helpers exported for other modules:

requirementHasCardio: on and mode is not stepsOnly.
requirementHasSteps: on and mode is not cardioOnly.
requirementCompensates: on and mode is bothCompensated. One fully met goal stands in for the other, so a day counts as done when either target is reached.
weeklyCardioMinutes(requirement, workoutsPerWeek): the minutes as they are for weekly scope, or minutes times workouts per week for perWorkout.
dayCardioMinutes(day, requirement, workoutsPerWeek): the day’s own cardioMinutes when set. Otherwise the plan target, divided by workouts per week and rounded when the scope is weekly.
dayStepsGoal(day, requirement): the day’s own stepsDaily when set, otherwise the plan’s daily steps. 0 when the requirement has no steps.

Days and strength rows

A day has id, label, strength, cardioMinutes and stepsDaily.

id defaults to d1, d2 and so on. Duplicate ids are replaced with the next free dN.
label defaults to Day A, Day B and so on.
cardioMinutes and stepsDaily are per-day overrides, stored as positive integer strings or "". After normalizing, a day value equal to the plan value is blanked, so only real overrides are stored.
Content with no days gets one empty day: { "id": "d1", "label": "Day A", "strength": [], "cardioMinutes": "", "stepsDaily": "" }.

A strength row:

Key	Type	Rule
`id`	string	Kept, or a random `s_` id
`exerciseId`	string or null	Library exercise
`muscle`	string
`sets`	string	The length of `setRows` when there are any, otherwise the label. Defaults to `"3"`, or `""` on imported content
`reps`, `repsHigh`, `rest`, `weight`, `rir`, `tempo`, `notes`	string	Numbers are converted to strings
`repType`	`fixed`, `range`, `seconds`, `minutes`	Default `fixed`. `repsHigh` is the upper bound and only matters for `range`
`setRows`	array	Per-set breakdown. When absent, built from the `sets` count, capped at 20
`alternatives`	string[]	Exercise ids, de-duplicated, empty strings dropped
`supersetParentId`	string or null	The id of the row this one is super-setted with
`techniqueVideo`	object	Technique video rule

A set row has id (random set_ id when missing), type (warmup, working or drop, default working), reps, repType (null inherits the row’s rep type), repsHigh, weight, rest and note.

Technique video rule

type TechniqueVideoRule = {
  mode: 'none' | 'free' | 'coachDemand';
  firstTime: boolean;
  everyN: string;
  requestedAt?: string;
};

everyN is a positive integer string or "".
When mode is missing or unknown, it is inferred: coachDemand if firstTime is true or everyN is set, otherwise none.
techniqueVideoRequired(rule) is true when mode is coachDemand and either trigger is set.
requestedAt is a coach’s one-off “film this in the next workout” request. It is kept only when it is a valid ISO instant, and the key is absent otherwise. stampTechniqueRequest(content, exerciseId, requestedAt) writes it onto every strength row that prescribes the exercise and returns the number of rows touched. It rewrites the stored shape and does not normalize the plan.

Migration from version 1

normalizeTrainingContent upgrades older content on read. There is no stored migration.

Old shape	Becomes
A nested `superset` object on a strength row	A second row placed right after its parent, with `supersetParentId` set to the parent id, `rest` `"00:00"`, the parent’s `muscle`, and its own `sets` and `reps`
A `sets` count with no `setRows`	A `setRows` array of that many empty working sets
A per-day `aerobic` array of rows with `duration`	The day’s `cardioMinutes`, the rounded sum of the durations (`HH:mm:ss`, `mm:ss` or minutes)
`meta.cardio` (the cardio-only requirement from before daily steps)	`meta.requirement` with `mode: "cardioOnly"`
No requirement at all, but a day with cardio minutes	A requirement that is on, `cardioOnly`, `perWorkout`, using the first such day’s minutes
`techniqueVideo` with triggers and no `mode`	`mode: "coachDemand"`

Nutrition content

Type NutritionContent in nutrition-schema.ts. schemaVersion is 1. Macros are not stored on items. They are computed from the referenced FoodLibraryItem, see Foods.

{
  "schemaVersion": 1,
  "meta": { "goal": "deficit", "autoAlts": true },
  "days": [
    {
      "id": "nd1",
      "label": "Day 1",
      "targets": { "kcal": 1800, "protein": 150, "carbs": 160, "fat": 55, "water": 3 },
      "meals": [
        {
          "id": "ml_p9q8r7s",
          "type": "breakfast",
          "label": "",
          "time": "08:00",
          "prep": "",
          "target": { "kcal": 450 },
          "items": [
            {
              "id": "mi_a1b2c3d",
              "foodId": "cmfood00010qz8h1a2b3c4d",
              "qty": "150",
              "note": "",
              "alts": [
                { "id": "al_e4f5g6h", "foodId": "cmfood00020qz8h5e6f7g8h", "qty": "120" }
              ]
            }
          ]
        }
      ]
    }
  ]
}

`meta`

Key	Type	Rule
`goal`	`deficit`, `balance` or `surplus`	Default `balance`
`level`	string	Kept only when non-empty
`autoAlts`	boolean	Always written. `true` only when the input is exactly `true`. Suggests alternatives to the trainee for every item
`imported`, `source`, `draft`, `goalSet`	plan import keys	Written only when set. `goalSet: false` means the imported document carried no goal
AutoFit keys	string or number	Same six keys as training

Days, targets, meals and items

A day has id (default nd1, nd2), label (default is the Hebrew word for “day” plus the day number), targets and meals. Content with no days gets one empty day.
targets holds kcal, protein, carbs, fat (grams) and water (litres). Defaults are 2000, 150, 200, 60 and 3. Optional mbpProtein, mbpCarb and mbpFat portion targets are kept only when finite and above zero. kcalOverride: true is set once the coach types a calorie target over the portion-derived one.
A top-level targets object is the legacy plan-level shape. It is used as the fallback for every day that lacks its own values and is not written back.
A meal has id, type (breakfast, snack_am, lunch, pre, post, dinner, default breakfast), label (custom name, empty falls back to the type’s label in the UI), time, prep, items, and an optional target. The default time comes from MEAL_TYPE_DEFAULT_TIME: 08:00, 10:30, 13:00, 16:00, 18:00 and 20:00 in the order above.
A meal target holds any of kcal (rounded to whole calories), mbpProtein, mbpCarb, mbpFat. Each key survives only when finite and above zero, and a target with no keys left is removed entirely.
An item has id, foodId, qty (string, default "100"), note, optional countsAs (protein or carb, for foods that can count toward either macro) and alts. An alternative has id, foodId, qty and optional countsAs.

Helpers used by the trainee side

nutritionDayIndexForOffset(dayCount, offset): plan days rotate around the trainee’s current day. Offset 0 is the first day, 1 the second, and the sequence wraps, including for negative offsets.
nutritionTargetsForOffset(content, offset): the targets of that day.
planWaterGoalMl(content, offset) and targetsWaterGoalMl(targets): the water target in millilitres (water times 1000, rounded), or 0 when there is none.

Imported content

When meta.imported is true, both normalizers stop filling builder defaults, because an empty value means “missing in the source document” and drives the review markers in the UI:

Training: a missing sets stays "" instead of "3".
Nutrition: a missing qty stays "" instead of "100", a missing meal time stays "", and missing targets fall back to 0 instead of the defaults.

imported, source, draft and goalSet ride through every normalize untouched and stay absent on content that never carried them.

AutoFit keys

autofit-meta.ts lists the keys the AutoFit import stamps on content.meta so a re-sync finds the row it wrote instead of creating a second one:

export const AUTOFIT_META_KEYS = [
  'autofitTrainingId',
  'autofitMenuId',
  'autofitTemplateId',
  'autofitProgramId',
  'autofitWeek',
  'autofitNutritionTemplateId',
] as const;

pickAutofitMeta(meta) returns the keys present, verbatim. Ids stay strings and autofitWeek stays a number, because the import’s JSON path lookup compares types.
keepAutofitMeta(content, stored) removes whatever AutoFit keys the new content brought and puts back the stored row’s keys. Template update and program update both use it.
keepFilePlanKey(content, stored) does the same for meta.autofitPdfId on a trainee file plan, whose content skips the normalizers.

Who else uses this module

modules/programs/ imports both normalizers, keepAutofitMeta, keepFilePlanKey and filePlanContentForStore.
modules/programs/plan-diff.ts normalizes both sides before diffing.
modules/plan-import/ and modules/autofit-import/ produce content in these shapes.
The trainee, check-in and client tracking modules read plans through the same normalizers and helpers. Their endpoints are documented on their own pages.

API basics

Trainees

Plans and libraries

Tracking

Imports

Forms

Tasks and automation

Communication

Studio and billing

Admin and internal services

Trainee app API

Partner and automation

Public, internal and auth

Program templates

The template object

Endpoints

`GET /v1/web/program-templates`

`POST /v1/web/program-templates`

`POST /v1/web/program-templates/generate-ai`

`GET /v1/web/program-templates/:id`

`PATCH /v1/web/program-templates/:id`

`DELETE /v1/web/program-templates/:id`

`POST /v1/web/program-templates/:id/duplicate`

`GET /v1/web/program-templates/:id/assignments`

`POST /v1/web/program-templates/:id/assign`

`POST /v1/web/program-templates/:id/assign-bulk`

Content contracts

Training content

`meta`

Movement requirement

Days and strength rows

Technique video rule

Migration from version 1

Nutrition content

`meta`

Days, targets, meals and items

Helpers used by the trainee side

Imported content

AutoFit keys

Who else uses this module

​The template object

​Endpoints

​GET /v1/web/program-templates

​POST /v1/web/program-templates

​POST /v1/web/program-templates/generate-ai

​GET /v1/web/program-templates/:id

​PATCH /v1/web/program-templates/:id

​DELETE /v1/web/program-templates/:id

​POST /v1/web/program-templates/:id/duplicate

​GET /v1/web/program-templates/:id/assignments

​POST /v1/web/program-templates/:id/assign

​POST /v1/web/program-templates/:id/assign-bulk

​Content contracts

​Training content

​meta

​Movement requirement

​Days and strength rows

​Technique video rule

​Migration from version 1

​Nutrition content

​meta

​Days, targets, meals and items

​Helpers used by the trainee side

​Imported content

​AutoFit keys

​Who else uses this module

The template object

Endpoints

`GET /v1/web/program-templates`

`POST /v1/web/program-templates`

`POST /v1/web/program-templates/generate-ai`

`GET /v1/web/program-templates/:id`

`PATCH /v1/web/program-templates/:id`

`DELETE /v1/web/program-templates/:id`

`POST /v1/web/program-templates/:id/duplicate`

`GET /v1/web/program-templates/:id/assignments`

`POST /v1/web/program-templates/:id/assign`

`POST /v1/web/program-templates/:id/assign-bulk`

Content contracts

Training content

`meta`

Movement requirement

Days and strength rows

Technique video rule

Migration from version 1

Nutrition content

`meta`

Days, targets, meals and items

Helpers used by the trainee side

Imported content

AutoFit keys

Who else uses this module