v0.9.2

• Boot-time configuration recording now survives every database failure, loudly. #240 guarded the
  boot-time write against a missing table, but the introspection query that finds that out needs a
  reachable database — and a fresh clone boots (package:discover during composer install, then
  key:generate) before its SQLite file exists. record() now skips on an unreachable database and
  on a failing write (read-only filesystem, full disk, unmigrated schema) exactly as it skips on a
  missing table — and, because those failures can also mean permanent misconfiguration, each skip
  dispatches a new CapabilityConfigurationUnrecorded event (once per store for an unreachable
  database, per configuration for a failed write) so operators can log what a silent skip would have
  hidden. hasTable() deliberately still throws, so verdict:validate keeps reporting "could not
  inspect its table" — a different remedy than "missing table" — now pinned by tests. Found by the
  reference app absorbing the v0.9.1 bump
  (verdict-storefront#12). Closes
  #256.