The container-runtime-policies document no longer carries named profiles: they moved to the agent-profiles control-plane resource (AgentProfileKind, internal/app/controlplane/agent_profiles.go), and the container document's decoder drops a profiles key. The Container runtime page was the only surface that ever edited them, and it still rendered a Profiles section bound to the removed key, so profiles have had no editor in the dashboard since the move. Wanted: a settings page backed by the agent-profiles resource (image, kit, adapter, tools), or a decision to keep profiles off the dashboard. Done when an operator can see and edit named profiles from Settings, or the omission is recorded as deliberate.
Close reason
Three routed settings editors with versioned save/review; Events mappings link to installed playbooks; browser verified add/edit/save/remove on each; task check passed; committed and pushed 0a1cba4c.
Imported from beads archie-core-x0wk · GitHub #1328 · type feature · priority P2 · created 2026-10-04 · closed 2026-10-08
The container-runtime-policies document no longer carries named profiles: they moved to the agent-profiles control-plane resource (AgentProfileKind, internal/app/controlplane/agent_profiles.go), and the container document's decoder drops a profiles key. The Container runtime page was the only surface that ever edited them, and it still rendered a Profiles section bound to the removed key, so profiles have had no editor in the dashboard since the move. Wanted: a settings page backed by the agent-profiles resource (image, kit, adapter, tools), or a decision to keep profiles off the dashboard. Done when an operator can see and edit named profiles from Settings, or the omission is recorded as deliberate.
### Close reason
Three routed settings editors with versioned save/review; Events mappings link to installed playbooks; browser verified add/edit/save/remove on each; task check passed; committed and pushed 0a1cba4c.
---
_Imported from beads `archie-core-x0wk` · GitHub #1328 · type feature · priority P2 · created 2026-10-04 · closed 2026-10-08_
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.
The container-runtime-policies document no longer carries named profiles: they moved to the agent-profiles control-plane resource (AgentProfileKind, internal/app/controlplane/agent_profiles.go), and the container document's decoder drops a profiles key. The Container runtime page was the only surface that ever edited them, and it still rendered a Profiles section bound to the removed key, so profiles have had no editor in the dashboard since the move. Wanted: a settings page backed by the agent-profiles resource (image, kit, adapter, tools), or a decision to keep profiles off the dashboard. Done when an operator can see and edit named profiles from Settings, or the omission is recorded as deliberate.
Close reason
Three routed settings editors with versioned save/review; Events mappings link to installed playbooks; browser verified add/edit/save/remove on each; task check passed; committed and pushed 0a1cba4c.
Imported from beads
archie-core-x0wk· GitHub #1328 · type feature · priority P2 · created 2026-10-04 · closed 2026-10-08