Review of d7f3d0da found the build-and-probe step shape-only: the check it
added re-ran workflow.ExecutionSettings.Validate, which the store runs before
writing the document and controlplane.Client runs again on the way out, so no
producer could trip it. That review was right; this corrects it.
- The probe is now this process's own runnability check on the candidate it
would switch to: configuration.Validate over the configuration snapshot the
new limits would be published as, the same gate runtimeConfig applies before
publishing a layered config and the readiness probe applies to the published
one. The duplicated schema check is gone.
- The refusal the daemon really meets arrives as a watch error, because the
client decodes every document before the apply path sees it. That branch
logged and returned without writing an apply-status record, so the settings
page showed a live resource as healthy while nothing was being applied. It
now reports the refusal, against the version the reporter last applied.
Whether the stream is re-established afterwards stays archie-core-yrmr.
- `Closes archie-core-nwa0` in d7f3d0da is withdrawn: the item stays open. For
a limits-only kind no producer can make the owned check fail today, so the
refusal path is exercised by test, not by traffic; the live kind whose
candidate check has content is personas (archie-core-nw7t). Both callers are
covered by tests now, through the client seam, instead of by calling the
apply function directly.
- The comments no longer claim behaviour the code lacks: the boot abort is the
fail-closed direction of a rule whose branch boot cannot reach, and the
carried-forward version is the reporter's property, not this call's.
Out of scope and recorded instead: the live apply still publishes with
cfgHolder.Set rather than publishConfig, leaving the dashboard's config
snapshot stale after a live change (archie-core-75cc). workflow-definitions
gets no check because nothing swaps a running definition: the daemon reads the
collection per task pin (daemon.go:1479, pinWorkflowFromCollection) and the
only other reader is the dashboard's stream, so there is no live replacement to
probe.