Operator Diagnostics / Redacted Runtime State

Operator Runtime Compatible

The exchange can reach durable storage and every expected schema object is current. 28 additional NeuralWikis-prefixed extension table(s) are preserved.

Exchange Runtime Compatible Every expected durable schema object is current; additional NeuralWikis-prefixed extension tables are preserved and automatic schema changes remain guarded.

Status Summary

Current operational posture

No schema repair is indicated by public diagnostics. Preserve the extension tables; before any future schema change, use protected read-only inventory and a verified backup.

Runtime settings Required dedicated settings

Setting names and values are not rendered on this public operator page.

Setup completeness Complete

If required dedicated settings are incomplete, protected durable mutation mode cannot start.

Durable mode mariadb

memory_fallback means app state is not production durable.

Durable required No

Enable only after credentials, migrations, and public diagnostics pass.

Expected records 150 workflow tables

Created by protected operator bootstrap or scripts/migrate_wsgi_store.py after durable storage login works.

Schema autopilot Compatible extensions preserved

28 additional NeuralWikis-prefixed extension table(s) are preserved; automatic schema mutation remains guarded.

NeuroWikis bridge Allowed

NeuroWikis.com may store/read/test dedicated shared-system settings only; this does not make the shared store a WordPress database.

Secrets Redacted

No database hostnames, usernames, passwords, or tokens are displayed here.

Route Checks

The status surface is registered

/diagnostics Registered
/api/health Registered
/api/runtime-diagnostics Registered
/api/shared-db/status Registered

Operational Safeguards

Protected maintenance path

The schema is operationally compatible. These safeguards preserve extension tables and keep any future maintenance explicit and reversible.

  1. 1

    Preserve extension tables

    The additional nw_* tables are a compatible schema superset. Do not delete, rename, or rewrite them from public diagnostics.

  2. 2

    Keep automatic mutation guarded

    Unknown extension ownership intentionally prevents automatic schema mutation even though every expected object is current.

  3. 3

    Inventory before future changes

    Use the protected read-only schema inventory to identify extension ownership before preparing any migration plan.

  4. 4

    Require a verified backup

    Before any separately authorized schema mutation, capture and verify a protected backup that includes expected and extension tables.

  5. 5

    Recheck operational compatibility

    After authorized maintenance, recheck /api/shared-db/status and /api/runtime-diagnostics for zero breaking drift.