feat(services): expose effective persistence settings in canonical and doctor

canonical と doctor のエントリーポイントから始め、Redis と Valkey で永続化モードとドライバー設定がどのように表示されるかを追跡します。整合したデフォルトと、明示的に異なる設定を比較し、ストレージの存続期間への影響も含め、他のモード由来のドライバーについても同じレポートモデルを確認します。完了の条件は、canonical が宣言されたモード、実効値、そしてそれらの出所を表示し、doctor が #79 のランタイム表示や遷移ゲートを変更せずに差異を説明することです。

Status

The runtime defect originally reported here was fixed by #79 (7f94af0):

• persistence.mode: ephemeral creates no durable Onebox volume for every managed driver;
• Redis and Valkey receive ephemeral persistence defaults;
• explicit driver settings override mode-derived server defaults exactly once;
• omitted and durable modes retain durable storage semantics;
• destructive persistence transitions remain gated.

Remaining problem

The override is effective but not visible enough. ob canonical and ob doctor do not explain when authored driver settings diverge from the persistence mode. An operator can deliberately enable AOF on ephemeral storage, for example, but Onebox does not state that the data survives a process restart and not a container recreate.

Scope

• Show the declared persistence mode and effective server persistence values with their origin in canonical output.
• Have doctor name actionable divergences between the mode and explicit driver settings.
• Document that persistence.mode owns Onebox storage lifetime while settings owns server internals and cannot create a durable Onebox volume.
• Report divergence; do not refuse a deliberate override.

Acceptance

• Redis and Valkey cover mode defaults and explicit overrides in canonical output.
• Doctor distinguishes a harmless aligned setting from a divergent one and explains the operational consequence.
• Other drivers with mode-derived persistence options follow the same reporting model.
• Runtime rendering and transition gates from #79 remain unchanged.

The original measurements and design discussion remain in this issue history and in #79.