Exercise client-side iss/sub verification via broken-AS sub-stage
AC4.10 lands: `ClientVerifiedIss` and `ClientVerifiedSub` are now
observable. The `RelyingParty` verifies `iss` on the authorize redirect
(RFC 9207) and `sub` on every token response (atproto's "critical
(mandatory)" check), raising `IssuerMismatch` / `SubMismatch` on
failure. A new `iss_sub_verification` interactive sub-stage drives two
broken-AS flows — `FlowScript::BogusIssOnRedirect` and `WrongSubInToken`
— through the shared happy-path RP (avoiding JTI replay collisions) and
observes whether the RP aborts; `Pass` / `SpecViolation` is emitted
accordingly. Test-surface helpers (`do_authorize_skipping_iss_verification`,
`do_token_skipping_sub_verification`, `do_refresh_skipping_sub_verification`)
let the broken-RP suite model non-conformant clients.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>