npm - forge-openclaw-plugin - Versions diffs - 0.2.94 → 0.2.96 - Mend

forge-openclaw-plugin 0.2.94 → 0.2.96

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (11) hide show

package/dist/assets/index-5w2YJv5G.css +1 -0
package/dist/assets/{index-DWZd3qT-.js → index-lOGIgdyP.js} +43 -43
package/dist/index.html +2 -2
package/dist/server/server/src/app.js +1 -0
package/dist/server/server/src/health.js +18 -3
package/dist/server/server/src/web.js +6 -0
package/openclaw.plugin.json +1 -1
package/package.json +1 -1
package/skills/forge-openclaw/SKILL.md +3 -2
package/skills/forge-openclaw/entity_conversation_playbooks.md +36 -0
package/dist/assets/index-PA_Ih223.css +0 -1

package/dist/index.html CHANGED Viewed

@@ -13,14 +13,14 @@
     />
     <link rel="icon" type="image/png" href="/forge/assets/favicon-BCHm9dUV.ico" />
     <link rel="alternate icon" href="/forge/assets/favicon-BCHm9dUV.ico" />
-    <script type="module" crossorigin src="/forge/assets/index-DWZd3qT-.js"></script>
+    <script type="module" crossorigin src="/forge/assets/index-lOGIgdyP.js"></script>
     <link rel="modulepreload" crossorigin href="/forge/assets/vendor-BS9OPVNh.js">
     <link rel="modulepreload" crossorigin href="/forge/assets/board-D1HbyD4u.js">
     <link rel="modulepreload" crossorigin href="/forge/assets/ui-DikPZj8S.js">
     <link rel="modulepreload" crossorigin href="/forge/assets/motion-D2OqILg_.js">
     <link rel="modulepreload" crossorigin href="/forge/assets/table-YWWjPjC_.js">
     <link rel="stylesheet" crossorigin href="/forge/assets/vendor-B-Lq_OG3.css">
-    <link rel="stylesheet" crossorigin href="/forge/assets/index-PA_Ih223.css">
+    <link rel="stylesheet" crossorigin href="/forge/assets/index-5w2YJv5G.css">
   </head>
   <body class="bg-canvas text-ink antialiased">
     <div id="root"></div>

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

@@ -3071,6 +3071,7 @@ const AGENT_ONBOARDING_CONVERSATION_RULES = [
     "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.",
     "After each substantive answer, briefly say what is becoming clearer and ask only for the next thing that still changes the record shape or usefulness.",
     "For strategic, reflective, or emotionally meaningful non-Psyche records, ask what feels important to keep true before you ask for labels, dates, or taxonomy.",
+    "For reflection-sensitive non-Psyche records such as questionnaire_instrument, questionnaire_run, self_observation, reflective note, wiki_page, sleep_session, workout_session, preference_judgment, and preference_signal, first ask what the reflection should help the user understand, decide, notice, remember, or change later; then keep the API posture exact: batch CRUD for normal stored records, questionnaire run actions for answer lifecycle, self-observation calendar reads plus observed-note writes, and wiki routes for wiki pages.",
     "For reusable records such as tags, event types, emotion definitions, preference contexts, or questionnaires, ask what distinction or decision the record should help with before you ask for wording.",
     "When useful, help the user name, define, and connect the record in that order: offer a working label, clarify what belongs inside it, then ask about links only after the record itself feels steady.",
     "When the meaning is clearer than the wording, offer a tentative title or formulation yourself and invite correction instead of forcing the user to wordsmith alone.",

package/dist/server/server/src/health.js CHANGED Viewed

@@ -2750,20 +2750,34 @@ function nestedRecord(value) {
         ? value
         : {};
 }
+const CURRENT_WORKOUT_RAW_EVIDENCE_VERSION = "healthkit-workout-raw-bulk-v4";
 function expectedWorkoutEvidenceCounts(derived) {
     const syncCursor = nestedRecord(derived.syncCursor);
     const captureQuality = nestedRecord(derived.captureQuality);
+    const captureQualityFlags = Array.isArray(captureQuality.flags)
+        ? captureQuality.flags.filter((flag) => typeof flag === "string")
+        : [];
+    const summaryOnlyExport = captureQuality.status === "summary_exported" ||
+        captureQualityFlags.includes("server_side_evidence_derivation");
     const syncTimeSeriesCount = finiteNumberFromUnknown(syncCursor.timeSeriesSampleCount);
-    const captureHeartRateCount = finiteNumberFromUnknown(captureQuality.heartRateSamples);
+    const captureHeartRateCount = summaryOnlyExport
+        ? null
+        : finiteNumberFromUnknown(captureQuality.heartRateSamples);
     const syncRoutePointCount = finiteNumberFromUnknown(syncCursor.routePointCount);
-    const captureRoutePointCount = finiteNumberFromUnknown(captureQuality.routePoints);
+    const captureRoutePointCount = summaryOnlyExport
+        ? null
+        : finiteNumberFromUnknown(captureQuality.routePoints);
     const expectedTimeSeriesSamples = Math.max(0, Math.ceil(Math.max(syncTimeSeriesCount ?? 0, captureHeartRateCount ?? 0)));
     const expectedHeartRateSamples = Math.max(0, Math.ceil(captureHeartRateCount ?? 0));
     const expectedRoutePoints = Math.max(0, Math.ceil(Math.max(syncRoutePointCount ?? 0, captureRoutePointCount ?? 0)));
+    const rawEvidenceVersion = typeof syncCursor.rawEvidenceVersion === "string"
+        ? syncCursor.rawEvidenceVersion
+        : "";
     return {
         expectedTimeSeriesSamples,
         expectedHeartRateSamples,
         expectedRoutePoints,
+        hasCurrentRawEvidenceVersion: rawEvidenceVersion === CURRENT_WORKOUT_RAW_EVIDENCE_VERSION,
         hasEvidenceMetadata: syncTimeSeriesCount !== null ||
             captureHeartRateCount !== null ||
             syncRoutePointCount !== null ||
@@ -2816,7 +2830,8 @@ function mobileHealthWorkoutImportState(userId) {
         const actualHeartRateCount = Math.max(0, row.heart_rate_count ?? 0);
         const actualRoutePointCount = Math.max(0, row.route_point_count ?? 0);
         const evidenceComplete = evidenceCounts.hasEvidenceMetadata
-            ? actualTimeSeriesCount >= evidenceCounts.expectedTimeSeriesSamples &&
+            ? evidenceCounts.hasCurrentRawEvidenceVersion &&
+                actualTimeSeriesCount >= evidenceCounts.expectedTimeSeriesSamples &&
                 actualHeartRateCount >= evidenceCounts.expectedHeartRateSamples &&
                 actualRoutePointCount >= evidenceCounts.expectedRoutePoints
             : false;

package/dist/server/server/src/web.js CHANGED Viewed

@@ -270,6 +270,12 @@ async function proxyDevWebSocket(input) {
         }
     });
     proxyRequest.on("upgrade", (response, proxySocket, proxyHead) => {
+        const closeBothSockets = () => {
+            proxySocket.destroy();
+            input.socket.destroy();
+        };
+        proxySocket.on("error", closeBothSockets);
+        input.socket.on("error", closeBothSockets);
         writeProxyUpgradeResponse(input.socket, response);
         if (proxyHead.length > 0) {
             input.socket.write(proxyHead);

package/openclaw.plugin.json CHANGED Viewed

@@ -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.94",
+  "version": "0.2.96",
   "activation": {
     "onStartup": true,
     "onCapabilities": [

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "forge-openclaw-plugin",
-  "version": "0.2.94",
+  "version": "0.2.96",
   "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 CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 name: forge-openclaw-plugin
-description: use when the user wants to save, search, update, review, start, stop, reward, explain, compare, or run Forge records, or when the conversation is clearly about a Forge entity or domain surface such as a goal, project, strategy, task, habit, note, wiki_page, calendar_event, calendar_connection, work_block_template, task_timebox, task_run, work_adjustment, insight, preference item, preference context, preference catalog, preference judgment, preference signal, questionnaire instrument, questionnaire run, self observation, movement, life_force, workbench, psyche_value, behavior_pattern, behavior, belief_entry, mode_profile, mode_guide_session, flashcard, trigger_report, event_type, emotion_definition, sleep_session, or workout_session. identify the exact Forge object or specialized surface, keep the main conversation natural, guide psyche intake with active listening before storing it, and for psyche issues that need understanding first usually begin with one exploratory question before any formulation or save suggestion.
+description: use when the user wants to save, search, update, review, start, stop, reward, explain, compare, or run Forge records, or when the conversation is clearly about a Forge entity or domain surface such as a goal, project, strategy, task, habit, note, wiki_page, calendar_event, calendar_connection, work_block_template, task_timebox, task_run, work_adjustment, insight, preference item, preference context, preference catalog, preference judgment, preference signal, questionnaire instrument, questionnaire run, self observation, movement, life_force, workbench, psyche_value, behavior_pattern, behavior, belief_entry, mode_profile, mode_guide_session, flashcard, trigger_report, event_type, emotion_definition, sleep_session, workout_session, or training_load. identify the exact Forge object or specialized surface, keep the main conversation natural, guide psyche intake with active listening before storing it, and for psyche issues that need understanding first usually begin with one exploratory question before any formulation or save suggestion.
 ---
 Forge is the user's structured system for planning work, doing work, reflecting on patterns, and keeping a truthful record of what is happening. Use it when the user is clearly working inside that system, or when they are describing something that naturally belongs there and would benefit from being stored, updated, reviewed, or acted on in Forge. Keep the conversation natural first. Do not turn every message into intake. When a real Forge entity is clearly present, name the exact entity type plainly, help with the substance of the conversation, and then offer Forge once, lightly, if storing it would genuinely help.
@@ -59,7 +59,7 @@ PM surface rule:
   human/bot ownership filters.
 - Guided modal flows handle create, edit, move, link, and closeout actions.
-Forge has four major stored-entity surfaces and three specialized domain surfaces. The planning side covers goals, projects, strategies, tasks, habits, notes, calendar events, recurring work blocks, task timeboxes, live work sessions, and agent-authored insights. The Health side covers sleep sessions, sports and workout sessions, companion pairing, and habit-generated workout records that should still stay linked to the broader Forge graph. The Preferences side covers contextual taste modeling, pairwise comparisons, direct signals, editable concept libraries, and preference items that can come from Forge entities or seeded concept domains such as food, activities, places, countries, fashion, people, media, and tools. The Psyche side covers values, patterns, behaviors, beliefs, modes, guided mode sessions, flashcards, trigger reports, event types, and reusable emotion definitions. The specialized domain surfaces are Movement, Life Force, and Workbench; agents must use their dedicated route families instead of forcing them through batch CRUD. Forge also has a SQLite-backed Wiki memory layer with explicit spaces, Markdown content in database rows, backlinks, optional embeddings, and structured links back to Forge entities. Forge is also multi-user: every entity can belong to a typed `human` or `bot` user through `userId`, and read routes can scope to one or many users with `userId` or repeated `userIds`. The current access posture is configurable through a directional user graph, but the live default is still permissive: Forge can list users directly, every relationship edge starts open, and a user can read or affect another user's linked records when the route explicitly asks for them. Use `forge_get_user_directory` when owner identity or cross-user access matters. Strategies can also be locked into a contract with `isLocked`; once locked, do not mutate the graph or target structure unless the user explicitly wants the strategy unlocked first. The model should use the real entity names, not vague substitutes. Say `project`, not “initiative”. Say `behavior_pattern`, not “theme”. Say `trigger_report`, not “incident note”.
+Forge has four major stored-entity surfaces and three specialized domain surfaces. The planning side covers goals, projects, strategies, tasks, habits, notes, calendar events, recurring work blocks, task timeboxes, live work sessions, and agent-authored insights. The Health side covers sleep sessions, sports and workout sessions, the read-only training-load surface for cardiovascular load and HR zone review, companion pairing, and habit-generated workout records that should still stay linked to the broader Forge graph. The Preferences side covers contextual taste modeling, pairwise comparisons, direct signals, editable concept libraries, and preference items that can come from Forge entities or seeded concept domains such as food, activities, places, countries, fashion, people, media, and tools. The Psyche side covers values, patterns, behaviors, beliefs, modes, guided mode sessions, flashcards, trigger reports, event types, and reusable emotion definitions. The specialized domain surfaces are Movement, Life Force, and Workbench; agents must use their dedicated route families instead of forcing them through batch CRUD. Forge also has a SQLite-backed Wiki memory layer with explicit spaces, Markdown content in database rows, backlinks, optional embeddings, and structured links back to Forge entities. Forge is also multi-user: every entity can belong to a typed `human` or `bot` user through `userId`, and read routes can scope to one or many users with `userId` or repeated `userIds`. The current access posture is configurable through a directional user graph, but the live default is still permissive: Forge can list users directly, every relationship edge starts open, and a user can read or affect another user's linked records when the route explicitly asks for them. Use `forge_get_user_directory` when owner identity or cross-user access matters. Strategies can also be locked into a contract with `isLocked`; once locked, do not mutate the graph or target structure unless the user explicitly wants the strategy unlocked first. The model should use the real entity names, not vague substitutes. Say `project`, not “initiative”. Say `behavior_pattern`, not “theme”. Say `trigger_report`, not “incident note”.
 Habits are a first-class recurring entity in the planning side.
 NEGATIVE HABIT CHECK-IN RULE: for a `negative` habit, the correct aligned/resisted outcome is `missed`. `missed` means the bad habit was resisted, the user stayed aligned, and the habit should award its XP bonus.
@@ -239,6 +239,7 @@ Entity conversation rule:
 - When updating an entity, start with what is changing, what should stay true, and what prompted the update now.
 - When enough is clear, briefly summarize what you heard in the user's own language before asking for the last missing structural detail.
 - Treat `userId` and human/bot assignees as accountability and scope, not as opening form fields. Ask whose human or bot record it is only when ownership changes visibility, review scope, collaboration, automation behavior, or later filtering; for read requests, ask user scope only when the answer would differ across owners.
+- Treat questionnaire runs, self-observations, reflective notes, wiki pages, sleep/workout enrichment, and preference signals as reflection-sensitive records: ask what the record should help the user understand, decide, notice, remember, or change later, then choose the right route. Do not flatten them into forms, but also do not automatically turn them into full Psyche intake unless a belief, mode, trigger report, or behavior pattern clearly emerges.
 - The quick intake prompts later in this file are fallback checkpoints, not a script to read aloud.
 Forge data location rule:

package/skills/forge-openclaw/entity_conversation_playbooks.md CHANGED Viewed

@@ -158,6 +158,42 @@ to the stronger container:
 - Use a linked `note` when nuance should be preserved without pretending it is the
   whole structured model.
+## Reflection-sensitive non-Psyche records
+Use this when the user is creating or updating a reflective record that is meaningful
+but not necessarily a full Psyche formulation: `questionnaire_instrument`,
+`questionnaire_run`, `self_observation`, reflective `note`, `wiki_page`,
+`sleep_session`, `workout_session`, and some `preference_judgment` or
+`preference_signal` moments.
+- Start by asking what the reflection should help the user understand, decide,
+  notice, remember, or change later.
+- Reflect the lived or practical stake once before asking for fields, but do not
+  over-therapize if the user is only trying to store a clear answer, note, or
+  health-context update.
+- For questionnaire instruments, ask what kind of honest moment, review, or decision
+  the instrument should reveal before asking for item wording, scales, scoring, or
+  provenance.
+- For questionnaire runs, ask whether the user is trying to start, continue, review,
+  or complete the run, then focus on the next answer, uncertainty, or insight that
+  changes the run. Do not turn answer collection into generic Psyche intake unless a
+  belief, mode, trigger report, or behavior pattern clearly emerges.
+- For self-observation, keep the chain concrete: situation, cue, emotion/body,
+  thought/meaning, behavior/urge, and consequence. If that chain reveals a recurring
+  loop, belief, mode, schema theme, or one charged trigger episode, route to the
+  stronger Psyche container.
+- For sleep and workout enrichment, ask what the user wants future review to remember:
+  recovery context, subjective effort, mood, meaning, social context, or links.
+  Preserve raw health facts through the health model and store reflection as notes,
+  tags, links, or batch updates.
+- For notes and wiki pages, distinguish temporary operating context from durable
+  memory. A note can preserve nuance around another record; a wiki page should carry
+  reusable knowledge, source synthesis, person/context memory, or a personal manual.
+- Route posture still matters: `questionnaire_instrument`, `note`, `sleep_session`,
+  and `workout_session` use shared batch routes for normal CRUD; `questionnaire_run`
+  uses questionnaire run actions; `self_observation` is note-backed; `wiki_page` uses
+  the wiki routes.
 ## Conversation arc
 Most good Forge intake flows follow this sequence: