From 761d3a1b306ad2b52af067957c0c51029b6c51ed Mon Sep 17 00:00:00 2001 From: gavrielc Date: Sun, 5 Apr 2026 00:22:13 +0300 Subject: [PATCH] feat: add migrated_from_openclaw field to setup diagnostics Tracks whether users came through the OpenClaw migration path during setup. Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude/skills/setup/diagnostics.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.claude/skills/setup/diagnostics.md b/.claude/skills/setup/diagnostics.md index c6a42db..26d79b1 100644 --- a/.claude/skills/setup/diagnostics.md +++ b/.claude/skills/setup/diagnostics.md @@ -9,6 +9,8 @@ uname -m node -p "process.versions.node.split('.')[0]" ``` +Check if the user migrated from OpenClaw during this setup session (i.e. `/migrate-from-openclaw` was invoked). If you're unsure (e.g. after context compaction), check for `migration-state.md` in the project root — it exists during and sometimes after migration. + Write `/tmp/nanoclaw-diagnostics.json`. No paths, usernames, hostnames, or IP addresses. ```json @@ -23,6 +25,7 @@ Write `/tmp/nanoclaw-diagnostics.json`. No paths, usernames, hostnames, or IP ad "arch": "arm64", "node_major_version": 22, "channels_selected": ["telegram", "whatsapp"], + "migrated_from_openclaw": false, "error_count": 0, "failed_step": null }