Preserve Celestia bridge archival mode across service restarts
A manually tested archival startup does not determine how a service manager will launch the bridge later. The archival flag belongs in the persistent start command.
Inspect the installed service
The documented bridge behavior requires --archival on the first start and on every subsequent start. Before enabling automatic restarts, inspect the effective service definition, including overrides, and confirm the network and storage path. Starting an existing archival store in pruned mode can remove old headers and original data.
first start: bridge + --archival
service restart: bridge + --archival
post-restart probe: historical header and known blob
Test historical service directly
Keep a receipt for a known old blob and query it after a controlled restart. Some pruning log entries can describe removal of redundant erasure-coded data even in archival mode. If a store already began in pruned mode, the documented recovery path requires a fresh archival store and peers serving history.