validateScheduling (internal/app/controlplane/operational_settings.go, validateScheduling) checks only DispatchTriggerValid and the interval/max_retries. It never mirrors the file layer's pairing rule in validateDispatch (internal/infrastructure/configuration/validate.go: 'label is required when dispatch.trigger is label/either' — the live-incident guard from GH#445 that stops an empty label matching every open issue). A scheduling-policy resource can therefore be STORED through the control-plane write path (Web UI handleControlPlaneCommand / staterpc) with trigger 'label' or 'either', while cfg.Label — which the resource does not carry — stays whatever the file set (often empty). At next boot, RuntimeConfig layers the stored policy over the file doc and configuration.Validate refuses the effective document ('label is required when dispatch.trigger is label/either'), so archied fails closed on a value the store blessed and the operator can only fix by editing the file or rolling back offline. This violates the parity rule the repo states for exactly this shape: TestResourceValidatorsRejectWhatEffectiveValidationRejects' doc comment ('a value the resource accepts must not stop the daemon's validation of the effective document') and ValidateRepositories' 'a stored value the daemon then refuses to start with'. The parity test battery has no trigger=label-without-label case, which is why the drift is invisible. Fix direction needs a decision: the write path cannot see the file's Label, so either validateScheduling gains the rule against the layered value (base-aware) or the label check must move where the effective document is built. Filed as found; the maintainer owns the fix location.
Close reason
Fixed in fbd57392: the scheduling policy carries the label its trigger pairs with, so the write path can no longer store a value boot refuses.
Imported from beads archie-core-7pyj · GitHub #1138 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-26
validateScheduling (internal/app/controlplane/operational_settings.go, validateScheduling) checks only DispatchTriggerValid and the interval/max_retries. It never mirrors the file layer's pairing rule in validateDispatch (internal/infrastructure/configuration/validate.go: 'label is required when dispatch.trigger is label/either' — the live-incident guard from GH#445 that stops an empty label matching every open issue). A scheduling-policy resource can therefore be STORED through the control-plane write path (Web UI handleControlPlaneCommand / staterpc) with trigger 'label' or 'either', while cfg.Label — which the resource does not carry — stays whatever the file set (often empty). At next boot, RuntimeConfig layers the stored policy over the file doc and configuration.Validate refuses the effective document ('label is required when dispatch.trigger is label/either'), so archied fails closed on a value the store blessed and the operator can only fix by editing the file or rolling back offline. This violates the parity rule the repo states for exactly this shape: TestResourceValidatorsRejectWhatEffectiveValidationRejects' doc comment ('a value the resource accepts must not stop the daemon's validation of the effective document') and ValidateRepositories' 'a stored value the daemon then refuses to start with'. The parity test battery has no trigger=label-without-label case, which is why the drift is invisible. Fix direction needs a decision: the write path cannot see the file's Label, so either validateScheduling gains the rule against the layered value (base-aware) or the label check must move where the effective document is built. Filed as found; the maintainer owns the fix location.
### Close reason
Fixed in fbd57392: the scheduling policy carries the label its trigger pairs with, so the write path can no longer store a value boot refuses.
---
_Imported from beads `archie-core-7pyj` · GitHub #1138 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-26_
sam
added the mediumbug labels 2026-10-27 13:39:08 +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.
validateScheduling (internal/app/controlplane/operational_settings.go, validateScheduling) checks only DispatchTriggerValid and the interval/max_retries. It never mirrors the file layer's pairing rule in validateDispatch (internal/infrastructure/configuration/validate.go: 'label is required when dispatch.trigger is label/either' — the live-incident guard from GH#445 that stops an empty label matching every open issue). A scheduling-policy resource can therefore be STORED through the control-plane write path (Web UI handleControlPlaneCommand / staterpc) with trigger 'label' or 'either', while cfg.Label — which the resource does not carry — stays whatever the file set (often empty). At next boot, RuntimeConfig layers the stored policy over the file doc and configuration.Validate refuses the effective document ('label is required when dispatch.trigger is label/either'), so archied fails closed on a value the store blessed and the operator can only fix by editing the file or rolling back offline. This violates the parity rule the repo states for exactly this shape: TestResourceValidatorsRejectWhatEffectiveValidationRejects' doc comment ('a value the resource accepts must not stop the daemon's validation of the effective document') and ValidateRepositories' 'a stored value the daemon then refuses to start with'. The parity test battery has no trigger=label-without-label case, which is why the drift is invisible. Fix direction needs a decision: the write path cannot see the file's Label, so either validateScheduling gains the rule against the layered value (base-aware) or the label check must move where the effective document is built. Filed as found; the maintainer owns the fix location.
Close reason
Fixed in
fbd57392: the scheduling policy carries the label its trigger pairs with, so the write path can no longer store a value boot refuses.Imported from beads
archie-core-7pyj· GitHub #1138 · type bug · priority P2 · created 2026-09-21 · closed 2026-09-26