@zackbart/connecta 0.34.1 → 0.36.0

package/dist/providers/notion/skill.generated.js

@@ -1,11 +0,0 @@
-// Generated by scripts/generate-providers.mjs; do not edit.
-export const skill = {
-    "content": "\n## Notion's data model\n\n- A database is a container; its rows and schema live in a *data source*\n  inside it. Queries, schema reads, and new rows take the data source, and\n  Notion rejects a database id in its place.\n- Property names in filters, sorts, and writes must match the schema exactly,\n  including case. Read the schema before composing one.\n- A `status` write must use an existing option name; inventing one fails.\n  A new `select` or `multi_select` name does not fail: when the connection\n  can write to the data source, Notion adds it to the schema as a new\n  option. Use the options the schema lists unless a schema change is meant.\n- Writes **replace** a property. Sending one item to a `multi_select` or\n  `relation` drops the others, so send the complete intended value.\n- `rollup`, `formula`, `unique_id`, and the created and edited fields are\n  computed. They cannot be written.\n- A data source's title column is rarely called \"title\". Read its name from\n  the schema before creating or renaming a row.\n- Notion has **no idempotency key**. A retried page create or comment makes a\n  duplicate. Confirm with a search before repeating a write that may have\n  partially succeeded.\n",
-    "instructionsHeading": "Workspace instructions",
-    "fragments": {
-        "oauth_head": "# Notion MCP usage\n\nOfficial MCP interface: tool names, descriptions, argument schemas, and result\nschemas come from Notion's live server. Connecta preserves that catalog and\napplies release-reviewed classification. Reviewed writes stay writes even when Notion claims they only read.\n\nWorkspace purpose: ",
-        "oauth": "\n\n- This connection acts as its OAuth-authorized user and reaches what that user\n  can. It holds no integration token. An internal integration (bot) is a\n  separate connector with `auth: { type: \"token\" }` under another id; never\n  switch to it to recover a failed call here.\n- Discover the live catalog before assuming a tool exists. Notion can gate\n  tools by workspace, account, client, and rollout independently of Connecta.\n  `notion-get-tool-access` reports what the workspace's plan allows.\n- Start broad discovery with `notion-search`, then use `notion-fetch` on\n  the exact page, database, data source, or object before changing it.\n- Use the live input schema as the contract. Notion owns these MCP schemas;\n  the REST schemas of Connecta's token connector do not apply to MCP tools with\n  similar names.\n- The next-step card tools return guidance without enabling access. Call\n  `notion-check-mcp-next-steps` only when fetch instructs you to, at most\n  once. Call `notion-show-advanced-analysis-next-steps` once at turn end\n  only when a multi-source query requires the full version.\n- Session and agent tools can launch asynchronous work. Read session state and\n  events before sending another message, waiting, or stopping a session.\n- File uploads and attachment tools create durable workspace state. Keep\n  downloads inside the requested task and do not expose signed attachment URLs.\n  `notion-get-file-download-urls` returns signed download URLs that expire\n  after a few minutes. Use them only for the requested download and keep\n  stable `notion-file-block://` references in edited or copied Markdown.\n  `notion-download-skill` also returns a signed, expiring archive URL.\n  The token connector's REST redaction does not apply to hosted tools;\n  do not repeat signed download URLs in replies.\n- `notion-upload-skill` is a write for both actions. `prepare` returns a\n  credential-bearing upload URL and headers with a ten-minute expiry;\n  keep them inside the upload flow and out of replies. `complete` replaces\n  the target page's title, Description, body, and Files.\n- Connecta's generic REST tools (`notion_api_*`) and the `integration_*`\n  helpers exist only on a token connector.\n- An `auth_required` failure means this connector's OAuth grant is missing or\n  expired. Run `authorize_connector` for this connector id, then retry.\n",
-        "key": "\n## Identity and tools\n\nThis is Connecta's REST connector to `api.notion.com`, acting as one internal\nintegration (a bot) with an operator-managed integration token. It reaches\nexactly the pages and data sources shared with that integration, and the\nintegration's capabilities decide which calls succeed: comment and\nuser-information capabilities are off by default. It never acts as a person.\nHosted Notion MCP is a separate OAuth connector.\n\n- Named tools cover the common path and flatten Notion's payloads:\n  `integration_search` (titles), `integration_get_page` (properties),\n  `integration_get_page_content` (blocks as text),\n  `integration_get_data_source_schema`, and `integration_query_data_source`\n  (rows). `integration_create_page` and `integration_append_blocks` author\n  Notion's rich-text and block shapes from plain text, Markdown, or checklists.\n- Four generic tools reach every other operation in the pinned API index.\n  `notion_api_search` finds operations, not content. `notion_api_details`\n  returns one operation's parameters. `notion_api_read` calls GETs plus the\n  read-only POST queries: search, data source and meeting note queries, and\n  agent, session, and session event queries. `notion_api_write` calls every\n  other POST, PATCH, and DELETE with `method` and `path` stated.\n- Every generic call is checked against the index before it is sent. An\n  unknown path returns the nearest operations, and an unknown or missing\n  parameter returns `validation.issues` with the accepted names. Nothing\n  reached Notion, so fix the call from that answer.\n- The generic set replaces the old one-operation tools. Read a database\n  container with `GET /v1/databases/{database_id}`, users with `GET /v1/users`\n  or `GET /v1/users/me`, and comments with `GET /v1/comments`. Update\n  properties, trash or restore (`in_trash`) with `PATCH /v1/pages/{page_id}`,\n  and comment with `POST /v1/comments` (`rich_text` or `markdown`).\n- Refused by design: Notion's OAuth token endpoints (`/v1/oauth/*`) and\n  multipart file sends. Import a file with `POST /v1/file_uploads` and\n  `mode: \"external_url\"` instead.\n- Notion-minted file links lose their whole query and fragment wherever\n  they appear, including page Markdown, async task results, and error text.\n  Connecta matches the actual authority: `file.notion.so`,\n  `secure.notion-static.com`, `notionusercontent.com` and their subdomains,\n  or the `prod-files-secure` and `secure.notion-static.com` S3 buckets,\n  virtual-hosted or exactly the first path segment on an S3 endpoint.\n  Escaped schemes, slashes, and query/fragment openers are recognized. The\n  withheld span runs through the next whitespace, quote, or angle bracket;\n  trailing closing punctuation comes back. A returned file URL names the\n  file but cannot download it. Links at other authorities, including proxy\n  URLs with a Notion URL inside their path or query, come back as written.\n  AWS `X-Amz-*` and Google `X-Goog-*` signing `Signature`, `Credential`, and\n  `Security-Token` values are withheld at any host.\n- A write whose Notion file link carries the exact `[redacted]` placeholder\n  in its own query or fragment, plain or up to four layers encoded, is\n  refused before dispatch. Each inline Markdown destination is checked,\n  including adjacent links and images, balanced or escaped parentheses, and\n  leading spaces, tabs, or one line ending. A marker after the destination's\n  close is ordinary text. To keep a file, leave its block in place or\n  re-upload it with `POST /v1/file_uploads`; to edit Markdown around media,\n  match `old_str` on nearby text rather than the withheld URL.\n- Each string is scanned separately. Links split across rich-text runs,\n  encoded hostnames or signing-parameter names, bare hosts without `//`,\n  and userinfo before a Notion host are outside this scan's threat model.\n  The shared URL rule still removes userinfo from whole URL fields.\n  Credential-named fields read as `\"[redacted]\"`, a database property named\n  like a credential (`API token`) included. Failures of the OAuth, file upload, bot user, and\n  agent operations carry Notion's code, not its message.\n- Not here: the hosted MCP's user identity, its search across connected\n  apps, page duplication, team and skill search, attachment downloads, and\n  page-to-skill conversion. Those need an OAuth connector.\n\n## Databases contain data sources\n\n- The id in a Notion database URL is a **database id**.\n  `GET /v1/databases/{database_id}` through `notion_api_read` lists its\n  `data_sources`, usually one. `integration_search` returns data sources\n  directly and skips that step.\n- `integration_get_data_source_schema` and `integration_query_data_source`\n  take the **data_source_id**, and `integration_create_page` takes it as\n  `parent_data_source_id` when adding a row.\n\nSo the sequence for \"find rows in this database\" is the database read, then\n`integration_get_data_source_schema`, then `integration_query_data_source`.\n\n## Reading\n\n- `integration_get_page` returns properties. To read or summarize a whole\n  body, prefer `notion_api_read` `GET /v1/pages/{page_id}/markdown`: one\n  request returns every nested level as Markdown (headings, lists, to-dos,\n  toggles, tables, code, links, mentions, equations). A huge page comes back\n  with `truncated: true` and the unread blocks in `unknown_block_ids`; read\n  each id as a `page_id` on the same path.\n- `integration_get_page_content` returns the body as flat blocks with ids,\n  for quoting a block or appending after one. Nested blocks (toggles, list\n  children, table rows) need `depth`, and each level multiplies requests. A\n  deep read stops at an internal ceiling and reports `truncated: true` rather\n  than spending the whole rate-limit budget.\n- Notion truncates `title`, `rich_text`, `relation`, and `people` at 25\n  entries. `integration_get_page` reports each in `truncated_properties` as\n  `{ name, id }`; read the complete value with `notion_api_read`\n  `GET /v1/pages/{page_id}/properties/{property_id}` and follow its cursor.\n- Every named read projects Notion's payload to ids, plain text, and\n  flattened property values. Pass `raw: true` for the full response, with\n  the same value-safety redaction, when a specific field is missing. It is\n  much larger. Narrow\n  `integration_query_data_source` and `integration_get_page` with `properties`\n  when the goal is fewer fields. This also narrows the request to Notion with\n  repeated `filter_properties` URL parameters, shrinking the response before\n  Connecta reads it. The title property is always fetched so the projected\n  `title` stays populated. Page retrieval allows at most 100 distinct filters,\n  including the title id. A larger selection fetches all properties and still\n  projects only the selected names locally. Data source queries have no\n  documented filter count limit. `raw: true` returns the upstream response,\n  filtered when those filters fit and full when page retrieval falls back.\n  Omit `properties` for the full response on either tool.\n  `integration_get_page_content` with `raw: true` returns one level and ignores\n  `depth`.\n\n## Writing content\n\n`integration_append_blocks` adds children and nothing else. It cannot move,\nreorder, or replace an existing block, and a block appended through the API can\nnever be relocated by it afterwards. Get the position right the first time with\n`position` and `after_block_id`. Notion caps one call at 100 blocks. Text\nlonger than Notion's 2,000-character run limit is split into runs for you.\n\nFor formatted content, write Markdown to a page with `notion_api_write`\n`PATCH /v1/pages/{page_id}/markdown`. Append with\n`{\"type\":\"insert_content\",\"insert_content\":{\"content\":\"## Notes\\n- one\",\"position\":{\"type\":\"end\"}}}`\n(`start` prepends). Edit text in place with `update_content`, whose\n`content_updates` are `{ old_str, new_str }` pairs copied exactly from the\npage's Markdown, and `replace_content` swaps the whole page for `new_str`.\nNotion refuses an edit that would delete a child page or database with a\n`validation_error` naming them. Removing ordinary text needs no flag; to delete\nthose children, set `allow_deleting_content: true` inside the command body\n(`{\"type\":\"update_content\",\"update_content\":{\"content_updates\":[…],\"allow_deleting_content\":true}}`),\nand leave it out unless the task is to delete them. `integration_create_page`\ntakes the same Markdown for a new page's body.\n\n## Pagination\n\n- Named list tools take `page_size` (max 100) and return `has_more` with\n  `next_cursor`; pass it back as `start_cursor`.\n- Generic results arrive as `{ status, data, page? }`. On a list,\n  `page.next` is the cursor and `page.param` is `start_cursor`: send it in\n  `query` for a GET, and in `body` when `page.in` is `body`, as on the POST\n  queries. Pass `select` dot paths relative to `data`, such as `results.id`;\n  `page` survives any `select`.\n- A view query is created with `notion_api_write`\n  `POST /v1/views/{view_id}/queries`, a write because Notion stores it until\n  `expires_at`. Its first page names the continuation in `page.path`: read\n  `GET /v1/views/{view_id}/queries/{query_id}` with `start_cursor` in `query`.\n- Meeting-note queries have no cursor. `limit` caps at 50, and\n  `page.hasMore` without `page.next` means more notes exist: narrow the\n  filter (for example by `created_time`) rather than paging.\n- A data source query stops at 10,000 rows. `integration_query_data_source`\n  then returns `incomplete: true`, and a generic query `page.hasMore` without\n  `page.next`: narrow the filter rather than trusting the count.\n- Cursors are opaque: never parse or construct one. Follow pages inside\n  `execute_code` and reduce there.\n\n## Failures worth reading carefully\n\n- **404** means \"no such object\" *or* \"not shared with this integration\", and\n  Notion will not say which. Never conclude a page was deleted from it; check\n  that the page is shared with the integration in Notion.\n- **403** is not an expired token. The integration is missing a capability\n  (comment capabilities are off by default), the object was never shared, or\n  the workspace is past its plan's block limit; Notion's message says which.\n  Re-authorizing cannot fix it; an operator must change it in Notion.\n- **429** carries a retry window. Notion's [request limits](https://developers.notion.com/reference/request-limits)\n  allow 600 requests a minute per connection on Business and Enterprise and\n  180 on other plans, plus a workspace-wide limit shared by all connections.\n  Connecta defaults to 180 calls a minute, three at a time, per runtime.\n  A token connector's optional `callAdmission` replaces that whole policy;\n  account for other runtime traffic and tools that make multiple HTTP requests.\n  Wait out the window rather than retrying immediately. A 429 that says the\n  integration's API access is blocked is not retryable.\n- **5xx on a write** may still have been saved. When Notion names the\n  object it committed, the failure says so: read that object instead of\n  repeating the write. Otherwise check the target before trying again.\n",
-        "shared": "\n## Notion's data model\n\n- A database is a container; its rows and schema live in a *data source*\n  inside it. Queries, schema reads, and new rows take the data source, and\n  Notion rejects a database id in its place.\n- Property names in filters, sorts, and writes must match the schema exactly,\n  including case. Read the schema before composing one.\n- A `status` write must use an existing option name; inventing one fails.\n  A new `select` or `multi_select` name does not fail: when the connection\n  can write to the data source, Notion adds it to the schema as a new\n  option. Use the options the schema lists unless a schema change is meant.\n- Writes **replace** a property. Sending one item to a `multi_select` or\n  `relation` drops the others, so send the complete intended value.\n- `rollup`, `formula`, `unique_id`, and the created and edited fields are\n  computed. They cannot be written.\n- A data source's title column is rarely called \"title\". Read its name from\n  the schema before creating or renaming a row.\n- Notion has **no idempotency key**. A retried page create or comment makes a\n  duplicate. Confirm with a search before repeating a write that may have\n  partially succeeded.\n"
-    }
-};

package/dist/providers/notion/value-safety.js

@@ -1,56 +0,0 @@
-// Notion's reviewed value-safety table (#801), on the shared mechanism in
-// `../_shared/rest/value-safety.ts`: every operation the detector flags in
-// the pinned spec (`value-safety.candidates.json`) has one verdict here, and
-// `value-safety.node.test.ts` runs the shared harness over it.
-//
-// Notion's API returns little that is a credential: an integration token
-// never appears in a response. The OAuth endpoints mint, introspect, and
-// revoke tokens with a public integration's client secret and are refused.
-// A file upload's `upload_url` is Notion's own send endpoint and needs the
-// integration token, so it is kept. Notion-minted file URLs are pre-signed:
-// sanitizeLinks removes their whole query/fragment wherever they appear,
-// including page Markdown and free-form async results, before projections
-// or the shared whole-URL heuristic. The same scan precedes error mapping.
-import { refuse, safe, withholdSignedLinksIn, } from "../_shared/rest/value-safety.js";
-const OAUTH = "Notion's OAuth token endpoints are not reachable through Connecta: they mint and revoke credentials with a public integration's client secret, which this connector never holds.";
-const UPLOAD = "A file upload's upload_url is Notion's own send endpoint, which needs the integration token; it grants nothing alone.";
-const AGENT = "Custom agents name their connected MCP server's host, never its URL or credentials.";
-const OPERATIONS = {
-    "POST /v1/oauth/token": refuse(OAUTH),
-    "POST /v1/oauth/introspect": refuse(OAUTH),
-    "POST /v1/oauth/revoke": refuse(OAUTH),
-    "GET /v1/users/me": safe("Answers the integration's bot user; no token."),
-    "GET /v1/file_uploads": safe(UPLOAD, ["results.upload_url"]),
-    "POST /v1/file_uploads": safe(UPLOAD, ["upload_url"]),
-    "GET /v1/file_uploads/{file_upload_id}": safe(UPLOAD, ["upload_url"]),
-    "POST /v1/file_uploads/{file_upload_id}/complete": safe(UPLOAD, ["upload_url"]),
-    "POST /v1/file_uploads/{file_upload_id}/send": safe(UPLOAD, ["upload_url"]),
-    "POST /v1/agents/query": safe(AGENT, ["results.connections.account.server_host"]),
-    "GET /v1/agents/{agent_id}": safe(AGENT, ["connections.account.server_host"]),
-};
-export const NOTION_VALUE_SAFETY = { title: "Notion", operations: OPERATIONS };
-/**
- * Where Notion stores the files it signs. Its S3 buckets, virtual-hosted
- * (`prod-files-secure.s3.us-west-2.amazonaws.com`) or as the first path
- * segment on an S3 endpoint (`s3.us-west-2.amazonaws.com/secure.notion-static.com/…`,
- * Notion's file object reference), and its own file, static, and image-proxy
- * hosts and their subdomains (`file.notion.so`, `img.notionusercontent.com`).
- * Never all of `amazonaws.com`, and never a host or path that merely
- * contains one of these names: a person's link is their content.
- */
-export const NOTION_FILE_HOSTS = {
-    domains: ["file.notion.so", "secure.notion-static.com", "notionusercontent.com"],
-    buckets: ["prod-files-secure", "secure.notion-static.com"],
-};
-/**
- * Every response with each pre-signed file link embedded in its strings
- * withheld. Images in page Markdown render as `![caption](url)` and files,
- * PDFs, audio, and video as `<file src="url">`, so a Notion-hosted file's
- * pre-signed URL arrives inside text rather than as a field: in `GET` and
- * `PATCH /v1/pages/{page_id}/markdown`, and in a completed async task's
- * `result`, which is free-form. Every response and error body is scanned
- * rather than those paths, so no route to page Markdown can skip it.
- */
-export function sanitizeLinks(body) {
-    return withholdSignedLinksIn(body, NOTION_FILE_HOSTS);
-}

package/dist/providers/revenuecat/index.d.ts

@@ -1,51 +0,0 @@
-import { type RemoteMcpAuth } from "../../connectors/remote-mcp.js";
-import type { ConnectorCallAdmissionPolicy } from "../../types.js";
-/** RevenueCat publishes one hosted MCP endpoint, streamable HTTP. */
-export declare const REVENUECAT_MCP_ENDPOINT = "https://mcp.revenuecat.ai/mcp";
-export interface RevenueCatOptions {
-    /**
-     * Display name. It defaults to the credential's scope, because that is what
-     * decides how an agent must address the connector: `RevenueCat (single
-     * project)` for a project-wide `sk_` key, plain `RevenueCat` for an
-     * account-scoped OAuth session that must resolve a `project_id` first.
-     */
-    title?: string;
-    /** Downstream auth ownership. Defaults to one shared deployment grant. */
-    authScope?: "shared" | "personal";
-    /**
-     * Which project this connector is for and what decisions it answers. With
-     * headers auth this is the only place the project a key reaches is named,
-     * so it goes in the guide's first line and its summary.
-     */
-    purpose: string;
-    /**
-     * OAuth (account-scoped, reaches every project the account can see) or an
-     * API v2 `sk_` secret key, which RevenueCat scopes to exactly one project —
-     * hence one key, one connector, and no `project` option: checking a declared
-     * project against `list-projects` at construction would be the unasked-for
-     * credential test P10 forbids. RevenueCat may omit tools based on key
-     * permissions; Connecta serves the live catalog, not the reviewed superset.
-     * A served tool can still be refused by RevenueCat for missing permissions.
-     */
-    auth?: RemoteMcpAuth;
-    /** Project-specific conventions appended to the maintained provider guide. */
-    instructions?: string;
-    /** Connector-specific inline result limit; omit to inherit the deployment. */
-    maxResultBytes?: number;
-    /** Serve only read-classified tools on every endpoint. Defaults to false. */
-    readOnly?: boolean;
-    /**
-     * Optional per-runtime policy. There is no default even though RevenueCat
-     * publishes numbers (API v2, read 2026-08-18): the limit is per minute per
-     * domain — 480 for customer information, virtual currencies, and refunds; 60
-     * for audiences and project configuration; 25 for charts and metrics — and a
-     * policy carries one rule, so any single number is wrong for most tools. The
-     * metering scope is per developer for developer-level keys, which a
-     * per-runtime counter cannot approximate either. The operator picks (P12).
-     */
-    callAdmission?: ConnectorCallAdmissionPolicy;
-}
-/** A maintained RevenueCat hosted-MCP connection. */
-export declare const revenuecat: import("../../provider.js").ProviderFactory<RevenueCatOptions>;
-/** @deprecated Read `revenuecat.definition.classify` instead. Kept for existing imports. */
-export declare const REVENUECAT_VETTED_CATALOG: import("../../catalog-drift.js").VettedCatalog;