forge-openclaw-plugin 0.2.40 → 0.2.42

package/dist/index.html

@@ -13,7 +13,7 @@
     />
     <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-46NL_IaJ.js"></script>
+    <script type="module" crossorigin src="/forge/assets/index-Fe5y4VWU.js"></script>
     <link rel="modulepreload" crossorigin href="/forge/assets/vendor-DK-mJFy6.js">
     <link rel="modulepreload" crossorigin href="/forge/assets/board-C3BJqvZu.js">
     <link rel="modulepreload" crossorigin href="/forge/assets/ui-CQzq3TE5.js">

package/dist/openclaw/plugin-sdk-types.d.ts

@@ -42,6 +42,11 @@ export type ForgeCliRegistrarContext = {
         debug?(message: string): void;
     };
 };
+export type ForgeCliCommandDescriptor = {
+    name: string;
+    description: string;
+    hasSubcommands?: boolean;
+};
 export type ForgePluginServiceContext = {
     config?: unknown;
     workspaceDir?: string;
@@ -77,6 +82,7 @@ export type ForgePluginRegistrationApi = {
     }): void;
     registerCli?(registrar: (context: ForgeCliRegistrarContext) => void, options?: {
         commands?: string[];
+        descriptors?: ForgeCliCommandDescriptor[];
     }): void;
     registerService?(service: ForgeRegisteredService): void;
 };

package/dist/openclaw/routes.js

@@ -1158,5 +1158,14 @@ export function registerForgePluginCli(api, config) {
             .action(async () => {
             console.log(JSON.stringify(await runRouteCheck(config), null, 2));
         });
-    }, { commands: ["forge"] });
+    }, {
+        commands: ["forge"],
+        descriptors: [
+            {
+                name: "forge",
+                description: "Inspect and operate Forge through the OpenClaw plugin",
+                hasSubcommands: true
+            }
+        ]
+    });
 }

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

@@ -62,7 +62,7 @@ import { registerWebRoutes } from "./web.js";
 import { createManagerRuntime } from "./managers/runtime.js";
 import { isManagerError } from "./managers/type-guards.js";
 import { createCompanionPairingSession, createCompanionPairingSessionSchema, createSleepSession, createSleepSessionSchema, createWorkoutSession, createWorkoutSessionSchema, deleteSleepSession, deleteWorkoutSession, getCompanionPairingSessionById, getCompanionOverview, getFitnessViewData, getSleepSessionById, getSleepSessionDetailById, getSleepViewData, getVitalsViewData, getWorkoutSessionById, ingestMobileHealthSync, mobileHealthSyncSchema, patchCompanionPairingSourceState, patchCompanionPairingSourceStateSchema, companionSourceKeySchema, requireValidPairing, revokeAllCompanionPairingSessions, revokeAllCompanionPairingSessionsSchema, revokeCompanionPairingSession, updateMobileCompanionSourceState, updateMobileCompanionSourceStateSchema, verifyCompanionPairing, verifyCompanionPairingSchema, updateSleepMetadata, updateSleepMetadataSchema, updateWorkoutMetadata, updateWorkoutMetadataSchema } from "./health.js";
-import { analyzeMovementUserBoxPreflight, createMovementUserBox, createMovementPlace, deleteMovementUserBox, getMovementAllTimeSummary, getMovementBoxDetail, getMovementDayDetail, getMovementMobileBootstrap, getMovementTimeline, getMovementSelectionAggregate, getMovementSettings, getMovementTripDetail, getMovementMonthSummary, invalidateAutomaticMovementBox, listMovementPlaces, movementAutomaticBoxInvalidateSchema, movementMobileBootstrapSchema, movementMobilePlaceMutationSchema, 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 { 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";
 const COMPATIBILITY_SUNSET = "transitional-node";
@@ -2654,7 +2654,8 @@ const AGENT_ONBOARDING_ENTITY_CATALOG = [
         ],
         searchHints: [
             "Clarify whether the user wants a behavioral query, one trip or place, a missing-gap overlay, a manual add or update, or a link before choosing the route.",
-            "If the user already named a concrete missing span, confirm only the remaining time or place ambiguity, then use the movement overlay route and read the timeline back."
+            "If the user already named a concrete missing span, confirm only the remaining time or place ambiguity, then use the movement overlay route and read the timeline back.",
+            "If the user wants to revise or remove an already-saved correction, identify whether it is a user-defined box, automatic box, recorded stay, recorded trip, or trip point before choosing the repair or delete route."
         ],
         fieldGuide: []
     }),
@@ -2668,7 +2669,8 @@ const AGENT_ONBOARDING_ENTITY_CATALOG = [
         ],
         searchHints: [
             "Clarify whether the user wants explanation, durable model changes, or a real-time tired or recovered signal before choosing the route.",
-            "Separate durable profile assumptions, weekday-template edits, and right-now fatigue signals before choosing the mutation path."
+            "Separate durable profile assumptions, weekday-template edits, and right-now fatigue signals before choosing the mutation path.",
+            "When the user is trying to understand the practical result of a change, read the overview again after the write instead of stopping at the mutation response."
         ],
         fieldGuide: []
     }),
@@ -2682,7 +2684,8 @@ const AGENT_ONBOARDING_ENTITY_CATALOG = [
         ],
         searchHints: [
             "Clarify whether the user wants flow discovery, editing, execution, published output, run inspection, or node-level output before choosing the route.",
-            "Distinguish flow contract, published output, run history, and latest-node-output questions before reaching for a route."
+            "Distinguish flow contract, published output, run history, latest-node-output, and chat follow-up questions before reaching for a route.",
+            "If the user is still deciding how to run or edit a flow, read flow detail or the box catalog before asking them for payload structure."
         ],
         fieldGuide: []
     }),
@@ -3061,7 +3064,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
     },
     {
         focus: "movement",
-        openingQuestion: "Are you trying to understand where you stayed and traveled, change one stay or trip, or answer a question about your movement behavior?",
+        openingQuestion: "What are you trying to understand, correct, or preserve about where you stayed and traveled?",
         coachingGoal: "Clarify whether the user wants a time-in-place query, travel-history review, a missing-gap overlay, one stay or trip change, one place summary, or a link before choosing the dedicated movement route.",
         askSequence: [
             "Ask whether the user is trying to query behavior, add something manually, update an existing movement item, or link movement to another Forge entity.",
@@ -3071,6 +3074,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
             "Skip the meta lane question when the user already named the exact correction or review target and only one ambiguity remains.",
             "If the request is filling a missing-data gap, use a user-defined movement box rather than a raw stay or trip patch.",
             "If the request is repairing already-saved movement data, use the repair route that matches the saved object instead of treating it like a missing span.",
+            "If the request is removing an already-saved correction, identify whether it is a user-defined box, recorded stay, recorded trip, or trip point before choosing the delete route.",
             "When the user wants place creation or place cleanup, use the dedicated movement place routes rather than a generic entity mutation.",
             "When the user already gave a concrete correction like 'I stayed home during that missing block', confirm only the interval or place if needed, then create the overlay and read the timeline back."
         ]
@@ -3086,12 +3090,13 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
             "Ask whether the user is describing a stable weekly shape or just how today feels when the lane is still blurred.",
             "If the user already named the life-force lane clearly, skip the meta lane question and ask only for the specific weekday, profile field, or signal that still matters.",
             "If the request is about a durable baseline, use profile or weekday-template mutation rather than a fatigue signal; if it is about right now, prefer the fatigue-signal route.",
+            "If the user wants to see what changed after a write, read the overview back instead of leaving the result implicit.",
             "Route to the dedicated life-force path once the lane is clear."
         ]
     },
     {
         focus: "workbench",
-        openingQuestion: "Are you trying to inspect a flow, change it, run it, or inspect one run's outputs?",
+        openingQuestion: "What are you trying to inspect, change, run, or publish through Workbench?",
         coachingGoal: "Clarify whether the user wants flow discovery, editing, execution, run history, published outputs, or node-level inspection before using the dedicated workbench route family.",
         askSequence: [
             "Ask whether the job is flow discovery, one flow edit, execution, run history, published output, node-level inspection, or latest-node-output lookup.",
@@ -3099,6 +3104,7 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
             "Ask whether they need the flow contract, a run result, a published output, or a node result.",
             "Ask what the user is trying to learn, repair, or publish through that flow.",
             "If the user already named the flow and action clearly, skip the meta lane question and ask only for the missing run, node, or output scope.",
+            "If the user is still shaping a payload or edit, prefer flow detail or box catalog reads before asking for structured inputs.",
             "Prefer flow detail or published-output reads for stable contracts, and use run or node-result routes only when the user is asking about execution history or debugging.",
             "Route to the dedicated workbench route family once the execution lane is clear."
         ]
@@ -4065,25 +4071,32 @@ function buildAgentOnboardingPayload(request) {
                         allTime: "/api/v1/movement/all-time",
                         timeline: "/api/v1/movement/timeline",
                         places: "/api/v1/movement/places",
+                        boxDetail: "/api/v1/movement/boxes/:id",
                         tripDetail: "/api/v1/movement/trips/:id",
                         selection: "/api/v1/movement/selection",
                         settings: "/api/v1/movement/settings"
                     },
                     writeRoutes: {
+                        settingsUpdate: "/api/v1/movement/settings",
                         placeCreate: "/api/v1/movement/places",
                         placeUpdate: "/api/v1/movement/places/:id",
                         userBoxCreate: "/api/v1/movement/user-boxes",
                         userBoxPreflight: "/api/v1/movement/user-boxes/preflight",
                         userBoxUpdate: "/api/v1/movement/user-boxes/:id",
+                        userBoxDelete: "/api/v1/movement/user-boxes/:id",
                         automaticBoxInvalidate: "/api/v1/movement/automatic-boxes/:id/invalidate",
                         stayUpdate: "/api/v1/movement/stays/:id",
+                        stayDelete: "/api/v1/movement/stays/:id",
                         tripUpdate: "/api/v1/movement/trips/:id",
-                        tripPointUpdate: "/api/v1/movement/trips/:id/points/:pointId"
+                        tripDelete: "/api/v1/movement/trips/:id",
+                        tripPointUpdate: "/api/v1/movement/trips/:id/points/:pointId",
+                        tripPointDelete: "/api/v1/movement/trips/:id/points/:pointId"
                     },
                     notes: [
                         "Movement is not a normal batch CRUD entity family. It is a dedicated record of stays and trips: a stay means the user remained in the same place for a span of time, and a trip means they traveled between places.",
                         "Use /api/v1/movement/day, /month, /all-time, /timeline, or /selection when the user wants behavioral answers such as how long they stayed at home, when they traveled, which places dominated a period, or what happened across a selected span.",
                         "Use the movement write routes when the user wants to add a place or manual overlay, update a specific stay or trip, repair one recorded movement span, or attach movement context to another Forge record. If the user is filling a missing-data gap, the usual write path is a user-defined overlay box rather than a raw stay or trip patch.",
+                        "If the user is revising or removing an existing correction, first identify whether the saved object is a user-defined box, automatic box, recorded stay, recorded trip, or trip point so the repair or delete path stays truthful.",
                         "For an explicit statement like 'that missing block was me staying home', do not reopen broad intake. Preflight only if timing overlap is unclear, then create a user-defined `stay` box for that interval and read the updated timeline back."
                     ]
                 },
@@ -4101,6 +4114,7 @@ function buildAgentOnboardingPayload(request) {
                         "Life Force is a focused domain surface, not a batch CRUD entity type.",
                         "Use GET /api/v1/life-force for the current overview payload with stats, drains, recommendations, and current-curve state.",
                         "Patch the profile only for durable personal settings, update weekday templates only for the curve itself, and post fatigue signals for real-time tired or recovered observations.",
+                        "If the user is asking what changed after a profile, template, or fatigue write, read the overview back so the effect stays visible.",
                         "If the user already knows they want a profile change, weekday-template edit, or right-now fatigue signal, skip the broad lane question and ask only for the missing weekday, profile field, or signal detail."
                     ]
                 },
@@ -4129,6 +4143,7 @@ function buildAgentOnboardingPayload(request) {
                     notes: [
                         "Workbench is a dedicated execution surface, not a batch CRUD entity family.",
                         "Use the flow routes when the agent needs stable public input contracts, published outputs, node-level results, or reusable execution history.",
+                        "If the user is still figuring out inputs or editable structure, read flow detail or box catalog before asking them to author a payload from memory.",
                         "Prefer the dedicated output and node-result routes over reverse-engineering raw traces.",
                         "If the user already named the flow and wants one output or one run, skip the broad lane question and ask only for the missing run, node, or output scope."
                     ]
@@ -4330,8 +4345,8 @@ function buildAgentOnboardingPayload(request) {
             saveSuggestionPlacement: "end_of_message",
             saveSuggestionTone: "gentle_optional",
             maxQuestionsPerTurn: 1,
-            psycheExplorationRule: "When a Psyche entity needs understanding first, begin with one exploratory question before any working formulation, replacement belief, suggested title, or save pitch. Keep the opening reflection to one or two short sentences, stay in plain prose instead of bullets or numbered lists, keep that first reply short, do not mention Forge search or save structure yet, avoid colons or list-shaped phrasing, prefer what/when/how over why until the experience is grounded, wait for the user's answer before offering a fuller formulation, ask permission before moving from charged exploration into naming or challenge when needed, do not widen into adjacent entities until the current one has a working sentence the user recognizes, and once the lived experience is coherent stop deepening and help the user name it cleanly. If the user accepts the wording, move toward the save instead of reopening deeper exploration.",
-            specializedSurfaceRule: "For Movement, Life Force, and Workbench, clarify the lane first, then name the dedicated route family in plain language and do not guess at a generic CRUD path. When the user already named a precise correction or review target, confirm only the route-selecting detail that is still missing. The canonical runtime routes stay under /api/v1/*, and the OpenClaw HTTP mirror exposes the same families under /forge/v1/movement, /forge/v1/life-force, and /forge/v1/workbench.",
+            psycheExplorationRule: "When a Psyche entity needs understanding first, begin with one exploratory question before any working formulation, replacement belief, suggested title, or save pitch. Keep the opening reflection to one or two short sentences, stay in plain prose instead of bullets or numbered lists, keep that first reply short, do not mention Forge search or save structure yet, avoid colons or list-shaped phrasing, prefer what/when/how over why until the experience is grounded, wait for the user's answer before offering a fuller formulation, ask permission before moving from charged exploration into naming or challenge when needed, do not widen into adjacent entities until the current one has a working sentence the user recognizes, and once the lived experience is coherent stop deepening and help the user name it cleanly. When the user is updating a Psyche record because of one fresh episode, anchor in that episode before renaming the durable formulation. If the user accepts the wording, move toward the save instead of reopening deeper exploration.",
+            specializedSurfaceRule: "For Movement, Life Force, and Workbench, clarify the lane first, then name the dedicated route family in plain language and do not guess at a generic CRUD path. When the user already named a precise correction or review target, confirm only the route-selecting detail that is still missing. After a concrete specialized-surface correction, read the relevant specialized view back when the user is trying to understand the result rather than just store it. The canonical runtime routes stay under /api/v1/*, and the OpenClaw HTTP mirror exposes the same families under /forge/v1/movement, /forge/v1/life-force, and /forge/v1/workbench.",
             reviewShortcutRule: "When the user is reviewing or correcting an existing record, 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. 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.",
@@ -5868,9 +5883,20 @@ export async function buildServer(options = {}) {
         };
     });
     app.patch("/api/v1/mobile/movement/stays/:id", async (request, reply) => {
-        reply.code(409);
+        const parsed = movementMobileStayPatchSchema.parse(request.body ?? {});
+        const pairing = requireValidPairing(parsed.sessionId, parsed.pairingToken);
+        const { id } = request.params;
+        const stay = updateMovementStay(id, parsed.patch, {
+            actor: "Forge Companion",
+            source: "system"
+        }, { userId: pairing.user_id });
+        if (!stay) {
+            reply.code(404);
+            return { error: "Movement stay not found" };
+        }
         return {
-            error: "Recorded stays are immutable in product UI. Create or edit a user-defined movement box instead."
+            stay,
+            place: stay.place
         };
     });
     app.patch("/api/v1/mobile/movement/trips/:id", async (request, reply) => {

package/dist/server/server/src/movement.js

@@ -130,7 +130,7 @@ const linkedPersonSchema = z.object({
     label: z.string().trim().min(1)
 });
 const movementPlaceInputSchema = z.object({
-    externalUid: z.string().trim().min(1).default(""),
+    externalUid: z.string().trim().default(""),
     label: z.string().trim().min(1),
     aliases: z.array(z.string().trim()).default([]),
     latitude: z.number().finite(),
@@ -1011,6 +1011,61 @@ function mapMovementPlace(row) {
             : null
     };
 }
+function readMovementPlaceLearningState(row) {
+    const metadata = safeJsonParse(row.metadata_json, {});
+    const sampleCount = Number(metadata.distributionSampleCount);
+    const averageLatitude = Number(metadata.distributionAverageLatitude);
+    const averageLongitude = Number(metadata.distributionAverageLongitude);
+    const maxDistanceMeters = Number(metadata.distributionMaxDistanceMeters);
+    return {
+        sampleCount: Number.isFinite(sampleCount) && sampleCount >= 1 ? Math.floor(sampleCount) : 1,
+        averageLatitude: Number.isFinite(averageLatitude) ? averageLatitude : row.latitude,
+        averageLongitude: Number.isFinite(averageLongitude) ? averageLongitude : row.longitude,
+        maxDistanceMeters: Number.isFinite(maxDistanceMeters) && maxDistanceMeters >= 0
+            ? maxDistanceMeters
+            : 0
+    };
+}
+function learnMovementPlaceObservation(input) {
+    const existing = getDatabase()
+        .prepare(`SELECT *
+       FROM movement_places
+       WHERE id = ?`)
+        .get(input.placeId);
+    if (!existing) {
+        return null;
+    }
+    const metadata = safeJsonParse(existing.metadata_json, {});
+    const learning = readMovementPlaceLearningState(existing);
+    const nextSampleCount = learning.sampleCount + 1;
+    const nextAverageLatitude = (learning.averageLatitude * learning.sampleCount + input.observation.latitude) /
+        nextSampleCount;
+    const nextAverageLongitude = (learning.averageLongitude * learning.sampleCount + input.observation.longitude) /
+        nextSampleCount;
+    const observationDistance = haversineDistanceMeters({ latitude: nextAverageLatitude, longitude: nextAverageLongitude }, input.observation);
+    const nextMaxDistanceMeters = Math.max(learning.maxDistanceMeters, observationDistance);
+    const nextRadiusMeters = Math.min(2000, Math.max(existing.radius_meters, Math.ceil(nextMaxDistanceMeters + 25)));
+    const nextMetadata = {
+        ...metadata,
+        distributionSampleCount: String(nextSampleCount),
+        distributionAverageLatitude: nextAverageLatitude.toFixed(6),
+        distributionAverageLongitude: nextAverageLongitude.toFixed(6),
+        distributionMaxDistanceMeters: nextMaxDistanceMeters.toFixed(1),
+        distributionLastObservedAt: nowIso()
+    };
+    getDatabase()
+        .prepare(`UPDATE movement_places
+       SET latitude = ?,
+           longitude = ?,
+           radius_meters = ?,
+           metadata_json = ?,
+           updated_at = ?
+       WHERE id = ?`)
+        .run(nextAverageLatitude, nextAverageLongitude, nextRadiusMeters, JSON.stringify(nextMetadata), nowIso(), input.placeId);
+    return mapMovementPlace(getDatabase()
+        .prepare(`SELECT * FROM movement_places WHERE id = ?`)
+        .get(input.placeId));
+}
 function mapMovementStay(row, placesById) {
     const note = row.published_note_id ? getNoteById(row.published_note_id) : null;
     const metrics = safeJsonParse(row.metrics_json, {});
@@ -1637,6 +1692,9 @@ function upsertMovementSettings(userId, input) {
 }
 function upsertMovementPlaceInternal(input) {
     const parsed = movementPlaceInputSchema.parse(input.place);
+    const externalUid = parsed.externalUid.trim().length > 0
+        ? parsed.externalUid.trim()
+        : `movement-place-${randomUUID().replaceAll("-", "").slice(0, 20)}`;
     const now = nowIso();
     const existing = input.id && input.id.trim().length > 0
         ? getDatabase()
@@ -1644,14 +1702,14 @@ function upsertMovementPlaceInternal(input) {
              FROM movement_places
              WHERE id = ?`)
             .get(input.id)
-        : parsed.externalUid.trim().length > 0
+        : externalUid.length > 0
             ? getDatabase()
                 .prepare(`SELECT *
                FROM movement_places
                WHERE user_id = ?
                  AND source = ?
                  AND external_uid = ?`)
-                .get(input.userId, input.source, parsed.externalUid)
+                .get(input.userId, input.source, externalUid)
             : undefined;
     const id = existing?.id ?? input.id ?? `mpl_${randomUUID().replaceAll("-", "").slice(0, 10)}`;
     getDatabase()
@@ -1677,7 +1735,7 @@ function upsertMovementPlaceInternal(input) {
          metadata_json = excluded.metadata_json,
          source = excluded.source,
          updated_at = excluded.updated_at`)
-        .run(id, parsed.externalUid, input.userId, parsed.label, JSON.stringify(uniqStrings(parsed.aliases)), parsed.latitude, parsed.longitude, parsed.radiusMeters, JSON.stringify(canonicalizeMovementCategoryTags(parsed.categoryTags)), parsed.visibility, parsed.wikiNoteId, JSON.stringify(parsed.linkedEntities), JSON.stringify(parsed.linkedPeople), JSON.stringify(parsed.metadata), input.source, existing?.created_at ?? now, now);
+        .run(id, externalUid, input.userId, parsed.label, JSON.stringify(uniqStrings(parsed.aliases)), parsed.latitude, parsed.longitude, parsed.radiusMeters, JSON.stringify(canonicalizeMovementCategoryTags(parsed.categoryTags)), parsed.visibility, parsed.wikiNoteId, JSON.stringify(parsed.linkedEntities), JSON.stringify(parsed.linkedPeople), JSON.stringify(parsed.metadata), input.source, existing?.created_at ?? now, now);
     syncPlaceWikiMetadata(id);
     return mapMovementPlace(getDatabase()
         .prepare(`SELECT * FROM movement_places WHERE id = ?`)
@@ -3868,6 +3926,8 @@ export function updateMovementStay(stayId, patch, context, options = {}) {
         ...safeJsonParse(existing.metadata_json, {}),
         ...(parsed.metadata ?? {})
     };
+    const shouldLearnPlaceObservation = resolvedPlace !== null &&
+        (hasOwn(parsed, "placeId") || hasOwn(parsed, "placeExternalUid"));
     getDatabase()
         .prepare(`UPDATE movement_stays
        SET place_id = ?,
@@ -3886,6 +3946,17 @@ export function updateMovementStay(stayId, patch, context, options = {}) {
        WHERE id = ?`)
         .run(resolvedPlace?.id ?? null, parsed.label ?? parsed.placeLabel ?? existing.label, parsed.status ?? existing.status, parsed.classification ?? existing.classification, startedAt, endedAt, parsed.centerLatitude ?? existing.center_latitude, parsed.centerLongitude ?? existing.center_longitude, parsed.radiusMeters ?? existing.radius_meters, parsed.sampleCount ?? existing.sample_count, JSON.stringify(metrics), JSON.stringify(metadata), nowIso(), stayId);
     reconcileMovementOverlapValidation(existing.user_id);
+    let learnedPlace = resolvedPlace ? mapMovementPlace(resolvedPlace) : null;
+    if (resolvedPlace && shouldLearnPlaceObservation) {
+        learnedPlace =
+            learnMovementPlaceObservation({
+                placeId: resolvedPlace.id,
+                observation: {
+                    latitude: parsed.centerLatitude ?? existing.center_latitude,
+                    longitude: parsed.centerLongitude ?? existing.center_longitude
+                }
+            }) ?? learnedPlace;
+    }
     const places = listMovementPlaceRows([existing.user_id]).map(mapMovementPlace);
     const placesById = new Map(places.map((place) => [place.id, place]));
     const updated = mapMovementStay(getDatabase()
@@ -3906,7 +3977,10 @@ export function updateMovementStay(stayId, patch, context, options = {}) {
             durationSeconds: updated.durationSeconds
         }
     });
-    return updated;
+    return {
+        ...updated,
+        place: learnedPlace && updated.placeId === learnedPlace.id ? learnedPlace : updated.place
+    };
 }
 export function updateMovementTrip(tripId, patch, context, options = {}) {
     const existing = getDatabase()

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.40",
+  "version": "0.2.42",
   "skills": [
     "./skills"
   ],

package/package.json

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

package/skills/forge-openclaw/SKILL.md

@@ -141,6 +141,7 @@ Psyche interview rule:
 - Sound professionally warm and therapist-like: grounded, accurate, reflective, and intentional, not clinical, vague, or lecture-like.
 - After the first real answer, choose one follow-up lane at a time: situation, sequence, meaning, protection, cost, longing/value, or tentative name.
 - For Psyche updates, start with what feels newly true, newly visible, or newly inaccurate, then ask what should stay true before changing the formulation.
+- If a fresh episode is what made a Psyche update visible, anchor in that episode before renaming the durable belief, pattern, mode, or value.
 - If the user says they want help understanding a Psyche issue before saving it, ask one orienting question first instead of jumping straight into a full interpretation, diagnosis-like label, save suggestion, replacement belief, or suggested title.
 - In that first exploratory turn, keep the reflection to one or two short sentences, avoid numbered lists or schema dumps, and wait for the user's answer before offering a fuller formulation.
 - In that first exploratory turn, stay in plain prose, end with one question, and do not mention Forge fields or save formatting yet unless the user interrupts to save immediately.
@@ -386,6 +387,7 @@ Use the dedicated domain routes for specialized surfaces that are not simple bat
   `/api/v1/workbench/flows/:id/output` for published outputs, and the run/node routes
   under `/api/v1/workbench/flows/:id` for run history and node-level inspection.
 - If you are unsure which specialized route family applies, check `forge_get_agent_onboarding` and use its `entityRouteModel.specializedDomainSurfaces` section before guessing.
+- After a concrete Movement, Life Force, or Workbench correction, read the relevant specialized view back when the user is trying to understand the result rather than only store it.
 
 Use live work tools for `task_run`:
 `forge_log_work`, `forge_start_task_run`, `forge_heartbeat_task_run`, `forge_focus_task_run`, `forge_complete_task_run`, `forge_release_task_run`

package/skills/forge-openclaw/entity_conversation_playbooks.md

@@ -1016,6 +1016,11 @@ Direct action rules:
   traveled.
 - Use raw `PATCH /api/v1/movement/stays/:id` or `/api/v1/movement/trips/:id` only for
   editing an already-recorded stay or trip, not for filling a missing span.
+- If the user wants to undo or remove one manual overlay, delete the saved
+  user-defined box instead of patching a recorded stay or trip.
+- If the user wants to inspect one already-saved movement correction before editing
+  it, read the box detail first so the follow-up write stays grounded in the saved
+  object.
 - When the user has already given the real answer, for example "I stayed home during
   that missing block", do not ask a broad review question again. Confirm only the
   interval or place if that is still ambiguous, then act.
@@ -1045,14 +1050,20 @@ Lane-to-route map:
   `/api/v1/movement/places` or `/api/v1/movement/places/:id`
 - inspect one trip:
   `/api/v1/movement/trips/:id`
+- inspect one saved movement box before repairing it:
+  `/api/v1/movement/boxes/:id`
 - fill a missing span:
   `/api/v1/movement/user-boxes/preflight` then `/api/v1/movement/user-boxes`
 - repair or revise one saved overlay:
   `/api/v1/movement/user-boxes/:id`
+- delete one saved overlay:
+  `DELETE /api/v1/movement/user-boxes/:id`
 - repair one recorded automatic box:
   `/api/v1/movement/automatic-boxes/:id/invalidate`
 - edit an already-recorded stay, trip, or trip point:
   `/api/v1/movement/stays/:id`, `/api/v1/movement/trips/:id`, or `/api/v1/movement/trips/:id/points/:pointId`
+- delete an already-recorded stay, trip, or trip point:
+  `DELETE /api/v1/movement/stays/:id`, `DELETE /api/v1/movement/trips/:id`, or `DELETE /api/v1/movement/trips/:id/points/:pointId`
 
 Ready to act when:
 
@@ -1063,7 +1074,7 @@ Ready to act when:
 
 Preferred opening question:
 
-- "What are you trying to make clearer or correct about where you stayed and traveled?"
+- "What are you trying to understand, correct, or preserve about where you stayed and traveled?"
 
 ## Life Force
 
@@ -1109,6 +1120,8 @@ Direct action rules:
   template instead of editing the profile.
 - If the user is describing right-now depletion or recovery, post a fatigue signal and
   then read the overview back if they want to see the updated picture.
+- After a profile or weekday-template change, read the overview back when the user is
+  trying to understand the practical impact of the change, not just store it silently.
 
 Ready to act when:
 
@@ -1118,7 +1131,7 @@ Ready to act when:
 
 Preferred opening question:
 
-- "What feels most off, important, or worth tracking in your energy picture right now?"
+- "What feels most off, important, or worth understanding in your energy picture right now?"
 
 ## Workbench
 
@@ -1153,6 +1166,8 @@ Lane-to-route map:
   `/api/v1/workbench/flows/:id/run`
 - run from a payload-first contract:
   `/api/v1/workbench/run`
+- send one follow-up message into a saved flow chat:
+  `/api/v1/workbench/flows/:id/chat`
 - inspect published output or run history:
   `/api/v1/workbench/flows/:id/output` or `/api/v1/workbench/flows/:id/runs`
 - inspect one run or node result:
@@ -1173,6 +1188,8 @@ Direct action rules:
   `/api/v1/workbench/run`.
 - If the user wants one node's latest successful output, do not browse old runs first
   unless they explicitly want historical debugging.
+- If the user wants to understand what inputs a flow can accept before editing or
+  running it, read the box catalog or flow detail before asking for a payload.
 
 Ready to act when:
 
@@ -1182,7 +1199,7 @@ Ready to act when:
 
 Preferred opening question:
 
-- "What are you trying to inspect a flow, change it, run it, or publish from Workbench?"
+- "What are you trying to inspect, change, run, or publish through Workbench?"
 
 ## Preference Catalog
 

package/skills/forge-openclaw/psyche_entity_playbooks.md

@@ -350,6 +350,9 @@ If the entity is already clear:
 
 - reflect briefly
 - name the core meaning in the user's language
+- if the user already gave a serviceable belief sentence, mode name, value phrase, or
+  pattern title, stay inside that wording long enough to reflect the live stake before
+  you ask for the one missing structural detail
 - keep the user's own wording when it is already serviceable and only refine one
   phrase if needed
 - ask only for the one missing structural detail
@@ -376,6 +379,8 @@ If the entity is not yet clear:
   replacing it with a more polished label unless they ask for help wording it.
 - When the user says the current wording misses, say what seems newly true before you
   ask whether the old name still fits.
+- If a recent charged episode is what made the update visible, anchor in that episode
+  before you rename the durable belief, pattern, mode, or value.
 - If another belief, value, pattern, mode, or note becomes visible, name it gently but
   do not switch containers unless the user wants to.
 
@@ -386,9 +391,11 @@ from scratch.
 
 1. Ask what feels newly true, newly visible, or newly inaccurate.
 2. Ask what still feels essentially right and should not be lost.
-3. Re-check the name only if the old wording no longer fits the lived experience.
-4. Ask for one concrete recent example if the update is abstract or sweeping.
-5. Then change only the parts the new understanding actually affects.
+3. If the update was triggered by one recent charged episode, anchor in that episode
+   before you re-check the durable formulation.
+4. Re-check the name only if the old wording no longer fits the lived experience.
+5. Ask for one concrete recent example if the update is abstract or sweeping.
+6. Then change only the parts the new understanding actually affects.
 
 If the update is mostly about wording, offer one revised sentence yourself and ask
 whether it lands more accurately before you reopen the whole exploration.