Onboard otel-a2a-relay-cli as a ward-managed repo #35

New issue

Closed

opened 2026-06-03 08:53:45 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-03 08:53:45 +00:00

Owner

Re-homed from closed coilyco-bridge/coily#174. o2r-cli's cli-guard consumer is ward, not coily - coily and ward are peer consumers of the same cli-guard engine, and coily stays unaware of o2r. So the onboarding belongs here.

Problem

coilyco-flight-deck/otel-a2a-relay-cli was created directly via the Forgejo API and has no cli-guard wiring yet. As a repo with external contributors, it should route dev/ops commands through ward (the contribution-friendly cli-guard consumer) instead of bare tools or the raw API.

Asks

Add otel-a2a-relay-cli to ward's managed-repo registry so ward <verb> resolves a commit scope there.
Create its .ward/ward.yaml with the baseline verb set (build / test / lint / etc. as appropriate once the CLI takes shape).
Run ward setup and confirm the lockdown files (.claude/lockdown-deny.sh, .claude/settings.json) get generated for it.

Context

Repo is private, canonical on Forgejo at coilyco-flight-deck/otel-a2a-relay-cli (verified 200 direct), default branch main. GitHub mirror not yet set up.
The o2r channel verbs themselves (list / handoff / request / verify, plus the MagicDNS resolver fix) are tracked as features in the o2r-cli repo: otel-a2a-relay-cli#10, #11, #12, #13. This issue is only about the cli-guard tooling wiring.

Filed by Claude on 2026-06-03, re-homing the onboarding asks from coily#174 after the coily->ward correction.

_Re-homed from closed coilyco-bridge/coily#174. o2r-cli's cli-guard consumer is **ward**, not coily - coily and ward are peer consumers of the same cli-guard engine, and coily stays unaware of o2r. So the onboarding belongs here._ ## Problem `coilyco-flight-deck/otel-a2a-relay-cli` was created directly via the Forgejo API and has no cli-guard wiring yet. As a repo with external contributors, it should route dev/ops commands through **ward** (the contribution-friendly cli-guard consumer) instead of bare tools or the raw API. ## Asks - Add `otel-a2a-relay-cli` to ward's managed-repo registry so `ward <verb>` resolves a commit scope there. - Create its `.ward/ward.yaml` with the baseline verb set (build / test / lint / etc. as appropriate once the CLI takes shape). - Run `ward setup` and confirm the lockdown files (`.claude/lockdown-deny.sh`, `.claude/settings.json`) get generated for it. ## Context - Repo is private, canonical on Forgejo at `coilyco-flight-deck/otel-a2a-relay-cli` (verified 200 direct), default branch `main`. GitHub mirror not yet set up. - The o2r channel *verbs* themselves (list / handoff / request / verify, plus the MagicDNS resolver fix) are tracked as features in the o2r-cli repo: otel-a2a-relay-cli#10, #11, #12, #13. This issue is only about the cli-guard tooling wiring. > Filed by Claude on 2026-06-03, re-homing the onboarding asks from coily#174 after the coily->ward correction.

coilysiren closed this issue

2026-06-03 23:51:28 +00:00