forge-openclaw-plugin 0.2.7 → 0.2.11

package/server/migrations/002_psyche.sql

@@ -81,18 +81,6 @@ CREATE TABLE IF NOT EXISTS trigger_reports (
   updated_at TEXT NOT NULL
 );
 
-CREATE TABLE IF NOT EXISTS entity_comments (
-  id TEXT PRIMARY KEY,
-  entity_type TEXT NOT NULL,
-  entity_id TEXT NOT NULL,
-  anchor_key TEXT,
-  body TEXT NOT NULL,
-  author TEXT,
-  source TEXT NOT NULL,
-  created_at TEXT NOT NULL,
-  updated_at TEXT NOT NULL
-);
-
 CREATE TABLE IF NOT EXISTS schema_catalog (
   id TEXT PRIMARY KEY,
   slug TEXT NOT NULL UNIQUE,
@@ -232,10 +220,173 @@ CREATE INDEX IF NOT EXISTS idx_psyche_values_domain ON psyche_values(domain_id,
 CREATE INDEX IF NOT EXISTS idx_behavior_patterns_domain ON behavior_patterns(domain_id, created_at DESC);
 CREATE INDEX IF NOT EXISTS idx_trigger_reports_domain ON trigger_reports(domain_id, created_at DESC);
 CREATE INDEX IF NOT EXISTS idx_trigger_reports_status ON trigger_reports(status, created_at DESC);
-CREATE INDEX IF NOT EXISTS idx_entity_comments_target ON entity_comments(entity_type, entity_id, created_at DESC);
 CREATE INDEX IF NOT EXISTS idx_event_types_domain ON event_types(domain_id, system DESC, label);
 CREATE INDEX IF NOT EXISTS idx_emotion_definitions_domain ON emotion_definitions(domain_id, system DESC, label);
 CREATE INDEX IF NOT EXISTS idx_psyche_behaviors_domain ON psyche_behaviors(domain_id, kind, updated_at DESC);
 CREATE INDEX IF NOT EXISTS idx_belief_entries_domain ON belief_entries(domain_id, updated_at DESC);
 CREATE INDEX IF NOT EXISTS idx_belief_entries_schema ON belief_entries(schema_id, updated_at DESC);
 CREATE INDEX IF NOT EXISTS idx_mode_profiles_domain ON mode_profiles(domain_id, family, updated_at DESC);
+
+ALTER TABLE behavior_patterns
+ADD COLUMN linked_mode_ids_json TEXT NOT NULL DEFAULT '[]';
+
+ALTER TABLE behavior_patterns
+ADD COLUMN linked_belief_ids_json TEXT NOT NULL DEFAULT '[]';
+
+ALTER TABLE schema_catalog
+ADD COLUMN schema_type TEXT NOT NULL DEFAULT 'maladaptive';
+
+UPDATE schema_catalog
+SET schema_type = 'maladaptive'
+WHERE schema_type IS NULL OR trim(schema_type) = '';
+
+INSERT OR IGNORE INTO schema_catalog (
+  id,
+  slug,
+  title,
+  family,
+  description,
+  schema_type,
+  created_at,
+  updated_at
+) VALUES
+  (
+    'schema_adaptive_stable_attachment',
+    'stable_attachment',
+    'Stable Attachment',
+    'disconnection_rejection',
+    'The belief that your close relationships are stable, loyal, and enduring.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_emotional_fulfilment',
+    'emotional_fulfilment',
+    'Emotional Fulfilment',
+    'disconnection_rejection',
+    'The belief that someone in your life can meet your needs for care, attachment, and emotional safety.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_social_belonging',
+    'social_belonging',
+    'Social Belonging',
+    'disconnection_rejection',
+    'The belief that you belong, fit in, and are accepted in groups and relationships.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_competence',
+    'competence',
+    'Competence',
+    'impaired_autonomy',
+    'The belief that you can handle daily problems, make decisions, and function capably in ordinary life.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_developed_self',
+    'developed_self',
+    'Developed Self',
+    'impaired_autonomy',
+    'The belief that you can live as your own person with mature boundaries and healthy independence from your parents.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_success',
+    'success',
+    'Success',
+    'impaired_autonomy',
+    'The belief that you are capable, effective, and able to do well in work, study, and achievement settings.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_empathic_consideration',
+    'empathic_consideration',
+    'Empathic Consideration',
+    'other_directedness',
+    'The belief that other people matter too and that you can respect different views without losing yourself.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_healthy_self_discipline',
+    'healthy_self_discipline',
+    'Healthy Self-Discipline',
+    'overvigilance_inhibition',
+    'The ability to stay with routines, persist through difficulty, and trade short-term comfort for long-term aims.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_healthy_self_care',
+    'healthy_self_care',
+    'Healthy Self-Care',
+    'other_directedness',
+    'The belief that your own needs matter too and that making room for rest, care, and boundaries is legitimate.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_self_directedness',
+    'self_directedness',
+    'Self-Directedness',
+    'healthy_selfhood',
+    'The belief that your own view of yourself matters more than performing for approval or admiration.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_optimism',
+    'optimism',
+    'Optimism',
+    'healthy_selfhood',
+    'The belief that good outcomes are possible and that life does not need to be ruled by catastrophe.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_emotional_openness',
+    'emotional_openness',
+    'Emotional Openness',
+    'healthy_selfhood',
+    'The willingness to express feelings, affection, and emotional truth with people you trust.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_realistic_expectations',
+    'realistic_expectations',
+    'Realistic Expectations',
+    'overvigilance_inhibition',
+    'The belief that good enough is acceptable, goals can be realistic, and mistakes do not cancel your worth.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  ),
+  (
+    'schema_adaptive_self_compassion',
+    'self_compassion',
+    'Self-Compassion',
+    'overvigilance_inhibition',
+    'The belief that you deserve kindness, forgiveness, and humane self-talk when you struggle or make mistakes.',
+    'adaptive',
+    CURRENT_TIMESTAMP,
+    CURRENT_TIMESTAMP
+  );

package/skills/forge-openclaw/SKILL.md

@@ -5,10 +5,20 @@ description: use when the user wants to save, search, update, review, start, sto
 
 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.
 
-Forge has two major domains. The planning side covers goals, projects, tasks, live work sessions, and agent-authored insights. The Psyche side covers values, patterns, behaviors, beliefs, modes, guided mode sessions, trigger reports, event types, and reusable emotion definitions. The model should use the real entity names, not vague substitutes. Say `project`, not “initiative”. Say `behavior_pattern`, not “theme”. Say `trigger_report`, not “incident note”.
+Forge has two major domains. The planning side covers goals, projects, tasks, notes, live work sessions, and agent-authored insights. The Psyche side covers values, patterns, behaviors, beliefs, modes, guided mode sessions, trigger reports, event types, and reusable emotion definitions. The model should use the real entity names, not vague substitutes. Say `project`, not “initiative”. Say `behavior_pattern`, not “theme”. Say `trigger_report`, not “incident note”.
 
 Write to Forge only with clear user consent. If the user is just thinking aloud, helping first is usually better than writing immediately. After helping, you may offer one short Forge prompt if the match is strong. If the user agrees, ask only for the missing fields and only one to three focused questions at a time. Do not offer Forge again after a decline unless the user reopens it.
 
+Forge data location rule:
+
+- by default, Forge stores data under the active runtime root at `data/forge.sqlite`
+- on a normal OpenClaw install, this usually means `~/.openclaw/extensions/forge-openclaw-plugin/data/forge.sqlite`
+- on a linked repo-local install, this usually means `<repo>/openclaw-plugin/data/forge.sqlite`
+- if the user wants the data somewhere else for persistence, backup, or manual control, tell them to set `plugins.entries["forge-openclaw-plugin"].config.dataRoot` and restart the OpenClaw gateway
+- if the user asks where the data is stored or how to move it, explain the current default plainly and show the exact config field
+- if the user wants to stop a plugin-managed local Forge runtime cleanly, tell them to run `forge stop`
+- `forge stop` only shuts down a runtime that the OpenClaw plugin auto-started itself; if Forge was started manually elsewhere, it will say so instead of killing random local processes
+
 Use these exact entity meanings when deciding what the user is describing.
 
 `goal` is a meaningful long-horizon direction or outcome. Use it for “be a great father”, “create meaningfully”, or “build a beautiful family”, not for one-off action items.
@@ -19,6 +29,8 @@ Use these exact entity meanings when deciding what the user is describing.
 
 `task_run` is one truthful live work session on a task. It is not the same thing as task status.
 
+`note` is a Markdown evidence record that can link to one or many entities. Use it for work summaries, context, progress logs, handoff explanations, or reflective detail that should stay searchable and attached to the right records.
+
 `insight` is an agent-authored observation, recommendation, or warning grounded in Forge data. It does not replace a requested goal, project, task, pattern, belief, or trigger report.
 
 `psyche_value` is a direction the user wants to live toward, such as honesty, courage, steadiness, compassion, or creativity.
@@ -159,7 +171,7 @@ Use the batch entity tools for stored records:
 `forge_search_entities`, `forge_create_entities`, `forge_update_entities`, `forge_delete_entities`, `forge_restore_entities`
 
 These tools operate on:
-`goal`, `project`, `task`, `psyche_value`, `behavior_pattern`, `behavior`, `belief_entry`, `mode_profile`, `mode_guide_session`, `trigger_report`, `event_type`, `emotion_definition`
+`goal`, `project`, `task`, `note`, `psyche_value`, `behavior_pattern`, `behavior`, `belief_entry`, `mode_profile`, `mode_guide_session`, `trigger_report`, `event_type`, `emotion_definition`
 
 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`
@@ -176,6 +188,8 @@ Use these exact payload expectations.
 
 For create operations, each item must include `entityType` and `data`.
 
+When creating `goal`, `project`, or `task`, the create payload may also include `notes: [{ contentMarkdown, author?, links? }]`. Forge will create real linked `note` entities automatically and attach them to the new parent record.
+
 For update operations, each item must include `entityType`, `id`, and `patch`.
 
 For delete operations, each item must include `entityType` and `id`. Delete is soft by default unless the user explicitly wants hard delete.
@@ -196,11 +210,11 @@ Use `forge_heartbeat_task_run` to keep an active run alive.
 
 Use `forge_focus_task_run` when one active run should become the current visible run.
 
-Use `forge_complete_task_run` to finish live work.
+Use `forge_complete_task_run` to finish live work. When the user or agent wants to preserve what was done, include `closeoutNote` so Forge creates a real linked `note` instead of losing that explanation inside ephemeral run metadata.
 
-Use `forge_release_task_run` to stop live work without completing the task.
+Use `forge_release_task_run` to stop live work without completing the task. `closeoutNote` is also available there for handoff or pause context.
 
-Use `forge_log_work` only for retroactive work that already happened.
+Use `forge_log_work` only for retroactive work that already happened. If the user explains the work in a way that should be preserved, include `closeoutNote`.
 
 Use these interaction rules.