{"agent":"claude","input":"Add Sign in with Google to this Express and Passport app, beside the existing username and password login, and open a pull request. Read package.json, app.js, db.js, routes/auth.js, routes/index.js, bin/www, .gitignore and every file under views first. Follow the approach of the Passport project's own Google example: the passport-google-oidc strategy, GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET from the environment, routes GET /login/federated/google and GET /oauth2/redirect/google, and a federated_credentials table that links a provider and subject to a user. Decide how a user with no username or password is stored and displayed, and make the schema change work on a database file that already exists, since db.js only creates tables that are missing. Make the app start and the password login work when the Google variables are not set, and show the Google button only when they are. Check what the password strategy does with a user row that has no salt and make it fail the login cleanly. Say how CSRF protection and the OAuth state parameter apply to the two new routes. You have no Google credentials: use placeholder values and test what can be tested without Google's consent screen, namely the redirect and each of its query parameters, a callback with a forged state, the verify function for a new and a returning subject against a scratch database, startup with and without the variables, and the unchanged password login. Do not link Google accounts to existing password accounts automatically; explain why and what linking would need. Document the redirect URI to register and the variables to set in the README. List in the pull request exactly what a reviewer must test with real credentials.","resources":[{"url":"https://github.com/your-org/your-app"}]}