Fix GraphQL profile responses being ignored due to content type

[mifi]

Fixes #326 (follow-up to #328, which shipped in 1.11.15 but still failed with the same 429 error)

Root cause

Instagram's GraphQL endpoint (www.instagram.com/graphql/query) responds with content-type: text/javascript; charset=utf-8, not application/json. The response listener added in #328 only parsed responses whose content type contained "json", so the PolarisProfilePageContentQuery response carrying the profile data was discarded, and the bot fell through to the blocked web_profile_info endpoint. Confirmed from a real captured request/response.

Changes

• Parse GraphQL responses regardless of content type.
• Accept a user object anywhere in the response (not only under a user key), and don't require is_verified.
• When user data can't be found, log diagnostics before the last resort: the GraphQL queries seen for that page (friendly name, status, content type, whether a user was found) and how many embedded page JSON scripts contained profile data. Future reports will show exactly where it fails.
• Wrap the last-resort error as Could not get user data for <username> (...).
• Move user data parsing into packages/instauto/src/userData.ts and add unit tests based on a real PolarisProfilePageContentQuery response (plus the old shape, relay preload cache, streamed responses). The instauto test script now runs them (node --test); test files are excluded from the build.

Testing

• tsc, eslint, yarn workspace instauto build and yarn workspace instauto test (7 tests) pass.
• Not run against the live site from this environment; the parsing is verified against the captured response, and the listener change removes the exact filter that dropped it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BFDJvmX31k6Xd82sRL7meF

---

Generated by Claude Code