@jskit-ai/connectors-catalog 0.1.39 → 0.1.41

package/docs/gatewayapi.md

@@ -17,7 +17,7 @@ Connection verification reads credit/currency without sending. Explicit applicat
    `gatewayapi.com` and `gatewayapi.eu`. The EU platform uses a different host;
    changing hosts requires verification again.
    [Platform routing](https://gatewayapi.com/docs/apis/legacy/rest/).
-4. In Vibe64 enter `env:GATEWAYAPI_TOKEN` as **API key reference**, click
+4. In the connection editor enter `env:GATEWAYAPI_TOKEN` as **API key reference**, click
    **Save configuration**, then **Set credential in Env**. Store the real token
    as `GATEWAYAPI_TOKEN` and return to connect. CLI apps call `connectApiKey`.
    Requests use `Authorization: Token <token>`.

package/docs/gemini-enterprise.md

@@ -80,7 +80,7 @@ Never accept a shared subject or application ID directly from an untrusted calle
    **Create** and securely save the displayed client ID and secret. Enter only
    the ID and secret reference in the integration file. Google documents this
    confidential flow in its [web-server OAuth guide](https://developers.google.com/identity/protocols/oauth2/web-server).
-7. In Vibe64, copy **Suggested callback URL** into the Google redirect URI
+7. In the connection editor, copy **Suggested callback URL** into the Google redirect URI
    registration. **Save configuration**, then use the Env links for the secret
    and callback references. For the example above, set `GEMINI_ENTERPRISE_SECRET`
    and `GEMINI_ENTERPRISE_CALLBACK` in the

package/docs/github-api.md

@@ -52,7 +52,7 @@ headers, paging, restart, rotation, disconnect and owner isolation.
 ## OAuth setup
 
 Open GitHub Settings > Developer settings > OAuth Apps > New OAuth App. Set the
-name and application homepage, and copy Vibe64's Suggested callback URL into
+name and application homepage, and copy the application's Suggested callback URL into
 Authorization callback URL. Register the app, copy Client ID, and generate a
 client secret. Save configuration and follow the Env links for client secret
 and callback references. The application owns the callback route and grants.

package/docs/gmail.md

@@ -126,7 +126,7 @@ Vibe64 running. There is no shared Vibe64 mailbox or Google registration.
 
 **LIMITATIONS:** no background/history sync, push watch service, mail-client UI,
 permanent message deletion or mailbox-settings administration. MIME composition
-and rendering belong to the framework; editor assistant attachment is deferred.
+and rendering belong to the framework; assistant tool attachment requires explicit host integration.
 Example: a booking app can read a customer's message, draft a reply, explicitly
 send it and archive the thread's selected message; installing the connector does
 not build the inbox UI or keep a local mailbox synchronized. Google approval,

package/docs/google-docs.md

@@ -73,7 +73,7 @@ native Google Docs client or HTTP. No JSKIT requirement or Vibe64 service applie
 **Limitations:** no visual editor, Google Picker component, sharing/Drive exports,
 comment/suggestion review UI, autonomous editing agent or editor chat attachment.
 For example, an app can create a booking report and format its text, but saving
-this connector does not let Vibe64's coding assistant edit the report. Fixtures
+this connector does not authorize an assistant to edit the report. Fixtures
 prove request flow, not Google's live document rendering or approval.
 
 References: [create](https://developers.google.com/workspace/docs/api/reference/rest/v1/documents/create),

package/docs/google-drive.md

@@ -70,8 +70,8 @@ larger JSON/base64 payload. No Vibe64 gateway receives or stores the content.
 sharing administration, permanent deletion, revision history or Workspace-format
 conversion on upload. Activity and app-data scopes do not implement those APIs.
 For example, a generated app can upload a booking report and offer a PDF export,
-but it cannot mirror a whole shared drive automatically. Editor assistant access
-is deferred. Controlled fixtures do not prove live Google sharing or file export.
+but it cannot mirror a whole shared drive automatically. Assistant tool access
+requires explicit host integration. Controlled fixtures do not prove live Google sharing or file export.
 
 References: [uploads](https://developers.google.com/workspace/drive/api/guides/manage-uploads),
 [downloads and exports](https://developers.google.com/workspace/drive/api/guides/manage-downloads).

package/docs/google-maps-platform.md

@@ -17,7 +17,7 @@ browser composition helper uses the Google Maps JavaScript SDK loaded by the app
    **Geocoding API**, and configure suitable server IP restrictions. For the
    additional operations, enable **Places API (New)** and **Routes API** in Library
    and allow those APIs on this server key as well. Save.
-4. Store that key as `GOOGLE_MAPS_SERVER_KEY`. In Vibe64, add Google Maps
+4. Store that key as `GOOGLE_MAPS_SERVER_KEY`. In the connection editor, add Google Maps
    Platform and enter `env:GOOGLE_MAPS_SERVER_KEY` in **Server API key reference**.
 5. For browser maps, create a different key, enable only the browser APIs the
    app uses, and apply **Websites** restrictions for the deployed and preview
@@ -200,8 +200,8 @@ Keep Google attribution and data-retention/display requirements intact.
 **Limitations:** no embedded map designer, SDK loader, autocomplete/session-token
 widget, Places photos/reviews, route optimization, transit or navigation product.
 For example, a generated app can find a groomer and display its location and a
-route, but cannot provide live voice navigation. Editor assistant attachment is
-deferred. Controlled HTTP/SDK fixtures do not prove live tiles, routes or billing.
+route, but cannot provide live voice navigation. Assistant tool attachment
+requires explicit host integration. Controlled HTTP/SDK fixtures do not prove live tiles, routes or billing.
 
 Sources: [Places Text Search](https://developers.google.com/maps/documentation/places/web-service/text-search),
 [Routes reference](https://developers.google.com/maps/documentation/routes/reference/rest/v2/TopLevel/computeRoutes),

package/docs/google-search-console.md

@@ -81,8 +81,8 @@ interpretation; no Vibe64 service receives search data.
 indexing requests, sitemap generation, crawler or SEO dashboard. No fresh/hourly
 performance mode or exhaustive traffic export. For example, an app can report
 its popular queries and submit an existing sitemap, but cannot make an unverified
-site appear in Google or guarantee rankings. Editor assistant attachment is
-deferred. Fixtures do not prove live property access or indexing results.
+site appear in Google or guarantee rankings. Assistant tool attachment
+requires explicit host integration. Fixtures do not prove live property access or indexing results.
 
 Sources: [performance queries](https://developers.google.com/webmaster-tools/v1/searchanalytics/query),
 [sitemap submission](https://developers.google.com/webmaster-tools/v1/sitemaps/submit),

package/docs/granola.md

@@ -12,7 +12,7 @@ For a personal key:
 1. Open the Granola desktop app, then **Settings → Connectors → API keys**.
 2. Choose **Create new key**. Select the note access scopes, then **Generate
    API Key**. Store the returned `grn_` value in `GRANOLA_API_KEY` outside source.
-3. In Vibe64 select **Granola** and enter `env:GRANOLA_API_KEY` as the API key
+3. In the connection editor select **Granola** and enter `env:GRANOLA_API_KEY` as the API key
    reference. Choose the intended owner and **Save configuration**. Use
    **Set credential in Env** to save the key as `GRANOLA_API_KEY`, then return
    and choose **Connect account**. CLI users write the JSON below.
@@ -131,7 +131,7 @@ For the MCP assistant connection:
    `offline_access` selected. Free accounts have limited personal-note access;
    workspace settings and subscription determine the available tools.
 2. Confirm the suggested callback is the exact route served by the assistant
-   host. In Vibe64 choose **Register client and connect**: the existing project
+   host. In the connection editor choose **Register client and connect**: the existing project
    registration action stores the client ID in configuration and secret, callback
    and recovery ID in development Env, then invokes the app-owned setup command.
    Existing Env values are not replaced; inspect Env after uncertain registration.
@@ -171,8 +171,8 @@ No live keys, meetings, provider registrations, generated apps or deployments ar
 used. The MCP fixture covers PKCE, verification, restart/refresh, replay rejection and credential-mode isolation. The controlled dual-mode browser journey and rendered setup instructions passed review. No live OAuth client or provider account was used. Webhooks, REST mutations and enterprise-managed authorization are not implemented.
 
 **LIMITATIONS:** The app/assistant host must authorize and attach MCP tools itself.
-Vibe64 coding-assistant attachment is deferred: configuring Granola does not make
-Codex or OpenCode able to answer questions about meetings. For example a generated
+Configuring Granola alone does not authorize an assistant to answer questions
+about meetings. For example a generated
 app can read a processed meeting transcript with the API key, but this editor will
 not automatically use it as chat context. No REST note creation, recording engine,
 webhook receiver or enterprise-managed OAuth is installed.

package/docs/hex.md

@@ -151,10 +151,10 @@ reference persistence. Live registrations, consent, actual Hex tool calls,
 single-tenant hosts, provider billing and real generated applications are not
 part of that proof. The separate Hex REST API/token mode is not implemented.
 
-**LIMITATIONS:** Editor coding-assistant attachment and notebook/Thread widgets
-are deferred. For example an app-owned MCP host can call Hex project or Thread
-tools after its own permission checks, but adding this form does not let Vibe64
-Codex/OpenCode analyze the workspace. The app owns tool discovery/schema use,
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration;
+notebook/Thread widgets are not supplied. For example an app-owned MCP host can
+call Hex project or Thread tools after its own permission checks, but saving the
+configuration alone does not authorize an assistant to analyze the workspace. The app owns tool discovery/schema use,
 status polling, output rendering, sensitive data policy and credit approval.
 Single-tenant custom hosts, REST/token mode and live Hex execution remain outside
 this adapter. Other frameworks use their native MCP client and the same project

package/docs/hubspot.md

@@ -138,5 +138,5 @@ configuration and operation sequence. Keys and tokens stay server-side.
 bulk import/sync, custom association labels, company/ticket API or archive/delete
 operations. Example: a booking app can create a linked deal and advance its stage,
 but it must supply the trigger and cannot import an entire CRM automatically.
-Editor-assistant attachment is deferred. Fixture success does not prove live CRM
+Assistant tool attachment requires explicit host integration. Fixture success does not prove live CRM
 installation, property availability, subscription features or generated-app use.

package/docs/incident-io.md

@@ -114,5 +114,5 @@ provisioning after an authorized bootstrap key; the owner supplies initial acces
 workflow engine, webhook receiver, postmortem importer, custom-field/role editing,
 catalogue schema editing or bulk synchronizer. Example: an app can show the next
 shift and resolve an alert, but cannot generate a rota or start monitoring servers
-just by connecting. Editor-assistant attachment is deferred. Fixture tests do not
+just by connecting. Assistant tool attachment requires explicit host integration. Fixture tests do not
 prove live delivery, role entitlement or provider-side workflow effects.

package/docs/inngest.md

@@ -174,5 +174,5 @@ provider app sync, workflow dashboard, run cancellation or self-hosted endpoint
 mode. Example: an app can submit a report event, but a report only runs after
 its own SDK function is deployed and synced. Schedule execution and SDK business
 functions are native application composition, not tested live or through a
-generated app here. Editor-assistant attachment is deferred. The connector's
+generated app here. Assistant tool attachment requires explicit host integration. The connector's
 metadata check does not prove the Event Key or function availability.

package/docs/klipy.md

@@ -10,7 +10,7 @@ emojis. It does not generate new emojis or implement managed billing.
 2. Enter the platform name, contact email, company website and product
    description; accept the API terms and submit.
 3. Create a named API key. Supply its **App URL** when available.
-4. Store the value as `KLIPY_APP_KEY` in the backend environment. In Vibe64,
+4. Store the value as `KLIPY_APP_KEY` in the backend environment. In the connection editor,
    add KLIPY, enter `env:KLIPY_APP_KEY` in **API key reference**, and choose
    **Save configuration**. Choose **Set credential in Env**, save the real key
    as `KLIPY_APP_KEY`, then return and choose **Connect account**. This reads

package/docs/lexware.md

@@ -14,7 +14,7 @@ its Public API; its bearer key is still a private backend credential.
    read access and invoice creation only for the operations needed. Choose **WEITER**,
    give the key a name, then choose **API-Schlüssel erstellen**.
 3. Copy the key before closing the dialog; it is not displayed again. Store it
-   as `LEXWARE_API_KEY` in the backend environment. Add Lexware in Vibe64 and
+   as `LEXWARE_API_KEY` in the backend environment. Add Lexware in the connection editor and
    enter `env:LEXWARE_API_KEY` in **API key reference**.
 4. Record the expiry for operations: keys may be valid for up to 24 months.
    Use the provider's renewal controls before expiry. Changed permissions
@@ -139,6 +139,6 @@ quotation workflows, gross/tax-free invoice creation, finalization or event
 subscription receiver. Example: a booking can prepare a draft for an existing
 customer, but cannot ingest an expense receipt or deliver an invoice PDF with
 this adapter. Native app code must cover those features separately. Editor
-assistant attachment is deferred. No live financial action or generated app was
+assistant tool attachment requires explicit host integration. No live financial action or generated app was
 executed. Failed/uncertain creation is never automatically repeated: inspect
 vouchers first. Provider validation remains authoritative.

package/docs/lightspeed.md

@@ -51,7 +51,7 @@ configuration contract. Saving the file does not connect a store.
 }
 ```
 
-In Vibe64, add **Lightspeed** in **Integrations**, choose the account mode, and
+Add a Lightspeed connection, choose the account mode, and
 enter **Client ID**, **Client secret reference**, **Callback URL reference** and
 **Domain prefix**. Edit permissions, then **Save configuration**. The client
 authentication method defaults to `client_secret_post`. Use reference values,

package/docs/linear.md

@@ -1,7 +1,7 @@
 # Linear
 
 Import `linearProvider` from `@jskit-ai/connectors-catalog/server/linear`.
-This adapter supports a personal API key or project-owned OAuth, with GraphQL reads and Linear MCP tools. Vibe64 edits the project configuration; the generated application owns its runtime and credentials.
+This adapter supports a personal API key or project-owned OAuth, with GraphQL reads and Linear MCP tools. The connection editor edits the project configuration; the generated application owns its runtime and credentials.
 
 ## Configure access
 
@@ -130,8 +130,7 @@ retry an uncertain create. CLI apps use the same library/configuration/Env; othe
 frameworks compose their native MCP client and authorization with those values.
 
 **LIMITATIONS:** No maintained tool catalogue, project-management UI or automatic
-Vibe64 Codex/OpenCode attachment. Example: an app can explicitly run an approved
-issue update, but saving a Linear connection alone does not teach Vibe64's coding
-chat to update that issue. Provider permissions and available tools determine what
+assistant tool attachment. Example: an app can explicitly run an approved
+issue update, but saving a Linear connection alone does not authorize assistant chat to update that issue. Provider permissions and available tools determine what
 can run. Fixture workflows prove argument/result transport and local denial, not
 actual Linear tool schemas or live execution.

package/docs/linkedin.md

@@ -22,7 +22,7 @@ Only OpenID and profile are required and selected by default. Publishing require
 4. For text publishing, request **Share on LinkedIn** under Products and
    confirm `w_member_social` is provisioned in Auth before selecting it.
    [Share product](https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/share-on-linkedin).
-5. In Vibe64 choose **Add LinkedIn**, enter display name, ownership, Client ID
+5. In the connection editor choose **Add LinkedIn**, enter display name, ownership, Client ID
    and the two Env references. Open **Permissions** for optional email/publishing.
    Choose **Save configuration**, then **Set credential in Env** to store the
    Client Secret. Use **Open Env** to set the same registered callback. Return

package/docs/logo-dev.md

@@ -9,7 +9,7 @@ exports `logoDevDefinition` for configuration and UI metadata.
 
 1. Sign into [Logo.dev API Keys](https://www.logo.dev/dashboard/api-keys).
    Copy the publishable `pk_` key.
-2. In Vibe64, add Logo.dev and enter `env:LOGO_DEV_PUBLISHABLE_KEY` in
+2. In the connection editor, add Logo.dev and enter `env:LOGO_DEV_PUBLISHABLE_KEY` in
    **Publishable key reference**. Choose **Save configuration**, then **Set
    credential in Env**, and store the actual `pk_` value as
    `LOGO_DEV_PUBLISHABLE_KEY`. Return after saving Env. The application resolves

package/docs/mapbox.md

@@ -11,7 +11,7 @@ Browser maps may use a separate public-token reference in the same configuration
    Copy a secret token immediately: Mapbox shows it only once.
    Select only the scopes needed by the intended APIs. Geocoding accepts a
    public token; secret scopes produce a private token that stays on the server.
-3. Store the backend token as `MAPBOX_BACKEND_TOKEN`. In Vibe64, enter
+3. Store the backend token as `MAPBOX_BACKEND_TOKEN`. In the connection editor, enter
    `env:MAPBOX_BACKEND_TOKEN` in **Backend access token reference**.
 4. For browser maps, create a separate public token with the map scopes the
    chosen SDK requires, including `styles:read` and `fonts:read` for styled maps. Add its allowed application URLs and store it as
@@ -143,7 +143,7 @@ expose it as deliberate browser configuration. Do not copy all Env values.
 
 The app installs Mapbox GL JS using its framework package workflow, imports
 `mapbox-gl/dist/mapbox-gl.css`, and supplies a visible container with a height.
-The following goes in its existing mount/unmount lifecycle, not in Vibe64:
+The following goes in its existing mount/unmount lifecycle, not in the connection editor:
 
 ```js
 const map = new mapboxgl.Map({ container: mapElement,

package/docs/microsoft-fabric.md

@@ -246,4 +246,4 @@ service credentials connect without a browser. Per-user mode requires individual
 connections inside the application. Saving alone grants neither API nor source
 access. Both methods use app-owned credentials and persistent grants.
 
-**LIMITATIONS (acceptance review):** No automatic table browser, schema-specific client, subscriptions, automatic pagination or Vibe64 assistant attachment. Example: the app can execute an inventory query using its real schema; this does not provide an inventory dashboard. Both authentication modes and operation/error handling have fixture proof, not live Fabric resource proof.
+**LIMITATIONS (acceptance review):** No automatic table browser, schema-specific client, subscriptions, automatic pagination or automatic assistant tool attachment. Example: the app can execute an inventory query using its real schema; this does not provide an inventory dashboard. Both authentication modes and operation/error handling have fixture proof, not live Fabric resource proof.

package/docs/microsoft-powerpoint.md

@@ -49,7 +49,7 @@ Env variable. Use an account with an existing drive; JSKIT does not provision it
 }
 ```
 
-The same values are editable in Vibe64: display name, account ownership, tenant,
+The same values are editable in the connection editor: display name, account ownership, tenant,
 Client ID, secret/callback references and the two permission choices. Saving the
 file does not open provider consent. The [OAuth composition pattern](../patterns/oauth-connection/PATTERN.md)
 uses the library for consent, private encrypted text storage and runtime access.

package/docs/microsoft-word.md

@@ -49,7 +49,7 @@ Env variable. Use an account with an existing drive; JSKIT does not provision it
 }
 ```
 
-The same values are editable in Vibe64: display name, account ownership, tenant,
+The same values are editable in the connection editor: display name, account ownership, tenant,
 Client ID, secret/callback references and the two permission choices. Saving the
 file does not open provider consent. The [OAuth composition pattern](../patterns/oauth-connection/PATTERN.md)
 uses the library for consent, private encrypted text storage and runtime access.

package/docs/miro.md

@@ -21,7 +21,7 @@ tools and calls explicitly authorized tools. Its fixed HTTP endpoint is
 4. Store the secret in the host's secret/environment facilities. Write the client
    ID, secret reference and callback reference into the portable registration.
    Never put the secret value in the configuration JSON.
-5. In Vibe64, select **Integrations → Add Miro**. Enter **Client ID**, **Client
+5. Add a Miro connection. Enter **Client ID**, **Client
    secret reference** and **Callback URL reference**. Keep **Assistant access**.
    **Read boards** starts selected; enable other permissions only as needed.
    The **OAuth client registration** panel supplies the endpoint and raw JSON
@@ -114,4 +114,4 @@ consent, board read/write or sample application was exercised. Managed
 assignments, automatic assistant attachment and application login remain
 outside this fragment.
 
-**LIMITATIONS (accepted deferral):** Automatic Vibe64 Codex/OpenCode attachment is deferred. Example: a wired CLI/assistant host may discover and authorize a board read or diagram tool, but connecting here does not make the board available in Vibe64 chat. No embedded board editor. Fixture board/diagram names are controlled test inputs, not claims about current remote tool names. Live board access remains unproven.
+**LIMITATIONS:** Assistant tool attachment requires explicit host integration. Example: a wired CLI/assistant host may discover and authorize a board read or diagram tool, but connecting here does not make the board available in assistant chat. No embedded board editor. Fixture board/diagram names are controlled test inputs, not claims about current remote tool names. Live board access remains unproven.

package/docs/n8n.md

@@ -166,4 +166,4 @@ Save configuration, and it neither reads nor writes Env.
 
 ## Accepted limitations
 
-LIMITATIONS: Automatic Vibe64 coding-chat attachment is deferred. A separately wired CLI or assistant host can discover and invoke exposed workflows through MCP after approving the exact tool and arguments; connecting alone does not attach chat tools. This connector is not the n8n REST API or a workflow designer. Example: an approved host can start an exposed report workflow and receive its result, but saving this connection alone does not let Vibe64 chat start that report. Workflow tools and schemas come from discovery, not a fixed catalogue. Fixture execution is not proof of a live workflow run.
+LIMITATIONS: Assistant tool attachment requires explicit host integration. A separately wired CLI or assistant host can discover and invoke exposed workflows through MCP after approving the exact tool and arguments; connecting alone does not attach chat tools. This connector is not the n8n REST API or a workflow designer. Example: an approved host can start an exposed report workflow and receive its result, but saving this connection alone does not let assistant chat start that report. Workflow tools and schemas come from discovery, not a fixed catalogue. Fixture execution is not proof of a live workflow run.

package/docs/posthog.md

@@ -14,7 +14,7 @@ session replay and automatic event batching are not implemented here.
    creation controls shown for your organization.
 2. Open that project's settings from the switcher or sidebar. Copy its numeric
    **Project ID** and public **Project token** beginning with `phc_`.
-3. In Vibe64, add PostHog. Set the display name, select **Region**, and paste the
+3. In the connection editor, add PostHog. Set the display name, select **Region**, and paste the
    ID into **Project ID**. The form defaults to Europe; choose United States
    for a US project.
 4. Store the token under `POSTHOG_PROJECT_TOKEN` in the application environment.
@@ -204,7 +204,7 @@ Nine controlled source tests and nine installed-package tests pass. Existing
 phone/desktop configuration evidence is retained; no new browser run was made
 for this closeout and no runtime/form behavior changed.
 
-Limitations and deferred work:
+Limitations:
 
 - No private analytics querying, dashboards, project provisioning, personal API
   credentials, OAuth, MCP or self-hosted/custom ingestion domains.
@@ -220,8 +220,8 @@ Limitations and deferred work:
 - Flag quota or partial-evaluation failures are errors, with no automatic
   fallback value. The backend supplies no visitor IP forwarding.
 - Disconnect removes local state only; rotate the token in PostHog when needed.
-  Editor coding-agent tool attachment is deferred. No live token, tracking,
+  Assistant tool attachment requires explicit host integration. No live token, tracking,
   ingestion, provider quota behavior or generated application was exercised.
 
-The broader browser lifecycle/analytics backlog stays deferred under the user's
-existing-capability milestone; this closeout does not claim full Lovable parity.
+The application must compose the browser lifecycle and analytics features
+it needs; this connector does not supply a complete analytics product.

package/docs/salesforce.md

@@ -229,6 +229,5 @@ does not establish access to a particular object or field. A missing token expir
 uses a five-minute local renewal policy, not a provider lifetime guarantee.
 Disconnect removes local grants only; provider revocation remains an org/admin
 action. Native framework routes, business UI, app sessions and access policy are
-application-owned. Editor coding-agent attachment, live org/consent/data outcomes
-and generated-app execution remain deferred or unverified. The original broader
-CRM checklist stays backlog; this is not full Lovable parity.
+application-owned. Assistant tool attachment requires explicit host integration. Live
+org/consent/data outcomes and generated-app execution remain unverified.

package/docs/sanity.md

@@ -14,7 +14,7 @@ S256 and the single `global` scope. Keep the resource value exact even though
 MCP transport uses the root URL. Metadata was read without authentication;
 no client or provider account was created during implementation.
 
-In Vibe64 development settings, choose **Register client and connect** after
+In the connection editor, choose **Register client and connect** after
 setting the suggested callback. The existing owner-authorized action saves the
 client ID in configuration, saves secret/callback/recovery ID in Env and starts
 the application's setup command. It refuses occupied Env keys and stale source.
@@ -94,7 +94,7 @@ run JSKIT or call an editor server for content. The generated application can us
 its own Sanity SDK for runtime content; this builder-context connection does not
 automatically become a public site's credential. CLI composition uses the same
 configuration and runtime API without Vibe64. Neither path automatically attaches
-these tools to Vibe64's coding assistant.
+these tools to an assistant.
 
 ## Automation and application ownership
 

package/docs/semrush.md

@@ -3,7 +3,7 @@
 Import `semrushProvider` from `@jskit-ai/connectors-catalog/server/semrush`.
 This adapter manages Projects API V4 records and reads keyword/backlink reports using an application-owned V4 API key.
 It works with the shared CLI/server connection service and encrypted file store;
-Vibe64 edits the same portable configuration. Saving fields does not verify a key.
+The connection editor edits the same portable configuration. Saving fields does not verify a key.
 
 ## Create and configure a key
 
@@ -16,7 +16,7 @@ Vibe64 edits the same portable configuration. Saving fields does not verify a ke
    renaming or deleting projects, and choose an expiry appropriate for the host.
 4. Copy the value when shown. Store it in the runtime's environment or secret
    store; configure only its reference below. The full value is shown once.
-5. Save the JSON through the CLI or Vibe64. Explicitly call `connectApiKey` to
+5. Save the JSON through the CLI or connection editor. Explicitly call `connectApiKey` to
    verify accessible projects. Empty project lists are valid.
 6. For rotation, create a replacement V4 key, update the same binding, verify
    access, then revoke the old key in the provider portal. Changing just the
@@ -198,7 +198,7 @@ unexpected columns, malformed rows and decoded reports over 2 MB are rejected.
 In **My profile > API Keys**, locate the autogenerated **Version 3** key and put
 it in the project's private Env as `SEMRUSH_V3_KEY`. Add
 `settings: { "v3ApiKeyRef": "env:SEMRUSH_V3_KEY" }` to the integration JSON or
-fill **V3 API key reference (optional)** in Vibe64 and use **Set credential in Env**.
+fill **V3 API key reference (optional)** in the connection editor and use **Set credential in Env**.
 The normal authentication reference still points to the separate V4 key.
 Leave the V3 field empty when using only V4 reports and projects.
 
@@ -240,7 +240,7 @@ Results use `{ columns, rows }` with Keyword, Position, Search Volume, CPC,
 Competition, Traffic (%) and Number of Results. Values remain strings, including
 large counts, decimals and escaped keyword text. No-data responses return an
 empty row list. The application owns cost approval, pagination, presentation and
-additional storage. Vibe64 does not execute keyword reports during connection.
+additional storage. The connection editor does not execute keyword reports during connection.
 Other provider columns are not currently exposed by these focused operations.
 
 Sources: [domain keyword reports](https://developer.semrush.com/api/v3/seo/domain-reports/),

package/docs/sentry.md

@@ -5,7 +5,7 @@ Import `sentryProvider` and `registerSentryClient` from
 
 The connector uses Sentry's hosted MCP service for an explicitly composed
 assistant. It does not configure SDK event ingestion, a DSN or application login.
-Vibe64 coding-assistant attachment remains deferred. Saving this configuration
+Assistant tool attachment requires explicit host integration. Saving this configuration
 alone does not give editor chat access to Sentry.
 
 ## Configure access
@@ -14,7 +14,7 @@ alone does not give editor chat access to Sentry.
    open Project Settings and copy the project slug if restricting to one project.
    Use slugs, not display names or numeric IDs. Organization selection is required;
    project selection is recommended.
-2. Make the assistant host serve its own HTTPS OAuth callback. In Vibe64, enter
+2. Make the assistant host serve its own HTTPS OAuth callback. In the connection editor, enter
    it in **Suggested callback URL**, then choose **Register client and connect**.
    From a trusted backend or CLI instead, call `registerSentryClient` with `clientName`, `callbackUrl`
    and `scopes` (start with `org:read`). It registers at

package/docs/sevdesk.md

@@ -2,7 +2,7 @@
 
 Import `sevdeskProvider` from `@jskit-ai/connectors-catalog/server/sevdesk`.
 This fragment verifies an account API token and lists contacts, including people
-by default. Vibe64 labels its credential field **API token reference**.
+by default. The connection editor labels its credential field **API token reference**.
 
 ## Provider setup
 
@@ -12,7 +12,7 @@ by default. Vibe64 labels its credential field **API token reference**.
    enter your password, then copy the revealed token. Some plans also expose
    **Erweiterungen → API**, with the same reveal/password step.
 3. Store the value as `SEVDESK_API_TOKEN` in the backend environment. Add
-   Sevdesk in Vibe64 and enter `env:SEVDESK_API_TOKEN` in **API token reference**.
+   Sevdesk in the connection editor and enter `env:SEVDESK_API_TOKEN` in **API token reference**.
    The portable file contains that reference, never the revealed token.
 
 This retrieves an existing credential; it is not a new OAuth-app registration.

package/docs/shopify.md

@@ -134,8 +134,8 @@ This is a distinct host lifecycle, not a GraphQL product mutation. Shopify place
 installation restrictions on client transfer stores; dev stores cannot be
 transferred. A transfer also moves the store out of the original organization,
 so organization-only client credentials cannot be assumed to remain usable.
-Vibe64's automatic create/claim workflow and any commercial Shopify arrangement
-are not delivered by this fragment. Do not promise Lovable's trial terms.
+Automatic store creation/claim workflows and commercial Shopify arrangements
+remain application responsibilities. Do not promise Lovable's trial terms.
 See [client transfer stores](https://shopify.dev/docs/apps/build/stores/client-transfer-stores).
 
 ## Runtime and assistant authorization

package/docs/slack.md

@@ -61,7 +61,7 @@ and [app credential details](https://docs.slack.dev/authentication/using-token-r
 
 ## Portable configuration
 
-The same `integrations.json` is usable by CLI code and Vibe64's form. Replace
+The same `integrations.json` is usable by CLI code and the connection editor. Replace
 the Client ID placeholder and supply the two referenced environment values.
 No client secret, access token or refresh token belongs in this file.
 
@@ -193,8 +193,8 @@ part of this proof. Current controlled source and installed-package suites each
 Current-source compact and expanded editor cases pass separately, including
 actor/scope persistence, signing-secret reference, inline guidance, per-user
 connection instructions and shared connect/cancel/disconnect controls. Registration
-provisioning remains an operator action; editor coding-assistant attachment is
-deferred.
+provisioning remains an operator action; assistant tool attachment requires
+explicit host integration.
 
 
 ## Message operations

package/docs/telegram.md

@@ -11,7 +11,7 @@ webhooks or authenticate application users.
 2. Send `/newbot`, supply a display name, then choose an available username
    ending in `bot`. Keep the returned token private.
 3. Store the token in your backend environment as `TELEGRAM_BOT_TOKEN`.
-4. Add Telegram in Vibe64. Enter `env:TELEGRAM_BOT_TOKEN` in **Bot token
+4. Add Telegram in the connection editor. Enter `env:TELEGRAM_BOT_TOKEN` in **Bot token
    reference** and save. The CLI uses exactly the same JSON below.
 5. Run the application's connection verification. Saving an editor form alone
    does not contact Telegram or prove that the token works.

package/docs/twilio.md

@@ -263,8 +263,8 @@ the same application-owned credentials.
 There is no OAuth callback in this API-key flow, so editor VM URLs and custom
 application domains do not add OAuth redirect registrations. Twilio Verify and
 SMS login are separate products and are outside this adapter. The application
-owns access policy; connections are project-owned. Editor coding-assistant
-attachment is deferred and not enabled by saving this connector.
+owns access policy; connections are project-owned. Assistant tool attachment
+requires explicit host integration and is not enabled by saving this connector.
 
 ## Proof
 

package/docs/wiz.md

@@ -152,9 +152,9 @@ custom domain does not alter that account or the worker's stable application ID.
 
 Workspace connection availability and granting access to everyone are host-owned
 policies. A project-local JSON slot does not automatically confer workspace-wide
-access. Vibe64's workspace scanner orchestration, automatic scan inclusion,
-findings display/aggregation, stale-result UI and connection removal propagation
-remain unfinished. The initial editor surface edits the configuration only.
+access. Workspace scanner orchestration, automatic scan inclusion, findings
+display/aggregation, stale-result UI and connection removal propagation belong
+to the host. The connection editor edits the configuration only.
 
 ## Automation feasibility and proof
 

package/docs/xero.md

@@ -418,8 +418,8 @@ that surface:
   invoice sharing. Larger files and other record types need native integration.
 - Native application composition: the framework owns routes, UI, authorization,
   business validations and operation calls. Installing the provider or saving the
-  editor form does not generate an accounting application. Editor coding-agent
-  tool attachment remains deferred under the shared milestone decision.
+  editor form does not generate an accounting application. Assistant tool
+  attachment requires explicit host integration.
 - Verification: controlled fixtures establish request/response and local lifecycle
   behavior. Live OAuth, actual Xero organisations, provider tiers, production
   permissions, accounting outcomes and generated-app execution are unverified.

package/docs/zoho-books.md

@@ -16,7 +16,7 @@ Saving configuration does not connect an account.
 3. Open the client's **Client Secret** section. Copy its **Client ID** into
    the registration. Store its secret in `ZOHO_BOOKS_CLIENT_SECRET`, and the
    registered callback URL in `ZOHO_BOOKS_CALLBACK_URL`.
-4. Select the matching **Data center** in Vibe64 or `settings.region` in JSON.
+4. Select the matching **Data center** in the connection editor or `settings.region` in JSON.
    For accounts in other regions, open the client's **Settings**, enable
    **Multi DC**, and enable each required region. Use that region's secret;
    do not assume all enabled regions share one secret.
@@ -209,6 +209,5 @@ Organisation discovery does not prove contact/invoice permissions; an unconfigur
 integration requires an explicit organisation per operation. The host must enforce
 its own organisation/user policy in addition to provider permissions. Callback
 routes, business/end-user connection UI and native framework wiring belong to the
-application. Disconnect is local. Editor coding-agent attachment, live regional
-consent/permissions/accounting outcomes and generated-app execution remain deferred
-or unverified. The original broader accounting packet remains backlog.
+application. Disconnect is local. Assistant tool attachment requires explicit host integration. Live regional
+consent/permissions/accounting outcomes and generated-app execution remain unverified.

package/docs/zoho-crm.md

@@ -187,6 +187,6 @@ No native/self/client-credentials grants, additional regions beyond the configur
 seven, region auto-discovery or provider-side revocation. Current-user verification
 does not prove module/field permissions. The application supplies callbacks,
 organisation/user policy, end-user connection screens and native framework wiring;
-connecting CRM is not app sign-in. Disconnect is local. Editor assistant attachment,
-live regional OAuth/permissions/data and generated-app execution remain deferred
-or unverified. The original broader CRM packet remains backlog.
+connecting CRM is not app sign-in. Disconnect is local. Assistant tool attachment
+requires explicit host integration. Live regional OAuth/permissions/data and
+generated-app execution remain unverified.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/connectors-catalog",
-  "version": "0.1.39",
+  "version": "0.1.41",
   "description": "Provider definitions and focused API operations for JSKIT connectors.",
   "type": "module",
   "exports": {
@@ -123,14 +123,14 @@
     "@aws-sdk/client-redshift-data": "3.1128.0",
     "@aws-sdk/client-s3": "3.1128.0",
     "@aws-sdk/s3-request-presigner": "3.1128.0",
-    "@jskit-ai/connectors-core": "0.1.39",
+    "@jskit-ai/connectors-core": "0.1.41",
     "@modelcontextprotocol/sdk": "1.30.0",
     "@smithy/fetch-http-handler": "5.8.0",
     "json-rest-schema": "^1.0.17",
     "jose": "^6.1.3"
   },
   "peerDependencies": {
-    "@jskit-ai/kernel": "0.1.222"
+    "@jskit-ai/kernel": "0.1.224"
   },
   "jskit": {
     "kind": "runtime",