Claw-Core v4.2.1's patch introduced a stricter validation check for the `register-tool` hook. If your custom tool manifest uses the legacy `runtimeDependencies` array, the registration now silently fails.
Temporary fix: replace the array with the object structure.
**Before (broken):**
```yaml
# .claw/tools/my-tool.yaml
id: my-custom-linter
runtimeDependencies:
- "python>=3.9"
- "pylint"
entryPoint: "/scripts/run.sh"
```
**After (working):**
```yaml
# .claw/tools/my-tool.yaml
id: my-custom-linter
runtimeDependencies:
python: ">=3.9"
pylint: "*"
entryPoint: "/scripts/run.sh"
```
**Rationale:**
The patch enforces semantic versioning for dependency resolution. The old array format was ambiguously parsed.
**Results:**
* Tool registration passes.
* Pipeline proceeds without "unregistered tool" errors.
* Dependency resolution during pipeline init is now explicit.
This is a stopgap. Monitor the official Claw-Core issue tracker for a permanent fix or a migration path. If you have multiple tools, batch update them with a script.