Crate umsh_journal_store 

Power-loss-safe two-page record journals shared by every UMSH device board.

Extracted from the nRF device firmware so the ESP32-S3 port reuses the same tested machinery. Three journal record formats ride one shared engine:

• record — the engine: the record::RecordWriter / record::PageEraser flash traits, the body-first/commit-word-last committed write, CRC32, and wraparound-safe generation comparison.
• ble — fixed-size BLE security snapshots (pairing PIN, local IRK, bonds).
• proto — variable-payload protocol records: opaque session snapshots, the device identity, and clear tombstones.
• counter — the device node’s frame-counter map, serialized as one whole-map proto payload per flush.

Flash addresses deliberately live with each firmware, not here: which pages a journal owns is a memory-map fact (memory.x on nRF, the partition table on ESP32). Structural constants — slot sizes, payload bounds, the 4 KiB page size both chips share — are this crate’s.

Mount scans and write-target rotation are not here either, but they are no longer per-firmware: they live in umsh-ulcp-runtime’s journal module, generic over a board’s flash via the record::RecordWriter / record::PageEraser / record::RecordReader traits. A board implements those three for its own flash type — which is where each chip’s quirks stay, such as blocking NVMC reads under MPSL on nRF and the fault-injection hooks.

Modules

ble

Power-loss-safe BLE security snapshot encoding.

counter

The device node’s persisted frame-counter map (device-node plan increment 4).

proto

Full-protocol snapshot journal records (spec §Saved State).

record

The shared journal record engine.