oomi-ai 0.3.3 → 0.3.4

package/README.md

@@ -181,9 +181,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

@@ -276,8 +276,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 {
@@ -229,8 +235,9 @@ Commands:
 
   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
@@ -582,6 +589,40 @@ async function handleContextHealthSyncCommand(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));
 }
 

package/package.json

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

package/persona-app/README.md

@@ -30,12 +30,12 @@ When answering data-backed health or fitness questions, agents should read appro
 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/skills/oomi/SKILL.md

@@ -126,8 +126,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

@@ -111,8 +111,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