scotttongandClaude Opus 5 e0fce1623d feat(connections): name the four setup states once and derive the card verb ...

Step 3 of the connector simplification. The gallery card and the connect
screen were each deciding "what kind of connector is this" from raw method
flags, which is how a card comes to offer Connect for something that then
demands a pasted key.

`connectionSetupStateForMethod` resolves one of instant/authorize/paste/
register, and the card's verb is a function of it. Both follow the instance's
ownership availability rather than catalog order, so GitHub reads Add key
until an operator configures the cloud connector and Connect afterwards.

Two catalog realities the plan had wrong are now pinned by tests: a
provider-generated URL (Zapier, Arcade, Executor) is not instant because the
operator brings the endpoint, and a templated URL (Shopify) is not either.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-30 10:57:42 -07:00

..

scripts

feat: create company skills from runner tasks (#13538)

2026-09-16 13:01:58 -05:00

src

feat(connections): name the four setup states once and derive the card verb

2026-09-30 10:57:42 -07:00

CHANGELOG.md

chore: release v0.3.1

2026-03-12 13:09:22 -05:00

package.json

feat(ui): integrate agent personas across the app (#13171)

2026-09-19 07:57:53 -05:00

tsconfig.json

Fix root TypeScript solution config

2026-03-09 14:09:30 -05:00

vitest.config.ts

Add first-class issue references (#4214)

2026-04-21 10:02:52 -05:00