forge-openclaw-plugin 0.2.99 → 0.2.100

package/dist/server/server/src/app.js

@@ -67,9 +67,10 @@ import { createManagerRuntime } from "./managers/runtime.js";
 import { isManagerError } from "./managers/type-guards.js";
 import { buildCompanionPairingTransport, getCompanionIrohStatus, stopCompanionIroh } from "./services/companion-iroh.js";
 import { createCompanionPairingSession, createCompanionPairingSessionSchema, createSleepSession, createSleepSessionSchema, createWorkoutSession, createWorkoutSessionSchema, deleteSleepSession, deleteWorkoutSession, getCompanionPairingSessionById, getCompanionOverview, getFitnessViewData, getSleepSessionById, getSleepSessionDetailById, getSleepTimelineOverlaysForRange, getSleepViewData, getTrainingLoadViewData, getVitalsViewData, getHealthZoneProfileForUser, getMobileHealthSyncSessionStatus, getWorkoutSessionById, getWorkoutSessionDetailById, heartbeatCompanionPairing, heartbeatCompanionPairingSchema, healthZoneProfilePatchSchema, abortMobileHealthSyncSession, completeMobileHealthSyncSession, ingestMobileHealthSync, ingestMobileHealthSyncChunk, mobileHealthSyncChunkSchema, mobileHealthSyncSessionCompleteSchema, mobileHealthSyncSessionStartSchema, mobileHealthSyncSchema, patchHealthZoneProfileForUser, patchCompanionPairingSourceState, patchCompanionPairingSourceStateSchema, companionSourceKeySchema, requireValidPairing, startMobileHealthSyncSession, revokeAllCompanionPairingSessions, revokeAllCompanionPairingSessionsSchema, revokeCompanionPairingSession, updateMobileCompanionSourceState, updateMobileCompanionSourceStateSchema, verifyCompanionPairing, verifyCompanionPairingSchema, updateSleepMetadata, updateSleepMetadataSchema, updateWorkoutMetadata, updateWorkoutMetadataSchema } from "./health.js";
+import { createNutritionAppearanceCheckin, createNutritionBodyCheckin, createNutritionExperiment, createNutritionFoodLog, createNutritionGutCheckin, createNutritionSubjectiveCheckin, deleteNutritionFoodLog, getWeightLossViewData, lookupNutritionBarcode, nutritionAppearanceCheckinCreateSchema, nutritionBarcodeLookupSchema, nutritionBodyCheckinCreateSchema, nutritionExperimentCreateSchema, nutritionExperimentPatchSchema, nutritionFoodLogCreateSchema, nutritionFoodLogPatchSchema, nutritionFoodSearchSchema, nutritionGutCheckinCreateSchema, nutritionParseRequestSchema, nutritionSubjectiveCheckinCreateSchema, nutritionTargetUpdateSchema, parseNutritionFoodLogWithChatGpt, patchNutritionExperiment, patchNutritionFoodLog, searchNutritionFoods, updateNutritionTarget } from "./health-weight-loss.js";
 import { analyzeMovementUserBoxPreflight, createMovementUserBox, createMovementPlace, deleteMovementUserBox, getMovementAllTimeSummary, getMovementBoxDetail, getMovementDayDetail, getMovementMobileBootstrap, getMovementTimeline, getMovementSelectionAggregate, getMovementSettings, getMovementTripDetail, getMovementMonthSummary, invalidateAutomaticMovementBox, listMovementPlaces, movementAutomaticBoxInvalidateSchema, movementMobileBootstrapSchema, movementMobilePlaceMutationSchema, movementMobileStayPatchSchema, movementMobileUserBoxCreateSchema, movementMobileUserBoxPreflightSchema, movementMobileUserBoxPatchSchema, movementMobileAutomaticBoxInvalidateSchema, movementMobileTimelineSchema, movementPlaceMutationSchema, movementPlacePatchSchema, movementSelectionAggregateSchema, movementStayPatchSchema, movementTripPatchSchema, movementUserBoxCreateSchema, movementUserBoxPreflightSchema, movementUserBoxPatchSchema, movementSettingsPatchSchema, movementTimelineQuerySchema, movementTripPointPatchSchema, deleteMovementStay, deleteMovementTrip, deleteMovementTripPoint, updateMovementPlace, updateMovementSettings, updateMovementStay, updateMovementTrip, updateMovementUserBox, updateMovementTripPoint, resolveMovementTimelineSegmentForBox } from "./movement.js";
 import { getScreenTimeAllTimeSummary, getScreenTimeDayDetail, getScreenTimeMonthSummary, getScreenTimeSettings, screenTimeSettingsPatchSchema, updateScreenTimeSettings } from "./screen-time.js";
-import { assertWatchReady, buildWatchBootstrap, ingestWatchCaptureBatch, mobileWatchBootstrapSchema, mobileWatchCaptureBatchSchema, mobileWatchHabitCheckInSchema } from "./watch-mobile.js";
+import { assertWatchReady, buildWatchBootstrap, ingestWatchCommandBatch, ingestWatchCaptureBatch, mobileWatchBootstrapSchema, mobileWatchCommandBatchSchema, mobileWatchCaptureBatchSchema, mobileWatchHabitCheckInSchema } from "./watch-mobile.js";
 const COMPATIBILITY_SUNSET = "transitional-node";
 function markCompatibilityRoute(reply) {
     reply.header("Deprecation", "true");
@@ -3066,6 +3067,7 @@ const AGENT_ONBOARDING_CONVERSATION_RULES = [
     "Use a progression of concrete example or intent, working name, purpose or meaning, placement in Forge, operational details, and linked context.",
     "Ask one to three focused questions at a time. One is usually best when the user is uncertain or emotionally loaded.",
     "One focused question is the default. Only stack a second question when both serve the same clarification job and the user is steady enough for it.",
+    "For operational create flows, do not bundle name, scope, and timing into one opener when the user has already supplied part of it. Ask the route-changing missing detail first, then move to the next detail only if it is still unknown.",
     "When the user wants review, comparison, or navigation around an existing record, ask what they are trying to understand first and look up the existing record before reopening create or update intake.",
     "If the user already answered the normal opening question, do not repeat it. Move to the next missing clarification.",
     "Do not over-therapize logistical entities. For tasks, calendar events, work blocks, timeboxes, and task runs, one brief confirming sentence plus one question is usually enough.",
@@ -3087,6 +3089,7 @@ const AGENT_ONBOARDING_CONVERSATION_RULES = [
     "Do not bury schema work in self-observation. If the user is describing a schema theme, preserve it through a belief_entry, behavior_pattern, mode_profile, mode_guide_session, trigger_report, or wiki_page depending on whether it appears as a rule, loop, part-state, live exploration, one episode, or durable explanation.",
     "Do not minimize functional analysis, trigger chains, behavior patterns, modes, beliefs, or schema themes. After at least one concrete example is clear, offer one careful interpretive hypothesis when it would help the user understand what the reaction may be protecting, predicting, relieving, or costing.",
     "Phrase Psyche interpretive hypotheses as collaborative and testable, not as verdicts. Ask whether the hypothesis lands or needs correction before turning it into a saved belief, pattern, mode, trigger report, or note.",
+    "A useful Psyche hypothesis starts from the user's concrete example, names one possible protection, prediction, relief, or cost, and asks for correction before it becomes a saved record shape.",
     "Once the Movement, Life Force, or Workbench job is clear, speak in product nouns such as timeline, overlay, weekday template, published output, run detail, or node result instead of generic record language.",
     "If the next answer would not change the route, wording, timing, or write shape in a meaningful way, stop asking and act.",
     "Before saving, briefly summarize the working formulation in the user's own language when that would reduce ambiguity.",
@@ -3216,7 +3219,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
     },
     {
         focus: "calendar_event",
-        openingQuestion: "What is the event, and when should it happen in your local time?",
+        openingQuestion: "What time should Forge hold for this event in your local timezone?",
         coachingGoal: "Make the event legible as a real commitment in time, with the right timezone and links.",
         askSequence: [
             "Ask what the event is.",
@@ -3227,7 +3230,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
     },
     {
         focus: "work_block_template",
-        openingQuestion: "What recurring block do you want to set up, and when should it repeat?",
+        openingQuestion: "When should this recurring block repeat?",
         coachingGoal: "Define a reusable availability rule rather than a one-off event.",
         askSequence: [
             "Ask what kind of block it is and what it should be called.",
@@ -3238,7 +3241,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
     },
     {
         focus: "task_timebox",
-        openingQuestion: "Which task are you trying to make time for, and when should the slot be?",
+        openingQuestion: "When should Forge reserve focused time for this task?",
         coachingGoal: "Reserve real time for one task without confusing planned work with completed work.",
         askSequence: [
             "Ask which task the slot belongs to.",
@@ -3260,7 +3263,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
     },
     {
         focus: "calendar_connection",
-        openingQuestion: "Which calendar provider are you trying to connect, and what do you want Forge to do with it?",
+        openingQuestion: "What workflow do you want this calendar connection to unlock?",
         coachingGoal: "Connect the right provider deliberately without turning setup into a credential dump.",
         askSequence: [
             "Ask which provider the user wants to connect and what they want Forge to do with it.",
@@ -3493,7 +3496,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
     },
     {
         focus: "questionnaire_run",
-        openingQuestion: "What do you want from this questionnaire run right now: start, continue, review, or finish it?",
+        openingQuestion: "Are you trying to start, continue, review, or finish this run right now?",
         coachingGoal: "Clarify whether the user wants to start, continue, review, or complete one answer session without turning the run into a mechanical form fill.",
         askSequence: [
             "Ask what the user wants from the run right now: start, continue, review, or finish.",
@@ -4273,6 +4276,68 @@ const AGENT_ONBOARDING_TOOL_INPUT_CATALOG = [
         ],
         example: '{"userIds":["user_operator"]}'
     },
+    {
+        toolName: "forge_get_weight_loss_overview",
+        summary: "Read the nutrition and weight-loss surface with calorie ledger, protein/fiber targets, energy balance, body trend, subjective energy, gut comfort, aesthetic check-ins, hypotheses, experiments, and data-quality flags.",
+        whenToUse: "Use when the operator wants food, body composition, sport-fueling, appearance, gut-health, or subjective-energy context before coaching or logging.",
+        inputShape: "{ userIds?: string[] }",
+        requiredFields: [],
+        notes: [
+            "The API path is /api/v1/health/weight-loss and the UI route is /weight-loss.",
+            "Use the dedicated nutrition logging tools for food, body, appearance, subjective, gut, and experiment mutations.",
+            "Food parsing uses Forge's configured openai-codex ChatGPT subscription connection, not the metered OpenAI Platform API."
+        ],
+        example: '{"userIds":["user_operator"]}'
+    },
+    {
+        toolName: "forge_parse_food_log_with_chatgpt",
+        summary: "Parse natural-language food text or a photo description into a candidate Forge nutrition log through the openai-codex ChatGPT subscription connection.",
+        whenToUse: "Use when the operator describes a meal imprecisely, wants AI-assisted food decomposition, or wants subjective food-effect notes captured alongside nutrition.",
+        inputShape: "{ text?: string, imageDescription?: string, loggedAt?: string, mealLabel?: string, userIds?: string[] }",
+        requiredFields: ["text/imageDescription"],
+        notes: [
+            "Requires a configured openai-codex model connection.",
+            "Returns a candidate log that should be confirmed or corrected when precision matters.",
+            "Do not route this through OpenAI Platform API billing."
+        ],
+        example: '{"text":"3 eggs, sourdough, Greek yogurt with honey, espresso; focused but bloated later","mealLabel":"breakfast"}'
+    },
+    {
+        toolName: "forge_log_food",
+        summary: "Create a food log with explicit food items, calories, macros, quality tags, hunger, satiety, cravings, and context.",
+        whenToUse: "Use for confirmed manual entries, search/barcode-selected foods, or corrected ChatGPT candidates.",
+        inputShape: "{ mealLabel?: string, loggedAt?: string, source?: string, confirmationState?: string, notes?: string, items: Array<{ name, quantity, unit?, caloriesKcal?, proteinG?, carbsG?, fatG?, fiberG?, tags? }>, userIds?: string[] }",
+        requiredFields: ["items"],
+        notes: [
+            "Prefer confirmed entries when the user gave concrete amounts.",
+            "Use candidate entries for rough estimates that need later correction."
+        ],
+        example: '{"mealLabel":"post-workout","items":[{"name":"Greek yogurt","quantity":250,"unit":"g","caloriesKcal":180,"proteinG":25}]}'
+    },
+    {
+        toolName: "forge_log_body_checkin | forge_log_appearance_checkin | forge_log_subjective_food_effect | forge_log_gut_checkin",
+        summary: "Record body composition, aesthetic look, energy/mood/focus/cravings/performance, and gut-comfort check-ins.",
+        whenToUse: "Use alongside food logs to let Forge discover links between eating, sport, visual look, energy, cravings, and gut health.",
+        inputShape: "{ checkedAt?: string, score fields, linkedFoodLogId?: string, notes?: string, userIds?: string[] }",
+        requiredFields: ["at least one metric field"],
+        notes: [
+            "Scores are 0-10 unless the field name gives a physical unit such as kg or cm.",
+            "Link subjective or gut check-ins to a food log when the timing is known."
+        ],
+        example: '{"energy":8,"focus":7,"bloating":2,"timeRelation":"2h after lunch","linkedFoodLogId":"nfl_123"}'
+    },
+    {
+        toolName: "forge_get_nutrition_patterns | forge_start_nutrition_experiment | forge_update_nutrition_experiment",
+        summary: "Review nutrition hypotheses and manage N-of-1 experiments for food, training fuel, gut comfort, cravings, and aesthetic outcomes.",
+        whenToUse: "Use when the operator wants to test a causal idea such as caffeine timing, carb timing, sodium/puffiness, fiber ramp, low-FODMAP trial, or pre-training fueling.",
+        inputShape: "{ title, hypothesis, metricKey, intervention, baseline dates?, experiment dates?, successCriteria?, userIds? }",
+        requiredFields: ["title", "hypothesis", "metricKey", "intervention"],
+        notes: [
+            "Experiments should name the metric being optimized and define success criteria before results are interpreted.",
+            "Forge treats hypotheses as decision aids, not medical diagnosis."
+        ],
+        example: '{"title":"Carbs before kickboxing","hypothesis":"60g carbs 2h before training improves performance without gut discomfort","metricKey":"workoutPerformance","intervention":"60g low-fat carbs before training"}'
+    },
     {
         toolName: "forge_update_sleep_session",
         summary: "Patch one sleep session with reflective notes, tags, or linked Forge context.",
@@ -5208,7 +5273,8 @@ function buildAgentOnboardingPayload(request) {
             batchSearch: "/api/v1/entities/search",
             psycheSchemaCatalog: "/api/v1/psyche/schema-catalog",
             psycheEventTypes: "/api/v1/psyche/event-types",
-            psycheEmotions: "/api/v1/psyche/emotions"
+            psycheEmotions: "/api/v1/psyche/emotions",
+            weightLoss: "/api/v1/health/weight-loss"
         },
         recommendedPluginTools: {
             bootstrap: ["forge_get_operator_overview"],
@@ -5220,6 +5286,7 @@ function buildAgentOnboardingPayload(request) {
                 "forge_get_sleep_overview",
                 "forge_get_sports_overview",
                 "forge_get_training_load_overview",
+                "forge_get_weight_loss_overview",
                 "forge_get_xp_metrics",
                 "forge_get_weekly_review"
             ],
@@ -5251,6 +5318,19 @@ function buildAgentOnboardingPayload(request) {
                 "forge_get_sleep_overview",
                 "forge_get_sports_overview",
                 "forge_get_training_load_overview",
+                "forge_get_weight_loss_overview",
+                "forge_search_foods",
+                "forge_search_nutrition_foods",
+                "forge_lookup_nutrition_barcode",
+                "forge_log_food",
+                "forge_parse_food_log_with_chatgpt",
+                "forge_log_body_checkin",
+                "forge_log_appearance_checkin",
+                "forge_log_subjective_food_effect",
+                "forge_log_gut_checkin",
+                "forge_get_nutrition_patterns",
+                "forge_start_nutrition_experiment",
+                "forge_update_nutrition_experiment",
                 "forge_update_sleep_session",
                 "forge_update_workout_session"
             ],
@@ -5284,6 +5364,10 @@ function buildAgentOnboardingPayload(request) {
             reviewShortcutRule: "When the user is reviewing or correcting an existing record, ask what practical question they want the read or correction to answer, then narrow the saved object, timeframe, or route family first. Do not reopen the whole intake unless the user is actually redefining the record.",
             readModelWriteRule: "Self-observation is note-backed and should be written through observed notes with frontmatter.observedAt only when a lightweight episode observation is the right container. Do not use it as the default bucket for Psyche material: prefer trigger_report for one emotionally meaningful episode, behavior_pattern for functional analysis of a recurring loop, behavior for one repeated move, belief_entry for a core sentence, mode_guide_session or mode_profile for a central part-state, and wiki_page for durable memory such as books, articles, concepts, sources, or personal manuals. Sleep and workout sessions stay on batch CRUD by default; use the reflective review helpers only when enriching one already-known record after review.",
             psycheOpeningQuestionRule: "Prefer a concrete opening question tied to the entity: ask when the value mattered, what happened the last time the pattern appeared, what cue or body signal came first before the behavior, what the belief starts saying about self or outcome, what feels most at risk inside the mode, what the part is trying to get the user to do or stop doing, or where the shift began in the incident. Reflect briefly before the question, choose one follow-up lane at a time, say what is becoming clearer before the next deeper question, and if several Psyche entities are visible hold the adjacent ones lightly until the main container is clear.",
+            psycheHypothesisRule: "When one concrete Psyche example is visible, a helpful hypothesis should start from evidence in the user's own example, offer one testable interpretation, name the function without blame such as protection, prediction, relief, or cost, and ask whether the danger, need, or wording fits. Do not present schema, mode, belief, or pattern language as a verdict. If the user corrects the hypothesis, revise it once and move toward the saveable record shape instead of asking for another broad story.",
+            mixedIntentSequencingRule: "When one user message combines several Forge jobs, identify the primary job and the order of operations before asking a follow-up. If a read changes the truth of a later write, read first: Movement timeline or box detail before correction, Workbench run or node detail before editing or publishing, and Life Force overview before changing durable assumptions when the current energy picture is uncertain. If the user asks to understand and save Psyche material plus create a support record, formulate the primary Psyche record first, then derive the flashcard, note, link, task, or habit from the accepted wording. If the user already gave the concrete action, do not ask a broad lane question; say the product sequence briefly and ask only for the missing span, wording, flow, run, node, weekday, or link that changes the next action.",
+            duplicateDisambiguationRule: "Before creating or updating a normal stored entity when duplicate risk is plausible, search the shared batch entity route by entity type, distinctive title or wording, owner scope, and linked content. If a likely existing record appears, ask whether the user wants to update that record, link to it, or save a separate new record; do not reopen the whole create flow. For Psyche records, a similar belief, pattern, mode, trigger report, value, or flashcard is a formulation choice, not a duplicate error: compare the sentence, cue/payoff/cost, protective job, episode, urge sentence, or message and let the user choose update, link, or new version. For wiki_page and calendar_connection, use dedicated search/list/read routes before creating another page or connection. For Movement, Life Force, and Workbench, use the dedicated read lanes instead of batch duplicate search.",
+            destructiveActionRule: "Before deleting, archiving, invalidating, overwriting, disconnecting, or substantially replacing a Forge record or specialized object, confirm the exact target and what should remain understandable. Prefer normal soft-delete for stored entities unless the user explicitly asks for permanent removal. For Psyche records, preserve therapeutic history by asking whether the old belief, pattern, mode, trigger report, value, or flashcard should be updated, linked as history, archived, or kept distinct; do not delete it just because a cleaner formulation exists. For Movement, distinguish user-defined overlay deletion from automatic-box invalidation and stay/trip/point deletion, and read the specific span first when the target is uncertain. For calendar connections, Workbench flows, wiki pages, and questionnaire instruments, ask what downstream sync, published output, backlinks, run history, or completed runs should remain understandable before deleting or replacing the saved object.",
             followUpQuestionRule: "After a substantive answer, do not restart the opener or jump to the next schema field. First say what became clearer in concrete language, then choose exactly one next lane: wording, boundary, placement, timing, route scope, link, hypothesis, or write confirmation. Ask the smallest question that would change the record shape, route choice, useful wording, timing, or links. If nothing decision-relevant would change, stop asking, summarize the working record, and act with consent.",
             antiDriftRule: "Avoid vague reflective filler and internal route language. Replace phrases like 'that sounds important' with the specific stake you heard, and replace API nouns like surface, CRUD, payload, mutation path, or endpoint with user-facing product nouns such as belief, pattern, note, wiki page, timeline, overlay, weekday template, flow, run, node result, or published output. If a question would only decorate the intake, skip it.",
             duplicateCheckRoute: "/api/v1/entities/search",
@@ -5683,6 +5767,7 @@ function buildV1Context(scope = {
     projectIds: [],
     tagIds: []
 }) {
+    const now = new Date();
     const users = listUsers();
     const { validScopedUserIds, scopedUserIdsForReads } = normalizeScopedUserIdsForReads({
         scope,
@@ -5702,17 +5787,26 @@ function buildV1Context(scope = {
         meta: {
             apiVersion: "v1",
             transport: "rest+sse",
-            generatedAt: new Date().toISOString(),
+            generatedAt: now.toISOString(),
             backend: "forge-node-runtime",
             mode: "transitional-node"
         },
-        metrics: buildGamificationProfile(goals, tasks, habits, new Date(), {
+        metrics: buildGamificationProfile(goals, tasks, habits, now, {
             userIds: scopedUserIdsForReads
         }),
         dashboard,
-        overview: getOverviewContext(new Date(), { userIds: scopedUserIdsForReads }),
-        today: getTodayContext(new Date(), { userIds: scopedUserIdsForReads }),
-        risk: getRiskContext(new Date(), { userIds: scopedUserIdsForReads }),
+        overview: getOverviewContext(now, {
+            userIds: scopedUserIdsForReads,
+            dashboard
+        }),
+        today: getTodayContext(now, {
+            userIds: scopedUserIdsForReads,
+            dashboard
+        }),
+        risk: getRiskContext(now, {
+            userIds: scopedUserIdsForReads,
+            dashboard
+        }),
         goals,
         projects,
         tags: listTags(),
@@ -5730,7 +5824,7 @@ function buildV1Context(scope = {
             ? []
             : listTaskRuns({ active: true, limit: 25, userIds: scopedUserIdsForReads }),
         activity: dashboard.recentActivity,
-        lifeForce: buildLifeForcePayload(new Date(), scopedUserIdsForReads)
+        lifeForce: buildLifeForcePayload(now, scopedUserIdsForReads)
     };
 }
 function buildXpMetricsPayload(input = {}) {
@@ -6302,6 +6396,42 @@ function compactVitals(vitals) {
         detailRoute: "/api/v1/health/vitals"
     };
 }
+function compactWeightLoss(weightLoss) {
+    return {
+        generatedAt: weightLoss.generatedAt,
+        userId: weightLoss.userId,
+        summary: weightLoss.summary,
+        todayLedger: {
+            dateKey: weightLoss.todayLedger.dateKey,
+            mealCount: weightLoss.todayLedger.meals.length,
+            totals: weightLoss.todayLedger.totals,
+            targetCalories: weightLoss.todayLedger.targetCalories,
+            calorieDelta: weightLoss.todayLedger.calorieDelta,
+            proteinCoverage: weightLoss.todayLedger.proteinCoverage,
+            fiberCoverage: weightLoss.todayLedger.fiberCoverage,
+            unconfirmedCount: weightLoss.todayLedger.unconfirmedCount
+        },
+        energyModel: {
+            estimatedTdeeKcal: weightLoss.energyModel.estimatedTdeeKcal,
+            activeBurnKcal: weightLoss.energyModel.activeBurnKcal,
+            movementCaloriesKcal: weightLoss.energyModel.movementCaloriesKcal,
+            averageCalorieIntake: weightLoss.energyModel.averageCalorieIntake,
+            estimatedDailyEnergyBalanceKcal: weightLoss.energyModel.estimatedDailyEnergyBalanceKcal,
+            wearableConfidence: weightLoss.energyModel.wearableConfidence
+        },
+        weightTrend: weightLoss.weightTrend,
+        foodQuality: weightLoss.foodQuality,
+        trainingFuel: weightLoss.trainingFuel,
+        subjective: weightLoss.subjective,
+        gut: weightLoss.gut,
+        topHypotheses: weightLoss.hypotheses.slice(0, 4),
+        activeExperiments: weightLoss.experiments
+            .filter((experiment) => experiment.status !== "completed")
+            .slice(0, 4),
+        dataQuality: weightLoss.dataQuality,
+        detailRoute: "/api/v1/health/weight-loss"
+    };
+}
 function compactLifeForce(lifeForce) {
     return {
         userId: lifeForce.userId,
@@ -6567,6 +6697,7 @@ function buildOperatorOverview(request) {
     const fitness = compactFitness(getFitnessViewData(userIds));
     const trainingLoad = compactTrainingLoad(getTrainingLoadViewData(userIds));
     const vitals = compactVitals(getVitalsViewData(userIds));
+    const weightLoss = compactWeightLoss(getWeightLossViewData(userIds));
     const lifeForce = compactLifeForce(buildLifeForcePayload(now, userIds));
     const psyche = canReadPsyche ? compactPsyche(getPsycheOverview(userIds)) : null;
     const onboarding = compactOnboardingPayload(buildAgentOnboardingPayload(request));
@@ -6649,6 +6780,7 @@ function buildOperatorOverview(request) {
         fitness,
         trainingLoad,
         vitals,
+        weightLoss,
         lifeForce,
         domains: listDomains().map((domain) => ({
             id: domain.id,
@@ -7332,6 +7464,118 @@ export async function buildServer(options = {}) {
     app.get("/api/v1/health/vitals", async (request) => ({
         vitals: getVitalsViewData(resolveScopedUserIds(request.query))
     }));
+    app.get("/api/v1/health/weight-loss", async (request) => ({
+        weightLoss: getWeightLossViewData(resolveScopedUserIds(request.query))
+    }));
+    app.patch("/api/v1/health/weight-loss/target", async (request) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/target"
+        });
+        return {
+            target: updateNutritionTarget(nutritionTargetUpdateSchema.parse(request.body ?? {}))
+        };
+    });
+    app.post("/api/v1/health/weight-loss/foods/search", async (request) => ({
+        ...(await searchNutritionFoods(nutritionFoodSearchSchema.parse(request.body ?? {})))
+    }));
+    app.post("/api/v1/health/weight-loss/foods/barcode", async (request) => ({
+        ...(await lookupNutritionBarcode(nutritionBarcodeLookupSchema.parse(request.body ?? {})))
+    }));
+    app.post("/api/v1/health/weight-loss/food-logs", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/food-logs"
+        });
+        const foodLog = createNutritionFoodLog(nutritionFoodLogCreateSchema.parse(request.body ?? {}));
+        reply.code(201);
+        return { log: foodLog };
+    });
+    app.patch("/api/v1/health/weight-loss/food-logs/:id", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/food-logs/:id"
+        });
+        const foodLog = patchNutritionFoodLog(request.params.id, nutritionFoodLogPatchSchema.parse(request.body ?? {}));
+        if (!foodLog) {
+            reply.code(404);
+            return { error: "Food log not found" };
+        }
+        return { log: foodLog };
+    });
+    app.delete("/api/v1/health/weight-loss/food-logs/:id", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/food-logs/:id"
+        });
+        const foodLog = deleteNutritionFoodLog(request.params.id);
+        if (!foodLog) {
+            reply.code(404);
+            return { error: "Food log not found" };
+        }
+        return { deleted: true };
+    });
+    app.post("/api/v1/health/weight-loss/parse", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/parse"
+        });
+        reply.code(201);
+        return await parseNutritionFoodLogWithChatGpt(nutritionParseRequestSchema.parse(request.body ?? {}), managers.llm);
+    });
+    app.post("/api/v1/health/weight-loss/body-checkins", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/body-checkins"
+        });
+        const bodyCheckin = createNutritionBodyCheckin(nutritionBodyCheckinCreateSchema.parse(request.body ?? {}));
+        reply.code(201);
+        return { checkin: bodyCheckin };
+    });
+    app.post("/api/v1/health/weight-loss/appearance-checkins", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/appearance-checkins"
+        });
+        const appearanceCheckin = createNutritionAppearanceCheckin(nutritionAppearanceCheckinCreateSchema.parse(request.body ?? {}));
+        reply.code(201);
+        return { checkin: appearanceCheckin };
+    });
+    app.post("/api/v1/health/weight-loss/subjective-checkins", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/subjective-checkins"
+        });
+        const subjectiveCheckin = createNutritionSubjectiveCheckin(nutritionSubjectiveCheckinCreateSchema.parse(request.body ?? {}));
+        reply.code(201);
+        return { checkin: subjectiveCheckin };
+    });
+    app.post("/api/v1/health/weight-loss/gut-checkins", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/gut-checkins"
+        });
+        const gutCheckin = createNutritionGutCheckin(nutritionGutCheckinCreateSchema.parse(request.body ?? {}));
+        reply.code(201);
+        return { checkin: gutCheckin };
+    });
+    app.get("/api/v1/health/weight-loss/patterns", async (request) => {
+        const weightLoss = getWeightLossViewData(resolveScopedUserIds(request.query));
+        return {
+            hypotheses: weightLoss.hypotheses,
+            experiments: weightLoss.experiments
+        };
+    });
+    app.post("/api/v1/health/weight-loss/experiments", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/experiments"
+        });
+        const experiment = createNutritionExperiment(nutritionExperimentCreateSchema.parse(request.body ?? {}));
+        reply.code(201);
+        return { experiment };
+    });
+    app.patch("/api/v1/health/weight-loss/experiments/:id", async (request, reply) => {
+        requireScopedAccess(request.headers, ["write"], {
+            route: "/api/v1/health/weight-loss/experiments/:id"
+        });
+        const experiment = patchNutritionExperiment(request.params.id, nutritionExperimentPatchSchema.parse(request.body ?? {}));
+        if (!experiment) {
+            reply.code(404);
+            return { error: "Nutrition experiment not found" };
+        }
+        return { experiment };
+    });
     app.get("/api/v1/health/zone-profile", async (request) => {
         const userIds = resolveScopedUserIds(request.query);
         return {
@@ -7878,6 +8122,15 @@ export async function buildServer(options = {}) {
             watch: buildWatchBootstrap(pairing)
         };
     });
+    app.post("/api/v1/mobile/watch/actions:batch", async (request) => {
+        const parsed = mobileWatchCommandBatchSchema.parse(request.body ?? {});
+        const pairing = requireValidPairing(parsed.sessionId, parsed.pairingToken);
+        assertWatchReady(pairing);
+        return {
+            receipt: ingestWatchCommandBatch(pairing, parsed),
+            watch: buildWatchBootstrap(pairing)
+        };
+    });
     app.post("/api/v1/mobile/healthkit/sync-sessions", async (request) => ({
         upload: startMobileHealthSyncSession(mobileHealthSyncSessionStartSchema.parse(request.body ?? {}))
     }));