internal/app/archied/gateway_runtime.go:37 watches personas and applies them live at :79-86, but never calls applyStatus.Report for the personas kind. The only daemon Report sites are internal/app/archied/control_plane.go:41 (restart-required kinds, fed only by RuntimeConfig's versions map) and :118 (workflow-execution-settings).
So the PRD clause the apply-status surface is built on is unmet for a live-applied kind: docs/prds/runtime-control-plane.md:65-66 "The database stores the requested settings. Each process reports the version it is using or why it failed. The UI shows both."
workflow-definitions is in the same class (no report), but the dashboard's SSE stream for it is a generic passthrough (internal/webui/api_control_plane.go:139) and not a component-replacement path, so personas is the live-watched kind that matters here.
Fix direction: report the personas kind at the apply point, as workflow-execution-settings does.
Close reason
Superseded: personas are replaced by SOUL and identity-per-action (docs/prds/soul.md, Persona removal gate); the persona surface itself is removed under archie-core-7ftt. This bead's work (apply-status and probe for the personas kind) loses its subject when that removal lands.
Imported from beads archie-core-aj35 · GitHub #1150 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-29
Found by the Wave 0R claims audit (c3, P2).
internal/app/archied/gateway_runtime.go:37 watches personas and applies them live at :79-86, but never calls applyStatus.Report for the personas kind. The only daemon Report sites are internal/app/archied/control_plane.go:41 (restart-required kinds, fed only by RuntimeConfig's versions map) and :118 (workflow-execution-settings).
So the PRD clause the apply-status surface is built on is unmet for a live-applied kind: docs/prds/runtime-control-plane.md:65-66 "The database stores the requested settings. Each process reports the version it is using or why it failed. The UI shows both."
workflow-definitions is in the same class (no report), but the dashboard's SSE stream for it is a generic passthrough (internal/webui/api_control_plane.go:139) and not a component-replacement path, so personas is the live-watched kind that matters here.
Fix direction: report the personas kind at the apply point, as workflow-execution-settings does.
### Close reason
Superseded: personas are replaced by SOUL and identity-per-action (docs/prds/soul.md, Persona removal gate); the persona surface itself is removed under archie-core-7ftt. This bead's work (apply-status and probe for the personas kind) loses its subject when that removal lands.
---
_Imported from beads `archie-core-aj35` · GitHub #1150 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-29_
sam
added the mediumbug labels 2026-10-27 13:39:30 +00:00
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.
Found by the Wave 0R claims audit (c3, P2).
internal/app/archied/gateway_runtime.go:37 watches personas and applies them live at :79-86, but never calls applyStatus.Report for the personas kind. The only daemon Report sites are internal/app/archied/control_plane.go:41 (restart-required kinds, fed only by RuntimeConfig's versions map) and :118 (workflow-execution-settings).
So the PRD clause the apply-status surface is built on is unmet for a live-applied kind: docs/prds/runtime-control-plane.md:65-66 "The database stores the requested settings. Each process reports the version it is using or why it failed. The UI shows both."
workflow-definitions is in the same class (no report), but the dashboard's SSE stream for it is a generic passthrough (internal/webui/api_control_plane.go:139) and not a component-replacement path, so personas is the live-watched kind that matters here.
Fix direction: report the personas kind at the apply point, as workflow-execution-settings does.
Close reason
Superseded: personas are replaced by SOUL and identity-per-action (docs/prds/soul.md, Persona removal gate); the persona surface itself is removed under archie-core-7ftt. This bead's work (apply-status and probe for the personas kind) loses its subject when that removal lands.
Imported from beads
archie-core-aj35· GitHub #1150 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-29