Priority Triage
wrong-block-commitment-while-catching-up
wrong block commitment while a node is still catching up or consuming stale state
A local miner or receipt may be comparing against a non-tip state, mismatched state-jam source, or suppressed gossip window.
syncMode, behindTipEstimate, stateJamFingerprint, nockchainCommit, routeTableSize
Do not classify the commitment as an app failure until the node is at Tip and state-jam provenance matches the intended network.
empty-routing-table-with-quiet-node
routing table is empty and the node is quiet
Peer discovery or local bind/peer configuration may be wrong, but a catching-up node can also intentionally avoid originating gossip.
connectedPeerCount, routeTableSize, syncMode, fakenetBindAddr, peerMultiaddr
Separate no-peer connectivity from behind-tip quietness before restarting miners or changing state.
miner-output-not-gossiped
mining output is produced locally but not gossiped
The driver suppresses mining-output gossip while CatchingUp so stale or out-of-order work does not pollute peers.
syncMode, gossipSuppressedBehindTipTotal, tipStatus, minerCommitment
Wait for Tip or prove the fakenet is intentionally isolated before treating miner silence as a bug.