Hashnode connector uses retired GraphQL endpoint and invalid auth header

Problem

1MarketingTool v1.1.0 cannot validate or publish through Hashnode. It reports a misleading Pro-plan error even when the saved PAT and publication configuration are present.

Reproduction

1. Configure Hashnode with a valid PAT and publication ID.
2. Run connector validation.
3. Validation fails with the message that Hashnode retired its free GraphQL API and the publication must upgrade to Pro.

The site integration already reads the same publication through the current public API and builds successfully. Headless CMS being disabled does not block this public gql-beta flow.

Root cause in packaged v1.1.0

Both validator and publisher use:

https://gql.hashnode.com/
Authorization: 

The old endpoint redirects with HTTP 301. Validation maps every status >= 300 to the Pro-plan message, hiding the actual endpoint/auth error.

Required fix

Update both validator and publisher:

POST https://gql-beta.hashnode.com/
Authorization: Bearer 
Content-Type: application/json

Recommended read-only validator:

query ValidateHashnode($id: ObjectId!) {
  me { username }
  publication(id: $id) { id title }
}

Please preserve actual HTTP and GraphQL errors instead of mapping redirects or malformed responses to a Pro-plan error. Fix must cover both connector validation and publishPost. No app.asar patch and no test post required.

Environment

• 1MarketingTool v1.1.0
• macOS arm64
• Hashnode current endpoint: gql-beta.hashnode.com

No PAT or vault payload included.