forge-openclaw-plugin 0.2.48 → 0.2.50

package/server/migrations/052_agent_identity_tightening.sql

@@ -0,0 +1,307 @@
+ALTER TABLE agent_identities ADD COLUMN identity_key TEXT;
+ALTER TABLE agent_identities ADD COLUMN provider TEXT;
+ALTER TABLE agent_identities ADD COLUMN machine_key TEXT;
+ALTER TABLE agent_identities ADD COLUMN persona_key TEXT;
+
+CREATE TABLE IF NOT EXISTS agent_identity_users (
+  agent_id TEXT NOT NULL REFERENCES agent_identities(id) ON DELETE CASCADE,
+  user_id TEXT NOT NULL REFERENCES users(id) ON DELETE CASCADE,
+  role TEXT NOT NULL DEFAULT 'linked',
+  created_at TEXT NOT NULL,
+  updated_at TEXT NOT NULL,
+  PRIMARY KEY (agent_id, user_id)
+);
+
+CREATE INDEX IF NOT EXISTS idx_agent_identity_users_user
+  ON agent_identity_users(user_id, role);
+
+INSERT OR IGNORE INTO users (
+  id, kind, handle, display_name, description, accent_color, created_at, updated_at
+) VALUES
+  ('user_agent_openclaw', 'bot', 'openclaw', 'OpenClaw', 'OpenClaw runtime actor linked to Forge agent identity and Kanban ownership.', '#38bdf8', datetime('now'), datetime('now')),
+  ('user_agent_hermes', 'bot', 'hermes', 'Hermes', 'Hermes runtime actor linked to Forge agent identity and Kanban ownership.', '#a78bfa', datetime('now'), datetime('now')),
+  ('user_agent_codex', 'bot', 'codex', 'Codex', 'Codex runtime actor linked to Forge agent identity and Kanban ownership.', '#22c55e', datetime('now'), datetime('now'));
+
+UPDATE agent_tokens
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+  ORDER BY CASE WHEN lower(label) = 'forge openclaw' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')) > 0;
+
+UPDATE agent_actions
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+  ORDER BY CASE WHEN lower(label) = 'forge openclaw' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')) > 0;
+
+UPDATE approval_requests
+SET requested_by_agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+  ORDER BY CASE WHEN lower(label) = 'forge openclaw' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE requested_by_agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')) > 0;
+
+UPDATE insights
+SET origin_agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+  ORDER BY CASE WHEN lower(label) = 'forge openclaw' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE origin_agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')) > 0;
+
+UPDATE agent_runtime_sessions
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+  ORDER BY CASE WHEN lower(label) = 'forge openclaw' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')) > 0;
+
+DELETE FROM agent_identities
+WHERE (lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel'))
+  AND id <> (
+    SELECT id FROM agent_identities
+    WHERE lower(agent_type) = 'openclaw' OR lower(label) IN ('forge openclaw', 'openclaw', 'aurel')
+    ORDER BY CASE WHEN lower(label) = 'forge openclaw' THEN 0 ELSE 1 END, created_at ASC
+    LIMIT 1
+  );
+
+UPDATE agent_identities
+SET label = 'Forge OpenClaw',
+    agent_type = 'openclaw',
+    provider = 'openclaw',
+    identity_key = 'runtime:openclaw:legacy:default',
+    machine_key = 'legacy',
+    persona_key = 'default',
+    description = 'OpenClaw runtime agent with stable Forge identity and linked Kanban user.',
+    updated_at = datetime('now')
+WHERE lower(agent_type) = 'openclaw' OR lower(label) = 'forge openclaw';
+
+UPDATE agent_tokens
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+  ORDER BY CASE WHEN lower(label) = 'forge hermes' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%') > 0;
+
+UPDATE agent_actions
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+  ORDER BY CASE WHEN lower(label) = 'forge hermes' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%') > 0;
+
+UPDATE approval_requests
+SET requested_by_agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+  ORDER BY CASE WHEN lower(label) = 'forge hermes' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE requested_by_agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%') > 0;
+
+UPDATE insights
+SET origin_agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+  ORDER BY CASE WHEN lower(label) = 'forge hermes' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE origin_agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%') > 0;
+
+UPDATE agent_runtime_sessions
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+  ORDER BY CASE WHEN lower(label) = 'forge hermes' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%') > 0;
+
+DELETE FROM agent_identities
+WHERE (lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%')
+  AND id <> (
+    SELECT id FROM agent_identities
+    WHERE lower(agent_type) = 'hermes' OR lower(label) LIKE 'forge hermes%'
+    ORDER BY CASE WHEN lower(label) = 'forge hermes' THEN 0 ELSE 1 END, created_at ASC
+    LIMIT 1
+  );
+
+UPDATE agent_identities
+SET label = 'Forge Hermes',
+    agent_type = 'hermes',
+    provider = 'hermes',
+    identity_key = 'runtime:hermes:legacy:default',
+    machine_key = 'legacy',
+    persona_key = 'default',
+    description = 'Hermes runtime agent with stable Forge identity and linked Kanban user.',
+    updated_at = datetime('now')
+WHERE lower(agent_type) = 'hermes' OR lower(label) = 'forge hermes';
+
+UPDATE agent_tokens
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+  ORDER BY CASE WHEN lower(label) = 'forge codex' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')) > 0;
+
+UPDATE agent_actions
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+  ORDER BY CASE WHEN lower(label) = 'forge codex' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')) > 0;
+
+UPDATE approval_requests
+SET requested_by_agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+  ORDER BY CASE WHEN lower(label) = 'forge codex' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE requested_by_agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')) > 0;
+
+UPDATE insights
+SET origin_agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+  ORDER BY CASE WHEN lower(label) = 'forge codex' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE origin_agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')) > 0;
+
+UPDATE agent_runtime_sessions
+SET agent_id = (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+  ORDER BY CASE WHEN lower(label) = 'forge codex' THEN 0 ELSE 1 END, created_at ASC
+  LIMIT 1
+)
+WHERE agent_id IN (
+  SELECT id FROM agent_identities
+  WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+)
+AND (SELECT COUNT(*) FROM agent_identities WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')) > 0;
+
+DELETE FROM agent_identities
+WHERE (lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)'))
+  AND id <> (
+    SELECT id FROM agent_identities
+    WHERE lower(agent_type) = 'codex' OR lower(label) IN ('forge codex', 'codex', 'albert (codex)')
+    ORDER BY CASE WHEN lower(label) = 'forge codex' THEN 0 ELSE 1 END, created_at ASC
+    LIMIT 1
+  );
+
+UPDATE agent_identities
+SET label = 'Forge Codex',
+    agent_type = 'codex',
+    provider = 'codex',
+    identity_key = 'runtime:codex:legacy:default',
+    machine_key = 'legacy',
+    persona_key = 'default',
+    description = 'Codex runtime agent with stable Forge identity and linked Kanban user.',
+    updated_at = datetime('now')
+WHERE lower(agent_type) = 'codex' OR lower(label) = 'forge codex';
+
+INSERT OR IGNORE INTO agent_identity_users (agent_id, user_id, role, created_at, updated_at)
+SELECT id, 'user_agent_openclaw', 'primary', datetime('now'), datetime('now')
+FROM agent_identities
+WHERE provider = 'openclaw';
+
+INSERT OR IGNORE INTO agent_identity_users (agent_id, user_id, role, created_at, updated_at)
+SELECT id, 'user_agent_hermes', 'primary', datetime('now'), datetime('now')
+FROM agent_identities
+WHERE provider = 'hermes';
+
+INSERT OR IGNORE INTO agent_identity_users (agent_id, user_id, role, created_at, updated_at)
+SELECT id, 'user_agent_codex', 'primary', datetime('now'), datetime('now')
+FROM agent_identities
+WHERE provider = 'codex';
+
+UPDATE agent_runtime_sessions
+SET agent_label = (
+      SELECT label FROM agent_identities WHERE agent_identities.id = agent_runtime_sessions.agent_id
+    ),
+    agent_type = (
+      SELECT agent_type FROM agent_identities WHERE agent_identities.id = agent_runtime_sessions.agent_id
+    ),
+    updated_at = datetime('now')
+WHERE agent_id IN (SELECT id FROM agent_identities WHERE provider IN ('openclaw', 'hermes', 'codex'));
+
+CREATE UNIQUE INDEX IF NOT EXISTS idx_agent_identities_identity_key
+  ON agent_identities(identity_key)
+  WHERE identity_key IS NOT NULL;

package/server/migrations/053_agent_runtime_session_canonical_labels.sql

@@ -0,0 +1,9 @@
+UPDATE agent_runtime_sessions
+SET agent_label = (
+      SELECT label FROM agent_identities WHERE agent_identities.id = agent_runtime_sessions.agent_id
+    ),
+    agent_type = (
+      SELECT agent_type FROM agent_identities WHERE agent_identities.id = agent_runtime_sessions.agent_id
+    ),
+    updated_at = datetime('now')
+WHERE agent_id IN (SELECT id FROM agent_identities WHERE provider IN ('openclaw', 'hermes', 'codex'));

package/server/migrations/054_sqlite_backed_wiki_memory.sql

@@ -0,0 +1,8 @@
+UPDATE wiki_spaces
+SET description = 'Shared wiki space for SQLite-backed Forge knowledge.'
+WHERE id = 'wiki_space_shared'
+  AND description != 'Shared wiki space for SQLite-backed Forge knowledge.';
+
+UPDATE notes
+SET source_path = ''
+WHERE source_path != '';

package/skills/forge-openclaw/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: forge-openclaw
+name: forge-openclaw-plugin
 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.
 ---
 
@@ -59,7 +59,7 @@ PM surface rule:
   human/bot ownership filters.
 - Guided modal flows handle create, edit, move, link, and closeout actions.
 
-Forge has four major surfaces. The planning side covers goals, projects, strategies, tasks, habits, notes, calendar events, recurring work blocks, task timeboxes, live work sessions, and agent-authored insights. The Health side covers sleep sessions, sports and workout sessions, companion pairing, and habit-generated workout records that should still stay linked to the broader Forge graph. The Preferences side covers contextual taste modeling, pairwise comparisons, direct signals, editable concept libraries, and preference items that can come from Forge entities or seeded concept domains such as food, activities, places, countries, fashion, people, media, and tools. The Psyche side covers values, patterns, behaviors, beliefs, modes, guided mode sessions, trigger reports, event types, and reusable emotion definitions. Forge also has a file-first Wiki memory layer with explicit spaces, local markdown pages, backlinks, optional embeddings, and structured links back to Forge entities. Forge is also multi-user: every entity can belong to a typed `human` or `bot` user through `userId`, and read routes can scope to one or many users with `userId` or repeated `userIds`. The current access posture is configurable through a directional user graph, but the live default is still permissive: Forge can list users directly, every relationship edge starts open, and a user can read or affect another user's linked records when the route explicitly asks for them. Use `forge_get_user_directory` when owner identity or cross-user access matters. Strategies can also be locked into a contract with `isLocked`; once locked, do not mutate the graph or target structure unless the user explicitly wants the strategy unlocked first. 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 four major surfaces. The planning side covers goals, projects, strategies, tasks, habits, notes, calendar events, recurring work blocks, task timeboxes, live work sessions, and agent-authored insights. The Health side covers sleep sessions, sports and workout sessions, companion pairing, and habit-generated workout records that should still stay linked to the broader Forge graph. The Preferences side covers contextual taste modeling, pairwise comparisons, direct signals, editable concept libraries, and preference items that can come from Forge entities or seeded concept domains such as food, activities, places, countries, fashion, people, media, and tools. The Psyche side covers values, patterns, behaviors, beliefs, modes, guided mode sessions, trigger reports, event types, and reusable emotion definitions. Forge also has a SQLite-backed Wiki memory layer with explicit spaces, Markdown content in database rows, backlinks, optional embeddings, and structured links back to Forge entities. Forge is also multi-user: every entity can belong to a typed `human` or `bot` user through `userId`, and read routes can scope to one or many users with `userId` or repeated `userIds`. The current access posture is configurable through a directional user graph, but the live default is still permissive: Forge can list users directly, every relationship edge starts open, and a user can read or affect another user's linked records when the route explicitly asks for them. Use `forge_get_user_directory` when owner identity or cross-user access matters. Strategies can also be locked into a contract with `isLocked`; once locked, do not mutate the graph or target structure unless the user explicitly wants the strategy unlocked first. 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”.
 Habits are a first-class recurring entity in the planning side.
 NEGATIVE HABIT CHECK-IN RULE: for a `negative` habit, the correct aligned/resisted outcome is `missed`. `missed` means the bad habit was resisted, the user stayed aligned, and the habit should award its XP bonus.
 
@@ -74,9 +74,9 @@ Preferences rule:
 Wiki rule:
 
 - Treat the Wiki as the canonical long-form memory surface, not as a loose note dump.
-- Use the wiki tools when the user wants file-first reference pages, backlink-aware recall, ingest from a URL or local file, or wiki maintenance work such as unresolved-link cleanup.
+- Use the wiki tools when the user wants SQLite-backed reference pages, backlink-aware recall, ingest from a URL or local file, or wiki maintenance work such as unresolved-link cleanup.
 - `forge_ingest_wiki_source` now queues the ingest as background work; use the Forge UI handoff when the user wants to review or keep only selected wiki/entity candidates after the ingest finishes.
-- Keep evidence notes and wiki pages conceptually distinct: evidence notes are linked operating records, while wiki pages are the curated memory vault.
+- Keep evidence notes and wiki pages conceptually distinct: evidence notes are linked operating records, while wiki pages are curated long-form memory.
 
 Wiki navigation and search rule:
 
@@ -90,7 +90,7 @@ Wiki navigation and search rule:
 - Use `forge_search_wiki` as the default wiki recall tool. It is the main route for people, conversations, concepts, and exact page lookup.
 - Use `forge_list_wiki_pages` when the user wants to browse structure, inspect a branch, or understand how pages are organized rather than search by phrase.
 - Use `forge_get_wiki_page` after search yields a likely hit, or when the user already identified the page to open.
-- Use `forge_get_wiki_settings` or `forge_get_wiki_health` when the task is about wiki maintenance, indexing, unresolved links, ingest setup, or vault integrity rather than content recall.
+- Use `forge_get_wiki_settings` or `forge_get_wiki_health` when the task is about wiki maintenance, indexing, unresolved links, ingest setup, or memory integrity rather than content recall.
 
 Health rule:
 
@@ -353,7 +353,7 @@ Use the batch entity tools for stored records:
 These tools operate on:
 `goal`, `project`, `strategy`, `task`, `habit`, `tag`, `note`, `insight`, `calendar_event`, `work_block_template`, `task_timebox`, `psyche_value`, `behavior_pattern`, `behavior`, `belief_entry`, `mode_profile`, `mode_guide_session`, `trigger_report`, `event_type`, `emotion_definition`, `preference_catalog`, `preference_catalog_item`, `preference_context`, `preference_item`, `questionnaire_instrument`, `sleep_session`, `workout_session`
 
-Use the wiki tools for file-first memory work:
+Use the wiki tools for SQLite-backed memory work:
 `forge_get_wiki_settings`, `forge_list_wiki_pages`, `forge_get_wiki_page`, `forge_search_wiki`, `forge_upsert_wiki_page`, `forge_get_wiki_health`, `forge_sync_wiki_vault`, `forge_reindex_wiki_embeddings`, `forge_ingest_wiki_source`
 
 Use the health tools for review and reflective enrichment, not as the default CRUD architecture:

package/skills/forge-openclaw/entity_conversation_playbooks.md

@@ -63,6 +63,11 @@ Forge correctly, and gather only the structure that still matters.
   and then act.
 - Once the route family is clear, say it plainly enough that another agent could follow
   the same path without guessing.
+- For updates, start with the smallest thing that now feels wrong, newly true, or
+  newly visible. Do not make the user retell the whole record unless the change is
+  genuinely structural.
+- For review requests, ask what practical question they want the read to answer before
+  you ask for more scope.
 - For meaning-bearing updates, especially in Psyche-adjacent work, briefly say what
   feels newly true before you ask for the one structural detail that still changes the
   save.
@@ -222,6 +227,31 @@ When you are about to save:
   enough or needs one correction
 - if the user confirms it, stop asking and save
 
+## Update And Review Shortcuts
+
+Use these when the user is correcting, reviewing, or tightening something that already
+exists.
+
+- When the user already gave the correction in usable language, reflect what still
+  seems true, then ask only for the one thing that no longer fits.
+- A good narrow update line is:
+  "I can stay narrow here. What is the one thing that no longer fits?"
+- When the user is revising placement, timing, or ownership rather than meaning, do
+  not reopen the whole story. Confirm only the parent, interval, owner, or route scope
+  that changes the write.
+- When the record is abstract or reusable and the user wants an update, ask what
+  future decision, comparison, or retrieval moment got muddy with the old wording.
+- When the user wants review rather than mutation, ask what answer they need from the
+  read:
+  what this would help them decide later is often the clearest scope signal.
+- For specialized surfaces, ask what exact saved object, span, weekday, flow, run, or
+  node the user wants to check before you ask why it matters.
+- If the next answer would not change the route, wording, timing, links, or useful
+  interpretation, stop asking and act.
+- Close cleanly:
+  once the user says the wording or route lands, summarize once and move to the read
+  or write.
+
 When an adjacent record becomes visible:
 
 - name it gently and ask whether it should be linked now, saved separately later, or
@@ -339,8 +369,10 @@ Connect:
   move to the save.
 - Prefer "what I have now is..." or "what seems clear now is..." over a cold final
   field check.
+- If the user already gave usable wording, do not ask them to rename it for style.
 - If the user gives a correction, revise the working formulation once and close again
   instead of reopening the whole intake.
+- If the next answer would not change the entity type, route, wording, timing, or useful links, stop asking and act.
 
 ## Question design rules
 
@@ -389,6 +421,15 @@ Connect:
   saved object, timeframe, or route family, not reopen the whole meaning-making arc.
 - When the user already gave the correction in usable language, prefer "what still
   needs deciding is..." over asking them to restate the whole situation.
+- The opening question should help the user understand what they are actually trying
+  to save, decide, review, or change, not make them perform the schema out loud.
+- For review or correction work, do not slip back into a create-style opener once the
+  saved object is already known.
+- Once a specialized-surface lane is clear, speak in route-relevant nouns such as
+  timeline, overlay, weekday template, published output, run detail, or node result
+  instead of generic "record" language.
+- If the user is emotionally loaded but the record is still non-Psyche, reflect the
+  lived stake once and then return to the one operational question that still matters.
 
 ## Ready-to-save check
 
@@ -421,6 +462,10 @@ Use this when the user is updating an existing record rather than creating a new
 If the current title or shape may no longer fit, offer one revised formulation yourself
 before asking the user to rewrite it from scratch.
 
+If the user already named the exact correction in usable language, do not ask a broad
+review question again. Confirm only the missing scope, timing, or route-selecting
+detail, then act.
+
 ## Update-first openers
 
 Use these when the user is correcting or revising something that already exists.
@@ -1146,6 +1191,8 @@ Direct action rules:
   instead of treating it as a one-off right-now feeling.
 - If the user is describing how one weekday should usually feel, update that weekday
   template instead of editing the profile.
+- If the user says something like "I always dip on Tuesdays after lunch", treat that
+  as a weekday-template edit, not as a one-off fatigue signal.
 - If the user is describing right-now depletion or recovery, post a fatigue signal and
   then read the overview back if they want to see the updated picture.
 - After a profile or weekday-template change, read the overview back when the user is
@@ -1223,6 +1270,8 @@ Direct action rules:
 - 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.
+- If the user only wants a published output, latest node output, or run detail, do not
+  reopen a flow-edit intake before reading that artifact.
 - If the user wants one node's latest successful output, do not browse old runs first
   unless they explicitly want historical debugging.
 - If the user wants to understand what inputs a flow can accept before editing or

package/skills/forge-openclaw/psyche_entity_playbooks.md

@@ -53,6 +53,8 @@ Forge without turning the conversation into a worksheet.
   naming, challenging, or solution-finding.
 - Your first job is not interpretation. It is to make the moment feel graspable enough
   that the user can stay with it and describe it.
+- The next question should help the user feel less alone with the experience and more
+  able to name it, not more examined.
 - Before you ask for change, naming, or repair, usually ask what the experience is
   trying to protect, prevent, or hold onto.
 - The warmth should come from accuracy and steadiness, not from extra softness,
@@ -70,6 +72,10 @@ Forge without turning the conversation into a worksheet.
   container first and hold the others lightly until the user wants to map them.
 - When the user has said enough for an accurate working formulation, stop deepening and
   help them name it cleanly.
+- For Psyche updates, begin with the smallest part of the old wording that no longer
+  fits instead of reopening the whole formulation immediately.
+- Do not reopen the full origin story when the update is really about one changed
+  meaning, one newly visible protection, or one new sentence the user can already say.
 
 ## First reflection menu
 
@@ -191,6 +197,23 @@ opening:
 - one missing-detail question
 - then move toward the write instead of forcing exploration
 
+## Update micro-openers
+
+Use these when the user is revising an existing Psyche record and the tone should stay
+therapist-like without becoming expansive again.
+
+- "Something about the old wording no longer holds the whole experience. What felt
+  different in the moment that made that visible?"
+- "The old name was trying to protect something real. What part of the recent episode
+  made it feel too small or off?"
+- "It sounds like the same pain, but not quite the same meaning. What changed in what
+  it started to say?"
+- If the user already gave the new sentence in usable language, reflect it once, ask
+  what part of the old wording it replaces, and then save.
+- If the user wants review rather than storage, ask whether they need clearer
+  language, better understanding, or next-step help before you reopen the whole
+  formulation.
+
 ## Therapeutic turn shapes
 
 Keep the pacing human and intentional.
@@ -302,6 +325,9 @@ Another strong shape when the user is getting abstract:
 - "So the painful part seems to be less the event itself and more what it starts to
   mean about you. What does it seem to prove in that moment?"
 
+Use that rhythm to contain before you interpret. The user should be able to feel what
+you understood before they have to answer the next deeper question.
+
 ## Formulation rules
 
 - Do not front-load a finished case formulation.
@@ -309,6 +335,8 @@ Another strong shape when the user is getting abstract:
   the user has answered at least one real exploratory question.
 - Do not ask for evidence, alternative beliefs, or repair plans before the user has had
   a fair chance to feel that the original experience was captured accurately.
+- If the moment is still hot, name what feels most painful, dangerous, or protective
+  before you ask for belief, mode, or pattern labels.
 - Do not make the user prove the experience before you have helped them feel that you
   understood it.
 - Help the user recognize the experience before you help them improve it.
@@ -386,6 +414,10 @@ If the entity is not yet clear:
 - If the user already gives the new sentence in usable language, revise the wording
   once and save instead of reopening evidence, origin, or repair just because those
   lanes are available.
+- Do not open a second broad origin story just because the update touched old pain.
+  If the wording is already clear enough, refine it once and save.
+- If the formulation already lands and the next answer would not change the wording,
+  links, or immediate write, stop asking and save.
 - If another belief, value, pattern, mode, or note becomes visible, name it gently but
   do not switch containers unless the user wants to.