Combine agentspan cli to conductor

[kowser-orkes]

What

Folds the standalone AgentSpan CLI into the conductor binary as first‑class subcommands, talking to the single merged Conductor server. The old AgentSpan runtime on :6767 is retired and never referenced — the server comes only from --server / CONDUCTOR_SERVER_URL.

• conductor agent — compile, delete, execution, get, init, list, prune, respond, run (SSE), status, stream.
• conductor skill — delete, get, list, pull, register, load, run (streams), serve.

Not migrated

• Dropped (superseded by Conductor): login / logout, configure → Conductor auth (config save, key/secret→JWT) and the existing secret store; version → root --version.
• Name collisions (Conductor's command wins): server (start / stop / logs / ps) and update — these managed the retired :6767 runtime / JAR. AgentSpan's data-op server prune survives, rehomed as agent prune.
• Deferred (in scope): tui, credentials (+ set / bind / bindings)

Followups

• tui
• credentials (+ set / bind / bindings)

[mp-orkes]

Do not merge to main

These commands hit /api/agent/* endpoints that neither Conductor OSS nor Orkes Conductor implement yet, and they're registered unconditionally with no capability check. In any current server every the command produces 404s with a cryptic error, exactly like conductor-oss/conductor#1197.

If Agentspan needs this, release it from its own branch. To land on main it needs capability detection or a config/feature flag plus a clear error when the server doesn't support it.