Troubleshooting
Legacy ownership warnings during an update
Doctor leaves legacy proposal metadata and collection backups in place when their workspace has no configured owner or maps to more than one agent. The warning names the retained path and candidate agents. These ownership warnings do not stop the other migrations or later Doctor repairs. Review the retained proposal or backup manifest alongside the configured agent workspaces. Correct a workspace mapping only when it identifies the actual owner; do not assign an arbitrary agent or delete the artifacts to clear the warning. Rerun Doctor after resolving ownership. Invalid metadata, failed writes, and unfinished recovery remain migration failures. A retarget count describes proposals changed during that pass. Any remaining external targets can belong to different proposals whose migration is blocked. Review their identifiers, paths, and migration warnings before retrying the same repair. Package rollback does not reverse the state-schema migration or relocated skill files. An older package can therefore be incompatible with the retained state. See Schema bumps and older updaters and Downgrade recovery.Tool-policy diagnostic
Inpropose and auto modes, openclaw doctor runs the
core/doctor/skill-workshop-tool-policy check for the default agent. If policy
hides skill_workshop, the warning names the first excluding config layer and
the exact allow or alsoAllow change to make. Older runbooks may still use
openclaw plugins inspect skill-workshop; that command now explains that Skill
Workshop is built in and prints the same policy hint when applicable.