forge-openclaw-plugin 0.2.24 → 0.2.26

package/server/migrations/028_movement_domain.sql

@@ -0,0 +1,136 @@
+CREATE TABLE IF NOT EXISTS movement_places (
+  id TEXT PRIMARY KEY,
+  external_uid TEXT NOT NULL DEFAULT '',
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  label TEXT NOT NULL,
+  aliases_json TEXT NOT NULL DEFAULT '[]',
+  latitude REAL NOT NULL,
+  longitude REAL NOT NULL,
+  radius_meters REAL NOT NULL DEFAULT 100,
+  category_tags_json TEXT NOT NULL DEFAULT '[]',
+  visibility TEXT NOT NULL DEFAULT 'shared',
+  wiki_note_id TEXT REFERENCES notes(id) ON DELETE SET NULL,
+  linked_entities_json TEXT NOT NULL DEFAULT '[]',
+  linked_people_json TEXT NOT NULL DEFAULT '[]',
+  metadata_json TEXT NOT NULL DEFAULT '{}',
+  source TEXT NOT NULL DEFAULT 'user',
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, source, external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_places_user
+  ON movement_places(user_id, updated_at DESC);
+
+CREATE TABLE IF NOT EXISTS movement_settings (
+  user_id TEXT PRIMARY KEY REFERENCES users(id) ON DELETE CASCADE,
+  tracking_enabled INTEGER NOT NULL DEFAULT 0,
+  publish_mode TEXT NOT NULL DEFAULT 'auto_publish',
+  retention_mode TEXT NOT NULL DEFAULT 'aggregates_only',
+  location_permission_status TEXT NOT NULL DEFAULT 'not_determined',
+  motion_permission_status TEXT NOT NULL DEFAULT 'unknown',
+  background_tracking_ready INTEGER NOT NULL DEFAULT 0,
+  last_companion_sync_at TEXT,
+  metadata_json TEXT NOT NULL DEFAULT '{}',
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL
+);
+
+CREATE TABLE IF NOT EXISTS movement_stays (
+  id TEXT PRIMARY KEY,
+  external_uid TEXT NOT NULL,
+  pairing_session_id TEXT REFERENCES companion_pairing_sessions(id) ON DELETE SET NULL,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  place_id TEXT REFERENCES movement_places(id) ON DELETE SET NULL,
+  label TEXT NOT NULL DEFAULT '',
+  status TEXT NOT NULL DEFAULT 'completed',
+  classification TEXT NOT NULL DEFAULT 'stationary',
+  started_at TEXT NOT NULL,
+  ended_at TEXT NOT NULL,
+  center_latitude REAL NOT NULL,
+  center_longitude REAL NOT NULL,
+  radius_meters REAL NOT NULL DEFAULT 100,
+  sample_count INTEGER NOT NULL DEFAULT 0,
+  weather_json TEXT NOT NULL DEFAULT '{}',
+  metrics_json TEXT NOT NULL DEFAULT '{}',
+  metadata_json TEXT NOT NULL DEFAULT '{}',
+  published_note_id TEXT REFERENCES notes(id) ON DELETE SET NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_stays_user
+  ON movement_stays(user_id, started_at DESC);
+
+CREATE TABLE IF NOT EXISTS movement_trips (
+  id TEXT PRIMARY KEY,
+  external_uid TEXT NOT NULL,
+  pairing_session_id TEXT REFERENCES companion_pairing_sessions(id) ON DELETE SET NULL,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  start_place_id TEXT REFERENCES movement_places(id) ON DELETE SET NULL,
+  end_place_id TEXT REFERENCES movement_places(id) ON DELETE SET NULL,
+  label TEXT NOT NULL DEFAULT '',
+  status TEXT NOT NULL DEFAULT 'completed',
+  travel_mode TEXT NOT NULL DEFAULT 'travel',
+  activity_type TEXT NOT NULL DEFAULT '',
+  started_at TEXT NOT NULL,
+  ended_at TEXT NOT NULL,
+  distance_meters REAL NOT NULL DEFAULT 0,
+  moving_seconds INTEGER NOT NULL DEFAULT 0,
+  idle_seconds INTEGER NOT NULL DEFAULT 0,
+  average_speed_mps REAL,
+  max_speed_mps REAL,
+  calories_kcal REAL,
+  expected_met REAL,
+  weather_json TEXT NOT NULL DEFAULT '{}',
+  tags_json TEXT NOT NULL DEFAULT '[]',
+  linked_entities_json TEXT NOT NULL DEFAULT '[]',
+  linked_people_json TEXT NOT NULL DEFAULT '[]',
+  metadata_json TEXT NOT NULL DEFAULT '{}',
+  published_note_id TEXT REFERENCES notes(id) ON DELETE SET NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_trips_user
+  ON movement_trips(user_id, started_at DESC);
+
+CREATE TABLE IF NOT EXISTS movement_trip_points (
+  id TEXT PRIMARY KEY,
+  trip_id TEXT NOT NULL REFERENCES movement_trips(id) ON DELETE CASCADE,
+  sequence_index INTEGER NOT NULL,
+  recorded_at TEXT NOT NULL,
+  latitude REAL NOT NULL,
+  longitude REAL NOT NULL,
+  accuracy_meters REAL,
+  altitude_meters REAL,
+  speed_mps REAL,
+  is_stop_anchor INTEGER NOT NULL DEFAULT 0,
+  created_at TEXT NOT NULL
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_trip_points_trip
+  ON movement_trip_points(trip_id, sequence_index ASC);
+
+CREATE TABLE IF NOT EXISTS movement_trip_stops (
+  id TEXT PRIMARY KEY,
+  external_uid TEXT NOT NULL DEFAULT '',
+  trip_id TEXT NOT NULL REFERENCES movement_trips(id) ON DELETE CASCADE,
+  sequence_index INTEGER NOT NULL DEFAULT 0,
+  label TEXT NOT NULL DEFAULT '',
+  place_id TEXT REFERENCES movement_places(id) ON DELETE SET NULL,
+  started_at TEXT NOT NULL,
+  ended_at TEXT NOT NULL,
+  duration_seconds INTEGER NOT NULL DEFAULT 0,
+  latitude REAL NOT NULL,
+  longitude REAL NOT NULL,
+  radius_meters REAL NOT NULL DEFAULT 80,
+  metadata_json TEXT NOT NULL DEFAULT '{}',
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_trip_stops_trip
+  ON movement_trip_stops(trip_id, sequence_index ASC);

package/server/migrations/029_watch_micro_capture.sql

@@ -0,0 +1,23 @@
+CREATE TABLE IF NOT EXISTS watch_capture_events (
+  id TEXT PRIMARY KEY,
+  pairing_session_id TEXT REFERENCES companion_pairing_sessions(id) ON DELETE SET NULL,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  dedupe_key TEXT NOT NULL,
+  source_device TEXT NOT NULL DEFAULT 'Apple Watch',
+  event_type TEXT NOT NULL,
+  prompt_id TEXT,
+  recorded_at TEXT NOT NULL,
+  received_at TEXT NOT NULL,
+  linked_context_json TEXT NOT NULL DEFAULT '{}',
+  payload_json TEXT NOT NULL DEFAULT '{}',
+  projection_status TEXT NOT NULL DEFAULT 'stored',
+  projection_details_json TEXT NOT NULL DEFAULT '{}',
+  created_at TEXT NOT NULL,
+  UNIQUE (user_id, dedupe_key)
+);
+
+CREATE INDEX IF NOT EXISTS idx_watch_capture_events_user_recorded
+  ON watch_capture_events(user_id, recorded_at DESC);
+
+CREATE INDEX IF NOT EXISTS idx_watch_capture_events_event_type
+  ON watch_capture_events(user_id, event_type, recorded_at DESC);

package/server/migrations/030_surface_layouts.sql

@@ -0,0 +1,5 @@
+CREATE TABLE IF NOT EXISTS surface_layouts (
+  surface_id TEXT PRIMARY KEY,
+  payload_json TEXT NOT NULL,
+  updated_at TEXT NOT NULL
+);

package/server/migrations/031_ai_processor_runtime_upgrades.sql

@@ -0,0 +1,10 @@
+ALTER TABLE ai_processors ADD COLUMN slug TEXT NOT NULL DEFAULT '';
+ALTER TABLE ai_processors ADD COLUMN agent_config_json TEXT NOT NULL DEFAULT '[]';
+ALTER TABLE ai_processors ADD COLUMN run_history_json TEXT NOT NULL DEFAULT '[]';
+
+UPDATE ai_processors
+SET slug = lower(replace(replace(trim(title), ' ', '-'), '--', '-')) || '-' || substr(id, -6)
+WHERE trim(slug) = '';
+
+CREATE UNIQUE INDEX IF NOT EXISTS idx_ai_processors_slug
+ON ai_processors(slug);

package/server/migrations/032_ai_connectors.sql

@@ -0,0 +1,44 @@
+CREATE TABLE IF NOT EXISTS ai_connectors (
+  id TEXT PRIMARY KEY,
+  slug TEXT NOT NULL UNIQUE,
+  title TEXT NOT NULL,
+  description TEXT NOT NULL DEFAULT '',
+  kind TEXT NOT NULL,
+  home_surface_id TEXT,
+  endpoint_enabled INTEGER NOT NULL DEFAULT 1,
+  graph_json TEXT NOT NULL,
+  published_outputs_json TEXT NOT NULL DEFAULT '[]',
+  last_run_json TEXT,
+  legacy_processor_id TEXT UNIQUE,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL
+);
+
+CREATE TABLE IF NOT EXISTS ai_connector_runs (
+  id TEXT PRIMARY KEY,
+  connector_id TEXT NOT NULL,
+  mode TEXT NOT NULL,
+  status TEXT NOT NULL,
+  user_input TEXT NOT NULL DEFAULT '',
+  context_json TEXT NOT NULL DEFAULT '{}',
+  conversation_id TEXT,
+  result_json TEXT,
+  error TEXT,
+  created_at TEXT NOT NULL,
+  completed_at TEXT,
+  FOREIGN KEY(connector_id) REFERENCES ai_connectors(id) ON DELETE CASCADE
+);
+
+CREATE INDEX IF NOT EXISTS idx_ai_connector_runs_connector_created
+ON ai_connector_runs(connector_id, created_at DESC);
+
+CREATE TABLE IF NOT EXISTS ai_connector_conversations (
+  id TEXT PRIMARY KEY,
+  connector_id TEXT NOT NULL UNIQUE,
+  provider TEXT,
+  external_conversation_id TEXT,
+  transcript_json TEXT NOT NULL DEFAULT '[]',
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  FOREIGN KEY(connector_id) REFERENCES ai_connectors(id) ON DELETE CASCADE
+);

package/server/migrations/033_movement_trip_point_sync.sql

@@ -0,0 +1,36 @@
+ALTER TABLE movement_trip_points
+ADD COLUMN external_uid TEXT NOT NULL DEFAULT '';
+
+UPDATE movement_trip_points
+SET external_uid = id
+WHERE trim(external_uid) = '';
+
+CREATE UNIQUE INDEX IF NOT EXISTS idx_movement_trip_points_trip_external
+ON movement_trip_points(trip_id, external_uid);
+
+CREATE TABLE IF NOT EXISTS movement_trip_point_tombstones (
+  id TEXT PRIMARY KEY,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  trip_external_uid TEXT NOT NULL,
+  point_external_uid TEXT NOT NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, trip_external_uid, point_external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_trip_point_tombstones_user_trip
+ON movement_trip_point_tombstones(user_id, trip_external_uid, updated_at DESC);
+
+CREATE TABLE IF NOT EXISTS movement_trip_point_overrides (
+  id TEXT PRIMARY KEY,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  trip_external_uid TEXT NOT NULL,
+  point_external_uid TEXT NOT NULL,
+  point_json TEXT NOT NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, trip_external_uid, point_external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_trip_point_overrides_user_trip
+ON movement_trip_point_overrides(user_id, trip_external_uid, updated_at DESC);

package/server/migrations/034_movement_segment_sync.sql

@@ -0,0 +1,49 @@
+CREATE TABLE IF NOT EXISTS movement_stay_tombstones (
+  id TEXT PRIMARY KEY,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  stay_external_uid TEXT NOT NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, stay_external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_stay_tombstones_user
+ON movement_stay_tombstones(user_id, updated_at DESC);
+
+CREATE TABLE IF NOT EXISTS movement_stay_overrides (
+  id TEXT PRIMARY KEY,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  stay_external_uid TEXT NOT NULL,
+  stay_json TEXT NOT NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, stay_external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_stay_overrides_user
+ON movement_stay_overrides(user_id, updated_at DESC);
+
+CREATE TABLE IF NOT EXISTS movement_trip_tombstones (
+  id TEXT PRIMARY KEY,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  trip_external_uid TEXT NOT NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, trip_external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_trip_tombstones_user
+ON movement_trip_tombstones(user_id, updated_at DESC);
+
+CREATE TABLE IF NOT EXISTS movement_trip_overrides (
+  id TEXT PRIMARY KEY,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  trip_external_uid TEXT NOT NULL,
+  trip_json TEXT NOT NULL,
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  UNIQUE (user_id, trip_external_uid)
+);
+
+CREATE INDEX IF NOT EXISTS idx_movement_trip_overrides_user
+ON movement_trip_overrides(user_id, updated_at DESC);

package/server/migrations/035_google_local_auth_settings.sql

@@ -0,0 +1,2 @@
+ALTER TABLE app_settings
+  ADD COLUMN google_client_id TEXT NOT NULL DEFAULT '';

package/server/migrations/036_google_local_auth_client_secret.sql

@@ -0,0 +1,2 @@
+ALTER TABLE app_settings
+  ADD COLUMN google_client_secret TEXT NOT NULL DEFAULT '';

package/skills/forge-openclaw/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: forge-openclaw
-description: use when the user wants to save, search, update, review, start, stop, reward, explain, or compare Forge records, or when the conversation is clearly about a Forge entity such as a goal, project, strategy, task, habit, note, calendar_event, work_block_template, task_timebox, task_run, insight, preference item, preference context, preference catalog, psyche_value, behavior_pattern, behavior, belief_entry, mode_profile, mode_guide_session, trigger_report, event_type, or emotion_definition. identify the exact Forge object, keep the main conversation natural, guide psyche intake with active listening before storing it, and for psyche issues that need understanding first usually begin with one exploratory question before any formulation or save suggestion.
+description: use when the user wants to save, search, update, review, start, stop, reward, explain, compare, or run Forge records, or when the conversation is clearly about a Forge entity such as a goal, project, strategy, task, habit, note, calendar_event, work_block_template, task_timebox, task_run, insight, preference item, preference context, preference catalog, questionnaire instrument, questionnaire run, self observation, psyche_value, behavior_pattern, behavior, belief_entry, mode_profile, mode_guide_session, trigger_report, event_type, emotion_definition, sleep_session, or workout_session. identify the exact Forge object, keep the main conversation natural, guide psyche intake with active listening before storing it, and for psyche issues that need understanding first usually begin with one exploratory question before any formulation or save suggestion.
 ---
 
 Forge is the user's structured system for planning work, doing work, reflecting on patterns, and keeping a truthful record of what is happening. Use it when the user is clearly working inside that system, or when they are describing something that naturally belongs there and would benefit from being stored, updated, reviewed, or acted on in Forge. Keep the conversation natural first. Do not turn every message into intake. When a real Forge entity is clearly present, name the exact entity type plainly, help with the substance of the conversation, and then offer Forge once, lightly, if storing it would genuinely help.
@@ -52,9 +52,12 @@ Entity conversation rule:
 - For all entity creation or update flows, first use [`entity_conversation_playbooks.md`](./entity_conversation_playbooks.md) to decide the next best question.
 - Ask only for what is missing or unclear. Do not walk through every schema field.
 - Let each question have one job. Know what you are trying to clarify before you ask it.
+- 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.
 - 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 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.
@@ -73,7 +76,9 @@ Psyche interview rule:
 - First use the active-listening playbooks in [`psyche_entity_playbooks.md`](./psyche_entity_playbooks.md).
 - Ask permission before going deeper, ask one or two focused questions at a time, reflect back what you heard, and summarize before moving on.
 - Start from a recent concrete example before naming an abstract pattern, belief, or mode.
+- 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 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.
@@ -466,3 +471,12 @@ When the user asks which Forge tools are available, list exactly these tools:
 `forge_create_work_block_template`
 `forge_recommend_task_timeboxes`
 `forge_create_task_timebox`
+
+Additional first-class surfaces:
+
+- Use the high-level batch routes for basic Preferences CRUD. `preference_catalog`, `preference_catalog_item`, `preference_context`, and `preference_item` all go through `forge_create_entities`, `forge_update_entities`, and `forge_delete_entities`.
+- Use the high-level batch routes for basic questionnaire CRUD too. `questionnaire_instrument` goes through `forge_create_entities`, `forge_update_entities`, and `forge_delete_entities`.
+- Keep the dedicated Preferences tools only for real preference actions and read models: `forge_get_preferences_workspace`, `forge_start_preferences_game`, `forge_merge_preferences_contexts`, `forge_enqueue_preferences_item_from_entity`, `forge_submit_preferences_judgment`, `forge_submit_preferences_signal`, and `forge_update_preferences_score`.
+- Keep the dedicated questionnaire tools only for real flow actions and read models: `forge_list_questionnaires`, `forge_get_questionnaire`, `forge_clone_questionnaire`, `forge_ensure_questionnaire_draft`, `forge_publish_questionnaire_draft`, `forge_start_questionnaire_run`, `forge_get_questionnaire_run`, `forge_update_questionnaire_run`, and `forge_complete_questionnaire_run`.
+- Self-observation is note-backed. Read the calendar through `forge_get_self_observation_calendar`, but create or update the stored observation as a `note` tagged `Self-observation` with `frontmatter.observedAt` and links to the relevant `behavior_pattern`, `trigger_report`, or other Forge records.
+- `sleep_session` and `workout_session` are first-class health records. Review them through the dedicated health tools instead of treating them like loose notes.