oomi-ai 0.3.3 → 0.3.5

package/README.md

@@ -150,6 +150,7 @@ Optional fields:
 Component-composed persona apps are the default Oomi mini-app path. Use these commands when the user asks about or updates an existing Oomi persona app such as Fitness Today:
 
 ```bash
+oomi fitness show --json
 oomi persona-apps list --json
 oomi persona-apps show fitness-today --json
 oomi persona-apps apply-action fitness-today --action fitness.complete_workout --payload-json '{"goalId":"easy-run","minutes":20}' --json
@@ -158,17 +159,21 @@ oomi persona-apps apply-action fitness-today --action fitness.complete_workout -
 Rules for agents:
 
 - Answer from returned `appState.bindings`, not from memory.
+- For Fitness questions, prefer `oomi fitness show --json` because it returns the Fitness mini-app state and approved health context together.
 - Apply updates only through approved `persona-apps apply-action` actions.
 - If the persona app does not exist, tell the user to add it from the Oomi client first.
 - Do not create local persona UI projects.
 
-For the Fitness v0 slice:
+For the Fitness slice:
 
 ```bash
+oomi persona-apps apply-action fitness-today --action fitness.set_goal --payload-json '{"goalId":"move_more"}' --json
 oomi persona-apps apply-action fitness-today --action fitness.complete_goal --payload-json '{"goalId":"easy-run"}' --json
 oomi persona-apps apply-action fitness-today --action fitness.complete_workout --payload-json '{"goalId":"easy-run","minutes":20}' --json
 ```
 
+Supported `fitness.set_goal` values are `move_more`, `sleep_better`, and `build_workout_habit`.
+
 ## Context Tools
 
 Use context tools when the user asks a data-backed question that should come from Oomi-approved mobile permissions, not model memory. For health and fitness questions, read the latest backend HealthKit context first:
@@ -181,9 +186,10 @@ Rules for agents:
 
 - Answer from `healthContext.summary` and `healthContext.derived`.
 - Respect `healthContext.agentGuidance.canAnswerFromContext`.
-- If context is `missing`, `needs_sync`, `permission_denied`, `disabled_by_user`, or `unavailable`, tell the user what repair action is needed instead of guessing.
-- If context is `stale`, mention freshness when timing matters.
-- To request a fresh phone-side HealthKit sync, run `oomi context health sync --json`. The iPhone app must open or refresh before it can read Apple Health and fulfill the pending request.
+- If `healthContext.agentGuidance.recommendedCommand` is present, run it before answering current/latest health questions.
+- If context is `stale` or `needs_sync`, run `oomi context health sync --wait --json`; answer only after fresh context is uploaded, or tell the user the phone sync is still pending if it times out.
+- If context is `missing`, `permission_denied`, `disabled_by_user`, or `unavailable`, tell the user what repair action is needed instead of guessing.
+- Never present stale HealthKit values as current values.
 - Do not ask the phone for HealthKit directly; the Oomi mobile app syncs HealthKit to the backend.
 
 ## Voice Contract

package/agent_instructions.md

@@ -12,6 +12,7 @@ Get OpenClaw into a state where:
 - Oomi device-backed voice can start cleanly
 - the bridge is supervised or restartable
 - component-composed persona apps can be inspected and updated through Oomi API tools
+- Fitness state can be inspected with one command that combines mini-app state and approved health context
 - approved user context, such as HealthKit data synced by the Oomi mobile app, can be read through Oomi backend context tools
 - the user never has to paste raw pair identifiers or gateway secrets manually when managed connect is available
 
@@ -248,8 +249,17 @@ When a user asks about an existing persona app:
 4. To update state, use a validated action: `oomi persona-apps apply-action <slug> --action <action-id> --payload-json '<json>' --json`.
 5. If `persona-apps list` returns no app for the user's request, tell the user they can add that persona from the Oomi client so the client can collect the right permissions and data sources.
 
-For the Fitness v0 slice:
+For Fitness questions, prefer the combined read command first:
 
+```bash
+oomi fitness show --json
+```
+
+It returns the linked Fitness persona app plus the latest approved health context in one payload.
+
+For the Fitness slice:
+
+- Use `fitness.set_goal` with payload `{"goalId":"move_more"}`, `{"goalId":"sleep_better"}`, or `{"goalId":"build_workout_habit"}` to set the active focus.
 - Use `fitness.complete_goal` with payload `{"goalId":"easy-run"}` to mark a known goal complete.
 - Use `fitness.complete_workout` with payload like `{"goalId":"easy-run","minutes":20}` when the user says they finished a workout.
 
@@ -276,8 +286,9 @@ Rules:
 
 - Answer only from `healthContext.summary` and `healthContext.derived`.
 - Respect `healthContext.agentGuidance.canAnswerFromContext`.
-- If `canAnswerFromContext` is false, tell the user the relevant `healthContext.repair.label` or `healthContext.repair.reason`.
-- If `healthContext.status` is `stale`, mention that the latest HealthKit sync may be out of date when timing matters.
-- If the user asks you to refresh stale HealthKit context, run `oomi context health sync --json`; tell the user the iPhone app must be opened for Oomi to read Apple Health and fulfill the pending sync.
+- If `healthContext.agentGuidance.recommendedCommand` is present, run it before answering current/latest health questions.
+- If `healthContext.status` is `stale` or `needs_sync`, run `oomi context health sync --wait --json`; answer only after fresh context is uploaded, or tell the user the phone sync is still pending if it times out.
+- If `canAnswerFromContext` is false and no sync command is recommended, tell the user the relevant `healthContext.repair.label` or `healthContext.repair.reason`.
+- Never present stale HealthKit values as current values.
 - Do not infer unavailable health fields.
 - Do not request HealthKit directly from the phone; the Oomi mobile app owns permission prompts and syncs approved data to the backend.

package/bin/oomi-ai.js

@@ -79,6 +79,12 @@ function parsePositiveInteger(value, fallback) {
   return Math.floor(num);
 }
 
+function delay(ms) {
+  return new Promise((resolve) => {
+    setTimeout(resolve, ms);
+  });
+}
+
 function readJsonSafe(filePath) {
   if (!fs.existsSync(filePath)) return null;
   try {
@@ -227,10 +233,14 @@ Commands:
   persona-apps apply-action <slug>
     Apply an approved persona app action through the Oomi backend.
 
+  fitness show
+    Show the linked Fitness persona app plus approved health context.
+
   context health
     Show the latest account-linked health context available to this paired OpenClaw device.
-  context health sync
+  context health sync [--wait]
     Request the linked Oomi mobile app to sync fresh HealthKit context.
+    Use --wait to poll until fresh context is uploaded or the timeout expires.
 
 Common flags:
   --agents-file PATH     Override AGENTS.md path
@@ -577,11 +587,73 @@ async function handleContextHealthCommand(flags = {}) {
   printStructuredResult(payload, isTruthyFlag(flags.json));
 }
 
+async function handleFitnessShowCommand(flags = {}) {
+  const client = createCliPersonaApiClient(flags);
+  const listPayload = await client.listPersonaApps();
+  const personaApps = Array.isArray(listPayload?.personaApps) ? listPayload.personaApps : [];
+  const fitnessApp = personaApps.find((app) => app?.personaType === 'fitness') ||
+    personaApps.find((app) => app?.slug === 'fitness-today');
+
+  if (!fitnessApp?.slug) {
+    throw new Error('Fitness persona app is not linked. Ask the user to add Fitness from the Oomi client first.');
+  }
+
+  const appPayload = await client.getPersonaApp({ slug: fitnessApp.slug });
+  let healthPayload = null;
+  let healthContextError = null;
+  try {
+    healthPayload = await client.getHealthContext();
+  } catch (err) {
+    healthContextError = err?.message || String(err);
+  }
+
+  printStructuredResult({
+    ok: true,
+    personaApp: appPayload?.personaApp || null,
+    healthContext: healthPayload?.healthContext || null,
+    healthContextError,
+  }, isTruthyFlag(flags.json));
+}
+
 async function handleContextHealthSyncCommand(flags = {}) {
   const client = createCliPersonaApiClient(flags);
   const payload = await client.requestHealthContextSync({
     reason: flags.reason || 'agent_requested',
   });
+
+  if (isTruthyFlag(flags.wait)) {
+    const previousCapturedAt = payload?.healthContext?.source?.capturedAt || null;
+    const timeoutMs = parsePositiveInteger(flags['timeout-ms'] || flags.timeoutMs, 30_000);
+    const pollMs = parsePositiveInteger(flags['poll-ms'] || flags.pollMs, 3_000);
+    const startedAt = Date.now();
+    let latestPayload = payload;
+
+    while (Date.now() - startedAt < timeoutMs) {
+      await delay(pollMs);
+      latestPayload = await client.getHealthContext();
+      const healthContext = latestPayload?.healthContext;
+      const capturedAt = healthContext?.source?.capturedAt || null;
+      if (healthContext?.status === 'ready' && (!previousCapturedAt || capturedAt !== previousCapturedAt)) {
+        printStructuredResult({
+          ...payload,
+          refreshed: true,
+          waitedMs: Date.now() - startedAt,
+          healthContext,
+        }, isTruthyFlag(flags.json));
+        return;
+      }
+    }
+
+    printStructuredResult({
+      ...payload,
+      refreshed: false,
+      waitedMs: Date.now() - startedAt,
+      waitTimedOut: true,
+      healthContext: latestPayload?.healthContext || payload.healthContext,
+    }, isTruthyFlag(flags.json));
+    return;
+  }
+
   printStructuredResult(payload, isTruthyFlag(flags.json));
 }
 
@@ -4331,6 +4403,11 @@ async function main() {
     return;
   }
 
+  if (command === 'fitness' && subcommand === 'show') {
+    await handleFitnessShowCommand(args.flags);
+    return;
+  }
+
   if (command === 'context' && subcommand === 'health') {
     if (args.positionals[0] === 'sync') {
       await handleContextHealthSyncCommand(args.flags);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oomi-ai",
-  "version": "0.3.3",
+  "version": "0.3.5",
   "description": "Managed Oomi channel, bridge, voice, and persona app API tooling for OpenClaw",
   "bin": {
     "oomi": "bin/oomi-ai.js"

package/persona-app/README.md

@@ -19,23 +19,26 @@ The current files are the first shared contract for the vertical slice:
 OpenClaw agents should use the packaged CLI to inspect and update account-linked persona apps:
 
 ```bash
+oomi fitness show --json
 oomi persona-apps list --json
 oomi persona-apps show fitness-today --json
 oomi persona-apps apply-action fitness-today --action fitness.complete_workout --payload-json '{"goalId":"easy-run","minutes":20}' --json
 ```
 
+For Fitness, prefer `oomi fitness show --json` before answering because it returns the mini-app state and approved health context together.
+
 When answering data-backed health or fitness questions, agents should read approved backend context first:
 
 ```bash
 oomi context health --json
 ```
 
-If the user asks you to refresh stale HealthKit context, run:
+If the user asks for current/latest health context and the context is stale or needs sync, run:
 
 ```bash
-oomi context health sync --json
+oomi context health sync --wait --json
 ```
 
-The iPhone app must open or refresh before it can read Apple Health and fulfill the pending request.
+Answer only after fresh context is uploaded. If the command times out, tell the user the phone sync is still pending.
 
 If a persona app is missing, ask the user to add it from the Oomi client first so platform-specific permissions and hydration can run.

package/persona-app/registry/v1.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": "persona-app.v1",
-  "registryVersion": "2026-04-24.1",
+  "registryVersion": "2026-04-25.1",
   "contextTools": [
     {
       "id": "health.context.read",
@@ -34,6 +34,21 @@
           "description": "Daily movement summary with progress, steps, and sleep context.",
           "targets": ["ios", "android", "web"]
         },
+        {
+          "type": "fitness.dataFreshnessCard",
+          "description": "Shows whether mobile health context is fresh enough for decisions and nudges.",
+          "targets": ["ios", "android", "web"]
+        },
+        {
+          "type": "fitness.dailyPlanCard",
+          "description": "Goal-aware daily plan generated from approved health context.",
+          "targets": ["ios", "android", "web"]
+        },
+        {
+          "type": "fitness.goalEditorCard",
+          "description": "Lets the user select one active fitness focus from approved Oomi goals.",
+          "targets": ["ios", "android", "web"]
+        },
         {
           "type": "fitness.goalChecklist",
           "description": "Checklist of suggested goals for today.",
@@ -72,6 +87,20 @@
               "minutes": { "type": "integer", "minimum": 1 }
             }
           }
+        },
+        {
+          "id": "fitness.set_goal",
+          "description": "Sets the user's active Fitness focus so Oomi can tune the mini-app and future nudges.",
+          "payloadSchema": {
+            "type": "object",
+            "required": ["goalId"],
+            "properties": {
+              "goalId": {
+                "type": "string",
+                "enum": ["move_more", "sleep_better", "build_workout_habit"]
+              }
+            }
+          }
         }
       ],
       "permissions": [

package/skills/oomi/SKILL.md

@@ -101,18 +101,25 @@ Interpret bridge states like this:
 Component-composed persona apps are the default Oomi mini-app path. Use these commands when the user asks about or updates an existing native/web Oomi persona app such as Fitness Today:
 
 ```bash
+oomi fitness show --json
 oomi persona-apps list --json
 oomi persona-apps show fitness-today --json
 oomi persona-apps apply-action fitness-today --action fitness.complete_workout --payload-json '{"goalId":"easy-run","minutes":20}' --json
 ```
 
 Rules:
+- prefer `oomi fitness show --json` for Fitness questions because it combines mini-app state and approved health context
 - answer from returned `appState.bindings`, not from memory
 - apply updates through approved `persona-apps apply-action` actions
 - if the persona app does not exist, ask the user to add it from the Oomi client first so permissions and hydration can run
 - do not create local persona UI projects from the OpenClaw machine
 - do not execute persona UI jobs or start local persona app runtimes
 
+Supported Fitness actions include:
+- `fitness.set_goal` with `{"goalId":"move_more"}`, `{"goalId":"sleep_better"}`, or `{"goalId":"build_workout_habit"}`
+- `fitness.complete_goal`
+- `fitness.complete_workout`
+
 ## Permissioned Context Tools
 
 Use context commands before answering personal data questions that should come from Oomi-approved permissions.
@@ -126,8 +133,10 @@ oomi context health --json
 Rules:
 - answer only from `healthContext.summary` and `healthContext.derived`
 - respect `healthContext.agentGuidance.canAnswerFromContext`
-- if context is missing, stale, denied, disabled, or unavailable, follow `healthContext.repair`
-- if the user asks you to refresh stale HealthKit context, run `oomi context health sync --json`; tell the user the iPhone app must be opened for Oomi to read Apple Health and fulfill the pending sync
+- if `healthContext.agentGuidance.recommendedCommand` is present, run it before answering current/latest health questions
+- if context is stale or needs sync, run `oomi context health sync --wait --json`; answer only after fresh context is uploaded, or tell the user the phone sync is still pending if it times out
+- if context is missing, denied, disabled, or unavailable, follow `healthContext.repair`
+- never present stale HealthKit values as current values
 - do not ask HealthKit directly; the Oomi mobile app syncs approved HealthKit data to the backend
 
 ## Hidden Speech Payload

package/skills/oomi/agent_instructions.md

@@ -87,17 +87,24 @@ Oomi persona apps are component-composed client surfaces backed by approved temp
 Persona UI creation and rendering happen inside Oomi-managed systems. Use the Oomi API tools instead:
 
 ```bash
+oomi fitness show --json
 oomi persona-apps list --json
 oomi persona-apps show fitness-today --json
 oomi persona-apps apply-action fitness-today --action fitness.complete_workout --payload-json '{"goalId":"easy-run","minutes":20}' --json
 ```
 
 Rules:
+- for Fitness questions, prefer `oomi fitness show --json` first because it combines mini-app state and approved health context
 - answer from returned `appState.bindings`, not memory
 - apply updates only through approved `persona-apps apply-action` actions
 - if the persona app is missing, ask the user to add it from the Oomi client first so permissions and hydration can run
 - do not execute persona UI jobs or start local persona app runtimes
 
+Supported Fitness actions include:
+- `fitness.set_goal` with `{"goalId":"move_more"}`, `{"goalId":"sleep_better"}`, or `{"goalId":"build_workout_habit"}`
+- `fitness.complete_goal`
+- `fitness.complete_workout`
+
 ## Permissioned Context Tools
 
 Use Oomi context tools when the user asks about personal data that should come from mobile permissions instead of memory.
@@ -111,8 +118,9 @@ oomi context health --json
 Rules:
 - answer only from `healthContext.summary` and `healthContext.derived`
 - respect `healthContext.agentGuidance.canAnswerFromContext`
-- if `canAnswerFromContext` is false, tell the user the relevant `healthContext.repair.label` or `healthContext.repair.reason`
-- if `healthContext.status` is `stale`, mention that the latest HealthKit sync may be out of date when timing matters
-- if the user asks you to refresh stale HealthKit context, run `oomi context health sync --json`; tell the user the iPhone app must be opened for Oomi to read Apple Health and fulfill the pending sync
+- if `healthContext.agentGuidance.recommendedCommand` is present, run it before answering current/latest health questions
+- if `healthContext.status` is `stale` or `needs_sync`, run `oomi context health sync --wait --json`; answer only after fresh context is uploaded, or tell the user the phone sync is still pending if it times out
+- if `canAnswerFromContext` is false and no sync command is recommended, tell the user the relevant `healthContext.repair.label` or `healthContext.repair.reason`
+- never present stale HealthKit values as current values
 - do not infer unavailable health fields
 - do not request HealthKit directly from the phone; the Oomi mobile app owns permission prompts and syncs approved data to the backend