forge-openclaw-plugin 0.2.47 → 0.2.49

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-openclaw-plugin",
-  "version": "0.2.47",
+  "version": "0.2.49",
   "description": "Curated OpenClaw adapter for the Forge collaboration API, UI entrypoint, and localhost auto-start runtime.",
   "type": "module",
   "license": "MIT",
@@ -95,10 +95,13 @@
     "zustand": "^5.0.5"
   },
   "overrides": {
+    "@aws-sdk/xml-builder": "^3.972.19",
     "basic-ftp": "^5.3.0",
     "axios": "^1.15.0",
+    "fast-xml-parser": "^5.7.1",
     "follow-redirects": "^1.16.0",
-    "hono": "4.12.14"
+    "hono": "4.12.14",
+    "uuid": "^14.0.0"
   },
   "scripts": {
     "build": "node ./scripts/build.mjs"

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/skills/forge-openclaw/SKILL.md

@@ -239,7 +239,8 @@ CRITICAL NEGATIVE-HABIT CHECK-IN RULE:
 - For a `negative` habit, the correct check-in outcome is `missed`.
 - On a `negative` habit, `missed` means the habit was resisted, the user stayed aligned, and the habit earns its XP bonus.
 - Do not treat `missed` on a `negative` habit as failure. In this case, `missed` is the successful outcome.
-- Habit check-ins written through `/api/v1/habits/:id/check-ins` can also include an optional `description`; when present, it replaces the habit's current `description` in the same write.
+- In OpenClaw, official habit outcome logging should go through `forge_update_entities` on `entityType: "habit"` with `patch: { checkIn: { status, dateKey?, note?, description? } }`.
+- Do not bypass the shared tool model with raw habit routes when the batch entity update already covers the write cleanly.
   Ask:
 
 1. What is the recurring behavior in one concrete sentence?
@@ -387,6 +388,7 @@ Use the dedicated domain routes for specialized surfaces that are not simple bat
   `/api/v1/workbench/flows/:id/output` for published outputs, and the run/node routes
   under `/api/v1/workbench/flows/:id` for run history and node-level inspection.
 - If you are unsure which specialized route family applies, check `forge_get_agent_onboarding` and use its `entityRouteModel.specializedDomainSurfaces` section before guessing.
+- If the truth of the current Movement, Life Force, or Workbench state is still unclear, prefer the dedicated read before the mutation so the correction stays truthful.
 - After a concrete Movement, Life Force, or Workbench correction, read the relevant specialized view back when the user is trying to understand the result rather than only store it.
 
 Use live work tools for `task_run`:

package/skills/forge-openclaw/entity_conversation_playbooks.md

@@ -56,6 +56,8 @@ Forge correctly, and gather only the structure that still matters.
 - For specialized surfaces, start from the user's real job in plain language, then
   narrow to the route family. Do not open with a route menu unless the user already
   named the exact object and action.
+- For specialized surfaces, if the truth of the current state is still uncertain, read
+  the relevant dedicated view before you mutate it.
 - When the user has already named a precise correction or review target, do not widen
   back out into a meta lane question. Confirm only the missing route-selecting detail
   and then act.
@@ -337,8 +339,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
 
@@ -387,6 +391,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
 
@@ -411,7 +424,7 @@ about linking only after the main record already feels named and steady.
 
 Use this when the user is updating an existing record rather than creating a new one.
 
-1. Ask what feels newly true, newly urgent, or newly clear.
+1. Ask what feels newly true, newly inaccurate, or newly clear.
 2. Ask what should stay true so the record keeps its core meaning.
 3. Ask what prompted the update now if that changes the shape of the record.
 4. Then ask only for the missing structural detail required by the change.
@@ -419,6 +432,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.
@@ -1017,9 +1034,11 @@ Arc:
 5. Ask what they are trying to notice, preserve, or answer through that movement context.
 6. Choose the dedicated day, month, all-time, timeline, places, trip-detail, or
    selection route once the question shape is clear.
-7. Skip the meta lane question when the user already named the exact correction or
+7. If the truth of one uncertain span is still unclear, read the timeline or saved-box
+   detail before you mutate it.
+8. Skip the meta lane question when the user already named the exact correction or
    review target and only one ambiguity remains.
-8. Route to the dedicated movement read or write path once the surface is clear.
+9. Route to the dedicated movement read or write path once the surface is clear.
 
 Direct action rules:
 
@@ -1036,6 +1055,8 @@ Direct action rules:
 - If the user wants to inspect one already-saved movement correction before editing
   it, read the box detail first so the follow-up write stays grounded in the saved
   object.
+- If the user is asking where they were during one uncertain window, prefer a timeline
+  read before you create a correction. Mutate only after the lived truth is clear.
 - When the user has already given the real answer, for example "I stayed home during
   that missing block", do not ask a broad review question again. Confirm only the
   interval or place if that is still ambiguous, then act.
@@ -1105,11 +1126,14 @@ Arc:
 4. Ask what should stay true if they are changing profile or template assumptions.
 5. Ask whether the user is describing a stable weekly shape or just how today feels
    when the lane is still blurred.
-6. If the user already named the life-force lane clearly, skip the meta lane question
+6. If the user describes a repeatable day-shape such as "Mondays crash after lunch",
+   treat that as a weekday-template question before you reach for profile or
+   fatigue-signal routes.
+7. If the user already named the life-force lane clearly, skip the meta lane question
    and ask only for the specific weekday, profile field, or signal that still matters.
-7. If the user wants to see what changed after a write, read the overview back instead
+8. If the user wants to see what changed after a write, read the overview back instead
    of leaving the result implicit.
-8. Route to the dedicated life-force path once the lane is clear.
+9. Route to the dedicated life-force path once the lane is clear.
 
 Helpful follow-up lanes:
 
@@ -1133,8 +1157,12 @@ Direct action rules:
 
 - If the user is describing a durable baseline such as work capacity, recovery style,
   or action-point assumptions, patch the profile instead of logging a fatigue signal.
+- If the user is describing a repeatable weekday rhythm, update that weekday template
+  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
@@ -1161,12 +1189,16 @@ Arc:
    before you narrow to flow discovery, editing, execution, or results.
 2. Ask whether the job is flow discovery, one flow edit, execution, run history, published output, node-level inspection, or latest-node-output lookup.
 3. Ask which flow, slug, run, or node the request is about.
-4. Ask whether they need the flow contract, a run result, a published output, or a node result.
+4. Ask whether they need the stable flow contract, one run result, one published
+   output, one node result, or the latest node output.
 5. If the user already named the flow and action clearly, skip the meta lane
    question and ask only for the missing run, node, or output scope.
 6. If the user wants a stable public input contract or published output, prefer those
    dedicated reads instead of detouring through run history first.
-7. Route to the dedicated workbench route family once the execution lane is clear.
+7. If the user is debugging one failed run, ask whether the useful artifact is the run
+   summary, one node result, the latest node output, or the published output before
+   you start asking for edits.
+8. Route to the dedicated workbench route family once the execution lane is clear.
 
 Helpful follow-up lanes:
 
@@ -1205,6 +1237,11 @@ Direct action rules:
 - If the user wants to execute a known saved flow, use `/api/v1/workbench/flows/:id/run`.
 - If the user wants payload-first execution without depending on a saved flow id, use
   `/api/v1/workbench/run`.
+- 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,
@@ -302,6 +304,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 +314,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.
@@ -383,6 +390,13 @@ If the entity is not yet clear:
   hold and what the new episode or evidence changes.
 - If a recent charged episode is what made the update visible, anchor in that episode
   before you rename the durable belief, pattern, mode, or value.
+- 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.