Unsaved transactions recovered

The host replayed transactions that were journaled but had not reached their document files. They are now in memory and marked for flushing; the message reports the number recovered.

#Common causes

• The previous host stopped before its debounced document writes completed.

#Fixes

• Nothing to fix; let the host finish saving and inspect session.status for file state.

• Use ara history or ara inspect to confirm the recovered changes, and stop the host cleanly so its final flush can complete.

• Code: ARA1906

• Constant: JOURNAL_REPLAYED

• Reported by: ara-host