Variable: SETUP_CHECK_IDS

const SETUP_CHECK_IDS: readonly ["provider.reachable", "provider.capabilities", "provider.converged", "provider.root_account", "organizations.request", "organizations.applied", "anchor.declared", "anchor.framework", "anchor.applied", "accounts.declared", "accounts.applied", "accounts.invitation", "module.library", "module.session", "module.identification", "module.test_key", "identifiers.declared", "identifiers.agent", "identifiers.registry", "identifiers.applied", "configuration.authority", "configuration.stored", "configuration.applied", "publish.federation", "publish.identifier", "root.signed_in"]

Defined in: packages/contracts/src/setup-checks.ts:35

The named checks, each belonging to one step. The console holds a sentence per id.

A check whose name ends in applied, converged or root_account reports on the step's own write, so under plan mode it either repeats what the store recorded (with the time, as evidence) or says not_run. The others are read-only and run in both modes. Three checks report on a write under another name, because the name says what was written: identifiers.agent (the shared agent instance registered), identifiers.registry (the throwaway object written and read back) and module.test_key (a key generated on the token, used and destroyed). SETUP_CHECKS is the authority: its reportsApply says which kind a check is.

The last three are the configuration step's self-test (design 08 step 12, DW17): what was published, read back as an outsider would read it, and the root account's first sign-in. They are reads, and run in both modes.