forge-openclaw-plugin 0.2.93 → 0.2.94

package/dist/server/server/src/openapi.js

@@ -3165,6 +3165,7 @@ export function buildOpenApiDocument() {
             "notes",
             "sleep",
             "fitness",
+            "trainingLoad",
             "vitals",
             "lifeForce",
             "domains",
@@ -3228,6 +3229,11 @@ export function buildOpenApiDocument() {
                 additionalProperties: true,
                 description: "Compact sports summary with recent workout IDs and the full fitness route."
             },
+            trainingLoad: {
+                type: "object",
+                additionalProperties: true,
+                description: "Compact cardiovascular training-load summary with acute/chronic load, intensity distribution, and the full training-load route."
+            },
             vitals: {
                 type: "object",
                 additionalProperties: true,
@@ -5161,6 +5167,42 @@ export function buildOpenApiDocument() {
             sessions: arrayOf({ $ref: "#/components/schemas/WorkoutSession" })
         }
     };
+    const trainingLoadViewData = {
+        type: "object",
+        additionalProperties: false,
+        required: [
+            "summary",
+            "zoneTotals",
+            "recentZoneTotals",
+            "intensityDistribution",
+            "recentIntensityDistribution",
+            "dailyLoad",
+            "weeklyLoad",
+            "activityBreakdown",
+            "vitalsTrend",
+            "sessionSignals",
+            "targetModel"
+        ],
+        properties: {
+            summary: { type: "object", additionalProperties: true },
+            zoneTotals: arrayOf({ type: "object", additionalProperties: true }),
+            recentZoneTotals: arrayOf({ type: "object", additionalProperties: true }),
+            intensityDistribution: arrayOf({
+                type: "object",
+                additionalProperties: true
+            }),
+            recentIntensityDistribution: arrayOf({
+                type: "object",
+                additionalProperties: true
+            }),
+            dailyLoad: arrayOf({ type: "object", additionalProperties: true }),
+            weeklyLoad: arrayOf({ type: "object", additionalProperties: true }),
+            activityBreakdown: arrayOf({ type: "object", additionalProperties: true }),
+            vitalsTrend: arrayOf({ type: "object", additionalProperties: true }),
+            sessionSignals: arrayOf({ type: "object", additionalProperties: true }),
+            targetModel: { type: "object", additionalProperties: true }
+        }
+    };
     const document = {
         openapi: "3.1.0",
         info: {
@@ -5272,6 +5314,7 @@ export function buildOpenApiDocument() {
                 WorkoutSession: workoutSession,
                 SleepViewData: sleepViewData,
                 FitnessViewData: fitnessViewData,
+                TrainingLoadViewData: trainingLoadViewData,
                 PsycheMetricsViewData: psycheMetricsViewData,
                 PsycheOverviewPayload: psycheOverviewPayload,
                 Insight: insight,
@@ -5563,6 +5606,22 @@ export function buildOpenApiDocument() {
                     }
                 }
             },
+            "/api/v1/health/training-load": {
+                get: {
+                    summary: "Read the Forge cardiovascular training load and target overview surface",
+                    responses: {
+                        "200": jsonResponse({
+                            type: "object",
+                            required: ["trainingLoad"],
+                            properties: {
+                                trainingLoad: {
+                                    $ref: "#/components/schemas/TrainingLoadViewData"
+                                }
+                            }
+                        }, "Training load overview")
+                    }
+                }
+            },
             "/api/v1/health/workouts": {
                 post: {
                     summary: "Create one manual workout session",

package/dist/server/src/lib/api.js

@@ -1734,6 +1734,12 @@ export function getFitnessView(userIds) {
     const suffix = search.size > 0 ? `?${search.toString()}` : "";
     return request(`/api/v1/health/fitness${suffix}`);
 }
+export function getTrainingLoadView(userIds) {
+    const search = new URLSearchParams();
+    appendUserIds(search, coerceUserIds(userIds));
+    const suffix = search.size > 0 ? `?${search.toString()}` : "";
+    return request(`/api/v1/health/training-load${suffix}`);
+}
 export function getWorkoutDetail(workoutId, resolution = "adaptive") {
     const search = new URLSearchParams({ resolution });
     return request(`/api/v1/health/workouts/${workoutId}/detail?${search.toString()}`);

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "forge-openclaw-plugin",
   "name": "Forge",
   "description": "Curated OpenClaw adapter for the Forge collaboration API, UI entrypoint, and localhost auto-start runtime.",
-  "version": "0.2.93",
+  "version": "0.2.94",
   "activation": {
     "onStartup": true,
     "onCapabilities": [
@@ -51,6 +51,7 @@
       "forge_get_self_observation_calendar",
       "forge_get_sleep_overview",
       "forge_get_sports_overview",
+      "forge_get_training_load_overview",
       "forge_get_ui_entrypoint",
       "forge_get_user_directory",
       "forge_get_weekly_review",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-openclaw-plugin",
-  "version": "0.2.93",
+  "version": "0.2.94",
   "description": "Curated OpenClaw adapter for the Forge collaboration API, UI entrypoint, and localhost auto-start runtime.",
   "type": "module",
   "license": "Apache-2.0",

package/skills/forge-openclaw/SKILL.md

@@ -199,14 +199,16 @@ Wiki navigation and search rule:
 Health rule:
 
 - Sleep and sports records are first-class health surfaces, not generic notes or tasks.
-- Use `forge_get_sleep_overview` and `forge_get_sports_overview` for review and trend reading.
+- Use `forge_get_sleep_overview`, `forge_get_sports_overview`, and
+  `forge_get_training_load_overview` for health review and trend reading.
 - In `forge_get_agent_onboarding.entityRouteModel.readModelOnlySurfaces`, operator,
-  calendar, self-observation, sleep, and sports read models are published with
+  calendar, self-observation, sleep, sports, and training-load read models are published with
   both camelCase names and entity-style aliases where useful, including
   `operatorOverview`, `operatorContext`, `calendarOverview`, `sleepOverview`,
-  `sportsOverview`, `operator_overview`, `operator_context`,
-  `calendar_overview`, `self_observation`, `sleep_overview`, and
-  `sports_overview`. Treat those as read-only surfaces, not batch CRUD entities.
+  `sportsOverview`, `trainingLoad`, `operator_overview`, `operator_context`,
+  `calendar_overview`, `self_observation`, `sleep_overview`,
+  `sports_overview`, and `training_load`. Treat those as read-only surfaces,
+  not batch CRUD entities.
 - Use `forge_get_operator_overview` for a broad Forge status read, `forge_get_operator_context`
   for current work and risk, and `forge_get_calendar_overview` before calendar-aware
   planning or scheduling mutations.
@@ -524,7 +526,7 @@ Use the wiki tools for SQLite-backed memory work:
 `forge_get_wiki_settings`, `forge_list_wiki_pages`, `forge_get_wiki_page`, `forge_search_wiki`, `forge_upsert_wiki_page`, `forge_get_wiki_health`, `forge_sync_wiki_vault`, `forge_reindex_wiki_embeddings`, `forge_ingest_wiki_source`
 
 Use the health tools for review and reflective enrichment, not as the default CRUD architecture:
-`forge_get_sleep_overview`, `forge_get_sports_overview`, `forge_update_sleep_session`, `forge_update_workout_session`
+`forge_get_sleep_overview`, `forge_get_sports_overview`, `forge_get_training_load_overview`, `forge_update_sleep_session`, `forge_update_workout_session`
 
 Use the dedicated domain routes for specialized surfaces that are not simple batch entities:
 
@@ -679,9 +681,10 @@ Use the health tools when the request is about sleep or sports review:
 
 - `forge_get_sleep_overview` to inspect recent nights, averages, regularity, stage breakdown, and linked reflective context
 - `forge_get_sports_overview` to inspect training volume, workout types, effort trends, habit-generated sessions, and linked context
+- `forge_get_training_load_overview` to inspect cardiovascular load, HR zone balance, acute/chronic stress, high-intensity pressure, VO2max context, and training target fit
 - `forge_update_sleep_session` to add sleep-quality notes, tags, or links back to Forge entities after review
 - `forge_update_workout_session` to add subjective effort, mood, meaning, tags, or links on one workout after review
-- remember that the UI route is `/sports` while the backend overview route is `/api/v1/health/fitness`
+- remember that the UI route is `/sports` while the backend overview route is `/api/v1/health/fitness`; the dedicated training-load UI is `/training-load` and its backend route is `/api/v1/health/training-load`
 
 Use these exact health batch payload shapes when the user is creating or editing the stored records themselves:
 
@@ -776,6 +779,7 @@ When the user asks which Forge tools are available, list exactly these tools:
 `forge_get_current_work`
 `forge_get_sleep_overview`
 `forge_get_sports_overview`
+`forge_get_training_load_overview`
 `forge_update_sleep_session`
 `forge_update_workout_session`
 `forge_get_preferences_workspace`

package/skills/forge-openclaw/entity_conversation_playbooks.md

@@ -257,10 +257,10 @@ Use this quick split before the conversation gets too detailed.
   the user is trying to do, then use the dedicated action tool or note-backed write
   model.
 - `operator_overview`, `operator_context`, `calendar_overview`, `sleep_overview`,
-  and `sports_overview` are read-model-only surfaces. Use them when the user wants
-  to understand current Forge state, work risk, calendar commitments, nights,
-  workouts, training load, recovery context, or health patterns before deciding
-  whether a stored entity needs creation or enrichment.
+  `sports_overview`, and `training_load` are read-model-only surfaces. Use them
+  when the user wants to understand current Forge state, work risk, calendar
+  commitments, nights, workouts, cardiovascular load, recovery context, or health
+  patterns before deciding whether a stored entity needs creation or enrichment.
 - Movement, Life Force, and Workbench are specialized domain areas. Use their
   dedicated route families for timelines and overlays, energy profile/templates and
   fatigue signals, and Workbench flow execution or result artifacts. When available,
@@ -332,9 +332,17 @@ still knowing the exact write/read family before it acts.
   score, stages, or recovery patterns before deciding whether a specific
   `sleep_session` needs reflective enrichment.
 - `sports_overview`: read-model-only health surface. Use the sports overview route or
-  `forge_get_sports_overview` when the user wants to review workouts, training load,
-  effort, type distribution, or recovery context before deciding whether a specific
-  `workout_session` needs reflective enrichment.
+  `forge_get_sports_overview` when the user wants to review workouts, effort, type
+  distribution, or recovery context before deciding whether a specific
+  `workout_session` needs reflective enrichment. Use
+  `forge_get_training_load_overview` or `/api/v1/health/training-load` for
+  cardiovascular load, HR zone balance, acute/chronic stress, VO2max context, or
+  training target questions.
+- `training_load`: read-model-only health surface. Use
+  `forge_get_training_load_overview` or `/api/v1/health/training-load` when the
+  user wants training-load trends, acute/chronic ratio, HR zone distribution,
+  threshold exposure, VO2max/resting-HR context, or optimization targets before
+  deciding whether a specific `workout_session` needs notes or links.
 - `movement`: specialized domain surface. Use the dedicated movement routes for day,
   month, all-time, timeline, places, trip detail, selection aggregates, manual
   overlays, and repair actions.
@@ -1360,14 +1368,15 @@ Preferred opening question:
 
 ## Sports Overview
 
-Aim: review workout and training-load context before deciding whether one workout
-needs a reflective update or recovery follow-up.
+Aim: review workout context before deciding whether one workout needs a
+reflective update, and route deeper cardiovascular load questions to the
+training-load read model.
 
 Arc:
 
 1. Ask what the user wants to understand from the sports picture: one workout, a
-   recent training trend, effort, volume, type mix, recovery, or links to mood and
-   goals.
+   recent training trend, effort, volume, type mix, recovery, zone balance, or
+   links to mood and goals.
 2. Read the sports overview before asking the user to reconstruct metrics from memory.
 3. Reflect the practical decision the review should support.
 4. Move to `workout_session` enrichment only when one specific workout needs context,
@@ -1382,8 +1391,12 @@ Helpful follow-up lanes:
 Route note:
 
 - `sports_overview` is a read-model-only surface. Use `forge_get_sports_overview` or
-  `/api/v1/health/fitness` for review. Do not create, update, or delete
+  `/api/v1/health/fitness` for session review. Do not create, update, or delete
   `sports_overview` through batch CRUD.
+- For cardiovascular load, HR zone distribution, acute/chronic load, VO2max
+  context, or training target questions, use `forge_get_training_load_overview`
+  or `/api/v1/health/training-load`. Treat `training_load` as read-model-only,
+  not a batch CRUD entity.
 - If the review reveals that one workout needs reflective context, switch to the
   stored `workout_session` batch route or reflective update helper for that known
   session.
@@ -1397,6 +1410,50 @@ Preferred opening question:
 
 - "What are you trying to understand from your workout picture right now?"
 
+## Training Load
+
+Aim: review cardiovascular load and training targets before deciding whether one
+workout needs reflective enrichment or a recovery/target adjustment.
+
+Arc:
+
+1. Ask what practical decision the user wants to support: build aerobic base,
+   control overload risk, preserve hard-day quality, understand combat-sport
+   intensity, or compare recent load against chronic base.
+2. Read the training-load overview before asking the user to reconstruct zones,
+   VO2max, or recent hard sessions from memory.
+3. Reflect the load signal with explicit confidence: HR coverage, sensor limits,
+   recent sample count, and whether kickboxing/wrist HR may be noisy.
+4. Move to `workout_session` enrichment only when one specific workout needs
+   notes, tags, context, or links.
+
+Helpful follow-up lanes:
+
+- whether the question is adaptation, overload risk, zone target, VO2max trend,
+  sport contribution, or one recent session
+- which date range matters if the default 7-day and 28-day windows are not enough
+- whether the user is optimizing health, performance, recovery, or a specific
+  upcoming training block
+
+Route note:
+
+- `training_load` is a read-model-only surface. Use
+  `forge_get_training_load_overview` or `/api/v1/health/training-load` for
+  cardiovascular load, HR zone distribution, acute/chronic load, VO2max context,
+  and training target analysis. Do not create, update, or delete `training_load`
+  through batch CRUD.
+- If one workout needs subjective effort, meaning, social context, or links,
+  switch to the stored `workout_session` batch route or reflective update helper.
+
+Ready to review when:
+
+- the user's practical adaptation or recovery question is clear
+- the relevant time window or default 7-day/28-day comparison is acceptable
+
+Preferred opening question:
+
+- "What training-load decision are you trying to support right now?"
+
 ## Calendar Overview
 
 Aim: review commitments, work blocks, provider state, and existing timeboxes before