feat(sse): add HyperAgent (hyperagent.com) unofficial web provider

[artickc]

Summary

Adds HyperAgent (hyperagent / alias ha) as an unofficial web-cookie provider reverse-engineered from the live SPA (hyperagent.com).

Protocol (from captures)

Step	Endpoint	Notes
Create thread	GET /threads/new (fallback POST /api/threads)	Extract cuid from redirect /thread/{id}
Chat	POST /api/threads/{id}/chat	SSE data: events
First turn	sessionId: null	session_start returns sessionId
Follow-up	same threadId + sessionId	sticky cache for OpenAI multi-turn
Limits	GET /api/settings/billing/usage	creditData.creditBlocks[].initialUsd/remainingUsd

Models

Hardcoded catalog from SPA pricing map. Pretty names in /v1/models (e.g. Claude Fable 5) while chat sends wire modelId (fable, opus-latest, gpt-5.6-sol, …).

Auth

Browser Cookie header (same pattern as other web-session providers).

Tests

tests/unit/executor-hyperagent.test.ts — 15/15 pass.

Risk

Unofficial/undocumented endpoints; labeled subscriptionRisk + webCookie risk notice.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[diegosouzapw]

Thanks for this — HyperAgent is wired correctly end-to-end (registry, executor, models, usage, web-cookie UI) and the executor's own test suite (16/16) is solid. Before merge, two EXISTING test suites need to be updated since they weren't touched by this PR and now fail:

1. tests/unit/provider-translate-path-golden.test.ts — the golden snapshot needs regenerating to include the new hyperagent/ha registry entries: UPDATE_GOLDEN=1 node --import tsx/esm --test tests/unit/provider-translate-path-golden.test.ts, then commit the updated snapshot file.
2. tests/unit/check-env-doc-sync.test.ts — HYPERAGENT_USAGE_URL and OMNIROUTE_DATA_DIR are read from process.env in the new code but aren't documented per the env/docs contract this test enforces; please add them (or drop OMNIROUTE_DATA_DIR if DATA_DIR alone covers it).

Optionally, worth a look: the sticky thread/session cache in hyperagent.ts does synchronous readFileSync/writeFileSync on every chat request — the sibling PromptQL provider keeps this in-memory only. Not blocking, just flagging for consistency.