The Skills and Curators pages show the live set Gateway runs, and Channels > Reload works, through the gateway contract.
Evidence
internal/app/archieui/compose.go:50-119 never sets Skills, Curators or ReloadChannel; api_skills.go:23 and api_curators.go:56 return empty, api_config.go:51 returns 501. proto/gateway/v1/chat.proto has no list-skills, curator-health or reload RPC.
Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run task check once at the end; if it fails twice on the same problem, comment on this bead and stop.
Stop when
Three gateway RPCs and their archie-ui clients wired in compose.go.
Pages show live data; reload returns 200.
Then commit (Conventional Commits, scoped by package), bd close this bead and stop.
Close reason
Skills and Curators delivered on main in 6bde185e (gateway ListSkills/CuratorHealth RPCs, archie-ui clients wired in compose.go; both pages now read the Gateway's live set). Channel reload split out and folded into archie-core-np7l because a Gateway hosts no channels.
Imported from beads archie-core-mqti.1 · GitHub #1393 · type bug · priority P0 · created 2026-10-05 · closed 2026-10-05
## Goal
The Skills and Curators pages show the live set Gateway runs, and Channels > Reload works, through the gateway contract.
## Evidence
internal/app/archieui/compose.go:50-119 never sets Skills, Curators or ReloadChannel; api_skills.go:23 and api_curators.go:56 return empty, api_config.go:51 returns 501. proto/gateway/v1/chat.proto has no list-skills, curator-health or reload RPC.
## Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run `task check` once at the end; if it fails twice on the same problem, comment on this bead and stop.
## Stop when
- [ ] Three gateway RPCs and their archie-ui clients wired in compose.go.
- [ ] Pages show live data; reload returns 200.
Then commit (Conventional Commits, scoped by package), `bd close` this bead and stop.
### Close reason
Skills and Curators delivered on main in 6bde185e (gateway ListSkills/CuratorHealth RPCs, archie-ui clients wired in compose.go; both pages now read the Gateway's live set). Channel reload split out and folded into archie-core-np7l because a Gateway hosts no channels.
---
_Imported from beads `archie-core-mqti.1` · GitHub #1393 · type bug · priority P0 · created 2026-10-05 · closed 2026-10-05_
sam
added the criticalbug labels 2026-10-27 13:36:02 +00:00
Skills and Curators now read live from the Gateway: ListSkills and CuratorHealth RPCs on ChatService, a Catalog seam the Gateway process fills from its live skill catalogue and curator registry, archie-ui adapters and compose wiring. commit e389c030 on agent/gateway-catalog; task check exit 0.
ReloadChannel is on the contract and wired, but the Gateway cannot serve it: the Gateway process hosts no channels. Channels run only in archie-messaging (deployments/INSTRUCTIONS.md), archie-messaging dials the Gateway (not the reverse), and the Gateway has no messaging client, so ReloadChannel answers Unavailable and /api/channels/{id}/reload returns 502 rather than 200. The channel reload request surface is archie-core-np7l (the UI asks the Messaging Service), with archie-core-ry4k the cross-process restart RPC. Leaving this bead open for that part.
_sam wrote (originally 2026-10-05):_
Skills and Curators now read live from the Gateway: ListSkills and CuratorHealth RPCs on ChatService, a Catalog seam the Gateway process fills from its live skill catalogue and curator registry, archie-ui adapters and compose wiring. commit e389c030 on agent/gateway-catalog; task check exit 0.
ReloadChannel is on the contract and wired, but the Gateway cannot serve it: the Gateway process hosts no channels. Channels run only in archie-messaging (deployments/INSTRUCTIONS.md), archie-messaging dials the Gateway (not the reverse), and the Gateway has no messaging client, so ReloadChannel answers Unavailable and /api/channels/{id}/reload returns 502 rather than 200. The channel reload request surface is archie-core-np7l (the UI asks the Messaging Service), with archie-core-ry4k the cross-process restart RPC. Leaving this bead open for that part.
Final commit c817a731 on agent/gateway-catalog (supersedes the sha above; amended to adopt the gate formatter's output). task check exit 0 on the clean tree.
_sam wrote (originally 2026-10-05):_
Final commit c817a731 on agent/gateway-catalog (supersedes the sha above; amended to adopt the gate formatter's output). task check exit 0 on the clean tree.
Landed on main as 6bde185e (cherry-picked from agent work): ListSkills + CuratorHealth RPCs and the archie-ui clients are wired, so the Skills and Curators pages read the Gateway's live set. ReloadChannel remains on the contract but cannot serve: channels run in archie-messaging, not the Gateway, so POST reload still answers 502. The reload half is tracked by archie-core-np7l and archie-core-ry4k.
_sam wrote (originally 2026-10-05):_
Landed on main as 6bde185e (cherry-picked from agent work): ListSkills + CuratorHealth RPCs and the archie-ui clients are wired, so the Skills and Curators pages read the Gateway's live set. ReloadChannel remains on the contract but cannot serve: channels run in archie-messaging, not the Gateway, so POST reload still answers 502. The reload half is tracked by archie-core-np7l and archie-core-ry4k.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
The Skills and Curators pages show the live set Gateway runs, and Channels > Reload works, through the gateway contract.
Evidence
internal/app/archieui/compose.go:50-119 never sets Skills, Curators or ReloadChannel; api_skills.go:23 and api_curators.go:56 return empty, api_config.go:51 returns 501. proto/gateway/v1/chat.proto has no list-skills, curator-health or reload RPC.
Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run
task checkonce at the end; if it fails twice on the same problem, comment on this bead and stop.Stop when
Then commit (Conventional Commits, scoped by package),
bd closethis bead and stop.Close reason
Skills and Curators delivered on main in
6bde185e(gateway ListSkills/CuratorHealth RPCs, archie-ui clients wired in compose.go; both pages now read the Gateway's live set). Channel reload split out and folded into archie-core-np7l because a Gateway hosts no channels.Imported from beads
archie-core-mqti.1· GitHub #1393 · type bug · priority P0 · created 2026-10-05 · closed 2026-10-05sam wrote (originally 2026-10-05):
Skills and Curators now read live from the Gateway: ListSkills and CuratorHealth RPCs on ChatService, a Catalog seam the Gateway process fills from its live skill catalogue and curator registry, archie-ui adapters and compose wiring. commit e389c030 on agent/gateway-catalog; task check exit 0.
ReloadChannel is on the contract and wired, but the Gateway cannot serve it: the Gateway process hosts no channels. Channels run only in archie-messaging (deployments/INSTRUCTIONS.md), archie-messaging dials the Gateway (not the reverse), and the Gateway has no messaging client, so ReloadChannel answers Unavailable and /api/channels/{id}/reload returns 502 rather than 200. The channel reload request surface is archie-core-np7l (the UI asks the Messaging Service), with archie-core-ry4k the cross-process restart RPC. Leaving this bead open for that part.
sam wrote (originally 2026-10-05):
Final commit c817a731 on agent/gateway-catalog (supersedes the sha above; amended to adopt the gate formatter's output). task check exit 0 on the clean tree.
sam wrote (originally 2026-10-05):
Landed on main as
6bde185e(cherry-picked from agent work): ListSkills + CuratorHealth RPCs and the archie-ui clients are wired, so the Skills and Curators pages read the Gateway's live set. ReloadChannel remains on the contract but cannot serve: channels run in archie-messaging, not the Gateway, so POST reload still answers 502. The reload half is tracked by archie-core-np7l and archie-core-ry4k.