forge-openclaw-plugin 0.2.27 → 0.2.29

package/dist/server/server/src/types.js

@@ -45,7 +45,8 @@ export const calendarProviderSchema = z.enum([
     "google",
     "apple",
     "caldav",
-    "microsoft"
+    "microsoft",
+    "macos_local"
 ]);
 export const calendarConnectionStatusSchema = z.enum([
     "connected",
@@ -59,8 +60,16 @@ export const calendarEventOriginSchema = z.enum([
     "apple",
     "caldav",
     "microsoft",
+    "macos_local",
     "derived"
 ]);
+export const macosCalendarAccessStatusSchema = z.enum([
+    "not_determined",
+    "denied",
+    "restricted",
+    "full_access",
+    "unavailable"
+]);
 export const calendarAvailabilitySchema = z.enum(["busy", "free"]);
 export const calendarEventStatusSchema = z.enum([
     "confirmed",
@@ -578,6 +587,7 @@ export const lifeForcePayloadSchema = z.object({
     spentTodayAp: z.number(),
     remainingAp: z.number(),
     forecastAp: z.number(),
+    plannedRemainingAp: z.number(),
     targetBandMinAp: z.number().min(0),
     targetBandMaxAp: z.number().min(0),
     instantCapacityApPerHour: z.number().min(0),
@@ -591,6 +601,7 @@ export const lifeForcePayloadSchema = z.object({
     stats: z.array(lifeForceStatStateSchema),
     currentCurve: z.array(lifeForceCurvePointSchema),
     activeDrains: z.array(lifeForceDrainEntrySchema),
+    plannedDrains: z.array(lifeForceDrainEntrySchema),
     warnings: z.array(lifeForceWarningSchema),
     recommendations: z.array(trimmedString),
     topTaskIdsNeedingSplit: z.array(z.string()),
@@ -790,7 +801,13 @@ export const calendarDiscoveryCalendarSchema = z.object({
     isPrimary: z.boolean(),
     canWrite: z.boolean(),
     selectedByDefault: z.boolean(),
-    isForgeCandidate: z.boolean()
+    isForgeCandidate: z.boolean(),
+    sourceId: trimmedString.nullable().default(null),
+    sourceTitle: trimmedString.nullable().default(null),
+    sourceType: trimmedString.nullable().default(null),
+    calendarType: trimmedString.nullable().default(null),
+    hostCalendarId: trimmedString.nullable().default(null),
+    canonicalKey: trimmedString.nullable().default(null)
 });
 export const calendarDiscoveryPayloadSchema = z.object({
     provider: calendarProviderSchema,
@@ -800,6 +817,19 @@ export const calendarDiscoveryPayloadSchema = z.object({
     homeUrl: z.string().nullable(),
     calendars: z.array(calendarDiscoveryCalendarSchema)
 });
+export const macosLocalCalendarSourceSchema = z.object({
+    sourceId: nonEmptyTrimmedString,
+    sourceTitle: trimmedString,
+    sourceType: trimmedString,
+    accountLabel: trimmedString,
+    accountIdentityKey: trimmedString,
+    calendars: z.array(calendarDiscoveryCalendarSchema)
+});
+export const macosLocalCalendarDiscoveryPayloadSchema = z.object({
+    status: macosCalendarAccessStatusSchema,
+    requestedAt: z.string(),
+    sources: z.array(macosLocalCalendarSourceSchema)
+});
 export const calendarSchema = z.object({
     id: z.string(),
     connectionId: z.string(),
@@ -812,6 +842,12 @@ export const calendarSchema = z.object({
     canWrite: z.boolean(),
     selectedForSync: z.boolean(),
     forgeManaged: z.boolean(),
+    sourceId: trimmedString.nullable().default(null),
+    sourceTitle: trimmedString.nullable().default(null),
+    sourceType: trimmedString.nullable().default(null),
+    calendarType: trimmedString.nullable().default(null),
+    hostCalendarId: trimmedString.nullable().default(null),
+    canonicalKey: trimmedString.nullable().default(null),
     lastSyncedAt: z.string().nullable(),
     createdAt: z.string(),
     updatedAt: z.string()
@@ -887,6 +923,7 @@ export const calendarEventSchema = z.object({
     categories: z.array(z.string()).default([]),
     sourceMappings: z.array(calendarEventSourceSchema).default([]),
     links: z.array(calendarEventLinkSchema).default([]),
+    actionProfile: actionProfileSchema.nullable().default(null),
     remoteUpdatedAt: z.string().nullable(),
     deletedAt: z.string().nullable(),
     createdAt: z.string(),
@@ -906,6 +943,7 @@ export const workBlockTemplateSchema = z
     startsOn: dateOnlySchema.nullable().default(null),
     endsOn: dateOnlySchema.nullable().default(null),
     blockingState: z.enum(["allowed", "blocked"]),
+    actionProfile: actionProfileSchema.nullable().default(null),
     createdAt: z.string(),
     updatedAt: z.string(),
     ...ownershipShape
@@ -937,6 +975,7 @@ export const workBlockInstanceSchema = z.object({
     color: z.string(),
     blockingState: z.enum(["allowed", "blocked"]),
     calendarEventId: z.string().nullable(),
+    actionProfile: actionProfileSchema.nullable().default(null),
     createdAt: z.string(),
     updatedAt: z.string()
 });
@@ -954,6 +993,7 @@ export const taskTimeboxSchema = z.object({
     startsAt: z.string(),
     endsAt: z.string(),
     overrideReason: trimmedString.nullable(),
+    actionProfile: actionProfileSchema.nullable().default(null),
     createdAt: z.string(),
     updatedAt: z.string(),
     ...ownershipShape
@@ -2352,6 +2392,15 @@ export const createCalendarConnectionSchema = z.discriminatedUnion("provider", [
         label: nonEmptyTrimmedString,
         authSessionId: nonEmptyTrimmedString,
         selectedCalendarUrls: z.array(nonEmptyTrimmedString.url()).min(1)
+    }),
+    z.object({
+        provider: z.literal("macos_local"),
+        label: nonEmptyTrimmedString,
+        sourceId: nonEmptyTrimmedString,
+        selectedCalendarUrls: z.array(nonEmptyTrimmedString.url()).min(1),
+        forgeCalendarUrl: nonEmptyTrimmedString.url().nullable().optional(),
+        createForgeCalendar: z.boolean().optional().default(false),
+        replaceConnectionIds: z.array(nonEmptyTrimmedString).optional().default([])
     })
 ]);
 export const discoverCalendarConnectionSchema = z.discriminatedUnion("provider", [
@@ -2416,7 +2465,11 @@ const workBlockTemplateMutationShape = {
     userId: nonEmptyTrimmedString.nullable().optional()
 };
 export const createWorkBlockTemplateSchema = z
-    .object(workBlockTemplateMutationShape)
+    .object({
+    ...workBlockTemplateMutationShape,
+    activityPresetKey: trimmedString.nullable().optional(),
+    customSustainRateApPerHour: z.number().min(0).nullable().optional()
+})
     .superRefine((value, context) => {
     if (value.endMinute <= value.startMinute) {
         context.addIssue({
@@ -2448,6 +2501,8 @@ export const updateWorkBlockTemplateSchema = z
     startsOn: dateOnlySchema.nullable().optional(),
     endsOn: dateOnlySchema.nullable().optional(),
     blockingState: z.enum(["allowed", "blocked"]).optional(),
+    activityPresetKey: trimmedString.nullable().optional(),
+    customSustainRateApPerHour: z.number().min(0).nullable().optional(),
     userId: nonEmptyTrimmedString.nullable().optional()
 })
     .superRefine((value, context) => {
@@ -2482,6 +2537,8 @@ export const createTaskTimeboxSchema = z
     source: calendarTimeboxSourceSchema.default("manual"),
     status: calendarTimeboxStatusSchema.default("planned"),
     overrideReason: trimmedString.nullable().default(null),
+    activityPresetKey: trimmedString.nullable().optional(),
+    customSustainRateApPerHour: z.number().min(0).nullable().optional(),
     userId: nonEmptyTrimmedString.nullable().optional()
 })
     .superRefine((value, context) => {
@@ -2499,6 +2556,8 @@ export const updateTaskTimeboxSchema = z.object({
     endsAt: z.string().datetime().optional(),
     status: calendarTimeboxStatusSchema.optional(),
     overrideReason: trimmedString.nullable().optional(),
+    activityPresetKey: trimmedString.nullable().optional(),
+    customSustainRateApPerHour: z.number().min(0).nullable().optional(),
     userId: nonEmptyTrimmedString.nullable().optional()
 });
 export const recommendTaskTimeboxesSchema = z.object({
@@ -2530,6 +2589,8 @@ export const updateCalendarEventSchema = z
     availability: calendarAvailabilitySchema.optional(),
     eventType: trimmedString.optional(),
     categories: z.array(trimmedString).optional(),
+    activityPresetKey: trimmedString.nullable().optional(),
+    customSustainRateApPerHour: z.number().min(0).nullable().optional(),
     preferredCalendarId: nonEmptyTrimmedString.nullable().optional(),
     userId: nonEmptyTrimmedString.nullable().optional(),
     links: z
@@ -2582,6 +2643,8 @@ export const createCalendarEventSchema = z
     availability: calendarAvailabilitySchema.default("busy"),
     eventType: trimmedString.default(""),
     categories: z.array(trimmedString).default([]),
+    activityPresetKey: trimmedString.nullable().optional(),
+    customSustainRateApPerHour: z.number().min(0).nullable().optional(),
     preferredCalendarId: nonEmptyTrimmedString.nullable().optional(),
     userId: nonEmptyTrimmedString.nullable().optional(),
     links: z
@@ -2814,6 +2877,7 @@ export const updateTaskSchema = z.object({
     title: nonEmptyTrimmedString.optional(),
     description: trimmedString.optional(),
     status: taskStatusSchema.optional(),
+    completedAt: dateTimeSchema.optional(),
     priority: taskPrioritySchema.optional(),
     owner: nonEmptyTrimmedString.optional(),
     userId: nonEmptyTrimmedString.nullable().optional(),

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

@@ -3,6 +3,7 @@ export class ForgeApiError extends Error {
     code;
     details;
     requestPath;
+    response;
     constructor(input) {
         super(input.message);
         this.name = "ForgeApiError";
@@ -10,6 +11,7 @@ export class ForgeApiError extends Error {
         this.code = input.code;
         this.details = input.details ?? [];
         this.requestPath = input.requestPath;
+        this.response = input.response ?? null;
     }
 }
 export function describeApiError(error) {

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

@@ -130,7 +130,12 @@ async function request(path, init) {
                         ? body
                         : `Request failed: ${response.status}`,
             requestPath: path,
-            details
+            details,
+            response: typeof body === "string"
+                ? body
+                : body && typeof body === "object"
+                    ? body
+                    : null
         });
     }
     return body;
@@ -161,7 +166,12 @@ async function requestBlob(path, init) {
                     ? maybeBody.message
                     : `Request failed: ${response.status}`,
             requestPath: path,
-            details: []
+            details: [],
+            response: typeof body === "string"
+                ? body
+                : body && typeof body === "object"
+                    ? body
+                    : null
         });
     }
     const disposition = response.headers.get("content-disposition");
@@ -1109,6 +1119,33 @@ export function discoverCalendarConnection(input) {
         discovery: dedupeCalendarDiscoveryPayload(response.discovery)
     }));
 }
+export function getMacOSLocalCalendarStatus() {
+    return request("/api/v1/calendar/macos-local/status");
+}
+export function requestMacOSLocalCalendarAccess() {
+    return request("/api/v1/calendar/macos-local/request-access", {
+        method: "POST"
+    });
+}
+export function discoverMacOSLocalCalendarSources() {
+    return request("/api/v1/calendar/macos-local/discovery").then((response) => ({
+        ...response,
+        discovery: {
+            ...response.discovery,
+            sources: response.discovery.sources.map((source) => ({
+                ...source,
+                calendars: dedupeCalendarDiscoveryPayload({
+                    provider: "macos_local",
+                    accountLabel: source.accountLabel,
+                    serverUrl: "forge-macos-local://eventkit/",
+                    principalUrl: null,
+                    homeUrl: null,
+                    calendars: source.calendars
+                }).calendars
+            }))
+        }
+    }));
+}
 export function startGoogleCalendarOauth(input) {
     return request("/api/v1/calendar/oauth/google/start", {
         method: "POST",

package/dist/server/src/lib/calendar-name-deduper.js

@@ -16,6 +16,8 @@ function shortCalendarProviderLabel(provider) {
             return "Apple";
         case "microsoft":
             return "Microsoft";
+        case "macos_local":
+            return "Mac";
         case "caldav":
         default:
             return "CalDAV";

package/dist/server/src/lib/snapshot-normalizer.js

@@ -394,6 +394,7 @@ export function normalizeForgeSnapshot(raw) {
             spentTodayAp: 0,
             remainingAp: 200,
             forecastAp: 0,
+            plannedRemainingAp: 0,
             targetBandMinAp: 170,
             targetBandMaxAp: 200,
             instantCapacityApPerHour: 0,
@@ -407,6 +408,7 @@ export function normalizeForgeSnapshot(raw) {
             stats: [],
             currentCurve: [],
             activeDrains: [],
+            plannedDrains: [],
             warnings: [],
             recommendations: [],
             topTaskIdsNeedingSplit: [],

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

package/package.json

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

package/server/migrations/044_macos_local_calendar_provider.sql

@@ -0,0 +1,21 @@
+ALTER TABLE calendar_calendars
+ADD COLUMN source_id TEXT;
+
+ALTER TABLE calendar_calendars
+ADD COLUMN source_title TEXT;
+
+ALTER TABLE calendar_calendars
+ADD COLUMN source_type TEXT;
+
+ALTER TABLE calendar_calendars
+ADD COLUMN calendar_type TEXT;
+
+ALTER TABLE calendar_calendars
+ADD COLUMN host_calendar_id TEXT;
+
+ALTER TABLE calendar_calendars
+ADD COLUMN canonical_key TEXT;
+
+UPDATE calendar_calendars
+SET canonical_key = remote_id
+WHERE canonical_key IS NULL OR TRIM(canonical_key) = '';

package/skills/forge-openclaw/SKILL.md

@@ -56,9 +56,16 @@ Entity conversation rule:
 - Before you ask, decide the exact missing thing you need and how that answer will help you name, place, or save the record.
 - Prefer a progression of:
   concrete example or intent -> working name -> purpose or meaning -> placement in Forge -> operational details -> linked context.
+- Use those same playbooks for action-heavy non-Psyche flows such as `work_adjustment`, `preference_judgment`, `preference_signal`, and specialized `movement`, `life_force`, or `workbench` requests so the conversation starts from what the user is trying to understand, change, add, update, link, or run before you choose the route.
+- When the operation is not already explicit, identify the job first:
+  add, update, review, compare, navigate, link, or run. Skip that meta question
+  when the action is already obvious from the user's wording.
 - For emotionally meaningful non-Psyche records such as goals, habits, and notes, reflect the meaning before you ask for structure.
 - When the user is vague, ask for one small concrete example, stake, or desired outcome before you ask them to name the record.
 - When the user is clear, say what the record seems to be becoming and ask only for the last missing detail.
+- When the user wants to review, compare, inspect, or navigate an existing Forge
+  record, ask what they are trying to understand first and prefer the read path before
+  you reopen create or update intake.
 - 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.
 - The quick intake prompts later in this file are fallback checkpoints, not a script to read aloud.
@@ -260,8 +267,9 @@ Minimum field: `label`
 Usually useful: `description`
 Ask:
 
-1. What should this event type be called?
-2. What kind of incident does it represent?
+1. What kind of repeated moment or incident do you want future reports to name the same way?
+2. What would count as inside this category, and what should stay outside it?
+3. If the meaning is clear but the wording is not, would you like me to suggest a concise label?
 
 `emotion_definition`
 Use for a reusable emotion vocabulary entry.
@@ -269,9 +277,9 @@ Minimum field: `label`
 Usually useful: `description`, `category`
 Ask:
 
-1. What emotion label do you want to reuse?
-2. How would you describe it?
-3. Does it belong to a broader category?
+1. When this feeling is present, what tells you it is this feeling and not a nearby one?
+2. What would you want a later trigger report to mean when it uses this label?
+3. If the felt meaning is clear but the wording is not, would you like me to suggest a concise label or broader category?
 
 Use these rules when choosing tools.
 
@@ -291,9 +299,34 @@ Use the wiki tools for file-first memory work:
 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`
 
+Use the dedicated domain routes for specialized surfaces that are not simple batch entities:
+
+- Movement lives under `/api/v1/movement/*`. Treat it as a dedicated timeline of `stays` and `trips`, not as generic batch CRUD. A `stay` means the user remained in the same place for a span of time. A `trip` means the user traveled between places. Use the movement routes when the user wants to understand time in place, travel behavior, specific stays or trips, known places, or selected-span aggregates such as "how long was I at home in the past 2 weeks?" or "when did I travel last month?".
+- Movement user actions are: query movement behavior, add a place or manual stay/trip overlay, update an existing stay/trip/place, or link a specific movement item to another Forge entity. Keep the explanation user-facing: where they stayed, when they traveled, what changed, and what this movement should be linked to.
+- Movement read lanes map cleanly to the dedicated routes:
+  `/api/v1/movement/day`, `/api/v1/movement/month`, `/api/v1/movement/all-time`,
+  `/api/v1/movement/timeline`, `/api/v1/movement/places`,
+  `/api/v1/movement/selection`, and `/api/v1/movement/trips/:id`.
+- When the user is filling a missing-data gap, the default write path is a user-defined overlay box, not a raw stay or trip patch. Use `POST /api/v1/movement/user-boxes/preflight` if you need to confirm overlap or snap to the nearest missing interval, then `POST /api/v1/movement/user-boxes` with `kind: "stay"` or `kind: "trip"`.
+- Use `PATCH /api/v1/movement/stays/:id` or `PATCH /api/v1/movement/trips/:id` only when the user is editing an existing recorded stay or recorded trip. Do not use those routes to fill a missing span.
+- If the user says something as explicit as "that missing block was me staying home", do not reopen broad intake. Confirm the interval or place only if it is still ambiguous, then create the overlay and read the timeline back.
+- Life Force lives under `/api/v1/life-force*`. Use `GET /api/v1/life-force` for the current energy overview, `PATCH /api/v1/life-force/profile` for durable profile changes, `PUT /api/v1/life-force/templates/:weekday` for weekday curve edits, and `POST /api/v1/life-force/fatigue-signals` for real-time tired or recovered signals.
+- Workbench lives under `/api/v1/workbench/*`. Use those dedicated routes for flow catalog reads, flow CRUD, runs, published outputs, node results, and latest-node-output reads instead of trying to force Workbench through the batch entity routes.
+- Workbench lane hints:
+  use `/api/v1/workbench/flows` for flow catalog and CRUD,
+  `/api/v1/workbench/flows/:id/run` or `/api/v1/workbench/run` for execution,
+  `/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.
+
 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`
 
+Use `forge_adjust_work_minutes` for `work_adjustment` when the user wants a truthful signed minute correction on an existing task or project rather than a fake live run or a retroactive new task.
+
+Use the dedicated Preferences action tools for `preference_judgment` and `preference_signal`:
+`forge_submit_preferences_judgment`, `forge_submit_preferences_signal`, `forge_update_preferences_score`
+
 Use `forge_post_insight` for `insight`.
 Use the calendar tools for provider sync and planning:
 `forge_get_calendar_overview`, `forge_connect_calendar_provider`, `forge_sync_calendar_connection`, `forge_create_work_block_template`, `forge_recommend_task_timeboxes`, `forge_create_task_timebox`