@jskit-ai/connectors-catalog 0.2.3 → 0.2.4

package/docs/google-sheets.md

@@ -74,7 +74,7 @@ No automatic retry follows a timeout/503: inspect the spreadsheet before repeati
 an append/create, or duplicate rows/files may result.
 
 Other frameworks use their native Google client or HTTP implementation with the
-same project-owned JSON/Env configuration; JSKIT is optional and requires no Vibe64
+same project-owned JSON/Env configuration; JSKIT is optional and requires no hosted
 runtime. No PHP code or editor-specific credential service is involved.
 
 ## Provisioning and limitations

package/docs/google-slides.md

@@ -20,7 +20,7 @@ file storage. No live Google presentation, consent or generated app was exercise
    Testing refresh-token expiry and domain changes.
 5. Enter the client ID and Env references, then Save configuration. **Set credential
    in Env** stores the secret; **Set callback in Env** stores the exact registered
-   URL. CLI users set the same references/file without Vibe64.
+   URL. CLI users set the same references/file by hand.
 6. Leave **Presentation ID (optional)** blank to verify accessible Drive metadata.
    Empty metadata is accepted without creating a deck; it does not verify that
    Slides API is enabled. For an existing deck, copy the ID between `/presentation/d/`
@@ -82,7 +82,7 @@ sharing, export and trash belong to the separately authorized Drive API.
 
 Authorized AI can enable APIs using gcloud/Service Usage and prepare configuration;
 client creation, branding, audience, approval and consent follow the console steps.
-No Vibe64-owned Google registration or gateway is required.
+No editor-owned Google registration or gateway is required.
 
 **LIMITATIONS:** No visual slide designer, template library, embedded Picker,
 whole-file sharing/export UI or editor-assistant attachment. For example an app can

package/docs/granola.md

@@ -153,7 +153,7 @@ For the MCP assistant connection:
 [Granola MCP](https://docs.granola.ai/help-center/sharing/integrations/mcp) and
 [live OAuth metadata](https://mcp-auth.granola.ai/.well-known/oauth-authorization-server)
 were reviewed on 2026-09-12. Registration, callbacks, tokens and runtime belong
-to the initiating application/assistant host. There is no Vibe64 gateway.
+to the initiating application/assistant host. There is no hosted gateway.
 Granola advertises DCR for compatible clients. The explicit Register client and
 connect action uses its existing helper; plain Connect does not silently create
 registrations. Enterprise-managed authorization is not implemented here.
@@ -162,7 +162,7 @@ AI can write and validate the file, compose the existing library, prepare host
 routes and automate the documented read operations after authorised credential
 setup. The reviewed API documentation does not establish an endpoint for creating
 personal/workspace API keys. Key creation, permissions, account sign-in and required
-provider subscription are operator/provider steps. Vibe64 need not gate its own
+provider subscription are operator/provider steps. The editor need not gate its own
 form, but cannot remove Granola's subscription or permission requirements.
 
 Focused proof uses controlled HTTP responses and temporary encrypted files,

package/docs/hex.md

@@ -9,7 +9,7 @@ It reuses the OAuth state, refresh and encrypted file-store implementations.
 
 1. Check the intended Hex workspace endpoint and account. Hex documents MCP on
    Team and Enterprise plans with an Explorer or higher role.
-2. Choose Standard, Europe or HIPAA in the Vibe64 **Hex workspace endpoint**
+2. Choose Standard, Europe or HIPAA in the editor's **Hex workspace endpoint**
    field. Single-tenant custom Hex domains are not supported by this fragment.
 3. Confirm **Suggested callback URL** is the route your host will serve. Choose
    **Register client and connect** to register at the selected fixed authority.
@@ -137,7 +137,7 @@ runtime records bound to that owner. Update registration and callback Env when
 the actual callback changes. Separate clients do not establish separate Hex
 workspace credits or capacity. Provider accounts, plans and workspace permissions
 still apply. Selecting the HIPAA endpoint is a routing choice, not a compliance
-certification for JSKIT, Vibe64 or a generated application. The explicit registration and controlled connection UI have been reviewed.
+certification for JSKIT, its editor or a generated application. The explicit registration and controlled connection UI have been reviewed.
 The explicit Register client and connect action supports DCR; ordinary Connect
 does not silently create another registration.
 

package/docs/heygen.md

@@ -88,7 +88,7 @@ To configure the OAuth assistant connection:
    and does not promise provider-wide revocation.
 
 The application/assistant host owns its registration, callback, Env and grants.
-There is no Vibe64 gateway. Ordinary Connect never silently registers a client;
+There is no hosted gateway. Ordinary Connect never silently registers a client;
 the explicit Register client and connect action uses the existing helper. Metadata
 advertises a revocation endpoint, but this adapter's Disconnect remains local;
 no provider-wide revocation claim is made. Both credential instruction screens were rendered and reviewed with controlled
@@ -118,7 +118,7 @@ user consent, content rights and credit limits. Fixtures prove transport and
 host policy, not actual media generation or current plan entitlement.
 
 CLI Node applications use the same exported provider and registration helper,
-JSON and Env without Vibe64. Other frameworks use their native MCP/OAuth client
+JSON and Env. Other frameworks use their native MCP/OAuth client
 with those same project-owned configuration values; no JSKIT runtime or Node
 sidecar is required. Select tools from discovery rather than hard-coding this
 module's example catalogue as permanent provider API contracts.

package/docs/inngest.md

@@ -63,7 +63,7 @@ the file. Changing either reference or the branch requires verification again.
 
 Compose the provider with the [API-key file-runtime pattern](../patterns/api-key-connection/PATTERN.md).
 The existing connection owner handles authorization, environment resolution,
-file persistence and disconnect. No database or Vibe64 server is required by
+file persistence and disconnect. No database or hosted server is required by
 the CLI. The [event-delivery pattern](../patterns/event-delivery/PATTERN.md)
 adds application-owned event authorization and explains the workflow boundary.
 

package/docs/klipy.md

@@ -49,7 +49,7 @@ adapter makes no unlimited-capacity promise.
 Compose the [API-key pattern](../patterns/api-key-connection/PATTERN.md) with
 `providers: [klipyProvider]`, application authorization and private file storage.
 The same configuration and runtime calls work from a manually wired CLI. The
-provider module adds no database or Vibe64 service dependency.
+provider module adds no database or hosted service dependency.
 
 ```js
 await connections.connectApiKey({ context, integrationId: "media" });

package/docs/lightspeed.md

@@ -119,7 +119,7 @@ do not repeatedly retry the spent refresh token.
 
 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.
 
@@ -185,7 +185,7 @@ reconciliation during concurrent stock changes.
 
 A CLI app uses these same connection operations. Other frameworks implement
 native HTTP calls with their own project-owned OAuth grant and the same JSON/Env
-contract; no Vibe64 runtime or JSKIT sidecar is required.
+contract; no hosted runtime or JSKIT sidecar is required.
 
 **LIMITATIONS:** No POS/dashboard UI, customer/product/stock/payment/sale writes,
 gift-card/store-credit workflows, webhook receiver or automatic editor tool

package/docs/linear.md

@@ -147,7 +147,7 @@ implement application login. This flow acts as the consenting Linear user.
 
 The same grant supports `tools.list` and `tools.call` against Linear's fixed MCP
 endpoint. Authorize each tool and its arguments before invocation; tools can
-write if the provider permissions allow it. No second MCP registration or Vibe64
+write if the provider permissions allow it. No second MCP registration or hosted
 gateway is needed. For personal keys use the [API-key pattern](../patterns/api-key-connection/PATTERN.md), keep the `read`
 configuration scope and restrict the actual key in Linear. Disconnect deletes
 the local grant; provider revocation remains a separate account action.

package/docs/linkedin.md

@@ -76,7 +76,7 @@ const protection = createCredentialProtection({
 const connections = createConnectionService({
   configuration, providers,
   store: createFileConnectionStore({ directory: process.env.CONNECTOR_STATE_DIRECTORY, protection }),
-  resolveReference: createEnvironmentReferenceResolver(), authorize: applicationConnectionPolicy
+  resolveReference: createEnvironmentReferenceResolver(process.env), authorize: applicationConnectionPolicy
 });
 ```
 
@@ -139,7 +139,7 @@ steps. Do not promise unattended provisioning from a client ID alone.
 
 Each application owns its provider registration, callback route, credentials
 and grants. Hosted and installed editors configure the same app-owned setup;
-neither supplies a shared Vibe64 registration or token gateway. Use the app's
+neither supplies a shared registration or token gateway. Use the app's
 assigned public URL as the initial callback origin, append the route the backend
 actually implements, and register the exact URL with the provider. Keep the
 client secret and callback binding in the application's Env.

package/docs/mailgun.md

@@ -3,7 +3,7 @@
 Import `mailgunProvider` from `@jskit-ai/connectors-catalog/server/mailgun`.
 The adapter verifies an account API key, sends transactional messages, creates
 and verifies sending domains, returns their DNS records, and queries delivery logs.
-DNS records are installed at the domain owner’s DNS host, not at Vibe64.
+DNS records are installed at the domain owner’s DNS host, not in the editor.
 
 ## Configure access
 

package/docs/microsoft-excel.md

@@ -74,8 +74,8 @@ Use `ranges.update` with the same inputs plus exactly one of
 Matrices must exactly match the address, with at most 10,000 cells. Null leaves
 the corresponding cell unchanged. Files.ReadWrite is required even for reading.
 The application owns workbook/worksheet selection, cell-edit authorization and
-presentation; Vibe64 only configures credentials. CLI applications use the same
-connection service without Vibe64; another framework calls Graph itself.
+presentation; the editor only configures credentials. CLI applications use the same
+connection service; another framework calls Graph itself.
 
 For a work/school account, call `sessions.create` with
 `{ itemId, persistChanges: true }` and pass returned `id` as `sessionId` to range

package/docs/microsoft-fabric.md

@@ -200,7 +200,7 @@ the runtime does not perform them automatically or request admin rights.
 
 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/microsoft-outlook.md

@@ -75,7 +75,7 @@ content; no automatic send retry after uncertainty.
 or Calendars.ReadWrite. `events.create({calendarId,subject,start,end})` requires
 Calendars.ReadWrite; start/end are UTC ISO strings ending in Z, with end after start.
 It creates an appointment with no attendees/invitations. The app owns time-zone
-presentation and event selection, not Vibe64.
+presentation and event selection, not the editor.
 
 CLI uses the same connections.invoke operations; other frameworks call these
 Graph endpoints with their own HTTP client and project-owned Env/grant store.

package/docs/microsoft-powerpoint.md

@@ -99,7 +99,7 @@ delegated permissions, secret Value and expiry steps. Save
 `env:MICROSOFT_POWERPOINT_CALLBACK_URL`; use **Set credential in Env** and
 **Open Env** to store the values. Shared/assistant **Connect account** invokes
 the prepared application runtime. Per-user connections belong to individual
-users inside that application. No Vibe64 gateway or shared registration is used.
+users inside that application. No hosted gateway or shared registration is used.
 
 ## Scope and limitations
 

package/docs/microsoft-teams.md

@@ -43,7 +43,7 @@ and rotation. Save `env:MICROSOFT_TEAMS_CLIENT_SECRET` and
 `env:MICROSOFT_TEAMS_CALLBACK_URL`, then use **Set credential in Env** and
 **Open Env** for their values. Shared/assistant **Connect account** uses the
 prepared project runtime. Per-user connections belong to authenticated users
-of that app. No Vibe64 gateway or editor-owned provider registration is used.
+of that app. No hosted gateway or editor-owned provider registration is used.
 Local disconnect does not revoke provider consent.
 
 ## Conversations in CLI and generated apps

package/docs/microsoft-word.md

@@ -99,7 +99,7 @@ delegated permissions, secret Value and expiry steps. Save
 use **Set credential in Env** and **Open Env** to store the values.
 Shared/assistant **Connect account** invokes the prepared application runtime.
 Per-user connections belong to individual users inside that application.
-No Vibe64 gateway or shared registration is used.
+No hosted gateway or shared registration is used.
 
 ## Scope and limitations
 

package/docs/notion.md

@@ -70,7 +70,7 @@ intended shared/per-user account mode. The app owns its callback route and uses
 `beginAuthorization`, `completeAuthorization`, `invoke` and `disconnect` from
 the common connection service with its authorized owner and configured storage.
 Laravel implements the same provider protocol in its own framework; JSKIT
-contains no PHP runtime. Vibe64 edits this configuration and the project's Env.
+contains no PHP runtime. The editor edits this configuration and the project's Env.
 
 The adapter sends owner=user and the exact callback at authorization. It uses
 confidential Basic authentication and JSON requests at the token endpoint, per

package/docs/oura.md

@@ -81,7 +81,7 @@ const protection = createCredentialProtection({
 const connections = createConnectionService({
   configuration, providers,
   store: createFileConnectionStore({ directory: process.env.CONNECTOR_STATE_DIRECTORY, protection }),
-  resolveReference: createEnvironmentReferenceResolver(),
+  resolveReference: createEnvironmentReferenceResolver(process.env),
   authorize: applicationConnectionPolicy
 });
 ```
@@ -125,7 +125,7 @@ creates and authorizes the registration; approval remains a provider process.
 
 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.
 
@@ -153,7 +153,7 @@ A user may decline heart-rate permission without preventing daily sleep access.
 
 The same service.invoke/configuration/Env/store contract works from a CLI app.
 Other frameworks use their native OAuth client and these Oura V2 endpoints,
-with per-user grants; Vibe64 holds no health-data gateway. The app owns charts,
+with per-user grants; no hosted health-data gateway is involved. The app owns charts,
 refresh scheduling, user access policy and private storage.
 
 **LIMITATIONS:** No continuous sync/webhooks, health dashboard, workouts, tags,

package/docs/paddle.md

@@ -152,7 +152,7 @@ approval can be read explicitly; full go-live readiness and arbitrary read/write
 actions remain outstanding and must not be advertised as executable merely because
 permission controls exist. No unrestricted API URL or write proxy is exposed.
 JSKIT owns the JavaScript configuration/runtime contract; Laravel applications
-use their own Paddle SDK and authorization implementation. Vibe64 edits the
+use their own Paddle SDK and authorization implementation. The editor edits the
 project configuration and does not become the merchant account owner.
 
 ## Full application payments
@@ -161,8 +161,8 @@ This connector's operations are only part of a billing implementation. For
 checkout, subscriptions, feature access, renewal credits and durable catalogue
 mappings, read [payments-core](../../payments-core/README.md) and its
 [standalone composition guide](../../payments-core/docs/standalone.md). These
-JavaScript libraries work from ordinary app code or a CLI without Vibe64 or
-Genesis. Other frameworks consume the [portable contract](../../payments-core/docs/contract.md)
+JavaScript libraries work from ordinary app code or a CLI without a hosted
+editor. Other frameworks consume the [portable contract](../../payments-core/docs/contract.md)
 and its static examples using their own runtime libraries. Keep provider setup
 from this guide; do not substitute a successful connection check for working
 checkout, verified webhooks or merchant approval.

package/docs/pipedrive.md

@@ -77,7 +77,7 @@ unattended app registration was established in this pass.
 The application owner supplies its authorized user token through private Env.
 Separate configuration names still reference the same user/company capacity.
 The project owns its registration, callback handler, Env secrets and private
-grants. Vibe64 configures these values; it does not operate a central gateway.
+grants. The editor configures these values; it does not operate a central gateway.
 JSKIT supplies the JavaScript runtime; Laravel implements the same provider
 contract with its own framework. Disconnect deletes the local grant; revoke
 provider access separately by uninstalling the app in Pipedrive.
@@ -111,7 +111,7 @@ never creates a CRM record; uncertain writes are not automatically replayed.
 
 CLI uses service.invoke with the same JSON/Env and authorized local operator.
 Other frameworks use these endpoints with their native client and company-bound
-OAuth grant. No central Vibe64 credential gateway.
+OAuth grant. No central credential gateway.
 **LIMITATIONS:** No full CRM UI, pipeline administration, custom fields/bulk import,
 attachments, webhooks or coding-chat attachment. Example: create a contact and
 follow-up deal; build the sales dashboard in the application. No live/generated-app proof.

package/docs/prestashop.md

@@ -114,7 +114,7 @@ The editor VM and application custom domain need no provider redirect
 registration. If the store itself changes address, update `siteUrl` and
 re-verify it. The application retains its credential in private Env and enforces
 access through its own authorization policy. See the
-[application setup contract](../../connectors-core/docs/online-setup.md).
+[application setup contract](../../connectors-core/docs/application-setup.md).
 
 ## Focused proof and remaining work
 

package/docs/replicate.md

@@ -53,7 +53,7 @@ file-store restart, rotation, isolation and HTTP failures. No model was run.
 3. Save the returned ID under the authorized app user. Poll `predictions.get({id})` on your application's schedule. Starting/processing are pending; succeeded exposes output; failed exposes error; canceled is terminal. `predictions.cancel({id})` explicitly requests cancellation. Do not resubmit a timed-out creation automatically: its outcome may be unknown.
 4. Output is preserved, including strings, arrays, structured JSON and image/audio/video URLs. The app renders the result and, when needed, saves files before the provider's retention window expires (normally one hour for API predictions). The adapter never fetches arbitrary result URLs.
 
-For CLI or another framework, use the same project slot and Env reference with these documented HTTP endpoints and ownership checks. JSKIT invokes them through the existing connection service; no Vibe64 execution service is required.
+For CLI or another framework, use the same project slot and Env reference with these documented HTTP endpoints and ownership checks. JSKIT invokes them through the existing connection service; no hosted execution service is required.
 
 **LIMITATIONS:** No media studio, background polling/history service, training, deployment administration, file uploader or editor-tool attachment. Example: an app can request a generated image and poll its ID, but must show progress and save/display the resulting image itself. Backend authorization must restrict prediction IDs to their initiating users; a shared provider token alone does not provide app-user isolation.
 

package/docs/resend.md

@@ -146,7 +146,7 @@ absence of automatic retries on uncertain delivery. No email is sent.
 5. Call `broadcasts.create({segment_id,from,subject,html,name?,text?,preview_text?})`. It always saves `send:false`; it cannot silently send. Read back with `broadcasts.get({id})`, list with `broadcasts.list({limit,after})`, or replace the editable content with `broadcasts.update({id,segment_id,from,subject,html,...})`. Review sender, recipient segment and rendered content in the app or Resend dashboard. For preview, use your framework's renderer; use a separate segment containing only your test addresses for an explicit test send.
 6. After the operator approves the selected recipients/content, invoke `broadcasts.send({id})`. This affects the whole selected segment. The application must authorize this operation separately from draft editing and restrict IDs to its tenant. API acceptance is not delivery proof. Creation/sending each make one request, with no automatic retries; inspect provider status after an uncertain outcome rather than creating duplicate campaigns.
 
-JSKIT uses the same connection slot and backend Env for these operations through `connections.invoke`. CLI apps compose that service directly; other frameworks use their own Resend client/HTTP implementation with the same project-owned configuration. Vibe64 edits setup; it does not run a shared sending service or own recipient lists.
+JSKIT uses the same connection slot and backend Env for these operations through `connections.invoke`. CLI apps compose that service directly; other frameworks use their own Resend client/HTTP implementation with the same project-owned configuration. The editor edits setup; it does not run a shared sending service or own recipient lists.
 
 **LIMITATIONS:** No visual campaign builder, hosted-template catalogue, topic/custom-property administration, automation engine, scheduling UI, inbound mail, attachments, delivery-webhook processor, analytics dashboard or automatic coding-assistant attachment. Example: the app can create a newsletter draft and explicitly send it to a reviewed segment, but its own UI or Resend dashboard supplies preview and reporting. Transactional `emails.send` remains plain text with the existing idempotency-key contract. The unsubscribe marker check cannot verify the quality/visibility of rendered HTML; review the actual content.
 

package/docs/salesforce.md

@@ -162,7 +162,7 @@ not exposed as user messages. Cancellation/deadlines do not replay a request.
 
 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/sanity.md

@@ -19,7 +19,7 @@ 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.
 An uncertain outcome requires inspection before retrying. This does not register
-a central Vibe64 client.
+a central hosted client.
 
 For manual setup, use the OAuth client registration screen's JSON, or invoke
 `registerSanityClient({ clientName, callbackUrl, scopes: ["global"] })` from
@@ -27,7 +27,7 @@ For manual setup, use the OAuth client registration screen's JSON, or invoke
 then save the returned client ID and private client secret into your own
 configuration/Env. Investigate an interrupted request before retrying, because
 the provider may already have created the client. Use the exact backend callback
-suggested by your project. No central Vibe64 callback or managed registration.
+suggested by your project. No central hosted callback or managed registration.
 
 Connect and consent only after the backend serves that callback. Sanity account
 permissions govern the grant; the host must still authorize project/dataset
@@ -93,7 +93,7 @@ private token store with the same fixed endpoint and Env references. It does not
 run JSKIT or call an editor server for content. The generated application can use
 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
+configuration and runtime API. Neither path automatically attaches
 these tools to an assistant.
 
 ## Automation and application ownership

package/docs/semrush.md

@@ -98,7 +98,7 @@ editor and hosted editor use the same configuration file and private Env
 reference. The editor does not provide a provider account, retain the key in a
 central connector service or assign capacity based on the editor subscription.
 
-For this V4 key flow, a universal OAuth callback is **not applicable**. VPS
+For this V4 key flow, a universal OAuth callback is **not applicable**. Server
 addresses and custom domains do not change provider key authentication. The
 application owner supplies its authorized key through private Env and retains
 that ownership when moving hosts.
@@ -269,7 +269,7 @@ The JSON response preserves keyword IDs, date-keyed rankings, visibility and
 other provider fields. `data` may be an indexed object rather than a JS array;
 use the framework's object-value iteration when rendering rows. The application
 must authorize project/campaign access, review unit usage and decide whether to
-request another page. Neither Vibe64 nor this adapter automatically polls campaigns.
+request another page. Neither the editor nor this adapter automatically polls campaigns.
 Connecting only checks V4 project access. Errors from tracking do not invalidate
 that separate V4 connection. No live campaigns were queried during verification.
 

package/docs/sentry.md

@@ -74,7 +74,7 @@ MCP requests. The provider constrains that resource; the application still owns
 caller authorization and review of any triage or write operation.
 
 The application owns tokens, encrypted persistence, callback execution and
-refresh. CLI applications use the ordinary connection service without Vibe64.
+refresh. CLI applications use the ordinary connection service.
 Other frameworks consume the same configuration and Env names using their native
 OAuth/MCP libraries, without importing JavaScript or running a Node sidecar.
 The editor's subscription does not supply a Sentry account or quota.

package/docs/slack.md

@@ -137,7 +137,7 @@ installs, GovSlack and Sign in with Slack are outside this initial fragment.
 
 Each application owns its provider registration, callback route, credentials
 and grants. Hosted and installed editors configure the same app-owned setup;
-neither supplies a shared Vibe64 registration or token gateway. Use the app's
+neither supplies a shared registration or token gateway. Use the app's
 assigned public URL as the initial callback origin, append the route the backend
 actually implements, and register the exact URL with the provider. Keep the
 client secret and callback binding in the application's Env.

package/docs/snowflake.md

@@ -25,9 +25,9 @@ stores the same JSON a CLI user writes. Saving configuration contacts no provide
       "accountMode": "per-user",
       "settings": {
         "accountUrl": "https://myorg-myaccount.snowflakecomputing.com",
-        "role": "VIBE64_READER"
+        "role": "REPORTING_READER"
       },
-      "scopes": ["refresh_token", "session:role:VIBE64_READER"],
+      "scopes": ["refresh_token", "session:role:REPORTING_READER"],
       "authentication": { "method": "oauth2", "registrationRef": "snowflake" }
     }
   }
@@ -83,7 +83,7 @@ account or role invalidates saved access and pending consent.
    production integration as a shortcut.
 
 ```sql
-CREATE SECURITY INTEGRATION DOGANDGROOM_READER
+CREATE SECURITY INTEGRATION APP_READER
   TYPE = OAUTH
   ENABLED = TRUE
   OAUTH_CLIENT = CUSTOM
@@ -94,8 +94,8 @@ CREATE SECURITY INTEGRATION DOGANDGROOM_READER
   OAUTH_REFRESH_TOKEN_VALIDITY = 86400
   OAUTH_USE_SECONDARY_ROLES = NONE;
 
-DESC SECURITY INTEGRATION DOGANDGROOM_READER;
-SELECT SYSTEM$SHOW_OAUTH_CLIENT_SECRETS('DOGANDGROOM_READER');
+DESC SECURITY INTEGRATION APP_READER;
+SELECT SYSTEM$SHOW_OAUTH_CLIENT_SECRETS('APP_READER');
 ```
 
 5. Copy `OAUTH_CLIENT_ID` into **Client ID**. Save one returned client secret in

package/docs/storyblok.md

@@ -119,7 +119,7 @@ The app owns its revalidation trigger and scheduler.
 
 A CLI-only or non-JSKIT app uses the same token Env and region with its native
 HTTP/Storyblok client. Keep the same published-default and preview authorization
-rules; it does not need Vibe64 or a JSKIT server.
+rules; it does not need a hosted editor or a JSKIT server.
 
 Current focused source proof: four Storyblok cases pass, covering all regions,
 credential rotation/restart, page/list results, linked content and assets,

package/docs/stripe.md

@@ -70,8 +70,8 @@ This connector's operations are only part of a billing implementation. For
 checkout, subscriptions, feature access, renewal credits and durable catalogue
 mappings, read [payments-core](../../payments-core/README.md) and its
 [standalone composition guide](../../payments-core/docs/standalone.md). These
-JavaScript libraries work from ordinary app code or a CLI without Vibe64 or
-Genesis. Other frameworks consume the [portable contract](../../payments-core/docs/contract.md)
+JavaScript libraries work from ordinary app code or a CLI without a hosted
+editor. Other frameworks consume the [portable contract](../../payments-core/docs/contract.md)
 and its static examples using their own runtime libraries. Keep provider setup
 from this guide; do not substitute a successful connection check for working
 checkout, verified webhooks or merchant approval.

package/docs/tally.md

@@ -57,7 +57,7 @@ The application owns who can read these responses and how they are retained.
 A shared key does not grant every app user access to every form. Do not fetch
 returned PDF/preview/file URLs automatically or render answers as trusted HTML.
 Other frameworks can use their native server HTTP client with the same Env
-Bearer token and version header; no JSKIT or Vibe64 process is required.
+Bearer token and version header; no JSKIT or hosted process is required.
 [Submission API](https://developers.tally.so/api-reference/endpoint/forms/submissions/list).
 
 No live submission was read.

package/docs/telegram.md

@@ -150,6 +150,6 @@ to contact arbitrary people. No send is retried automatically after uncertainty.
 [chat action](https://core.telegram.org/bots/api#sendchataction).
 
 A non-JavaScript framework uses its own HTTP client and worker with the same Env
-bot token, JSON payloads and offset contract. JSKIT is optional; Vibe64 hosts no
-polling service. Local disconnect leaves the bot and queued updates intact.
+bot token, JSON payloads and offset contract. JSKIT is optional; no hosted
+polling service is involved. Local disconnect leaves the bot and queued updates intact.
 Revoke/replace a compromised token with BotFather, change Env and verify again.

package/docs/tiktok.md

@@ -3,7 +3,7 @@
 Import `tiktokProvider` from `@jskit-ai/connectors-catalog/server/tiktok`.
 The library reads the consenting creator's profile, statistics and public video
 metadata. CLI and server consumers use the same configuration and connection
-service; Vibe64 edits that file through shared fields and validation.
+service; a hosted editor edits that file through shared fields and validation.
 
 ## Provider setup
 
@@ -162,7 +162,7 @@ vanish between pages; do not assume the feed is an immutable snapshot.
 [Public-video listing](https://developers.tiktok.com/docs/en/tiktok-api-v2-video-list).
 
 A Node app or CLI consumes the same installed JSKIT exports and file without
-Vibe64. A different framework owns its OAuth/token storage and native HTTP calls:
+a hosted editor. A different framework owns its OAuth/token storage and native HTTP calls:
 read the same registration references and ownership/scopes, call GET
 `/v2/user/info/` and JSON POST `/v2/video/list/`, then build the same gallery
 response. It must retain the provider-specific `client_key`, comma scopes and
@@ -172,7 +172,7 @@ refresh-token rules described above. JSKIT supplies no PHP implementation.
 
 Each application owns its provider registration, callback route, credentials
 and grants. Hosted and installed editors configure the same app-owned setup;
-neither supplies a shared Vibe64 registration or token gateway. Use the app's
+neither supplies a shared registration or token gateway. Use the app's
 assigned public URL as the initial callback origin, append the route the backend
 actually implements, and register the exact URL with the provider. Keep the
 client secret and callback binding in the application's Env.

package/docs/twilio.md

@@ -93,8 +93,8 @@ region on failure, and not every Twilio product is available in every region.
 Apply the [API-key source pattern](../patterns/api-key-connection/PATTERN.md)
 with `providers: [twilioProvider]`, the encrypted file connection store, the
 application's environment reference resolver and its authorization policy.
-Configuration and runtime state are text files. The runtime needs neither the
-Vibe64 editor nor a database.
+Configuration and runtime state are text files. The runtime needs neither a
+hosted editor nor a database.
 
 ```js
 await connections.connectApiKey({ context, integrationId: "voice" });
@@ -281,4 +281,4 @@ token references, all region choices, setup instructions, persistence and
 connect/disconnect at compact, medium and expanded sizes.
 Provider signup, real API use and generated applications are outside the test
 scope. The same ten tests pass using normal exports from an installed package
-in a disposable Node consumer, independently of Vibe64.
+in a disposable Node consumer, independently of any editor.

package/docs/twitch.md

@@ -319,7 +319,7 @@ These navigation steps follow Twitch's
 The confidential/public distinction is described in its
 [refresh documentation](https://dev.twitch.tv/docs/authentication/refresh-tokens/).
 A CLI uses these same packages and a callback served by its own backend/listener
-at a provider-accepted, registered URL. No Vibe64 account is required. Do not
+at a provider-accepted, registered URL. No hosted-editor account is required. Do not
 embed a confidential client secret into a distributed desktop binary.
 
 ## Portable configuration and library composition
@@ -410,7 +410,7 @@ Register the application's own callback route, using its assigned public origin
 as the starting point, and keep that exact URL in application Env. When it
 changes, update both the app binding and the provider registration. The
 [callback contract](../../connectors-core/docs/oauth-callbacks.md) describes
-identity, consent and grant handling during a move. No Vibe64 callback gateway
+identity, consent and grant handling during a move. No hosted callback gateway
 participates in this flow.
 
 The documented registration path is the console. No supported application

package/docs/wave.md

@@ -3,7 +3,7 @@
 `waveProvider` from `@jskit-ai/connectors-catalog/server/wave` provides OAuth
 consent, profile verification, business/accounting reads, customer/product and
 account/tax maintenance, invoice/estimate workflows and money-transaction creation. An ordinary CLI or backend composes the shared connection service
-with encrypted file storage. Vibe64 edits the same portable JSON; saving it
+with encrypted file storage. A hosted editor edits the same portable JSON; saving it
 does not connect an account.
 
 ## Provider registration
@@ -234,7 +234,7 @@ including final setup/lifecycle and distribution evidence, is still open.
 
 Each application owns its provider registration, callback route, credentials
 and grants. Hosted and installed editors configure the same app-owned setup;
-neither supplies a shared Vibe64 registration or token gateway. Use the app's
+neither supplies a shared registration or token gateway. Use the app's
 assigned public URL as the initial callback origin, append the route the backend
 actually implements, and register the exact URL with the provider. Keep the
 client secret and callback binding in the application's Env.
@@ -278,7 +278,7 @@ The implemented mutations are described below.
 Use `estimates.list` with `{ businessId, page, pageSize }` and `estimates.get`
 with `{ businessId, estimateId }` to populate the app's estimate screens. List
 ordering is newest-created first. The app owns those screens and the business
-access policy; Vibe64 does not approve or send estimates.
+access policy; the editor does not approve or send estimates.
 
 ```js
 const draft = await connections.invoke({ context, integrationId: "wave",