Add ops-eng-o2r-remote-debug skill (hard-point ssh reflex to o2r) #54
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay#54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add ops-eng-o2r-remote-debug skill
A new
skills/ops-eng-o2r-*operator skill that hard-points the SSH reflex to o2r: when the next step is "ssh into the host and look" at a host running o2r-coordinated agents (a stuck CI runner, a failed deploy, a pod), route the debugging through an o2r agent channel instead of ad-hoc ssh.Framed host-agnostic for o2r adopters (the shipped
o2r channelverbs, not the legacycoily channel). Argues ssh-to-debug is a bypass of the coordination substrate - no audit trail, no OTel span, no trust envelope, no role discipline - and gives the redirected loop (find/open channel -> post the symptom ascomms-> hand off viastateto the local agent -> read the result off the channel). Covers the human-bootstrap carve-out (first runner registration, secret minting) as a channel-recorded handover.Sits beside ops-eng-o2r-agent-channel / -phoenix / -grafana and cross-links them.
Motivation: surfaced while debugging coilyco-flight-deck/otel-a2a-relay-cli#9 (new repo dispatching zero Actions), where the reflex was to ssh into kai-server to inspect the runner.