@jskit-ai/connectors-catalog 0.2.3 → 0.2.5

package/README.md

@@ -9,7 +9,7 @@ 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
+and [application setup contract](../connectors-core/docs/application-setup.md), which
 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
@@ -25,9 +25,9 @@ is not proof that the application's requested feature is implemented.
 
 `integrations.json` is application-owned source; secret values belong in the
 application's Env or private grant storage. The same files can be authored by
-hand, by a coding agent or by an editor. Genesis is optional: when used, selected
-Stack guidance should lead to these same documents, while the application
-records its actual environment requirements and implemented commands.
+hand, by a coding agent or by an editor. Any project guidance the application
+keeps should lead to these same documents, while the application records its
+actual environment requirements and implemented commands.
 
 For full Stripe/Paddle checkout, subscriptions, features and usage credits,
 continue to [application-owned payments](../payments-core/README.md) and its

package/docs/ai.md

@@ -2,7 +2,7 @@
 
 This integration supplies configuration and authorized connection parameters.
 The application's AI library makes requests directly to its chosen provider.
-There is no JSKIT or Vibe64 inference gateway, token resale, conversation engine,
+There is no JSKIT or hosted inference gateway, token resale, conversation engine,
 coding-agent runtime, or automatic paid fallback.
 
 ## Ownership
@@ -17,7 +17,7 @@ coding-agent runtime, or automatic paid fallback.
 | Other frameworks | Read the same configuration or map it into their native configuration; use their own libraries and private credential storage |
 
 JSKIT is a JavaScript library for Node applications. A Laravel application does
-not install JSKIT, Node, OpenCode or Vibe64. Its backend can read the selected
+not install JSKIT, Node or OpenCode. Its backend can read the selected
 model and `env:NAME` reference and use its own environment/configuration and AI
 client. Framework-independent facts in this guide are usable by its coding AI;
 PHP code and a parallel PHP package are not part of JSKIT.
@@ -209,6 +209,6 @@ and selects its ID through `assistantServer.<surface>.aiIntegrationId`. An optio
 `aiIntegrationIds` list permits the shared chat model chooser. Resolve on every
 request so individual accounts and key rotation keep their existing owner.
 The Assistant guide and `assistant/assistant-surface` pattern document setup.
-No Vibe64 coding credentials, paid fallback or runtime package installation is
+No hosted coding credentials, paid fallback or runtime package installation is
 involved. The standalone conversation template includes a separate suggestion
 integration, streaming answers and app-owned uploads and storage.

package/docs/airtable.md

@@ -38,7 +38,7 @@ not prove access to a particular base. See [List bases](https://airtable.com/dev
 Use the [API-key source pattern](../patterns/api-key-connection/PATTERN.md),
 substituting this provider, slot and secret reference. The application owns
 authorization and maps the trusted caller to the connection owner. The library
-supplies validation, HTTP errors and file persistence. A CLI and Vibe64 edit
+supplies validation, HTTP errors and file persistence. A CLI and a hosted editor edit
 the same JSON. The provider supplies the record and schema operations below. Application screens
 and rules deciding which rows a caller may access remain application work.
 

package/docs/algolia.md

@@ -61,7 +61,7 @@ The application ID is public configuration. The two key values stay outside
 source. Omit `publicApiKeyRef` when all searches go through the backend. The
 reference validator accepts the same `env:NAME` format as other connectors.
 The shared UI provides an Application ID text field, optional public-key
-reference and the primary API-key reference. Vibe64 provides a separate Env
+reference and the primary API-key reference. A hosted editor can provide a separate Env
 shortcut for each configured key, including a notice that the frontend key may
 be published. Clearing its reference removes the shortcut, not the Env value.
 Sharing grants remain a separate host responsibility.
@@ -125,7 +125,7 @@ Current CLI documentation exposes `algolia application create`, with name,
 region, plan and dry-run options. For example, review each request first:
 
 ```sh
-algolia application create --name dogandgroom-search --region EU --plan free --dry-run
+algolia application create --name example-search --region EU --plan free --dry-run
 ```
 
 Actual creation requires the chosen plan's terms and, for paid plans, a payment

package/docs/amazon-redshift.md

@@ -94,7 +94,7 @@ For either deployment type:
    to the resulting database identity. Use database permissions to enforce
    read-only access where required; accepting SQL does not make it SELECT-only.
 4. Store the access key ID, secret key and any session token in the application's
-   secret environment. Enter references through Vibe64 or edit the JSON file.
+   secret environment. Enter references through the editor or edit the JSON file.
 5. Save, then explicitly call `connectApiKey`. It lists one metadata page in the
    configured database. An empty table list can still be a successful connection;
    it does not prove permission to read every table or execute every statement.
@@ -195,7 +195,7 @@ statement access in [Data API trusted identity propagation](https://docs.aws.ama
 The remaining configuration must capture the **identity provider issuer URL,
 OAuth client ID and secret reference, AWS region, Identity Center application
 ARN, bootstrap role ARN, and access role ARN**. The provider registration needs
-the application's explicitly configured callback, whether hosted by Vibe64 or
+the application's explicitly configured callback, whether hosted by a managed host or
 operated independently. Start from the project's actual public address and
 register the exact callback implemented by the application. No production
 Redshift federation callback implementation is shipped yet.

package/docs/apollo-io.md

@@ -43,7 +43,7 @@ limits. A scoped key can receive 403 when an endpoint is not allowed.
 
 Use the [API-key composition pattern](../patterns/api-key-connection/PATTERN.md)
 with `providers: [apolloIoProvider]`, environment-reference resolution and the
-file connection store. CLI and Vibe64 edit this same configuration. Runtime
+file connection store. The CLI and a hosted editor edit this same configuration. Runtime
 connection records remain encrypted JSON outside exported source.
 
 ```js
@@ -177,7 +177,7 @@ The HTTP layer makes one request per invocation. After an uncertain create or
 enrichment response, inspect Apollo before retrying; retrying can duplicate a
 record or spend credits again. Handle 403/422 as permission/input failures and
 429 with a bounded app policy. Do not expose the workspace key to browser code.
-The same operations work in a CLI-owned Node app without Vibe64; other frameworks
+The same operations work in a CLI-owned Node app; other frameworks
 use their own HTTP client against the documented endpoints and read the same Env
 reference from project configuration.
 

package/docs/asana.md

@@ -103,9 +103,9 @@ await connections.invoke({ context, integrationId: "work", operation: "tasks.upd
 A lost create response has an uncertain outcome. Inspect the project/task list
 before retrying; the adapter does not replay writes. Display permission failures,
 missing resources, invalid values and rate limits distinctly in the application.
-The same ordinary Node library works in CLI-built applications without Vibe64;
+The same ordinary Node library works in CLI-built applications;
 other frameworks read the configuration/Env reference and use their native HTTP
-client for these endpoints. No Vibe64 server is needed at application runtime.
+client for these endpoints. No hosted server is needed at application runtime.
 
 Sources: [projects](https://developers.asana.com/reference/getprojects),
 [create project](https://developers.asana.com/reference/createproject),

package/docs/ashby.md

@@ -156,7 +156,7 @@ await connections.invoke({ context, integrationId: "hiring",
 
 The generated application owns recruiter authorization, job/candidate visibility,
 consent to changes and UI. The organization API key is not a tenant/user identity.
-The optional Node runtime works without Vibe64 using the same JSON and Env
+The optional Node runtime works without a hosted editor using the same JSON and Env
 reference. Other frameworks can use their own HTTP client for these documented
 endpoints, preserving the same ownership and connection configuration.
 

package/docs/attention.md

@@ -137,8 +137,8 @@ operation runs when saving configuration. Writes are never retried automatically
 a lost response may mean the mutation succeeded. Inspect the provider before
 retrying imports, snippets, users or scorecard results.
 
-The same `integrations.json`, Env reference and API-key composition work from CLI
-without Vibe64. Other frameworks use their native HTTP/client, secret storage and
+The same `integrations.json`, Env reference and API-key composition work from
+the CLI. Other frameworks use their native HTTP/client, secret storage and
 application authorization against these endpoints; they need no Node service.
 
 ## LIMITATIONS

package/docs/aws-athena.md

@@ -71,7 +71,7 @@ For hosted and installed editors there is **no OAuth callback URL** in this
 mode. See [AWS ownership and quota isolation](aws-credentials.md#editors-and-independent-cli).
 Separate workgroups do not isolate account service quotas. The application
 operator supplies AWS credentials, chooses resources and controls their budget.
-The same application-owned setup works from CLI or editor without a Vibe64
+The same application-owned setup works from CLI or editor without a hosted
 managed service.
 
 ## Runtime contract

package/docs/aws-credentials.md

@@ -3,7 +3,7 @@
 S3 and Athena use AWS Signature Version 4, implemented by the official AWS SDK.
 The shared runtime resolves explicit credential references for each operation.
 It never falls back to environment names, AWS profiles, instance metadata or the
-machine operator's account. CLI and Vibe64 use the same configuration and file
+machine operator's account. The CLI and a hosted editor use the same configuration and file
 connection store. This is useful library code; provisioning remains host work.
 
 ## Create or obtain credentials
@@ -39,7 +39,7 @@ an integration does not create an AWS account or confer administrator rights.
 ## Editors and independent CLI
 
 There is **no OAuth registration, redirect URI or universal callback URL** for
-these credential modes. The app's VPS and custom domain do not change the AWS
+these credential modes. The app's server and custom domain do not change the AWS
 account, region or identity. Browser S3 access can require a CORS update when the
 app changes domain; server-side Athena calls do not use browser CORS.
 
@@ -48,7 +48,7 @@ configuration use the same application-owned Env bindings. Hosted and installed
 editors do not supply shared AWS credentials. Two access keys or roles in one
 account do not create separate quota pools.
 
-After saving the configuration, Vibe64 provides a **Set credential in Env**
+After saving the configuration, a hosted editor can provide a **Set credential in Env**
 link for the access key ID, secret access key and any configured session token.
 Each link opens that project's Env screen with the referenced variable name.
 Only references are saved in the integration file. Clearing the optional token

package/docs/aws-s3.md

@@ -130,7 +130,7 @@ or transfer files through issued URLs.
 
 The tested [transfer example](../patterns/aws-storage-queries/example/s3-transfer.js)
 composes the existing connection service with native Fetch. Copy it into an
-application server module or CLI; it needs no Vibe64 process. Supply the same
+application server module or CLI; it needs no hosted process. Supply the same
 authorized context and integration ID used by the service, an exact permitted
 key, and a timeout/cancellation signal. The upload body is a Blob, ArrayBuffer
 or typed array. Downloads return a Response whose body can be streamed to a file

package/docs/bigquery.md

@@ -119,9 +119,9 @@ other frameworks use their supported Google authentication tools. File-sourced
 OIDC tokens require the deployment to update the token file before expiration.
 [Google authentication library federation setup](https://github.com/googleapis/google-auth-library-nodejs#workload-identity-federation).
 
-Vibe64 should edit the application configuration and Env references. It must
+A hosted editor should edit the application configuration and Env references. It must
 not issue deployment identities or require an exported application to call a
-Vibe64 token gateway. The runtime implementation still needs to define and
+hosted token gateway. The runtime implementation still needs to define and
 validate its credential-source input and prove exchange and renewal before this
 mode can be offered as working.
 

package/docs/brevo.md

@@ -32,7 +32,7 @@ provider credentials. See [Get contacts](https://developers.brevo.com/reference/
 
 Use the [API-key source pattern](../patterns/api-key-connection/PATTERN.md).
 The application owns access to contact information and sending
-workflows. A CLI and Vibe64 configure the same slot and reference; connection
+workflows. A CLI and a hosted editor configure the same slot and reference; connection
 metadata lives in the chosen runtime file directory.
 
 ## Provisioning automation and capacity
@@ -97,7 +97,7 @@ Call path IDs are passed as `resource` (number for lists/campaigns; email for
 contacts; bare domain for domains). The same key and configuration are used
 from CLI through the [API-key pattern](../patterns/api-key-connection/PATTERN.md).
 Other frameworks use their native HTTP, Env and app authorization with these
-contracts; Vibe64 and a Node service are not required at runtime.
+contracts; a hosted editor and a Node service are not required at runtime.
 
 For an appointment reminder, confirm sender readiness, authorize the recipient,
 call email.send, save messageId and read email.events later. For a newsletter,

package/docs/calendly.md

@@ -46,7 +46,7 @@ personal-token creation flow is interactive. A public integration instead needs
 a developer account and OAuth application: sign into the developer portal,
 create an OAuth app, and set its name, client type and authorized callback.
 The generated application owns that registration and its callback. Hosted and
-installed editors do not supply shared Vibe64 registrations. These OAuth
+installed editors do not supply shared registrations. These OAuth
 credentials are consumed by the web OAuth mode described below.
 [OAuth app setup](https://developer.calendly.com/docs/authentication/creating-an-oauth-app).
 
@@ -104,7 +104,7 @@ Sources: [OAuth app creation](https://developer.calendly.com/docs/authentication
 
 Both authentication methods use these same operations through `service.invoke`.
 A CLI Node app installs the provider and composes the normal file connection service;
-Vibe64 is not required. Other frameworks use their native HTTP/OAuth library and the
+no hosted editor is required. Other frameworks use their native HTTP/OAuth library and the
 same project configuration, Env references and callback contract.
 
 | Operations | Input / useful result | Scope |
@@ -118,7 +118,7 @@ same project configuration, Env references and callback contract.
 | `events.cancel` | Event UUID, optional reason; cancellation confirmation | scheduled_events:write |
 | `noShows.create`, `noShows.get`, `noShows.delete` | Full invitee URI / no-show UUID; mark/read/undo no-show | scheduled_events:read or write |
 
-Example: DogAndGroom reads its owner profile, lists active event types, then creates
+Example: a grooming business reads its owner profile, lists active event types, then creates
 one link for its grooming event type and sends that URL to the customer. The customer
 selects and confirms the time on Calendly. A created link is not a scheduled event.
 For an app-owned booking form, fetch future availability then submit `invitees.create`;

package/docs/canva.md

@@ -172,7 +172,7 @@ The controlled design workflow fixture exercises candidate creation, transaction
 start/edit/commit, useful returned design content, host denial and a failed commit.
 It proves the transport and host-approval seam with representative provider payloads;
 it does not substitute for Canva's live discovered input schemas or run a design AI.
-CLI Node hosts use the same provider/pattern without Vibe64. Other frameworks use
+CLI Node hosts use the same provider/pattern. Other frameworks use
 a native MCP client with the same metadata identity, callback and private grant state.
 
 **LIMITATIONS:** Assistant tool attachment requires explicit host integration. For example,
@@ -180,7 +180,7 @@ 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
-does not publish a working endpoint. No shared Vibe64 registration, embedded design
+does not publish a working endpoint. No shared hosted registration, embedded design
 editor, Canva Connect REST implementation, app-user login or AI execution is supplied.
 Provider plan/license limits still apply; no live creation, editing or export was tested.
 

package/docs/chargebee.md

@@ -148,7 +148,7 @@ customer/subscription/page/event before deciding whether a new request is approp
 Do not generate a fresh key for a blind retry. Provider errors remain errors; this
 adapter does not expose the response's idempotency-replayed header.
 
-Example flow for DogAndGroom: authenticate the customer in the app, resolve their
+Example flow for a grooming business: authenticate the customer in the app, resolve their
 server-owned Chargebee customer ID, select a configured recurring item price, then
 create hosted checkout with that customer and the app's allowlisted return/cancel URLs.
 Keep the hosted page ID bound to that local customer. Send the returned URL to their
@@ -162,7 +162,7 @@ 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;
 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
+No Node bridge or hosted server is needed. The existing owner authorization callback
 must approve customer, subscription, return destination and financial intent.
 
 **LIMITATIONS:** Assistant tool attachment requires explicit host integration. For example, an app

package/docs/clay.md

@@ -103,7 +103,7 @@ The application owner supplies its authorized Clay key through private Env.
 Two keys alone do not establish separate quota or billing pools; confirm the
 provider's capacity terms. The application must not silently substitute an
 unrelated Clay workspace for the customer's. See the
-[application setup contract](../../connectors-core/docs/online-setup.md).
+[application setup contract](../../connectors-core/docs/application-setup.md).
 
 AI can generate the portable file, environment wiring, query operations and
 tests. The documentation reviewed exposes key creation through the console,
@@ -171,7 +171,7 @@ not treating that response as the full dataset.
 Current query-mode handles search criteria; legacy filters-mode is deprecated
 and is intentionally absent. Native frameworks can use these same fixed Public
 API endpoints with `clay-api-key` from private Env and their own HTTP client;
-JSKIT and Vibe64 are not required for execution.
+JSKIT and a hosted editor are not required for execution.
 
 ## Focused proof and limitations
 

package/docs/clickhouse.md

@@ -219,7 +219,7 @@ The database owner can create separate application users with distinct grants an
 quota profiles. Two usernames alone do not isolate CPU, memory or storage;
 independent capacity requires appropriate budgets or separate compute. Each
 application stores its own credential in private Env and enforces its access and
-network policy. The [application setup contract](../../connectors-core/docs/online-setup.md)
+network policy. The [application setup contract](../../connectors-core/docs/application-setup.md)
 also applies when the application moves hosts.
 
 ## Focused proof and remaining work

package/docs/confidence-flags.md

@@ -61,7 +61,7 @@ HTTP success. If a write times out, inspect the flag/rules before retrying; neit
 local cancellation nor disconnect undoes a remotely applied change.
 
 The host owns its OAuth registration, callback and private Env references. A CLI
-can use the same JSKIT methods without Vibe64, or another framework's native MCP
+can use the same JSKIT methods, or another framework's native MCP
 client with the same endpoint and its own OAuth storage. Production flag evaluation
 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.

package/docs/contentful.md

@@ -88,7 +88,7 @@ and management credentials are intentionally excluded.
 
 ## Provisioning and ownership
 
-The application owner supplies the space and key. No OAuth callback or Vibe64
+The application owner supplies the space and key. No OAuth callback or hosted
 registration is needed; custom application domains do not change this flow.
 An AI can prepare the configuration and framework wiring. Contentful documents
 Delivery key creation through its Content Management API after authorized

package/docs/dbt-semantic-layer.md

@@ -1,7 +1,7 @@
 # dbt Semantic Layer
 
 Import `dbtSemanticLayerProvider` from
-`@jskit-ai/connectors-catalog/server/dbt-semantic-layer`. The library verifies an environment, browses metadata and queries metric values. CLI and Vibe64 use the
+`@jskit-ai/connectors-catalog/server/dbt-semantic-layer`. The library verifies an environment, browses metadata and queries metric values. The CLI and a hosted editor use the
 same file and validators. Saving does not contact dbt or run a warehouse query.
 
 ## Provider setup
@@ -114,7 +114,7 @@ const page = await connections.invoke({
 Other frameworks use their native HTTP client with the same host, exact string
 Environment ID and backend Env token. They send the documented GraphQL requests
 and implement their own result parsing/access policy. No JSKIT dependency or
-Vibe64 service is required for those applications.
+hosted service is required for those applications.
 
 ## Editors and universal URLs
 

package/docs/elevenlabs.md

@@ -29,7 +29,7 @@ This connector discovers voices/models, generates audio and creates Instant Voic
 
 Compose the [API-key source pattern](../patterns/api-key-connection/PATTERN.md)
 with this provider and an application authorizer. Keep resource ownership in
-the application. A CLI edits the same portable JSON as Vibe64; neither requires
+the application. A CLI edits the same portable JSON as a hosted editor; neither requires
 a database to store connection state.
 
 ## Provisioning automation and capacity
@@ -85,7 +85,7 @@ const bytes = Buffer.from(audio.bodyBase64, "base64");
 The generated app owns authorization, voice selection, samples, storage, credit
 limits and playback. Other frameworks use their native HTTP/multipart clients
 with the same backend Env key and documented endpoints; no JSKIT runtime or
-Vibe64 gateway is needed. API-key setup has no OAuth client or callback URL.
+hosted gateway is needed. API-key setup has no OAuth client or callback URL.
 
 **LIMITATIONS:** Audio is buffered up to 16 MiB; it is not low-latency streaming.
 Use native ElevenLabs streaming for live conversation or larger outputs.

package/docs/firebase-cloud-messaging.md

@@ -97,7 +97,7 @@ Switching back to **Server or native only** removes the three web-only settings.
 ```
 
 For web push, use `clientMode: "web"` and add `apiKey`, `appId` and `vapidKey`.
-The same schema validates files edited by hand, AI or Vibe64. It accepts
+The same schema validates files edited by hand, AI or a hosted editor. It accepts
 `shared` and explicitly authorized `assistant` ownership. This service account
 does not represent a separate Google identity for every app user.
 
@@ -159,7 +159,7 @@ to send to arbitrary installations or topics. No login functionality is implied.
 ## Editors, hosting and custom domains
 
 **Universal OAuth callback URL: not applicable.** Service-account authorization
-is a server-to-server exchange, with no browser redirect to register. A VPS
+is a server-to-server exchange, with no browser redirect to register. A server
 address or custom domain does not change the target project or that exchange.
 Browser notification permission, service workers and registrations belong to
 the origin, so register the app on each new custom domain and update its stored
@@ -208,7 +208,7 @@ outside this initial fragment. These are explicit limits, not proven workflows.
 ## Client enrollment and expired recipients
 
 The app owns the registration endpoint and storage. It may use ordinary files or
-its own selected storage; this connector does not add a database to Vibe64. The
+its own selected storage; this connector does not add a database to the editor. The
 backend authenticates the current user, binds each FID/token to that user and
 device, and updates a server timestamp. Do not accept an arbitrary user ID as
 proof of ownership. Support multiple devices and remove the association on

package/docs/firecrawl.md

@@ -99,15 +99,15 @@ This adapter does not sell credits or provision a subscription.
 
 OAuth callback: **not applicable** to these API-key modes. Normal server API
 requests do not use the customer's browser origin. A custom web domain does
-not change the team/key binding; VPS changes must preserve the authorized
-application identity. Follow the [Online setup contract](../../connectors-core/docs/online-setup.md)
+not change the team/key binding; server changes must preserve the authorized
+application identity. Follow the [application setup contract](../../connectors-core/docs/application-setup.md)
 for application-owned readiness and failure states. This fragment does not configure
 crawl/job webhooks; those would require their own verified receiving endpoint.
 
 ## CLI and other frameworks
 
 Use the shared API-key runtime pattern with `firecrawlProvider`, the same
-`integrations.json` and private `FIRECRAWL_API_KEY`; Vibe64 is not required.
+`integrations.json` and private `FIRECRAWL_API_KEY`; no hosted editor is required.
 After the application has connected and authorized the caller:
 
 ```js
@@ -127,7 +127,7 @@ and [Search](https://docs.firecrawl.dev/api-reference/endpoint/search),
 [results](https://docs.firecrawl.dev/api-reference/endpoint/crawl-get),
 [errors](https://docs.firecrawl.dev/api-reference/endpoint/crawl-get-errors) and
 [cancel](https://docs.firecrawl.dev/api-reference/endpoint/crawl-delete) endpoints.
-No JSKIT or Vibe64 execution service is required.
+No JSKIT or hosted execution service is required.
 
 **LIMITATIONS:** no managed Firecrawl account/credits provisioning, browser
 sessions, monitor service or editor coding-assistant attachment. For example,

package/docs/fireflies.md

@@ -75,7 +75,7 @@ shared key. Do not render returned Markdown as untrusted raw HTML.
 
 CLI apps use the same file and private Env with the API-key pattern. Other
 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,
+Fireflies; JSKIT and a hosted editor are optional. The app owns its digest schedules,
 cache, task tracking and CRM writes through their respective APIs.
 
 **LIMITATIONS:** assistant tool attachment requires explicit host integration. Example: a

package/docs/gatewayapi.md

@@ -102,7 +102,7 @@ keep webhook history if the app needs delivery reporting.
 
 CLI apps use identical configuration, Env and these optional Node exports.
 Other frameworks use native HTTP and HMAC-SHA256 verification of raw bytes;
-no Vibe64 service is required. Disconnect does not remove provider webhooks;
+no hosted service is required. Disconnect does not remove provider webhooks;
 deactivate them in GatewayAPI when retiring the application.
 
 **LIMITATIONS:** no automatic webhook registration, number leasing, RCS agent

package/docs/gemini-enterprise.md

@@ -101,7 +101,7 @@ caller-selected source identity, impersonation header or Workforce Identity toke
 
 The application owner creates the provider registration and stores its secret
 in the application's private Env. Every editor and CLI uses this same
-[ownership model](../../connectors-core/docs/online-setup.md): the configuration
+[ownership model](../../connectors-core/docs/application-setup.md): the configuration
 file holds the client ID and Env references; the editor does not own the
 application's grants.
 

package/docs/github-api.md

@@ -66,7 +66,7 @@ GitHub.com. The adapter normalizes comma-separated returned scopes without
 changing authorization-request scope formatting. OAuth API requests retain the
 same GitHub headers as PAT requests. Disconnect is local; revoke authorization
 in GitHub separately. The app's OAuth registration, secret and provider quotas
-are not supplied by Vibe64.
+are not supplied by the editor.
 
 Focused OAuth fixtures cover confidential S256 exchange, cancellation,
 denial, replay, refresh rotation, file restart, PAT coexistence, per-user and

package/docs/gitlab-api.md

@@ -73,7 +73,7 @@ queries, pagination, file persistence, rotation, isolation and provider errors.
    [OAuth connection pattern](../patterns/oauth-connection/PATTERN.md), binds it
    to its authenticated user and completes the original attempt. Its backend
    owns the tokens and refresh lifecycle. Laravel uses its own framework;
-   this JavaScript runtime does not introduce a Vibe64 dependency.
+   this JavaScript runtime does not introduce a hosted-editor dependency.
 6. Verify the profile. After changing the instance, client or callback,
    reconnect. **Disconnect** removes the local connection; revoke the grant
    in GitLab as well when provider-side revocation is intended.

package/docs/gmail.md

@@ -122,7 +122,7 @@ CLI users use the same JSON and private Env with optional JSKIT libraries.
 Other frameworks use their native OAuth and MIME tools with the same settings
 and [Gmail REST methods](https://developers.google.com/workspace/gmail/api/reference/rest).
 An AI can wire those operations using the provider schema and this guide without
-Vibe64 running. There is no shared Vibe64 mailbox or Google registration.
+a hosted editor running. There is no shared hosted mailbox or Google registration.
 
 **LIMITATIONS:** no background/history sync, push watch service, mail-client UI,
 permanent message deletion or mailbox-settings administration. MIME composition

package/docs/gong.md

@@ -187,7 +187,7 @@ HTTP Basic against the selected company host and the official
 [call-data](https://help.gong.io/apidocs/retrieve-detailed-call-data-by-various-filters-v2callsextensive-2),
 [transcript](https://help.gong.io/apidocs/retrieve-transcripts-of-calls-by-date-or-callids-v2callstranscript-2)
 and [interaction-statistics](https://help.gong.io/apidocs/retrieve-interaction-stats-for-applicable-users-by-date-v2statsinteraction)
-APIs. No Vibe64 runtime or AI service is involved.
+APIs. No hosted runtime or AI service is involved.
 
 **LIMITATIONS:** no CRM synchronization, standalone deal timeline, recording
 uploads, media archive, OAuth or editor assistant attachment. Example: an app

package/docs/google-ads.md

@@ -72,7 +72,7 @@ callback. Keep persistent grants and application identity when moving hosts.
 An authorized AI can prepare configuration and enable APIs using Google Cloud's
 normal tooling. OAuth client creation, consent verification and access approval
 require the actual owner's permissions and provider processes. There is no
-universal Vibe64 credential or automatic approval. API quotas follow the Cloud
+universal hosted credential or automatic approval. API quotas follow the Cloud
 project and account limits; a second OAuth client does not imply independent
 capacity. The adwords permission can authorize writes even though this fragment
 only implements reads.
@@ -123,7 +123,7 @@ Its reusable operations discover accounts/website conversion goals and targeting
 validate a saved plan with Google, atomically create a paused Search campaign,
 inspect a current campaign, separately launch/pause it and report last-30-days
 metrics. The application owns the authenticated administrator and connection
-service; CLI apps use this without Vibe64.
+service; CLI apps use this unchanged.
 
 Store plans at `extensions.googleAdsSearch[integrationId]`, outside OAuth settings.
 Use `validateGoogleAdsSearchPlan` from the shared `google-ads-search` export. Read
@@ -194,5 +194,5 @@ application-owned callback configuration and account quota boundaries.
 Different client IDs do not automatically separate developer-token capacity;
 approved pilot projects can have usage caps while organization/account limits
 still apply. The CLI uses exactly this library and file configuration without
-Vibe64. No generated app or live provider operation is required to validate the
+a hosted editor. No generated app or live provider operation is required to validate the
 configuration, run the focused provider tests or read the [OAuth pattern](../patterns/oauth-connection/PATTERN.md).

package/docs/google-analytics.md

@@ -28,7 +28,7 @@ Saving this configuration is not evidence that tracking is installed.
 Google's [ID instructions](https://support.google.com/analytics/answer/9539598?hl=en)
 and [tag installation instructions](https://support.google.com/analytics/answer/15756615?hl=en-GB)
 are the provider references. This flow does not require a Google OAuth client,
-client secret, callback URL, or Vibe64-owned Google registration.
+client secret, callback URL, or editor-owned Google registration.
 
 ## Configuration and ownership contract to implement
 
@@ -190,7 +190,7 @@ A missing slot must not instantiate a tracker.
 
 Other frameworks use their existing tag/Tag Manager support and native consent
 and route hooks with the same public ID. They do not need the JavaScript helper
-or a Node daemon. The app/framework remains the tracking owner; Vibe64 only edits
+or a Node daemon. The app/framework remains the tracking owner; the editor only edits
 configuration and supplies guidance. See Google's
 [manual page views](https://developers.google.com/analytics/devguides/collection/ga4/views)
 and [disable flag](https://developers.google.com/tag-platform/security/guides/privacy).

package/docs/google-docs.md

@@ -68,7 +68,7 @@ review a conflict rather than blindly retrying. The app renders content safely,
 authorizes user/document mappings and reviews destructive edits.
 
 Other frameworks use the same config and private Env references with their
-native Google Docs client or HTTP. No JSKIT requirement or Vibe64 service applies.
+native Google Docs client or HTTP. No JSKIT requirement or hosted service applies.
 
 **Limitations:** no visual editor, Google Picker component, sharing/Drive exports,
 comment/suggestion review UI, autonomous editing agent or editor chat attachment.

package/docs/google-drive.md

@@ -64,7 +64,7 @@ const downloaded = await connections.invoke({ context, integrationId: "drive",
 
 Other frameworks use native Drive clients/HTTP with the same project config and
 private Env. For larger transfers use native resumable upload/streaming, not a
-larger JSON/base64 payload. No Vibe64 gateway receives or stores the content.
+larger JSON/base64 payload. No hosted gateway receives or stores the content.
 
 **Limitations:** no sync/watch service, embedded Picker, large/resumable transfer,
 sharing administration, permanent deletion, revision history or Workspace-format

package/docs/google-maps-platform.md

@@ -170,7 +170,7 @@ const mounted = await mountGoogleMap({
   element: document.querySelector("#map"), maps: google.maps,
   center: { lat: -31.95, lng: 115.86 }, zoom: 12,
   mapId: configuredMapId,
-  markers: [{ position: { lat: -31.95, lng: 115.86 }, title: "DogAndGroom" }],
+  markers: [{ position: { lat: -31.95, lng: 115.86 }, title: "Grooming salon" }],
   path: routeCoordinates.map(([lng, lat]) => ({ lat, lng })),
   signal: componentAbortController.signal
 });
@@ -188,7 +188,7 @@ it also owns place selection, viewport/route updates and readable error/empty UI
 No SDK or API request is made before the app explicitly loads and invokes it.
 
 Other frameworks use their own browser/native Google Maps tools and the same
-config/Env split; they do not need this JavaScript helper or a Vibe64 service.
+config/Env split; they do not need this JavaScript helper or a hosted service.
 Keep Google attribution and data-retention/display requirements intact.
 
 **Limitations:** no embedded map designer, SDK loader, autocomplete/session-token

package/docs/google-search-console.md

@@ -75,7 +75,7 @@ Inspect the entry after an uncertain write before deciding to repeat it.
 
 Other frameworks use the same project config/Env with their native Google client
 or HTTP. The app owns property authorization, report UI, comparisons and indexing
-interpretation; no Vibe64 service receives search data.
+interpretation; no hosted service receives search data.
 
 **Limitations:** no DNS/HTML ownership deployment, Site Verification API, automated
 indexing requests, sitemap generation, crawler or SEO dashboard. No fresh/hourly