controlplane.Client.RuntimeConfig (internal/app/controlplane/runtime_config.go) layers every stored kind and RuntimeConfig (servicekit) reports the whole versions map for the calling process. archie-gateway layers all of it at boot, but watches only provider, model-role and tool kinds (gatewayRuntimeKinds); so its records for repository-policies, scheduling-policy, review-settings, plugin-settings, container-runtime-policies, agent-profiles, credential-bindings and identity-grants report the boot version and lag forever under whatever the catalog's apply_mode says. Under a live label a permanent lag reads as a reporting lag; archie-messaging likewise reports kinds it only boot-layers.
Done when
[ ] The apply-status page's records for a process cover exactly the kinds that process re-applies live, or a lag under a live label is bounded in time by the process actually catching up.
[ ] No record sits stale under a live label.
Noted during archie-core-4q28.16; do not widen labels to paper over it -- the fix is in what processes report, not in the kind labels.
Close reason
Gateway now reports only provider, model-role and tool kinds; Messaging already reported only channel settings
Imported from beads archie-core-mt91 · GitHub #1497 · type task · priority P2 · created 2026-10-05 · closed 2026-10-13
controlplane.Client.RuntimeConfig (internal/app/controlplane/runtime_config.go) layers every stored kind and RuntimeConfig (servicekit) reports the whole versions map for the calling process. archie-gateway layers all of it at boot, but watches only provider, model-role and tool kinds (gatewayRuntimeKinds); so its records for repository-policies, scheduling-policy, review-settings, plugin-settings, container-runtime-policies, agent-profiles, credential-bindings and identity-grants report the boot version and lag forever under whatever the catalog's apply_mode says. Under a live label a permanent lag reads as a reporting lag; archie-messaging likewise reports kinds it only boot-layers.
Done when
[ ] The apply-status page's records for a process cover exactly the kinds that process re-applies live, or a lag under a live label is bounded in time by the process actually catching up.
[ ] No record sits stale under a live label.
Noted during archie-core-4q28.16; do not widen labels to paper over it -- the fix is in what processes report, not in the kind labels.
### Close reason
Gateway now reports only provider, model-role and tool kinds; Messaging already reported only channel settings
---
_Imported from beads `archie-core-mt91` · GitHub #1497 · type task · priority P2 · created 2026-10-05 · closed 2026-10-13_
sam
added the mediumtask labels 2026-10-27 13:40:27 +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.
controlplane.Client.RuntimeConfig (internal/app/controlplane/runtime_config.go) layers every stored kind and RuntimeConfig (servicekit) reports the whole versions map for the calling process. archie-gateway layers all of it at boot, but watches only provider, model-role and tool kinds (gatewayRuntimeKinds); so its records for repository-policies, scheduling-policy, review-settings, plugin-settings, container-runtime-policies, agent-profiles, credential-bindings and identity-grants report the boot version and lag forever under whatever the catalog's apply_mode says. Under a live label a permanent lag reads as a reporting lag; archie-messaging likewise reports kinds it only boot-layers.
Done when
[ ] The apply-status page's records for a process cover exactly the kinds that process re-applies live, or a lag under a live label is bounded in time by the process actually catching up.
[ ] No record sits stale under a live label.
Noted during archie-core-4q28.16; do not widen labels to paper over it -- the fix is in what processes report, not in the kind labels.
Close reason
Gateway now reports only provider, model-role and tool kinds; Messaging already reported only channel settings
Imported from beads
archie-core-mt91· GitHub #1497 · type task · priority P2 · created 2026-10-05 · closed 2026-10-13