dispatch help text says 'refuses outside coilysiren/*' but runtime accepts all primary orgs #67

New issue

Closed

opened 2026-06-04 10:06:19 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-04 10:06:19 +00:00

Owner

`dispatch` help text says "refuses anything outside the coilysiren/* org" — multi-org-aware refusal already accepts coilyco-bridge/* + coilyco-flight-deck/*

The runtime gate (Config.ownerAllowed) accepts AllowedOwner plus every entry in AllowedOwners. Coily passes all three primary orgs (coilysiren, coilyco-bridge, coilyco-flight-deck) via AllowedOwners: r.primaryOrgs(), and dispatch correctly accepts a coilyco-bridge/coily#1 ref (refusing only because that issue is closed).

But the help text on both dispatch and dispatch headless interpolates d.cfg.AllowedOwner (single owner) into the "refuses anything outside the X/* org" sentence (dispatch.go:187 and dispatch.go:245). Operators reading the help reasonably conclude that coilyco-* refs will be refused and avoid using them.

Fix

Swap the format-string substitution from d.cfg.AllowedOwner to d.cfg.allowedOwnersLabel() — the same helper used in the actual refusal message at dispatch.go:421. The label renders coilysiren/* for single-owner and {coilysiren, coilyco-bridge, coilyco-flight-deck}/* for multi-owner.

Where this came up

A Claude Code session in the Kapwing workdir read the misleading help text, told the operator that coilyco-* repos were out of scope for dispatch, and tried to pull the operator into widening the gate (which was already wide). Confirmed otherwise only after probing with a real ref.

## `dispatch` help text says "refuses anything outside the coilysiren/* org" — multi-org-aware refusal already accepts coilyco-bridge/* + coilyco-flight-deck/* The runtime gate (`Config.ownerAllowed`) accepts `AllowedOwner` plus every entry in `AllowedOwners`. Coily passes all three primary orgs (`coilysiren`, `coilyco-bridge`, `coilyco-flight-deck`) via `AllowedOwners: r.primaryOrgs()`, and dispatch correctly accepts a `coilyco-bridge/coily#1` ref (refusing only because that issue is closed). But the help text on both `dispatch` and `dispatch headless` interpolates `d.cfg.AllowedOwner` (single owner) into the "refuses anything outside the X/* org" sentence (dispatch.go:187 and dispatch.go:245). Operators reading the help reasonably conclude that coilyco-* refs will be refused and avoid using them. ### Fix Swap the format-string substitution from `d.cfg.AllowedOwner` to `d.cfg.allowedOwnersLabel()` — the same helper used in the actual refusal message at dispatch.go:421. The label renders `coilysiren/*` for single-owner and `{coilysiren, coilyco-bridge, coilyco-flight-deck}/*` for multi-owner. ### Where this came up A Claude Code session in the Kapwing workdir read the misleading help text, told the operator that coilyco-* repos were out of scope for dispatch, and tried to pull the operator into widening the gate (which was already wide). Confirmed otherwise only after probing with a real ref.

coilysiren added this to the sunday-sprint milestone

2026-06-05 03:41:16 +00:00

coilysiren added the

sunday-sprint

label

2026-06-05 03:41:17 +00:00

coilysiren added the

label

2026-06-06 04:27:10 +00:00

coilysiren added

and removed

labels

2026-06-17 08:39:58 +00:00

coilysiren added the

headless

label

2026-06-18 06:17:44 +00:00

coilysiren commented

2026-06-18 07:30:12 +00:00

Author

Owner

🔒 Reserved by ward agent claude — container ward-cli-guard-issue-67-claude-81d7f53c on host kais-macbook-pro.local is carrying this issue (reserved 2026-06-18T07:30:11Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent claude` — container `ward-cli-guard-issue-67-claude-81d7f53c` on host `kais-macbook-pro.local` is carrying this issue (reserved 2026-06-18T07:30:11Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-06-18 07:33:27 +00:00

fix(dispatch): help text advertises full accepted-owner set, not just AllowedOwner

coilysiren closed this issue

2026-06-18 07:33:27 +00:00

coilysiren referenced this issue from a commit

2026-06-18 07:33:27 +00:00

Merge issue-67: dispatch help text full owner set (closes #67)

coilysiren referenced this issue from a commit

2026-06-18 08:39:11 +00:00

feat(specverb): mount-target actions shadow a generated leaf