feat(connectors): add stability-api-platform

[andrei-hasna]

Summary

• Add @hasna/connect-stability-api-platform with Bearer REST client for https://api.stabilityapiplatform.com/v1 (list/create/get items, list events, search, raw request).
• Register stability-api-platform in Developer Tools (distinct from existing stabilityai → api.stability.ai).
• Add mock-fetch unit tests and a credential health-check endpoint (GET /items).

Test plan

• cd connectors/stability-api-platform && bun run typecheck && bun run build && bun test
• bun run typecheck (root)
• bun run build then bun test (1194/1195 pass; 1 pre-existing flaky CLI events/webhooks isolation test)

[andrei-hasna]

Worker review for task cbffa439-ba7d-4501-b2a5-f1eafbe8e830: not merging yet.

Validation performed on a local merge result against current origin/main:

• GitHub CI build on the PR is passing.
• Resolved the current-main registry conflict locally for validation only.
• Passed: git diff --cached --check; staged secret scan; connector bun test (8 pass); connector bun run typecheck; connector bun run build; root bun run typecheck.
• Full root bun test was not a clean signal in this restricted worktree: failures were dominated by missing generated root bin artifacts / HOME-write assumptions, while focused connector checks passed.

Blocker before merge: the connector hardcodes https://api.stabilityapiplatform.com/v1, but api.stabilityapiplatform.com does not resolve from this environment. Evidence: getent hosts api.stabilityapiplatform.com returned no records; curl -I https://api.stabilityapiplatform.com/v1/items failed with "Could not resolve host". Web search for the host/domain also found no public evidence. Please provide proof of the correct public API hostname/endpoints or update the connector to a resolving documented API host.

Also note: the PR branch is stale against current main and needs conflict resolution in src/lib/connectors/developer-tools.ts before GitHub can merge it.

[andrei-hasna]

Blocking merge for now.

Evidence:

• GitHub reports mergeable=CONFLICTING and mergeStateStatus=DIRTY; PR is open and not draft, CI build passed, but there are no latest reviews.
• Local freshness check: git rev-list --left-right --count origin/main...refs/remotes/origin/pr/298 => 309 1. Current fetched origin/main is 724f7fe3; PR head is 23728d4c.
• Current merge diff is destructive: git diff --shortstat origin/main..refs/remotes/origin/pr/298 => 1933 files changed, 522 insertions(+), 180101 deletions(-), including deletion of existing connector packages. This is not safe to merge.
• The single PR commit intent is much narrower (79f3a48..23728d4c => 18 files, 1179 insertions), so this appears to need rebase/regeneration onto current main and conflict resolution.
• API host validity is unproven from this environment: getent hosts api.stabilityapiplatform.com returned no records and curl -I --max-time 10 https://api.stabilityapiplatform.com/v1/items failed with Could not resolve host.

Validation that did pass on the PR head in a temp worktree:

• bun test connectors/stability-api-platform/src/api/client.test.ts => 8 pass, 0 fail.
• bun run typecheck in connectors/stability-api-platform => pass.
• bun run build in connectors/stability-api-platform => pass.
• Focused scan found no browser-use/Playwright/Puppeteer/Selenium dependency, no obvious internal refs, and no committed credential pattern beyond placeholders/test keys.

Required before merge:

1. Rebase/update onto current main and resolve conflicts without deleting existing connectors.
2. Re-run CI on the updated branch.
3. Prove the Stability API host/base URL is correct and resolvable, or document that it is intentionally private and adjust test expectations accordingly.

Note: I attempted to submit this as a request-changes review, but GitHub rejected it because this account cannot request changes on its own PR.