readiness
One-call tenant-onboarding probe: readiness:query:status rolls up every config key and secret declared required: true across all mounted features and reports which still lack a usable value for the calling tenant, plus a single ready boolean. Provider-features under an r.extensionSelector-declared extension point count only while their provider is the selected one — a tenant on the inmemory mail transport is not blocked by unset SMTP keys. Mount it (together with config and secrets) when an admin UI needs a settings checklist before the first mail-send or file-write; the per-concern lists stay available via config:query:readiness and secrets:query:list. readiness:write:run-probes runs the live probes features register with r.probe (mail, files, mailboxes, PDF service and more) as a job; the system-check screen shows the latest run and the history once nav is passed.
How it fits
Section titled “How it fits”What this feature needs to run (Requires, top) and the write commands this feature provides (Provides, bottom).
flowchart TB
n_readiness["readiness"]
subgraph how_reqs["Requires / optional"]
n_config["config"]
n_secrets["secrets"]
n_user["user"]
end
subgraph how_provides["Provides"]
n_cmd_readiness_write_run_probes(["run-probes"])
end
n_config --> n_readiness
n_secrets --> n_readiness
n_user -.->|optional| n_readiness
n_readiness --> n_cmd_readiness_write_run_probes
Provides — write commands this feature registers (dispatch them through the command bus):