8ad7ae06e7
The 400-recovery reload installs a disk pair and only then re-runs issuer binding on it. When that pair was minted by a different issuer the enforcer strips its refresh token, and the reload must report "no recovery" so the session is cleared like any other dead grant. No test pinned that verdict: a reload that ignored the install result would keep a stripped pair in the context and return True. The new invariant drives a real 400 through _handle_refresh_response against a foreign-bound disk pair and asserts the result is False, the context is cleared, and the foreign refresh token does not survive on disk. _hermes_live_ttl read expires_in off current_tokens without checking for None; getattr(None, ...) happened to yield the default and report "live". Both current callers install a pair first, but the helper is now explicit that an empty context is never live, so a future call site cannot adopt nothing.