forge-openclaw-plugin 0.2.88 → 0.2.90

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

@@ -66,7 +66,7 @@ import { registerWebRoutes } from "./web.js";
 import { createManagerRuntime } from "./managers/runtime.js";
 import { isManagerError } from "./managers/type-guards.js";
 import { buildCompanionPairingTransport, getCompanionIrohStatus, stopCompanionIroh } from "./services/companion-iroh.js";
-import { createCompanionPairingSession, createCompanionPairingSessionSchema, createSleepSession, createSleepSessionSchema, createWorkoutSession, createWorkoutSessionSchema, deleteSleepSession, deleteWorkoutSession, getCompanionPairingSessionById, getCompanionOverview, getFitnessViewData, getSleepSessionById, getSleepSessionDetailById, getSleepTimelineOverlaysForRange, getSleepViewData, getVitalsViewData, getHealthZoneProfileForUser, getWorkoutSessionById, getWorkoutSessionDetailById, heartbeatCompanionPairing, heartbeatCompanionPairingSchema, healthZoneProfilePatchSchema, abortMobileHealthSyncSession, completeMobileHealthSyncSession, ingestMobileHealthSync, ingestMobileHealthSyncChunk, mobileHealthSyncChunkSchema, mobileHealthSyncSessionCompleteSchema, mobileHealthSyncSessionStartSchema, mobileHealthSyncSchema, patchHealthZoneProfileForUser, patchCompanionPairingSourceState, patchCompanionPairingSourceStateSchema, companionSourceKeySchema, requireValidPairing, startMobileHealthSyncSession, revokeAllCompanionPairingSessions, revokeAllCompanionPairingSessionsSchema, revokeCompanionPairingSession, updateMobileCompanionSourceState, updateMobileCompanionSourceStateSchema, verifyCompanionPairing, verifyCompanionPairingSchema, updateSleepMetadata, updateSleepMetadataSchema, updateWorkoutMetadata, updateWorkoutMetadataSchema } from "./health.js";
+import { createCompanionPairingSession, createCompanionPairingSessionSchema, createSleepSession, createSleepSessionSchema, createWorkoutSession, createWorkoutSessionSchema, deleteSleepSession, deleteWorkoutSession, getCompanionPairingSessionById, getCompanionOverview, getFitnessViewData, getSleepSessionById, getSleepSessionDetailById, getSleepTimelineOverlaysForRange, getSleepViewData, getVitalsViewData, getHealthZoneProfileForUser, getMobileHealthSyncSessionStatus, getWorkoutSessionById, getWorkoutSessionDetailById, heartbeatCompanionPairing, heartbeatCompanionPairingSchema, healthZoneProfilePatchSchema, abortMobileHealthSyncSession, completeMobileHealthSyncSession, ingestMobileHealthSync, ingestMobileHealthSyncChunk, mobileHealthSyncChunkSchema, mobileHealthSyncSessionCompleteSchema, mobileHealthSyncSessionStartSchema, mobileHealthSyncSchema, patchHealthZoneProfileForUser, patchCompanionPairingSourceState, patchCompanionPairingSourceStateSchema, companionSourceKeySchema, requireValidPairing, startMobileHealthSyncSession, 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, 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";
@@ -279,6 +279,8 @@ const AGENT_ONBOARDING_ENTITY_CATALOG_BASE = [
         relationshipRules: [
             "Every project belongs to a goal through goalId.",
             "Tasks can link to a project through projectId.",
+            "Projects can have one owner through userId plus one or more human or bot assignees through assigneeUserIds.",
+            "Projects are PRD-backed initiatives: productRequirementsDocument stores the project brief and workflowStatus stores the board lane separately from lifecycle status.",
             "Projects inherit strategic meaning from their parent goal."
         ],
         searchHints: [
@@ -315,6 +317,14 @@ const AGENT_ONBOARDING_ENTITY_CATALOG_BASE = [
                 enumValues: ["active", "paused", "completed"],
                 defaultValue: "active"
             },
+            {
+                name: "workflowStatus",
+                type: "backlog|focus|in_progress|blocked|done",
+                required: false,
+                description: "Board workflow lane. Keep this separate from lifecycle status.",
+                enumValues: ["backlog", "focus", "in_progress", "blocked", "done"],
+                defaultValue: "backlog"
+            },
             {
                 name: "userId",
                 type: "string|null",
@@ -323,6 +333,26 @@ const AGENT_ONBOARDING_ENTITY_CATALOG_BASE = [
                 defaultValue: null,
                 nullable: true
             },
+            {
+                name: "assigneeUserIds",
+                type: "string[]",
+                required: false,
+                description: "Human or bot user ids assigned to collaborate on the project.",
+                defaultValue: []
+            },
+            {
+                name: "productRequirementsDocument",
+                type: "string",
+                required: false,
+                description: "Project PRD or brief: outcome, scope, constraints, and acceptance direction.",
+                defaultValue: ""
+            },
+            {
+                name: "schedulingRules",
+                type: "CalendarSchedulingRules",
+                required: false,
+                description: "Optional calendar/work-block rules that govern when this project may be scheduled."
+            },
             {
                 name: "targetPoints",
                 type: "integer",
@@ -431,19 +461,24 @@ const AGENT_ONBOARDING_ENTITY_CATALOG_BASE = [
     },
     {
         entityType: "task",
-        purpose: "A concrete actionable work item. Tasks are what the user actually does.",
+        purpose: "A concrete actionable work item. The same stored family carries issue, task, and subtask levels; tasks are the one-session execution layer.",
         minimumCreateFields: ["title"],
         relationshipRules: [
-            "A task can link to a goal, a project, both, or neither.",
+            "Use level=issue for vertical slices under a project, level=task for one focused AI or human work session, and level=subtask for lightweight child steps.",
+            "In hierarchy-aware Forge PM, issues live directly under projects, tasks live under issues, and subtasks live under tasks.",
+            "Legacy or inbox tasks may still link to a goal, project, both, or neither when the hierarchy is intentionally absent.",
+            "When placement matters, ask for the project, issue, or parent task that changes the hierarchy instead of asking a flat parent question.",
+            "Work items can have one owner through userId plus one or more human or bot assignees through assigneeUserIds.",
             "Live work is tracked by task runs, not by task status alone.",
             "A task status of in_progress does not guarantee a live active run."
         ],
         searchHints: [
             "Search by title before creating a duplicate task.",
-            "Use linkedTo filters when you know the parent goal or project."
+            "Use linkedTo filters when you know the parent goal, project, issue, task, or subtask.",
+            "Use level and parentWorkItemId filters when the user is navigating the issue/task/subtask hierarchy."
         ],
         examples: [
-            '{"title":"Write the plugin release notes","projectId":"project_forge_plugin_launch","status":"focus","priority":"high"}'
+            '{"title":"Add route-key example coverage","level":"task","projectId":"project_forge_plugin_launch","parentWorkItemId":"issue_question_flow_contract","aiInstructions":"Update the onboarding contract and tests so Workbench one-off execution has a route-key example.","status":"focus","priority":"high"}'
         ],
         fieldGuide: [
             {
@@ -459,6 +494,14 @@ const AGENT_ONBOARDING_ENTITY_CATALOG_BASE = [
                 description: "Markdown context, constraints, or acceptance notes.",
                 defaultValue: ""
             },
+            {
+                name: "level",
+                type: "issue|task|subtask",
+                required: false,
+                description: "Work-item level. Use issue for vertical slices, task for one focused execution session, and subtask for lightweight child steps.",
+                enumValues: ["issue", "task", "subtask"],
+                defaultValue: "task"
+            },
             {
                 name: "status",
                 type: "backlog|focus|in_progress|blocked|done",
@@ -490,6 +533,13 @@ const AGENT_ONBOARDING_ENTITY_CATALOG_BASE = [
                 defaultValue: null,
                 nullable: true
             },
+            {
+                name: "assigneeUserIds",
+                type: "string[]",
+                required: false,
+                description: "Human or bot user ids assigned to collaborate on this issue, task, or subtask.",
+                defaultValue: []
+            },
             {
                 name: "goalId",
                 type: "string|null",
@@ -506,6 +556,52 @@ const AGENT_ONBOARDING_ENTITY_CATALOG_BASE = [
                 defaultValue: null,
                 nullable: true
             },
+            {
+                name: "parentWorkItemId",
+                type: "string|null",
+                required: false,
+                description: "Parent issue id for level=task or parent task id for level=subtask. Issues should sit directly under projectId.",
+                defaultValue: null,
+                nullable: true
+            },
+            {
+                name: "aiInstructions",
+                type: "string",
+                required: false,
+                description: "Execution instructions for the agent or human doing the one-session task.",
+                defaultValue: ""
+            },
+            {
+                name: "executionMode",
+                type: "afk|hitl|null",
+                required: false,
+                description: "Whether the issue or task is intended for autonomous work or human-in-the-loop work.",
+                enumValues: ["afk", "hitl"],
+                defaultValue: null,
+                nullable: true
+            },
+            {
+                name: "acceptanceCriteria",
+                type: "string[]",
+                required: false,
+                description: "Structured success criteria, usually Given/When/Then for issues or concrete done checks for tasks.",
+                defaultValue: []
+            },
+            {
+                name: "blockerLinks",
+                type: "Array<{ entityType, entityId, label? }>",
+                required: false,
+                description: "Optional blockers linked to Forge entities that make the work unable to proceed.",
+                defaultValue: []
+            },
+            {
+                name: "completionReport",
+                type: "{ modifiedFiles: string[], workSummary: string, linkedGitRefIds: string[] }|null",
+                required: false,
+                description: "Closeout report for completed work items, especially tasks finished by agents.",
+                defaultValue: null,
+                nullable: true
+            },
             {
                 name: "dueDate",
                 type: "YYYY-MM-DD|null",
@@ -3007,10 +3103,11 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
             "Ask what this piece of work is trying to make true.",
             "Reflect the emerging boundary so the user can hear what is in scope.",
             "Ask what outcome would make the project feel real or complete for now.",
+            "Ask what belongs in the project PRD or brief when the user is shaping delivery rather than only naming a project.",
             "Ask what belongs inside the boundary and what can stay out if the scope still feels muddy.",
             "Ask which goal it belongs under.",
             "Land on a working name once the scope is clear.",
-            "Clarify status, owner, and notes only after the scope is clear."
+            "Clarify lifecycle status, workflow lane, owner, human/bot assignees, scheduling rules, and notes only after the scope is clear."
         ]
     },
     {
@@ -3028,11 +3125,13 @@ const AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS = [
     {
         focus: "task",
         openingQuestion: "What is the next concrete move here?",
-        coachingGoal: "Identify the next concrete move, not just capture a vague obligation.",
+        coachingGoal: "Identify the next concrete one-session work item and place it in the issue/task/subtask hierarchy when that hierarchy matters.",
         askSequence: [
             "Ask what the next concrete action is.",
-            "Ask where it belongs: project, goal, both, or standalone.",
-            "Ask what would make it easier to do: due date, priority, owner, or brief context."
+            "Ask whether this is an issue, one-session task, or subtask only when the level is not already obvious.",
+            "Ask where it belongs in the hierarchy: project for an issue, issue for a task, or parent task for a subtask. Use goal or standalone only when the user is intentionally outside the PM hierarchy.",
+            "Capture the execution contract in aiInstructions when the task is for an agent session.",
+            "Ask what would make it easier to do: due date, priority, owner, human/bot assignees, acceptance criteria, or brief context."
         ]
     },
     {
@@ -3499,6 +3598,7 @@ const AGENT_ONBOARDING_PSYCHE_PLAYBOOKS = [
             "Use an ACT-style values clarification stance: values are directions to live toward, not boxes to complete.",
             "Ask one or two questions at a time, reflect back the user's language, and only then move toward naming committed actions or linked work items.",
             "Reflect the pain, longing, or importance that makes the value alive before narrowing to action.",
+            "Once one ordinary moment is clear, offer one tentative hypothesis about the pain, longing, or value conflict that makes this value alive now, then ask whether it lands before turning it into action wording.",
             "If the user says they want to understand it first, start with one orienting question before offering a formulation or save suggestion."
         ]
     },
@@ -3585,7 +3685,8 @@ const AGENT_ONBOARDING_PSYCHE_PLAYBOOKS = [
             "When the behavior clearly belongs inside a larger loop, suggest linking or also mapping the related behavior_pattern.",
             "If the user asks for understanding before storage, ask about the recent example and function of the move before classifying it.",
             "Ask what the move is trying to do for the user before moving into replacement planning.",
-            "Name the immediate protective job before discussing costs or alternatives."
+            "Name the immediate protective job before discussing costs or alternatives.",
+            "Once one example is clear, offer one tentative hypothesis about the immediate problem the behavior solves, the cue or urge that pulls it online, and the cost it creates later."
         ]
     },
     {
@@ -3703,7 +3804,8 @@ const AGENT_ONBOARDING_PSYCHE_PLAYBOOKS = [
         notes: [
             "A mode_guide_session is the exploration worksheet, not the final identity claim.",
             "Store the user's answers faithfully and keep interpretations tentative unless the user wants a durable mode_profile.",
-            "Use candidate mode interpretations as testable hypotheses tied to the user's answers, not as certain labels."
+            "Use candidate mode interpretations as testable hypotheses tied to the user's answers, not as certain labels.",
+            "After enough answers are visible, offer one hypothesis about what the active part is trying to stop, force, prevent, or secure before proposing any durable mode label."
         ]
     },
     {
@@ -3750,6 +3852,7 @@ const AGENT_ONBOARDING_PSYCHE_PLAYBOOKS = [
             "Use shared batch entity routes for flashcard create, update, delete, restore, and search.",
             "When the user says they feel an urge or trigger, search flashcards by triggerSentence, triggerSituation, tags, message, and linked Psyche records before creating a new card.",
             "When showing a card, display or quote the message first, then add brief grounding, urge-surfing, cognitive defusion, schema-mode, or values-based coaching around it.",
+            "If the cue, urge sentence, mode, belief, or value pivot is clear, offer one hypothesis about what the card needs to meet in the hard moment before polishing its final wording.",
             "Do not make the user fill styling fields before the therapeutic sentence is clear."
         ]
     },
@@ -3830,7 +3933,8 @@ const AGENT_ONBOARDING_PSYCHE_PLAYBOOKS = [
         notes: [
             "event_type is a Psyche taxonomy record, but it still needs active listening because it names emotionally meaningful episodes.",
             "Do not open with pure label wording unless the lived category and boundary are already clear.",
-            "Offer a candidate label after the repeated moment is understood, and keep the user's wording when it already fits."
+            "Offer a candidate label after the repeated moment is understood, and keep the user's wording when it already fits.",
+            "Once one recurring example is clear, offer one hypothesis about the repeated emotional or relational stake that future reports need this event type to preserve."
         ]
     },
     {
@@ -3864,6 +3968,7 @@ const AGENT_ONBOARDING_PSYCHE_PLAYBOOKS = [
         notes: [
             "emotion_definition is a Psyche taxonomy record, not a generic dictionary entry.",
             "Start from the lived feeling before asking for category or browsing fields.",
+            "Once the lived signature is visible, offer one hypothesis about what the emotion warns about, protects, demands, or longs for before saving the reusable definition.",
             "If the user already gives a good label, reflect the felt signature and ask only for the one boundary or definition detail that still matters."
         ]
     }
@@ -4501,11 +4606,13 @@ function buildAgentOnboardingPayload(request) {
         entityConversationPlaybooks: AGENT_ONBOARDING_ENTITY_CONVERSATION_PLAYBOOKS.map(enrichConversationPlaybookWithRouteInfo),
         relationshipModel: [
             "Every Forge record belongs to one typed user owner: either human or bot.",
+            "Projects and work items can also carry assigneeUserIds for one or more human or bot collaborators; ownership and assignment are separate.",
             "Read routes may scope to one user with userId or to several users with repeated userIds.",
             "Ownership and linkage are separate: a human-owned project can link to bot-owned tasks, strategies, notes, or insights.",
             "Goals are the top-level strategic layer.",
             "Projects belong to one goal through goalId.",
-            "Tasks can belong to a goal, a project, both, or neither.",
+            "The task entity is the stored work-item family for issue, task, and subtask levels.",
+            "Hierarchy-aware PM should place issues under projects, tasks under issues, and subtasks under tasks; standalone or goal-linked tasks are legacy/inbox escape hatches rather than the default planning path.",
             "Strategies can target one or many goals or projects while sequencing project and task nodes through a directed acyclic graph.",
             "A strategy remains editable until it is locked. Once locked, the plan becomes a contract and graph-shape edits should stop until the strategy is explicitly unlocked.",
             "Habits are recurring records that can connect directly to goals, projects, tasks, and durable Psyche entities.",
@@ -5114,6 +5221,8 @@ function buildAgentOnboardingPayload(request) {
             reviewShortcutRule: "When the user is reviewing or correcting an existing record, ask what practical question they want the read or correction to answer, then 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 only when a lightweight episode observation is the right container. Do not use it as the default bucket for Psyche material: prefer trigger_report for one emotionally meaningful episode, behavior_pattern for functional analysis of a recurring loop, behavior for one repeated move, belief_entry for a core sentence, mode_guide_session or mode_profile for a central part-state, and wiki_page for durable memory such as books, articles, concepts, sources, or personal manuals. 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.",
+            followUpQuestionRule: "After a substantive answer, do not restart the opener or jump to the next schema field. First say what became clearer in concrete language, then choose exactly one next lane: wording, boundary, placement, timing, route scope, link, hypothesis, or write confirmation. Ask the smallest question that would change the record shape, route choice, useful wording, timing, or links. If nothing decision-relevant would change, stop asking, summarize the working record, and act with consent.",
+            antiDriftRule: "Avoid vague reflective filler and internal route language. Replace phrases like 'that sounds important' with the specific stake you heard, and replace API nouns like surface, CRUD, payload, mutation path, or endpoint with user-facing product nouns such as belief, pattern, note, wiki page, timeline, overlay, weekday template, flow, run, node result, or published output. If a question would only decorate the intake, skip it.",
             duplicateCheckRoute: "/api/v1/entities/search",
             uiSuggestionRule: "offer_visual_ui_when_review_or_editing_would_be_easier",
             browserFallbackRule: "Do not open the Forge UI or a browser just to create or update normal entities when the batch entity tools can do the job. Batch CRUD is the default for simple entities; avoid spamming the agent with a large one-route-per-entity mental model.",
@@ -5161,6 +5270,7 @@ function buildAgentOnboardingPayload(request) {
                 workbenchPublishedOutput: '{"routeKey":"publishedOutput","pathParams":{"id":"flow_research_digest"}}',
                 workbenchLatestNodeOutput: '{"routeKey":"latestNodeOutput","pathParams":{"id":"flow_research_digest","nodeId":"node_summary"}}',
                 workbenchRunFlow: '{"routeKey":"runFlow","pathParams":{"id":"flow_research_digest"},"body":{"input":{"topic":"question flow quality"}}}',
+                workbenchRunByPayload: '{"routeKey":"runByPayload","body":{"flow":{"title":"One-off digest","nodes":[]},"input":{"topic":"question flow quality"}}}',
                 workbenchChatFlow: '{"routeKey":"chatFlow","pathParams":{"id":"flow_research_digest"},"body":{"message":"Refine the summary around API route risks and keep the published output stable."}}'
             }
         }
@@ -7670,6 +7780,18 @@ export async function buildServer(options = {}) {
     app.post("/api/v1/mobile/healthkit/sync-sessions", async (request) => ({
         upload: startMobileHealthSyncSession(mobileHealthSyncSessionStartSchema.parse(request.body ?? {}))
     }));
+    app.get("/api/v1/mobile/healthkit/sync-sessions/:id", async (request) => {
+        const { id } = request.params;
+        const query = z
+            .object({
+            sessionId: z.string().trim().min(1),
+            pairingToken: z.string().trim().min(1)
+        })
+            .parse(request.query ?? {});
+        return {
+            upload: getMobileHealthSyncSessionStatus(id, query)
+        };
+    });
     app.post("/api/v1/mobile/healthkit/sync-sessions/:id/chunks", { bodyLimit: 40_000_000 }, async (request) => {
         const { id } = request.params;
         const rawPayloadJson = JSON.stringify((request.body ?? {}).payload ?? {});

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

@@ -2714,6 +2714,57 @@ function readMobileSyncSession(syncSessionId) {
         .prepare(`SELECT * FROM health_mobile_sync_sessions WHERE id = ?`)
         .get(syncSessionId);
 }
+function mobileSyncSessionProgress(syncSessionId) {
+    const chunks = getDatabase()
+        .prepare(`SELECT family, record_count, byte_count
+       FROM health_mobile_sync_chunks
+       WHERE sync_session_id = ?`)
+        .all(syncSessionId);
+    const receivedCounts = {};
+    const byteTotals = {};
+    for (const chunk of chunks) {
+        receivedCounts[chunk.family] =
+            (receivedCounts[chunk.family] ?? 0) + chunk.record_count;
+        byteTotals[chunk.family] =
+            (byteTotals[chunk.family] ?? 0) + chunk.byte_count;
+    }
+    return {
+        receivedCounts,
+        byteTotals,
+        chunkCount: chunks.length,
+        receivedBytes: chunks.reduce((sum, chunk) => sum + chunk.byte_count, 0)
+    };
+}
+function mobileSyncSessionUploadPayload(session, receivedChunkIds) {
+    return {
+        syncSessionId: session.id,
+        schemaVersion: HEALTH_MOBILE_SYNC_SCHEMA_VERSION,
+        status: session.status,
+        chunkTargetBytes: HEALTH_MOBILE_SYNC_CHUNK_TARGET_BYTES,
+        chunkMaxBytes: HEALTH_MOBILE_SYNC_CHUNK_MAX_BYTES,
+        chunkPayloadEncoding: HEALTH_MOBILE_SYNC_CHUNK_PAYLOAD_ENCODING,
+        acceptedPayloadEncodings: HEALTH_MOBILE_SYNC_ACCEPTED_CHUNK_PAYLOAD_ENCODINGS,
+        supportsCompression: true,
+        acceptedFamilies: safeJsonParse(session.requested_families_json, []),
+        receivedChunkIds,
+        progress: mobileSyncSessionProgress(session.id)
+    };
+}
+export function getMobileHealthSyncSessionStatus(syncSessionId, payload) {
+    const pairing = requireValidPairing(payload.sessionId, payload.pairingToken);
+    const session = readMobileSyncSession(syncSessionId);
+    if (!session || session.pairing_session_id !== pairing.id) {
+        throw new HttpError(404, "sync_session_not_found", "The HealthKit sync session does not exist.");
+    }
+    const receivedChunkIds = getDatabase()
+        .prepare(`SELECT chunk_id
+       FROM health_mobile_sync_chunks
+       WHERE sync_session_id = ?
+       ORDER BY sequence ASC`)
+        .all(syncSessionId)
+        .map((row) => row.chunk_id);
+    return mobileSyncSessionUploadPayload(session, receivedChunkIds);
+}
 function ensureRunningMobileSyncSession(syncSessionId) {
     expireStaleMobileSyncSessions();
     const session = readMobileSyncSession(syncSessionId);
@@ -3038,30 +3089,13 @@ function applyWorkoutEvidenceChunkImmediately(session, payload) {
     });
 }
 function updateMobileSyncSessionProgress(syncSessionId) {
-    const chunks = getDatabase()
-        .prepare(`SELECT family, record_count, byte_count
-       FROM health_mobile_sync_chunks
-       WHERE sync_session_id = ?`)
-        .all(syncSessionId);
-    const receivedCounts = {};
-    const byteTotals = {};
-    for (const chunk of chunks) {
-        receivedCounts[chunk.family] =
-            (receivedCounts[chunk.family] ?? 0) + chunk.record_count;
-        byteTotals[chunk.family] =
-            (byteTotals[chunk.family] ?? 0) + chunk.byte_count;
-    }
+    const progress = mobileSyncSessionProgress(syncSessionId);
     getDatabase()
         .prepare(`UPDATE health_mobile_sync_sessions
        SET received_counts_json = ?, byte_totals_json = ?, updated_at = ?
        WHERE id = ?`)
-        .run(JSON.stringify(receivedCounts), JSON.stringify(byteTotals), nowIso(), syncSessionId);
-    return {
-        receivedCounts,
-        byteTotals,
-        chunkCount: chunks.length,
-        receivedBytes: chunks.reduce((sum, chunk) => sum + chunk.byte_count, 0)
-    };
+        .run(JSON.stringify(progress.receivedCounts), JSON.stringify(progress.byteTotals), nowIso(), syncSessionId);
+    return progress;
 }
 export function startMobileHealthSyncSession(payload) {
     const parsed = mobileHealthSyncSessionStartSchema.parse(payload);
@@ -3092,17 +3126,7 @@ export function startMobileHealthSyncSession(payload) {
              ORDER BY sequence ASC`)
                     .all(resumeSyncSessionId)
                     .map((row) => row.chunk_id);
-                return {
-                    syncSessionId: resumeSyncSessionId,
-                    schemaVersion: HEALTH_MOBILE_SYNC_SCHEMA_VERSION,
-                    chunkTargetBytes: HEALTH_MOBILE_SYNC_CHUNK_TARGET_BYTES,
-                    chunkMaxBytes: HEALTH_MOBILE_SYNC_CHUNK_MAX_BYTES,
-                    chunkPayloadEncoding: HEALTH_MOBILE_SYNC_CHUNK_PAYLOAD_ENCODING,
-                    acceptedPayloadEncodings: HEALTH_MOBILE_SYNC_ACCEPTED_CHUNK_PAYLOAD_ENCODINGS,
-                    supportsCompression: true,
-                    acceptedFamilies: existingFamilies,
-                    receivedChunkIds
-                };
+                return mobileSyncSessionUploadPayload(existing, receivedChunkIds);
             }
             getDatabase()
                 .prepare(`UPDATE health_mobile_sync_sessions
@@ -3127,17 +3151,11 @@ export function startMobileHealthSyncSession(payload) {
         sourceStates: parsed.sourceStates,
         metadata: parsed.metadata
     }), JSON.stringify(parsed.expectedCounts), now, now, now);
-    return {
-        syncSessionId,
-        schemaVersion: HEALTH_MOBILE_SYNC_SCHEMA_VERSION,
-        chunkTargetBytes: HEALTH_MOBILE_SYNC_CHUNK_TARGET_BYTES,
-        chunkMaxBytes: HEALTH_MOBILE_SYNC_CHUNK_MAX_BYTES,
-        chunkPayloadEncoding: HEALTH_MOBILE_SYNC_CHUNK_PAYLOAD_ENCODING,
-        acceptedPayloadEncodings: HEALTH_MOBILE_SYNC_ACCEPTED_CHUNK_PAYLOAD_ENCODINGS,
-        supportsCompression: true,
-        acceptedFamilies: parsed.requestedFamilies,
-        receivedChunkIds: []
-    };
+    const session = readMobileSyncSession(syncSessionId);
+    if (!session) {
+        throw new HttpError(500, "sync_session_not_found", "The HealthKit sync session could not be created.");
+    }
+    return mobileSyncSessionUploadPayload(session, []);
 }
 export function ingestMobileHealthSyncChunk(syncSessionId, payload, rawPayloadJson) {
     const parsed = mobileHealthSyncChunkSchema.parse(payload);

package/dist/server/server/src/openapi.js

@@ -28,6 +28,49 @@ const HTTP_METHODS = new Set([
     "options",
     "head"
 ]);
+const mobileHealthSyncProgressSchema = {
+    type: "object",
+    required: [
+        "chunkCount",
+        "receivedBytes",
+        "receivedCounts",
+        "byteTotals"
+    ],
+    properties: {
+        chunkCount: { type: "number" },
+        receivedBytes: { type: "number" },
+        receivedCounts: { type: "object", additionalProperties: { type: "number" } },
+        byteTotals: { type: "object", additionalProperties: { type: "number" } }
+    }
+};
+const mobileHealthSyncUploadSchema = {
+    type: "object",
+    required: [
+        "syncSessionId",
+        "schemaVersion",
+        "status",
+        "targetChunkBytes",
+        "maxChunkBytes",
+        "payloadEncodings",
+        "acceptedFamilies",
+        "receivedChunkIds",
+        "progress"
+    ],
+    properties: {
+        syncSessionId: { type: "string" },
+        schemaVersion: { type: "string" },
+        status: {
+            type: "string",
+            enum: ["running", "completed", "failed", "aborted"]
+        },
+        targetChunkBytes: { type: "number" },
+        maxChunkBytes: { type: "number" },
+        payloadEncodings: arrayOf({ type: "string" }),
+        acceptedFamilies: arrayOf({ type: "string" }),
+        receivedChunkIds: arrayOf({ type: "string" }),
+        progress: mobileHealthSyncProgressSchema
+    }
+};
 const CALENDAR_PROVIDER_VALUES = [
     "google",
     "apple",
@@ -4052,6 +4095,8 @@ export function buildOpenApiDocument() {
                     "reviewShortcutRule",
                     "readModelWriteRule",
                     "psycheOpeningQuestionRule",
+                    "followUpQuestionRule",
+                    "antiDriftRule",
                     "duplicateCheckRoute",
                     "uiSuggestionRule",
                     "browserFallbackRule",
@@ -4067,6 +4112,8 @@ export function buildOpenApiDocument() {
                     reviewShortcutRule: { type: "string" },
                     readModelWriteRule: { type: "string" },
                     psycheOpeningQuestionRule: { type: "string" },
+                    followUpQuestionRule: { type: "string" },
+                    antiDriftRule: { type: "string" },
                     duplicateCheckRoute: { type: "string" },
                     uiSuggestionRule: { type: "string" },
                     browserFallbackRule: { type: "string" },
@@ -5291,6 +5338,144 @@ export function buildOpenApiDocument() {
                     }
                 }
             },
+            "/api/v1/mobile/healthkit/sync-sessions": {
+                post: {
+                    summary: "Start or resume a resumable mobile HealthKit upload session",
+                    requestBody: {
+                        required: true,
+                        content: {
+                            "application/json": {
+                                schema: {
+                                    type: "object",
+                                    required: ["sessionId", "pairingToken", "schemaVersion"],
+                                    properties: {
+                                        sessionId: { type: "string" },
+                                        pairingToken: { type: "string" },
+                                        schemaVersion: { type: "string" },
+                                        resumeSyncSessionId: nullable({ type: "string" }),
+                                        requestedFamilies: arrayOf({ type: "string" }),
+                                        sourceStates: arrayOf({
+                                            type: "object",
+                                            additionalProperties: true
+                                        }),
+                                        device: {
+                                            type: "object",
+                                            additionalProperties: true
+                                        }
+                                    }
+                                }
+                            }
+                        }
+                    },
+                    responses: {
+                        "200": jsonResponse({
+                            type: "object",
+                            required: ["upload"],
+                            properties: {
+                                upload: mobileHealthSyncUploadSchema
+                            }
+                        }, "Accepted upload session plus received chunk progress")
+                    }
+                }
+            },
+            "/api/v1/mobile/healthkit/sync-sessions/{id}": {
+                get: {
+                    summary: "Inspect a mobile HealthKit upload session and accepted chunk progress",
+                    parameters: [
+                        {
+                            name: "id",
+                            in: "path",
+                            required: true,
+                            schema: { type: "string" }
+                        },
+                        {
+                            name: "sessionId",
+                            in: "query",
+                            required: true,
+                            schema: { type: "string" }
+                        },
+                        {
+                            name: "pairingToken",
+                            in: "query",
+                            required: true,
+                            schema: { type: "string" }
+                        }
+                    ],
+                    responses: {
+                        "200": jsonResponse({
+                            type: "object",
+                            required: ["upload"],
+                            properties: {
+                                upload: mobileHealthSyncUploadSchema
+                            }
+                        }, "Upload session status and accepted chunk progress")
+                    }
+                }
+            },
+            "/api/v1/mobile/healthkit/sync-sessions/{id}/chunks": {
+                post: {
+                    summary: "Upload one idempotent HealthKit chunk into a resumable session",
+                    parameters: [
+                        {
+                            name: "id",
+                            in: "path",
+                            required: true,
+                            schema: { type: "string" }
+                        }
+                    ],
+                    requestBody: {
+                        required: true,
+                        content: {
+                            "application/json": {
+                                schema: {
+                                    type: "object",
+                                    required: [
+                                        "sessionId",
+                                        "pairingToken",
+                                        "chunkId",
+                                        "family",
+                                        "sequence",
+                                        "records",
+                                        "byteCount",
+                                        "checksum"
+                                    ],
+                                    properties: {
+                                        sessionId: { type: "string" },
+                                        pairingToken: { type: "string" },
+                                        chunkId: { type: "string" },
+                                        family: { type: "string" },
+                                        sequence: { type: "number" },
+                                        records: { type: "number" },
+                                        byteCount: { type: "number" },
+                                        checksum: { type: "string" },
+                                        compression: nullable({ type: "string" }),
+                                        payloadEncoding: nullable({ type: "string" }),
+                                        payload: {}
+                                    }
+                                }
+                            }
+                        }
+                    },
+                    responses: {
+                        "200": jsonResponse({
+                            type: "object",
+                            required: ["chunk"],
+                            properties: {
+                                chunk: {
+                                    type: "object",
+                                    additionalProperties: true,
+                                    required: ["accepted", "duplicate", "progress"],
+                                    properties: {
+                                        accepted: { type: "boolean" },
+                                        duplicate: { type: "boolean" },
+                                        progress: mobileHealthSyncProgressSchema
+                                    }
+                                }
+                            }
+                        }, "Chunk receipt with duplicate detection and aggregate progress")
+                    }
+                }
+            },
             "/api/v1/doctor": {
                 get: {
                     summary: "Run Forge Doctor diagnostics for runtime, settings, storage, entities, hierarchy, rewards, and fix proposals",

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-openclaw-plugin",
-  "version": "0.2.88",
+  "version": "0.2.90",
   "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

@@ -145,6 +145,8 @@ Concrete route-key examples for internal use:
   `{"routeKey":"latestNodeOutput","pathParams":{"id":"flow_research_digest","nodeId":"node_summary"}}`
 - Workbench run execution:
   `{"routeKey":"runFlow","pathParams":{"id":"flow_research_digest"},"body":{"input":{"topic":"question flow quality"}}}`
+- Workbench one-off input execution:
+  `{"routeKey":"runByPayload","body":{"flow":{"title":"One-off digest","nodes":[]},"input":{"topic":"question flow quality"}}}`
 - Workbench flow chat follow-up:
   `{"routeKey":"chatFlow","pathParams":{"id":"flow_research_digest"},"body":{"message":"Refine the summary around API route risks and keep the published output stable."}}`
 
@@ -349,7 +351,8 @@ Only ask if missing or unclear:
 `project`
 Use for a bounded workstream under a goal.
 Minimum field: `title`
-Usually useful: `goalId`, `description`, `status`
+Usually useful: `goalId`, `description`, `productRequirementsDocument`,
+`status`, `workflowStatus`, `userId`, `assigneeUserIds`, `schedulingRules`
 Only ask if missing or unclear:
 
 1. What should this project be called?
@@ -357,14 +360,18 @@ Only ask if missing or unclear:
 3. What outcome should it produce?
 
 `task`
-Use for one concrete action or deliverable.
+Use for one concrete work item; the same stored family carries `issue`, `task`, and
+`subtask` levels.
 Minimum field: `title`
-Usually useful: `projectId`, `goalId`, `priority`, `dueDate`, `status`, `owner`
+Usually useful: `level`, `projectId`, `parentWorkItemId`, `aiInstructions`,
+`executionMode`, `acceptanceCriteria`, `priority`, `dueDate`, `status`, `userId`,
+`assigneeUserIds`
 Only ask if missing or unclear:
 
 1. What is the task in one concrete sentence?
-2. Should it live under an existing goal or project?
-3. Does it need a due date, priority, or owner?
+2. Is this an issue, one-session task, or subtask?
+3. Should it live under a project, issue, parent task, or intentional inbox?
+4. Does it need agent instructions, acceptance criteria, a due date, priority, owner, or assignees?
 
 `habit`
 Use for a recurring commitment or recurring slip with explicit cadence and XP consequences.

package/skills/forge-openclaw/entity_conversation_playbooks.md

@@ -370,6 +370,23 @@ Closing turn:
 - ask whether it feels true enough to save or needs one correction
 - if the user says yes, move to the write instead of reopening the intake
 
+## Second-turn discipline
+
+After the user answers the opening question, do not restart the opener and do not
+jump to the next schema field. First say what became clearer in concrete language,
+then choose exactly one next lane: wording, boundary, placement, timing, route scope,
+link, hypothesis, or write confirmation.
+
+The second question should be the smallest question that would change the record
+shape, route choice, useful wording, timing, or links. If no answer would change one
+of those things, stop asking, summarize the working record, and act with consent.
+
+Do not drift into vague reflection or internal route language. Replace "that sounds
+important" with the specific stake you heard, and replace API words such as surface,
+CRUD, payload, mutation path, or endpoint with product nouns the user recognizes:
+belief, pattern, note, wiki page, timeline, overlay, weekday template, flow, run,
+node result, or published output.
+
 ## Steering moves
 
 Use these small moves to keep the intake natural and intentional.
@@ -690,17 +707,23 @@ Arc:
 1. Ask what this piece of work is trying to make true.
 2. Reflect the emerging boundary so the user can hear what is in scope.
 3. Ask what outcome would make it feel real or complete for now.
-4. Ask what belongs inside the boundary and what can stay out if the scope still
+4. Ask what belongs in the project PRD or brief when the user is shaping delivery
+   rather than only naming a project.
+5. Ask what belongs inside the boundary and what can stay out if the scope still
    feels muddy.
-5. Ask which goal it belongs under.
-6. Land on a working name once the scope is clear.
-7. Clarify status, owner, and notes only after the scope is clear.
+6. Ask which goal it belongs under.
+7. Land on a working name once the scope is clear.
+8. Clarify lifecycle status, workflow lane, owner, human/bot assignees, scheduling
+   rules, and notes only after the scope is clear.
 
 Helpful follow-up lanes:
 
 - what concrete outcome would make this project complete enough
+- what should go into the PRD or brief
 - what belongs inside the boundary and what does not
 - which goal gives the project meaning
+- whether one owner or several human/bot assignees need to be explicit
+- whether scheduling rules or a board workflow lane matter now
 
 Ready to save when:
 
@@ -744,26 +767,37 @@ Preferred opening question:
 
 ## Task
 
-Aim: identify the next concrete move, not just capture a vague obligation.
+Aim: identify the next concrete one-session work item and place it correctly in the
+issue/task/subtask hierarchy when that hierarchy matters.
 
 Arc:
 
 1. Ask what the next concrete action is.
-2. Ask where it belongs: project, goal, both, or standalone.
-3. Ask what would make it easier to do: due date, priority, owner, or one line of
-   context.
+2. Ask whether it is an issue, one-session task, or subtask only when the level is
+   not already obvious.
+3. Ask where it belongs in the hierarchy: project for an issue, issue for a task, or
+   parent task for a subtask. Use goal or standalone only when the user is
+   intentionally outside the PM hierarchy.
+4. Capture the execution contract in `aiInstructions` when the work is meant for an
+   AI or agent session.
+5. Ask what would make it easier to do: due date, priority, owner, human/bot
+   assignees, acceptance criteria, or one line of context.
 
 Helpful follow-up lanes:
 
 - turn vague intent into an actionable verb
-- identify parent project or goal
-- capture the one timing or priority detail that will actually help
+- decide whether the work item is an issue, task, or subtask
+- identify parent project, issue, or task
+- capture the one-session execution contract in `aiInstructions`
+- decide whether one owner or several human/bot assignees need to be explicit
+- capture the one timing, priority, or acceptance detail that will actually help
 
 Ready to save when:
 
 - the task is phrased as an actionable move
-- placement is clear enough
-- any crucial timing or priority is captured
+- the level is clear enough: issue, task, or subtask
+- placement is clear enough: project, issue, parent task, or intentional inbox
+- any crucial timing, acceptance criteria, or execution instruction is captured
 
 Preferred opening question:
 
@@ -1760,7 +1794,8 @@ Direct action rules:
   "catalog" read when the user needs a runnable flow versus an input-box contract.
 - If the user wants to execute a known saved flow, use `/api/v1/workbench/flows/:id/run`.
 - If the user wants one-off input execution without depending on a saved flow id, use
-  `/api/v1/workbench/run`.
+  `POST /api/v1/workbench/run` through the dedicated one-off execution lane and keep
+  the user-facing question about the one-off input contract.
 - If the user wants to debug one failed execution, narrow whether they need the run
   detail, one node result, the latest node output, or the published output before you
   ask for flow changes.

package/skills/forge-openclaw/psyche_entity_playbooks.md

@@ -339,6 +339,23 @@ Closing turn:
   linked
 - if the user says it lands, move toward the write instead of reopening exploration
 
+## Second-turn therapeutic discipline
+
+After the user's first real answer, do not simply ask another broad origin question
+and do not move into repair because the schema has optional fields left. Briefly name
+the emotional center, function, danger, or value conflict that became clearer, then
+choose one next lane: situation, sequence, meaning, protection, cost, longing,
+naming, hypothesis, link, or save confirmation.
+
+When one concrete example is already clear, a useful second or third turn can be a
+careful interpretive hypothesis rather than another request for raw material. The
+hypothesis should name what the response may be protecting, predicting, relieving, or
+costing, then ask whether that lands or needs correction.
+
+If the accepted formulation is already accurate enough to save, stop deepening. Ask
+one accuracy question, preserve the user's wording, and write through the shared
+batch entity route after consent.
+
 ## Name, Define, Connect
 
 Use this checkpoint once the material is coherent enough.