[USABILITY] OpenClaw first-class startup/skill path

[LucielAI]

Problem

SPINE is "compatible" with OpenClaw but not yet first-class in OpenClaw onboarding or skill setup. This means OpenClaw agents that encounter SPINE get a generic "compatible in principle" signal rather than a clear path to getting SPINE running immediately.

Goal

Move OpenClaw from "compatible" to a clearer first-class onboarding/skill path without changing SPINE's core identity or creating runtime coupling.

Constraints

• Do NOT turn SPINE into an OpenClaw-specific tool
• SPINE must remain runtime-agnostic and repo-native
• The improvement is about discoverability and startup clarity, not feature parity

Possible approaches

• A spine-agent skill that auto-loads when SPINE is detected in a repo
• OpenClaw startup guidance that detects .spine/ and surfaces relevant commands
• A thin SPINE_ROOT integration for OpenClaw's workspace model

Triage classification

GOOD TO FIX BEFORE BETA EXIT IF CHEAP (Phase 3B candidate)

---

Post-beta stabilization — milestone #6