Strategy dependencies captured by the public facade.
Resolved scrape options for the current bank.
Configured provider scraper and credentials, the watches on the token and device state they carry, and whether its login callback stores a durable token.
Builds the provider scraper and credentials for one live attempt.
Both lifecycle callbacks are attached here: the browser capture for every bank, and the token capture for the API-direct banks, whose logins mint a durable token. Pepper also gets its device login, which keeps the state that replaced its long-term token. The retriever is attached for exactly the banks the token capture skips, since the API-direct ones read it from the credentials. The capture and the token resolver share one parameter bundle, so the token an attempt sends is read under the key and login it is stored under; the resolver also reads the tokens that were not accepted before.