3jane: monitor nominal backing floor and IS_PAUSED

[spalen0]

Summary

• Adds check_nominal_backing_floor to 3jane/main.py — alerts on any change to SUSD3_NOMINAL_BACKING_FLOOR, and a separate alert-once when the floor exceeds current sUSD3 totalAssets (a state in which sUSD3 redemptions can be blocked).
• Adds check_protocol_paused — alert-once on IS_PAUSED 0→1 transition. Distinct from the existing per-vault isShutdown() check.
• Extends 3jane/abi/ProtocolConfig.json with the generic config(bytes32) getter, and folds both new reads into the existing main() batch (no extra RPC round-trips).

Why now

A pending TimelockController op (executing in ~1 day) upgrades the sUSD3 proxy 0xf689…64a7 to a new implementation 0x2038a352… that introduces a nominal backing floor and starts using a protocol-wide pause flag in ProtocolConfig. Current on-chain value of the floor is 0 (unused until governance sets it), so this monitor is silent until then.

Behavior verified locally

• First run with floor=0 and IS_PAUSED=false: silent init, cache populated.
• Floor 0 → 5M (no breach): single change alert.
• Floor 5M → 10M crossing $6.9M backing: change alert + breach alert.
• Steady state next tick: silent.
• Backing recovers above floor then drops below again: breach re-alerts (cache resets on clear).
• IS_PAUSED false→true: single alert. Stays true: silent.

End-to-end dry-run against mainnet (telegram mocked) completed cleanly with the expanded 8-call batch.

Test plan

• Confirm telegram credentials TELEGRAM_BOT_TOKEN_3JANE / TELEGRAM_CHAT_ID_3JANE are still wired in the scheduled workflow.
• After the pending timelock op executes, run python 3jane/main.py and confirm the floor read still returns 0 (governance hasn't set it yet) and no spurious alert fires.
• Optional: temporarily fork-test by overriding SUSD3_NOMINAL_BACKING_FLOOR to a non-zero value to confirm both the change and breach alert messages render correctly in Telegram.

🤖 Generated with Claude Code