fix: lazysecrets expiring says each problem once, and exits like grep

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/azure.md

@@ -72,8 +72,7 @@ with the lists. It says how many vaults it covers; `ctrl+a` in search
 loads the rest.
 
 For a pipeline or a cron job, `lazysecrets expiring` lists them in every
-vault of every account, loading each vault's lists (a few at a time), and
-exits 1 when it lists anything:
+vault of every account, loading each vault's lists (a few at a time):
 
 ```sh
 $ lazysecrets expiring --days 30
@@ -82,8 +81,10 @@ expired  2026-03-01  certificate  kv-app-prod  old-tls  lazysecrets://azure/kv-a
 12d      2026-10-23  secret       kv-app-prod  api-key  lazysecrets://azure/kv-app-prod.vault.azure.net/secrets/api-key
 ```
 
-`--days` defaults to `expiryWarningDays`. Lists it can't read are named on
-stderr.
+`--days` defaults to `expiryWarningDays`. Accounts that need a sign-in and
+lists it can't read are named on stderr, one line each. Like grep, it
+exits 0 when nothing expires, 1 when it lists something, and 2 when it
+couldn't check everything.
 
 On a vault, the right pane shows its settings: resource group, location,
 SKU, whether access is by Azure roles or access policies, soft delete and