walletAutoShieldSupportedProvider top-level property
HOST SEAM (#383 R2): whether the host's custody model supports the
AUTO-SHIELD policy loop (#328). The loop's spends are origin: automatic —
no user is present at a prompt — so a per-spend-credential host (every
automatic spend is policy-denied) should override this to false: the
auto-shield toggle is then HIDDEN in the Transparent-funds sheet and the
loop never arms — an honest absence instead of a switch that reads ON but
can never run (the walletOfflineQueueSupportedProvider honesty rule).
UX honesty, not a safety boundary: even when true on such custody, every
attempt still routes through the authorizer and a denial stops the loop
for the session with the funds honestly visible.
Implementation
final walletAutoShieldSupportedProvider = Provider<bool>((ref) => true);