@jskit-ai/connectors-catalog 0.1.39 → 0.1.41

package/README.md

@@ -10,8 +10,10 @@ business workflows. There is no automatic provider installation or activation.
 Each application owns its registration, callback, credentials and grants. Read
 the core package's [callback guide](../connectors-core/docs/oauth-callbacks.md)
 and [application setup contract](../connectors-core/docs/online-setup.md), which
-apply to hosted editors, installed editors and CLI use. There is no shared
-Vibe64 provider registration or token gateway.
+apply to hosted editors, installed editors and CLI use. The catalogue supplies no
+shared provider registration or token gateway. An assistant host must explicitly
+expose authorized connector operations as tools; saving a connection alone does
+not attach those tools to a conversation.
 
 ## Finding setup instructions from a CLI or coding agent
 

package/docs/ai.md

@@ -11,8 +11,8 @@ coding-agent runtime, or automatic paid fallback.
 | --- | --- |
 | JSKIT `connectors-catalog` | Static provider/model data, settings schema, free-access classification and Node credential resolver |
 | JSKIT `connectors-web` | Reusable Vue configuration fields, including searchable model selection |
-| Vibe64 | Edit the project's portable `integrations.json`; manage administrator secrets through its existing Env system |
-| Vibe64 Online | Supply the same editor and Env facilities; it supplies no AI credit or shared commercial AI identity |
+| Connection editor host | Edit the project's portable `integrations.json`; manage administrator secrets through its existing Env system |
+| Hosted application | Supply the same editor and Env facilities; it supplies no AI credit or shared commercial AI identity |
 | Generated application | Authenticate and authorize its users, own credentials and individual connection screens, choose its AI SDK, execute requests and handle provider failures |
 | Other frameworks | Read the same configuration or map it into their native configuration; use their own libraries and private credential storage |
 
@@ -34,6 +34,16 @@ The raw-source hashes and source URLs are in the bundled `ai-models.json`;
 [upstream MIT notices](ai-upstream-notices.md) accompany it. Updates require
 deliberate review and a new package release.
 
+The 2 October review adds the exact `deepseek/deepseek-flash` identity for
+DeepSeek V4.1 Flash and removes its two retired direct-provider Flash entries
+from the bundled data. They are absent even when requesting deprecated models.
+Existing configuration using a removed name must explicitly select a current
+model; JSKIT does not translate it. The source hashes identify the original
+extraction, before this reviewed update. The new entry declares paid access without a fixed price because the
+provider has peak and off-peak rates. See the
+[provider update](https://api-docs.deepseek.com/updates/) and
+[model details](https://api-docs.deepseek.com/quick_start/pricing/).
+
 `listAiModels()` hides deprecated entries and sorts free choices first, with
 `opencode/big-pickle` first. `includeDeprecated: true` exposes retained upstream
 history; `providerId`, `access` and `configurableOnly` filter the list.
@@ -91,7 +101,7 @@ This is enough to select the no-setup default:
 
 For an administrator-funded model, select `authentication.method: "api-key"`
 and `authentication.secretRef: "env:APP_AI_API_KEY"`. Store the **value** in the
-existing Env screen or the application's normal private environment. Vibe64's
+existing Env screen or the application's normal private environment. The host's
 existing launch/deployment environment mechanism supplies it to the backend;
 this integration adds no token delivery service. Do not use `VITE_` or another
 browser-exposed environment prefix. The JSON and source control contain only
@@ -186,7 +196,7 @@ account creation or generated-application execution.
 
 A static, attributed September 10 provider/model catalogue, searchable free/paid model configuration and a backend-only authorized credential/SDK-parameter resolver. The default is the snapshot's Zen Big Pickle no-account route; administrator keys resolve through Env, and individual keys through an app-supplied user/provider-scoped reference resolver.
 
-No inference engine, streaming, tools, conversation storage, provider OAuth/login screens, account/key provisioning, live credential verification, usage metering, billing, token resale or Vibe64 AI gateway. No automatic SDK installation, catalogue updates, model replacement or paid fallback. Only the 13 explicitly supported direct-key routes are configurable; other catalogue entries are framework metadata, not implemented cloud/coding-subscription authentication. Model availability, pricing/free classification and endpoint operation are dated source information, not live proof; even no-setup choices can be unavailable or capacity-limited. Detailed provider-specific personal-key entry, verification, encrypted storage, rotation/disconnect and authorization remain application work; the resolver only consumes those bindings. The app/framework owns SDK installation, protocol selection, requests, errors and UI. Generic key-creation guidance and linked provider documentation are supplied; bespoke audited login/key-creation screens for every catalogue provider are not. To extend: deliberately refresh the static snapshot, improve selected provider-specific instructions, and wire any desired app-native key-entry/inference features. This intentionally differs from Lovable managed AI; Vibe64 coding-agent credentials and runtime remain separate.
+No inference engine, streaming, tools, conversation storage, provider OAuth/login screens, account/key provisioning, live credential verification, usage metering, billing, token resale or Vibe64 AI gateway. No automatic SDK installation, catalogue updates, model replacement or paid fallback. Only the 13 explicitly supported direct-key routes are configurable; other catalogue entries are framework metadata, not implemented cloud/coding-subscription authentication. Model availability, pricing/free classification and endpoint operation are dated source information, not live proof; even no-setup choices can be unavailable or capacity-limited. Detailed provider-specific personal-key entry, verification, encrypted storage, rotation/disconnect and authorization remain application work; the resolver only consumes those bindings. The app/framework owns SDK installation, protocol selection, requests, errors and UI. Generic key-creation guidance and linked provider documentation are supplied; bespoke audited login/key-creation screens for every catalogue provider are not. To extend: deliberately refresh the static snapshot, improve selected provider-specific instructions, and wire any desired app-native key-entry/inference features. This intentionally differs from Lovable managed AI; coding-agent credentials and runtimes remain separate from direct-provider API authentication.
 
 10 source and 10 installed-package tests passed on September 13, proving snapshot/default selection, rejected unsupported modes, no-network public parameters, authorized Env and individual references, rotation/deletion, redaction and SDK handoff. Historical September 10 compact/medium/expanded UI evidence is retained; no fresh browser, live inference, provider account, generated-app execution or release was performed.
 

package/docs/amplitude.md

@@ -17,16 +17,16 @@ requires remote HTTP MCP with OAuth; an API key cannot replace this flow.
    Management**, creates/edits the role, and selects **AI Features → Use MCP
    (read)** and, when needed, **Use MCP (write)**. Assign the role to the intended
    user/group/service account and projects.
-4. In Vibe64, leave the new Client ID empty, set the Suggested callback URL and
+4. In the connection editor, leave the new Client ID empty, set the Suggested callback URL and
    choose **Register client and connect**. The workspace owner can register once
-   at the selected regional authority; Vibe64 saves the client ID in configuration
+   at the selected regional authority; the connection editor saves the client ID in configuration
    and its secret, callback and recovery client ID in development Env before
    starting the application’s connection command. Existing Env values are not
    overwritten. If local saving fails, recover the client from Env/provider state
    before trying again. CLI users can use the setup operation below. The reviewed
    documentation establishes dynamic registration, not a manual developer-app
    creation screen; do not search for an invented console form.
-5. Enter the returned **Client ID** in Vibe64. Store its secret and the exact
+5. Enter the returned **Client ID** in the connection editor. Store its secret and the exact
    callback URL through Env, then fill **Client secret reference** and
    **Callback URL reference**. Keep secrets outside `integrations.json`.
 6. Save. Through the runtime's authorization flow, open the returned URL, sign
@@ -80,7 +80,7 @@ for every account or client policy; that acceptance check remains unperformed.
 
 For manual registration, use an HTTP client on your own machine:
 
-In Vibe64, expand **Set up Amplitude → OAuth client registration**. Set the
+In the connection editor, expand **Set up Amplitude → OAuth client registration**. Set the
 region, permissions and **Suggested callback URL** first. **Copy registration
 endpoint** and **Copy registration request** provide the values for this
 project without requiring a Client ID. Copying sends no request. The example
@@ -91,9 +91,9 @@ below is for CLI users or an HTTP client configured by hand.
    `/mcp`, `/authorize` or `/token` endpoint.
 2. Set the request header `Content-Type: application/json`. Set the body to
    raw JSON using the example below. Replace the example name and callback
-   with the owning application's name and exact callback shown in Vibe64.
+   with the owning application's name and exact callback shown in the connection editor.
    The application must implement that route before user consent can finish.
-3. Match `scope` to the permissions selected in Vibe64. The example uses the
+3. Match `scope` to the permissions selected in the connection editor. The example uses the
    default read and refresh permissions; add `mcp:write` only when needed.
 4. Send once. On a successful response, copy `client_id` into **Client ID**.
    Store `client_secret` as `AMPLITUDE_CLIENT_SECRET` through the project's
@@ -202,9 +202,8 @@ signup, live registration/consent, live tool calls and generated apps are exclud
 
 ## LIMITATIONS
 
-Editor coding-assistant tool attachment is deferred. For example, this runtime
+Assistant tool attachment requires explicit host integration. For example, this runtime
 can call an authorized Amplitude analytics tool from an explicitly composed
-application-owned assistant, but configuring it in Vibe64 does not let Codex or
-OpenCode answer “where are customers dropping out of my funnel?” from your live
+application-owned assistant, but saving its configuration alone does not authorize an assistant to answer “where are customers dropping out of my funnel?” from your live
 Amplitude data. Registration and consent do not attach tools to editor chat.
 No live Amplitude registration, consent or generated application was exercised.

package/docs/apify.md

@@ -24,7 +24,7 @@ start runs, create schedules or spend compute credits.
 4. Store the token outside application source as `APIFY_TOKEN`. Set the
    configuration slot's provider to `apify`, mode to `shared` or `assistant`,
    scopes to `[]`, and authentication to `api-key` with reference
-   `env:APIFY_TOKEN`. In Vibe64, enter that value in **API key reference**, save,
+   `env:APIFY_TOKEN`. In the connection editor, enter that value in **API key reference**, save,
    then use **Set credential in Env** to save the token as `APIFY_TOKEN`.
    This mode has no callback/client registration.
 5. Save and choose **Connect account**, or **Verify again** for a connected
@@ -153,9 +153,9 @@ No live Actor or paid account operation was performed.
 
 ## Limitations
 
-Vibe64 coding-assistant attachment is deferred. For example, the generated app
+Assistant tool attachment requires explicit host integration. For example, the generated app
 can start an authorized scraper, show run progress and read the resulting dataset,
-but asking Vibe64's Codex/OpenCode assistant to scrape a site does not grant it
+but asking an assistant to scrape a site does not grant it
 access to this connection. The app composes its own input screen, bounded status
 polling and output presentation. This connector does not create Actors or schedules.
 Records over 8 MiB use the framework's native streaming client. Live token issuance,

package/docs/apollo-io.md

@@ -13,7 +13,7 @@ changes saved contacts, accounts and deals in an Apollo workspace.
    Add the endpoint permissions below only for capabilities the app will use.
 3. Choose **Create API key**, then **Copy**. Store the value under
    `APOLLO_API_KEY` in the backend environment.
-4. Add Apollo.io in Vibe64, give the integration a display name and enter
+4. Add Apollo.io in the connection editor, give the integration a display name and enter
    `env:APOLLO_API_KEY` in **API key reference**. Save the file configuration,
    use **Set credential in Env** to supply the value, then **Connect account**
    (or **Verify again**). **Check connection** only reads current status.
@@ -191,9 +191,8 @@ reference from project configuration.
 
 ## Limitations
 
-Editor coding-assistant attachment is deferred. For example, a generated sales
-app can search, enrich approved leads and save deals, but asking Vibe64's coding
-assistant to find leads does not grant it this connection. The app owns lead and
+Assistant tool attachment requires explicit host integration. For example, a generated sales
+app can search, enrich approved leads and save deals, but asking an assistant to find leads does not grant it this connection. The app owns lead and
 CRM screens, authorization and usage budgets. This adapter does not implement
 partner OAuth, outreach sequences, bulk jobs, deletion, custom-field discovery,
 or phone/waterfall webhooks. Native framework clients can compose those separate

package/docs/asana.md

@@ -14,7 +14,7 @@ and tasks through a personal access token.
    local prefix/length assumption about Asana's token format.
 4. Save provider `asana`, mode `shared` or `assistant`, `scopes: []`, and
    authentication `{ "method": "api-key", "secretRef": "env:ASANA_TOKEN" }`.
-5. In Vibe64 use **Set credential in Env** to save the token, then
+5. In the connection editor use **Set credential in Env** to save the token, then
    **Connect account** or **Verify again**. **Check connection** only reads
    status. CLI applications verify with `connectApiKey`. Manage/deauthorize personal tokens from the
    developer console. Organization policy can limit personal-token access.
@@ -118,9 +118,8 @@ Sources: [projects](https://developers.asana.com/reference/getprojects),
 
 ## Limitations
 
-Editor coding-assistant attachment is deferred. For example, a generated app can
-create a release project, assign a task and mark it complete, but asking Vibe64's
-coding assistant to inspect your Asana backlog does not give it this connection.
+Assistant tool attachment requires explicit host integration. For example, a generated app can
+create a release project, assign a task and mark it complete, but asking an assistant to inspect your Asana backlog does not give it this connection.
 The app owns its work-tracking screens and resource permissions. OAuth user consent,
 attachments, comments, custom fields, task moves and destructive deletion are not
 implemented here. Live Asana access and generated-app execution were not exercised.

package/docs/ashby.md

@@ -16,7 +16,7 @@ cursor/incremental sync, and supports candidate/application hiring workflows.
    confidential jobs/private fields and other extra permissions off unless needed.
    Choose **Save and Continue**. Copy the key before closing the wizard.
 3. Copy the issued key into the backend environment as `ASHBY_API_KEY`.
-   In Vibe64, add Ashby and enter `env:ASHBY_API_KEY` in **API key reference**.
+   In the connection editor, add Ashby and enter `env:ASHBY_API_KEY` in **API key reference**.
    Save, choose **Set credential in Env** to enter the key, then **Connect account**
    or **Verify again**. **Check connection** reads status only. CLI uses the same
    file and `connectApiKey`. To revoke, open the key by name and choose **Disable**;
@@ -180,9 +180,9 @@ Sources: [candidates](https://developers.ashbyhq.com/reference/candidatelist),
 
 ## Limitations
 
-Editor coding-assistant attachment is deferred. For example, a generated hiring
+Assistant tool attachment requires explicit host integration. For example, a generated hiring
 app can display candidates and advance a recruiter-selected application, but
-asking Vibe64's assistant to inspect your candidates does not give it access.
+asking an assistant to inspect your candidates does not give it access.
 The app owns its hiring screens and policies. Public careers forms, scheduling,
 offer management, file upload, messages and custom fields are not supplied here.
 Live hiring changes, real credentials and generated-app execution were not tested.

package/docs/atlassian.md

@@ -5,7 +5,7 @@ Import `atlassianProvider` and `registerAtlassianClient` from
 the assistant owner's account to Rovo MCP v2. It uses `tools.list` and explicit
 `tools.call` through the existing OAuth/file runtime and official MCP SDK.
 
-## Vibe64 setup
+## Connection setup
 
 Open **Integrations → Add Atlassian**. Choose permissions, set the owning
 application's **Suggested callback URL**, and select **Register client and connect**.
@@ -25,7 +25,7 @@ is configured on Deploy; copying configuration alone does not copy secrets.
    HTTP request. The reviewed metadata establishes dynamic registration; these
    instructions do not assume a developer-console form for creating an MCP v2
    client. A Jira REST OAuth client or an old MCP v1 client is not interchangeable.
-3. In Vibe64, open **Integrations → Add Atlassian → Credentials**. Enter the
+3. Add an Atlassian connection and open its credentials settings. Enter the
    returned **Client ID**. Store the returned secret and callback URL through
    Env; enter their names as **Client secret reference** and **Callback URL
    reference**, for example `env:ATLASSIAN_CLIENT_SECRET` and
@@ -81,7 +81,7 @@ never on file save, startup or every Connect action.
 
 For manual registration, use an HTTP client on your own machine:
 
-In Vibe64, expand **Set up Atlassian → OAuth client registration**. Set the
+In the connection editor, expand **Set up Atlassian → OAuth client registration**. Set the
 permissions and **Suggested callback URL** first. **Copy registration endpoint**
 and **Copy registration request** supply this project's values before a Client
 ID exists. Copying sends no request. CLI users can prepare the example below
@@ -92,9 +92,9 @@ with their own framework tools.
    This is the registration endpoint, not the `/v2/mcp` tool endpoint.
 2. Set `Content-Type: application/json` and select a raw JSON body. Replace
    the example name and callback below with the owning application's name and
-   exact callback shown in Vibe64. Implement that route in the application
+   exact callback shown in the connection editor. Implement that route in the application
    before attempting user consent.
-3. Set the space-delimited `scope` to the permissions selected in Vibe64.
+3. Set the space-delimited `scope` to the permissions selected in the connection editor.
    The example below matches the screen's default profile/account, refresh,
    Jira read/search and Confluence read/search permissions. Remove products
    you do not need from both places.
@@ -213,10 +213,10 @@ consent, provider tool use or generated application is included.
 
 ## LIMITATIONS
 
-Vibe64's coding assistants do not yet receive these tools automatically. For
-example, connecting Jira here does not let the editor's Codex/OpenCode chat
-retrieve DOG-42. An application-owned assistant can call the runtime's tools
-with its own authorization policy; this bridge to editor chat is deferred.
+An assistant host must explicitly attach and authorize these tools. For
+example, saving a Jira connection alone does not give chat access to DOG-42.
+An application-owned assistant can call the runtime's tools under its own
+authorization policy.
 
 The runtime preserves Jira issue and Confluence page content supplied by tools,
 but the application owns how it presents, summarizes or acts on that content.

package/docs/attention.md

@@ -12,7 +12,7 @@ explicit conversation, coaching and organization operations.
    and enter a descriptive name.
 3. Copy the key from **API Key Created**; it is shown only once. Put it in the
    backend environment as `ATTENTION_API_KEY`.
-4. Add Attention in Vibe64 and enter `env:ATTENTION_API_KEY` in **API key
+4. Add Attention in the connection editor and enter `env:ATTENTION_API_KEY` in **API key
    reference**. Save, choose **Set credential in Env**, save the value there, then return and
    choose **Connect account** or **Verify again**. **Check connection** only reloads
    status; it does not validate a newly entered key.
@@ -151,9 +151,9 @@ application authorization against these endpoints; they need no Node service.
 
 ## LIMITATIONS
 
-Editor coding-assistant attachment is deferred. For example, an app can display
+Assistant tool attachment requires explicit host integration. For example, an app can display
 a sales-call transcript and save a manager's coaching score, but configuring this
-connector does not let Vibe64's Codex/OpenCode read those calls from editor chat.
+connector does not authorize an assistant to read those calls from chat.
 The app owns its dashboard, permissions, polling and handling of pending/error
 results. This does not supply Attention's recorder, CRM installation, webhooks,
 SCIM, scorecard-template designer or per-user OAuth. Media imports use an accessible

package/docs/aws-athena.md

@@ -52,7 +52,7 @@ ownership is supported; application users still share the configured AWS identit
    workgroup. Grant only the required source data, catalog, result storage and
    encryption access. Permissions depend on the actual query's data sources.
 5. Follow [AWS credential setup](aws-credentials.md), enter the references,
-   region and workgroup in Vibe64 or the JSON file, and save.
+   region and workgroup in the connection editor or the JSON file, and save.
 6. In the editor, use **Set credential in Env** for each saved reference and enter
    its value, then return and choose **Connect account**. CLI callers resolve the
    same references from their private environment and call `connectApiKey`.

package/docs/aws-s3.md

@@ -2,7 +2,7 @@
 
 Import `awsS3Provider` from `@jskit-ai/connectors-catalog/server/aws-s3` and use
 `createConnectionService` or the ordinary JSKIT connector Feature. The shared
-catalogue definition drives Vibe64's form. Runtime state can use encrypted JSON
+catalogue definition drives the connection editor. Runtime state can use encrypted JSON
 files; no database or generated application is required.
 
 ## Portable configuration

package/docs/brevo.md

@@ -15,7 +15,7 @@ marketing campaigns, sender/domain setup and automation events.
 5. In `integrations.json`, choose provider `brevo`, mode `shared` or `assistant`,
    empty `scopes`, and `authentication: { "method": "api-key", "secretRef":
    "env:BREVO_API_KEY" }`. This slot needs no OAuth registration.
-6. In Vibe64 save configuration, choose **Set credential in Env**, save the key,
+6. In the connection editor save configuration, choose **Set credential in Env**, save the key,
    return and choose **Connect account** or **Verify again**. **Check connection**
    reloads status only. CLI apps call `connectApiKey`. Manage/revoke keys through
    the same console; disconnect only removes the local runtime grant.
@@ -109,8 +109,8 @@ No ambiguous send or creation request is automatically retried.
 
 ## LIMITATIONS
 
-Editor coding-assistant attachment is deferred. For example, the app can send a
-booking email and show its bounce status, but Vibe64's Codex/OpenCode cannot inspect
+Assistant tool attachment requires explicit host integration. For example, the app can send a
+booking email and show its bounce status, but an assistant cannot inspect
 Brevo merely because this connector is configured. The app owns message content,
 recipient authorization and scheduling. This does not supply a template/automation
 visual designer, webhook receiver, SMTP service, WhatsApp integration or account

package/docs/calendly.md

@@ -69,7 +69,7 @@ Provider setup, checked against the official guide on 12 September 2026:
 2. Create an OAuth application. Supply its name, select **web**, and choose
    **Sandbox** for development or **Production** for production. Calendly
    recommends separate applications for those environments.
-3. Copy the generated application's exact callback URL from Vibe64 into
+3. Copy the application's exact callback URL into
    **Redirect URI**. Production requires HTTPS. Sandbox permits HTTP localhost;
    a hosted development URL should still use its actual HTTPS address.
 4. Select **users:read** for the profile check and **event_types:read** for
@@ -143,7 +143,7 @@ The application owns who can read whose invitee data, booking confirmation, time
 display, cancellations, persistence and polling. Reschedule using the invitee's returned
 `reschedule_url`; this adapter does not invent a reschedule API.
 
-**LIMITATIONS:** Public Vibe64 coding-assistant attachment is deferred. For example,
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration. For example,
 connecting Calendly does not let the editor's assistant inspect tomorrow's appointments;
 the generated app's backend can use the scheduling operations above. Webhook receivers,
 organization administration and advanced location/routing/customized event-type creation

package/docs/canva.md

@@ -12,15 +12,15 @@ The client identifier is a hosted JSON URL; this client has no secret.
 2. Supply the company/integration details and exact callback URL requested by
    the form. Wait for Canva's eligibility decision and callback allowlisting.
    This is a real provider prerequisite. Publishing metadata or entering a URL
-   in Vibe64 does not grant access, and JSKIT cannot approve an application.
+   in the connection editor does not grant access, and JSKIT cannot approve an application.
 3. Choose a public HTTPS URL that your assistant host controls, including a
    document path, such as `https://assistant.example/oauth/canva.json`.
 4. Generate the client metadata with the library helper below, or fill the metadata
-   URL and suggested callback in Vibe64 and choose **Copy client metadata** in
+   URL and suggested callback in the connection editor and choose **Copy client metadata** in
    the setup section. Serve that JSON
    at exactly the chosen URL with `Content-Type: application/json`, without
    authentication. The document contains public client information only.
-5. In Vibe64 open **Integrations → Add Canva → Credentials**. Enter **Client
+5. Add a Canva connection and open its credentials settings. Enter **Client
    metadata URL** and the **Callback URL reference**, for example
    `env:CANVA_CALLBACK_URL`. Store the actual callback through Env. No Client
    secret input is shown. **Display name** can supply the name used when
@@ -175,8 +175,8 @@ it does not substitute for Canva's live discovered input schemas or run a design
 CLI Node hosts use the same provider/pattern without Vibe64. Other frameworks use
 a native MCP client with the same metadata identity, callback and private grant state.
 
-**LIMITATIONS:** Vibe64's coding-assistant attachment is deferred. For example,
-configuring Canva does not yet let you ask Vibe64's Codex/OpenCode to create or edit
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration. For example,
+configuring Canva alone does not authorize an assistant to create or edit
 your shop's poster. An explicitly wired application-owned assistant can invoke the
 supplied MCP runtime after Canva approves its callback and each owner consents.
 Metadata hosting and provider approval remain owner setup steps; Copy client metadata

package/docs/chargebee.md

@@ -19,7 +19,7 @@ Payment details stay in Chargebee-hosted screens. It does not implement OAuth.
    **Create Key**, then retain the issued key securely. A publishable key or
    a key restricted to product-catalog reads is insufficient for this fragment.
 4. Store the key under `CHARGEBEE_API_KEY` in the backend environment. Enter
-   `env:CHARGEBEE_API_KEY` in Vibe64's API-key reference field and the site name
+   `env:CHARGEBEE_API_KEY` in the connection editor's API-key reference field and the site name
    in **Site name**. Save the configuration, then choose **Set credential in Env**,
    enter the issued key as `CHARGEBEE_API_KEY`, and save it. Return to the
    integration and choose **Connect account** or **Verify again**. **Check connection**
@@ -169,13 +169,13 @@ must decide access policy and reconcile later events. Never trust a browser-supp
 customer ID to issue a portal session: that URL grants billing-account access.
 
 Use the same service.invoke operations in a standalone Node/CLI application;
-Vibe64 only edits the portable configuration. Other frameworks use native Chargebee
+The connection editor only edits the portable configuration. Other frameworks use native Chargebee
 SDK/HTTP with these Env bindings, indexed form fields and app-owned intent state.
 No Node bridge or Vibe64 server is needed. The existing owner authorization callback
 must approve customer, subscription, return destination and financial intent.
 
-**LIMITATIONS:** Editor coding-assistant attachment is deferred. For example, an app
-can launch customer checkout and show invoices, but Vibe64's Codex/OpenCode cannot
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration. For example, an app
+can launch customer checkout and show invoices, but an assistant cannot
 inspect the billing site through this saved connection. This is a connector, not the
 Stripe/Paddle payments product: product authoring, entitlement/credit engines,
 webhook receivers, immediate/prorated changes, refunds, contract-term cancellation,

package/docs/clay.md

@@ -11,7 +11,7 @@ runs enrichment routines, reads results and queries Enterprise tables. It uses a
    [direct API-key settings link](https://app.clay.com/workspaces/~/settings/account?accountTab=api-keys-beta).
 2. Create a Public API key. Copy the newly issued value
    into the backend environment as `CLAY_PUBLIC_API_KEY`.
-3. In Vibe64, open **Integrations → Add Clay**. Enter a display name and
+3. Add a Clay connection. Enter a display name and
    `env:CLAY_PUBLIC_API_KEY` in **Public API key reference**. Choose shared
    application access or assistant access for the intended owner, then save.
 4. The host explicitly calls `connectApiKey`. Its `GET /public/v0/me` check
@@ -55,7 +55,7 @@ API access with Clay before configuring this connector.
 Compose this file with `providers: [clayProvider]`, an authorization policy and
 the encrypted file connection store as in the
 [API-key pattern](../patterns/api-key-connection/PATTERN.md). A CLI uses these
-same library methods. Vibe64 writes the same source file and supplies no separate
+same library methods. The connection editor writes the same source file and supplies no separate
 database requirement.
 
 ```js
@@ -183,8 +183,8 @@ Public API key label, raw-secret rejection, reference persistence, function API
 enablement, Enterprise prerequisite and local-disconnect explanation.
 No live provider calls or generated applications are part of this proof.
 
-**LIMITATIONS:** Automatic Vibe64 coding-assistant attachment is deferred. For
-example, saving Clay here does not let you ask the Vibe64 chat to enrich leads;
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration. For
+example, saving Clay here does not let you ask an assistant to enrich leads;
 the generated app or explicitly wired assistant host can invoke these operations.
 Clay's workflow/function authoring UI, large JSONL batch uploads, webhook
 provisioning/verification and automatic key issuance remain provider/native app

package/docs/clickhouse.md

@@ -232,9 +232,9 @@ The shared form tests cover mode changes, hidden-field removal, locking, CLI
 import and remount at 390, 820 and 1440 pixels. Public-editor cases cover phone
 and desktop file persistence. These checks do not execute SQL on a live server.
 
-**LIMITATIONS:** Automatic Vibe64 coding-assistant attachment remains deferred.
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration.
 For example, the app can show monthly booking totals through `queries.read`, but
-saving this configuration does not enable Vibe64 chat to query that database.
+saving this configuration does not authorize assistant chat to query that database.
 Writes, database provisioning/administration and per-user database identity
 management remain native work; use an administrator outside this connector to
 create a reporting user and its row/resource policies. There is no query-builder

package/docs/confidence-exp.md

@@ -64,8 +64,8 @@ a winning experiment. Do not fabricate a shipping recommendation or recalculate
 provider statistics from a summary. Other frameworks can connect their native
 MCP clients to the same endpoint with their own OAuth/grant storage.
 
-**LIMITATIONS:** Vibe64 coding-assistant attachment is deferred. For example,
-saving this connection does not make Vibe64 chat explain an A/B result; an
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration. For example,
+saving this connection does not authorize an assistant to explain an A/B result; an
 explicitly wired assistant host can retrieve it. Confidence owns statistical
 analysis, metric/event ingestion and experiment execution. This adapter transports
 its tools and results, not a new experimentation engine. Controlled fixtures

package/docs/confidence-flags.md

@@ -66,8 +66,8 @@ client with the same endpoint and its own OAuth storage. Production flag evaluat
 belongs to that framework's Confidence/OpenFeature integration; never place this
 management grant in a browser or treat it as the application's client secret.
 
-**LIMITATIONS:** Automatic Vibe64 coding-assistant attachment is deferred. Saving
-this connection does not let Vibe64 chat switch a feature on; an explicitly wired
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration. Saving
+this connection does not let assistant chat switch a feature on; an explicitly wired
 host can approve and call these management tools. This is not a feature-flag
 execution engine, event pipeline or visual rollout dashboard. The generated app
 must separately implement runtime evaluation if it wants to hide/show features.

package/docs/confidence-oauth.md

@@ -8,8 +8,7 @@ either provider entry point. Both support assistant ownership only.
 
 1. Sign into the intended Confidence account and confirm access to the target
    organisation. The provider's account policy remains authoritative.
-2. Add **Confidence Flags** or **Confidence Exp** in Vibe64. These configure an explicitly wired assistant host; automatic Vibe64 chat
-   attachment is deferred. They do not configure production flag evaluation.
+2. Add **Confidence Flags** or **Confidence Exp** in the connection editor. These configure an explicitly wired assistant host; connecting alone does not attach tools to chat. They do not configure production flag evaluation.
 3. Confirm the suggested callback is the exact route served by that host and
    choose identity/profile/email/refresh permissions. In development, the owner
    can choose **Register client and connect**: the existing project registration action

package/docs/contentful.md

@@ -113,7 +113,7 @@ page limits, private file-store restart, token rotation, isolation, disconnect
 and provider failures. No live Contentful account or generated app was used.
 
 
-**LIMITATIONS:** Vibe64 chat attachment is deferred: the app can display published
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration: the app can display published
 articles and images, but saving this connection does not let the coding assistant
 browse the space. This connector does not author/publish content or render a CMS
 interface. For example, publish the article and hero asset in Contentful first;

package/docs/dbt-semantic-layer.md

@@ -15,7 +15,7 @@ same file and validators. Saving does not contact dbt or run a warehouse query.
    credential**. Supply a warehouse identity allowed to read the source schemas.
 4. Map a new service token to that credential. Name it for this application and
    grant **Semantic Layer Only** and **Metadata Only** permissions. Save.
-5. Copy the one-time token. In Vibe64 enter `env:DBT_SERVICE_TOKEN` in
+5. Copy the one-time token. In the connection editor enter `env:DBT_SERVICE_TOKEN` in
    **Service token reference**, save configuration, and use **Set credential in
    Env** to paste and save the token as `DBT_SERVICE_TOKEN`. CLI users supply the
    same backend environment variable; source stores only its reference.
@@ -91,7 +91,7 @@ Disconnect removes local connection state, not the provider token.
 ## Application and CLI wiring
 
 Compose this provider with the existing connection service, your file-backed
-store, Env resolver and authorization callback. Vibe64 writes the same JSON;
+store, Env resolver and authorization callback. The connection editor writes the same JSON;
 it is not needed at runtime. After explicit token verification:
 
 ```js
@@ -163,8 +163,8 @@ performance cost. This path supports small metric tables; large production
 analytics should use native dbt/Arrow tooling. Arrow decoding, SQL compilation,
 saved-query execution, webhooks and app-user login are not supplied. For example,
 an app can fetch monthly revenue and render its own chart, but this connector
-does not build the chart or a continuous warehouse dashboard. Editor
-Codex/OpenCode attachment remains deferred. Personal access
+does not build the chart or a continuous warehouse dashboard. Assistant tool attachment
+requires explicit host integration. Personal access
 tokens are another documented provider option; the captured service-token setup
 is the supported initial onboarding journey.
 

package/docs/elevenlabs.md

@@ -92,8 +92,8 @@ Use native ElevenLabs streaming for live conversation or larger outputs.
 Professional Voice Cloning, realtime agents, regional residency and provider
 verification workflows are not implemented here. For example, an app can generate
 an appointment announcement with an authorized cloned voice, but configuring this
-connector does not create a phone agent or let Vibe64's coding assistant use it.
-Editor assistant attachment is deferred. A failed or timed-out POST may already
+connector does not create a phone agent or authorize an assistant to use it.
+Assistant tool attachment requires explicit host integration. A failed or timed-out POST may already
 have consumed credits or created a clone; no automatic retry is performed.
 
 Focused fixtures additionally verify playable audio bytes/content type, malformed

package/docs/figma.md

@@ -18,7 +18,7 @@ The registration endpoint's existence does not remove that requirement.
 2. Choose the callback implemented by your backend or CLI host. For your own
    application, this is its actual HTTPS callback, or a loopback callback where
    accepted. The host must retain the pending owner and state through consent.
-3. After approval, use Vibe64's **OAuth client registration** section to copy
+3. After approval, use the connection editor's **OAuth client registration** section to copy
    the endpoint and JSON body into an HTTP client and send one POST with
    Content-Type application/json. Alternatively invoke `registerFigmaClient`
    once from a trusted setup command.
@@ -28,7 +28,7 @@ The registration endpoint's existence does not remove that requirement.
 4. Put the returned client ID in `registrations.figma.clientId`. Store the
    returned secret and callback in your host's existing secret/environment
    facilities; place only references in `clientSecretRef` and `callbackUrlRef`.
-5. In Vibe64, open **Integrations → Add Figma**. Enter **Client ID**,
+5. Add a Figma connection. Enter **Client ID**,
    **Client secret reference** and **Callback URL reference**. Keep **Assistant
    access** and **Use Figma MCP tools**, then save. Use **Set credential in Env** for the returned secret and **Set
    callback in Env** for the exact registered URL. Saving edits the same JSON
@@ -123,9 +123,9 @@ local to the machine running Figma Desktop and the consuming client: on Online,
 Figma Desktop independently; no tunnel/proxy is provided here. Government-only
 desktop deployments are outside this remote connector.
 
-Editor coding-assistant attachment is deferred. For example, an explicitly wired
+Assistant tool attachment requires explicit host integration. For example, an explicitly wired
 assistant host can receive an authorized booking-card layout and screenshot, but
-saving Figma in Vibe64 does not yet let Codex/OpenCode reproduce that frame.
+saving a Figma connection alone does not authorize an assistant to reproduce that frame.
 App-user login, Make resources/prompts and a visual Figma editor are not supplied.
 Other frameworks use a native MCP/OAuth client and the same config/Env contract;
 PHP/other runtime code does not belong in JSKIT. Provider approval remains external;

package/docs/firebase-cloud-messaging.md

@@ -25,7 +25,7 @@ Connecting performs a dry-run check; it does not deliver a notification.
    key > JSON > Create**. Give this identity **Firebase Cloud Messaging API
    Admin** on the target project, or an appropriate custom role. Organization
    policy can prevent key creation. Do not substitute an unrelated credential.
-6. In Vibe64, enter `env:FIREBASE_SERVICE_ACCOUNT` in **Service-account JSON
+6. In the connection editor, enter `env:FIREBASE_SERVICE_ACCOUNT` in **Service-account JSON
    reference**, then **Save configuration**. Follow **Set credential in Env**
    and store the complete JSON under `FIREBASE_SERVICE_ACCOUNT`, not a filename
    or path. Return to the integration and connect. CLI applications supply the

package/docs/fireflies.md

@@ -13,7 +13,7 @@ The provider reads the key owner profile, meeting lists, transcript content and
 3. Save provider `fireflies`, mode `shared` or `assistant`, `scopes: []`, and
    authentication
    `{ "method": "api-key", "secretRef": "env:FIREFLIES_API_KEY" }`.
-4. In Vibe64, enter `env:FIREFLIES_API_KEY` as **API key reference**, click
+4. In the connection editor, enter `env:FIREFLIES_API_KEY` as **API key reference**, click
    **Save configuration**, then **Set credential in Env**. Store the real key
    as `FIREFLIES_API_KEY` and return to connect. CLI applications invoke
    `connectApiKey` to verify the profile. Token replacement belongs in Env.
@@ -79,8 +79,8 @@ frameworks use their native HTTP client to POST the fixed query/variables to
 Fireflies; JSKIT and Vibe64 are optional. The app owns its digest schedules,
 cache, task tracking and CRM writes through their respective APIs.
 
-**LIMITATIONS:** editor assistant attachment remains deferred. Example: a
-published app can show a sales call's action items; the Vibe64 coding assistant
+**LIMITATIONS:** assistant tool attachment requires explicit host integration. Example: a
+published app can show a sales call's action items; an assistant
 does not gain meeting access from this configuration. Recording, transcript
 mutation, incoming webhooks and per-user OAuth are not supplied (the Lovable
 reference also describes these as excluded). Exact signed-in screen placement
@@ -91,5 +91,5 @@ Rechecked 13 September 2026 against [transcript detail](https://docs.fireflies.a
 [authorization](https://docs.fireflies.ai/fundamentals/authorization) and
 [Lovable's current fields/capabilities](https://docs.lovable.dev/integrations/fireflies).
 The latter resolves the empty original form: display name and an API key are
-required inputs for its shared connection. Vibe64 stores a private Env reference
+required inputs for its shared connection. The host stores a private Env reference
 instead of putting the key in the source file. No live meetings were read.