Move agent lifecycle UX under obol agent

.agents/skills/obol-stack-dev/SKILL.md

@@ -121,7 +121,7 @@ Known existing-stack migration failures:
 
 - `Namespace "hermes-obol-agent" ... exists and cannot be imported into the current release`: the namespace or monetize RBAC predated Helm ownership. Current `obol stack up` adopts known base-owned resources before Helm sync. If doing it manually, label and annotate the existing resource with `app.kubernetes.io/managed-by=Helm`, `meta.helm.sh/release-name=base`, and `meta.helm.sh/release-namespace=kube-system`.
 - `conflict with "kubectl-patch" ... llm/litellm-config .data.config.yaml`: older writers used a non-Helm field manager for `data.config.yaml`, which conflicts with Helm server-side apply. Current writers use Helm's field manager. During `obol stack up`, the existing LiteLLM config is backed up and previous model entries are merged into the new chart config; if a non-Helm manager is detected, the ConfigMap is deleted before Helm sync so ownership is recreated cleanly.
-- `/etc/hosts` updates require interactive sudo. Codex cannot satisfy the password prompt in non-interactive execution; if DNS fails in the browser, run `obol stack up` or `obol hermes sync obol-agent` from a normal terminal, or manually add `127.0.0.1 obol-agent.obol.stack` and flush local DNS.
+- `/etc/hosts` updates require interactive sudo. Codex cannot satisfy the password prompt in non-interactive execution; if DNS fails in the browser, run `obol stack up` or `obol agent sync obol-agent` from a normal terminal, or manually add `127.0.0.1 obol-agent.obol.stack` and flush local DNS.
 
 ## 4 Inference Paths (All Through LiteLLM)
 

README.md

@@ -53,8 +53,8 @@ obol stack up
 obol agent init
 
 # Inspect the default Hermes agent
-obol hermes list
-obol hermes token obol-agent
+obol agent list
+obol agent auth obol-agent
 ```
 
 `obol stack up` provisions the default [Hermes Agent](https://github.com/NousResearch/hermes-agent) runtime behind LiteLLM. `obol agent init` applies the controller-based agent capabilities used for monetization and reconciliation.
@@ -151,24 +151,24 @@ Hermes is the default AI agent runtime deployed by the stack as `obol-agent`. Op
 
 ```bash
 # Default stack-managed Hermes agent
-obol hermes list
-obol hermes token obol-agent
+obol agent list
+obol agent auth obol-agent
 obol hermes skills list
 
 # Create and deploy an additional Hermes instance
-obol hermes onboard --id research
+obol agent new --id research
 
 # Create and deploy an optional OpenClaw instance
-obol openclaw onboard
+obol agent new --runtime openclaw
 
 # List optional OpenClaw instances
-obol openclaw list
+obol agent list --runtime openclaw
 
 # Open the OpenClaw web dashboard
 obol openclaw dashboard
 ```
 
-When only one runtime-specific instance is installed, the instance ID is optional. With multiple instances, specify the name: `obol hermes sync research` or `obol openclaw setup prod`.
+Use `obol agent` for Obol-managed lifecycle and auth flows. Use `obol hermes` for native Hermes CLI commands against the default instance, or pass `--agent <id>` for a non-default Hermes instance.
 
 ### Skills