@zackbart/connecta 0.34.0 → 0.35.0

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

@@ -1,8 +0,0 @@
-// Generated by scripts/generate-providers.mjs; do not edit.
-export const skill = {
-    "content": "Start with `list_projects` for project IDs and environment slugs, then `list_folders` for absolute paths.\n\nKeep value reads narrow. `list_secrets` returns identifiers only by default, even if the server sends values or comments; use `get_secret` or opt into `includeValues` only when needed. These explicit reads return secrets, including values and comments. Comments are available only from these value-read tools. Do not echo values unless the user asks. Imports follow the same value policy.\n\nValues can reference secrets as `${env.KEY}`. Value reads expand references by default. Use `expandReferences: false` to read the literal reference before editing; updating a value changes only that secret, not the secrets it references. Updates send only named changes. Writes omit values and report `pendingApproval` when an environment's change policy requires approval.\n\nEvery value-free result returns only checked identifiers: UUID or legacy 24-hex IDs, secret keys, positive integer versions, known type/approval enums, environment and tag slugs, absolute paths, and ISO timestamps. Projects expose IDs and environment identifiers; folders expose IDs and paths. Project slugs are withheld because Infisical can derive them from free-text project names. Comments, descriptions, free-form names, reminder notes, and arbitrary nested objects are withheld. `metadataOmitted: true` reports dropped or unavailable metadata; success or pending-approval context remains available. Identifier fields outside the conservative grammar are dropped.\n\nKnown, accepted residual risk: environment slugs are returned as required routing identifiers. Infisical's UI derives them from environment names by default, so secrets entered in those names can appear in returned slugs. Operators must not put secrets in environment names or slugs. Secrets placed in identifiers or key names are out of scope.\n\nThe provider assumes an honest Infisical server and protects against careless human entry of secrets in free text. It does not match submitted values or defend against a malicious server encoding values into valid identifiers. Submitted secret data never joins credential redaction, so later calls in the same program keep their authorized arguments. Client credentials and tokens retain request-scoped credential protection.\n\nThis finite surface has no guarded raw-REST tool. These endpoints return complete collections without a page cursor; narrow the path and avoid recursive/value listings to stay below Connecta's 8 MiB response ceiling. Temporary result paging does not reduce the upstream response size.\n\nUniversal Auth tokens remain in memory only and refresh before expiry. Reads may retry once after a rejected token. Writes refresh a rejected token for a later explicit call and return the auth failure without resending; reconcile the target before another call. Recovery echoes marked `argsRedacted` omit secret values, secret comments, and folder descriptions, so any new call requires the original arguments. The operator's machine identity must belong to each project with the right role; a 403 needs an operator to fix membership or role. US cloud is the default; set `baseUrl: \"https://eu.infisical.com/api\"` for EU cloud or your self-hosted HTTPS API base including `/api`. Preserve the connector id and the `clientId`/`clientSecret` fields when migrating existing credentials.\n\nNo default call budget is assumed. Operators can supply `callAdmission` for their instance's limits. The credential test performs a Universal Auth login only, without reading projects or secrets.\n",
-    "instructionsHeading": "Organization instructions",
-    "fragments": {
-        "guide": "Start with `list_projects` for project IDs and environment slugs, then `list_folders` for absolute paths.\n\nKeep value reads narrow. `list_secrets` returns identifiers only by default, even if the server sends values or comments; use `get_secret` or opt into `includeValues` only when needed. These explicit reads return secrets, including values and comments. Comments are available only from these value-read tools. Do not echo values unless the user asks. Imports follow the same value policy.\n\nValues can reference secrets as `${env.KEY}`. Value reads expand references by default. Use `expandReferences: false` to read the literal reference before editing; updating a value changes only that secret, not the secrets it references. Updates send only named changes. Writes omit values and report `pendingApproval` when an environment's change policy requires approval.\n\nEvery value-free result returns only checked identifiers: UUID or legacy 24-hex IDs, secret keys, positive integer versions, known type/approval enums, environment and tag slugs, absolute paths, and ISO timestamps. Projects expose IDs and environment identifiers; folders expose IDs and paths. Project slugs are withheld because Infisical can derive them from free-text project names. Comments, descriptions, free-form names, reminder notes, and arbitrary nested objects are withheld. `metadataOmitted: true` reports dropped or unavailable metadata; success or pending-approval context remains available. Identifier fields outside the conservative grammar are dropped.\n\nKnown, accepted residual risk: environment slugs are returned as required routing identifiers. Infisical's UI derives them from environment names by default, so secrets entered in those names can appear in returned slugs. Operators must not put secrets in environment names or slugs. Secrets placed in identifiers or key names are out of scope.\n\nThe provider assumes an honest Infisical server and protects against careless human entry of secrets in free text. It does not match submitted values or defend against a malicious server encoding values into valid identifiers. Submitted secret data never joins credential redaction, so later calls in the same program keep their authorized arguments. Client credentials and tokens retain request-scoped credential protection.\n\nThis finite surface has no guarded raw-REST tool. These endpoints return complete collections without a page cursor; narrow the path and avoid recursive/value listings to stay below Connecta's 8 MiB response ceiling. Temporary result paging does not reduce the upstream response size.\n\nUniversal Auth tokens remain in memory only and refresh before expiry. Reads may retry once after a rejected token. Writes refresh a rejected token for a later explicit call and return the auth failure without resending; reconcile the target before another call. Recovery echoes marked `argsRedacted` omit secret values, secret comments, and folder descriptions, so any new call requires the original arguments. The operator's machine identity must belong to each project with the right role; a 403 needs an operator to fix membership or role. US cloud is the default; set `baseUrl: \"https://eu.infisical.com/api\"` for EU cloud or your self-hosted HTTPS API base including `/api`. Preserve the connector id and the `clientId`/`clientSecret` fields when migrating existing credentials.\n\nNo default call budget is assumed. Operators can supply `callAdmission` for their instance's limits. The credential test performs a Universal Auth login only, without reading projects or secrets.\n"
-    }
-};

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

@@ -1,55 +0,0 @@
-import { type RemoteMcpAuth } from "../../connectors/remote-mcp.js";
-import { type ProviderOptions } from "../../provider.js";
-import type { ConnectorCallAdmissionPolicy } from "../../types.js";
-/** Which of Linear's two hosted MCP endpoints this connection is bound to. */
-export type LinearAccess = "read-write" | "read-only";
-/**
- * Linear publishes two hosted endpoints. `read-only` is not a client-side
- * filter: it advertises the `read` scope alone, so the token minted for it
- * cannot reach Linear's write APIs at all. The deprecated `/sse` transport is
- * deliberately absent — it now answers 404.
- */
-export declare const LINEAR_MCP_ENDPOINTS: Readonly<Record<LinearAccess, string>>;
-export interface LinearOptions extends ProviderOptions {
-    /**
-     * Human-readable display name; defaults to "Linear", or
-     * "Linear (read-only)" when `access` is `"read-only"`.
-     */
-    title?: string;
-    /** Which workspace this is and what decisions it answers. */
-    purpose: string;
-    /**
-     * Endpoint selection, required with no default. Linear's read-only endpoint
-     * advertises the `read` scope alone, so its token cannot reach the write APIs
-     * — a stronger guarantee than any annotation. Neither default is safe:
-     * read-write hands out access nobody asked for, and read-only breaks a
-     * writing deployment at runtime, where no agent can repair it.
-     */
-    access: LinearAccess;
-    /**
-     * OAuth 2.1 with dynamic client registration by default. Linear's MCP server
-     * also accepts a personal API key in `Authorization: Bearer` — note this is
-     * the MCP endpoint's own documented contract, not the GraphQL API convention.
-     * A personal key carries the acting user's full permissions, so pair it with
-     * `access: "read-only"` unless the deployment genuinely writes.
-     */
-    auth?: RemoteMcpAuth;
-    /** Workspace-specific conventions appended to the maintained provider guide. */
-    instructions?: string;
-    /**
-     * Optional per-runtime policy. There is no default: Linear documents no
-     * MCP-specific limit, the GraphQL limits it rides are metered per user per
-     * hour (and its own page disagrees with itself on the API-key figure), and
-     * Connecta's counter is per runtime. Only the operator knows the workspace.
-     */
-    callAdmission?: ConnectorCallAdmissionPolicy;
-}
-/** A maintained Linear hosted-MCP connection. */
-export declare const linear: import("../../provider.js").ProviderFactory<LinearOptions>;
-/**
- * The reviewed classification in the legacy manifest form.
- *
- * @deprecated Read `linear.definition.classify` instead. This alias is derived
- * from it and retained for existing public imports.
- */
-export declare const LINEAR_VETTED_CATALOG: import("../../catalog-drift.js").VettedCatalog;

package/dist/providers/linear/index.js

@@ -1,352 +0,0 @@
-import { skill } from "./skill.generated.js";
-import { remoteMcp, withCredentialDefaults } from "../../connectors/remote-mcp.js";
-import { keys, optionsOf } from "../../config-schema.js";
-import { REMOTE_MCP_AUTH } from "../../connectors/option-shapes.js";
-import { reviewedCatalog } from "../../catalog-drift.js";
-import { defineProvider, PROVIDER_COMMON } from "../../provider.js";
-/**
- * Linear publishes two hosted endpoints. `read-only` is not a client-side
- * filter: it advertises the `read` scope alone, so the token minted for it
- * cannot reach Linear's write APIs at all. The deprecated `/sse` transport is
- * deliberately absent — it now answers 404.
- */
-export const LINEAR_MCP_ENDPOINTS = {
-    "read-write": "https://mcp.linear.app/mcp",
-    "read-only": "https://mcp.linear.app/mcp/readonly",
-};
-/**
- * Every `save_*` is destructive because Linear's `save_*` tools are upserts:
- * omitting a record id creates, supplying one overwrites in place, and the
- * schema cannot tell them apart.
- */
-const UPSERT = "An upsert: supplying a record id overwrites that record in place, and the schema cannot tell a create from an update.";
-/**
- * The release-reviewed classification (P5), used both to classify a live tool
- * and as the record the drift check compares against, so the annotation a
- * caller gets and the verdict a check reads can never disagree. It is a
- * superset: Linear's hosted `tools/list` varies by plan and enabled features,
- * so a name this workspace never returns costs nothing, while an unlisted new
- * one fails closed. The genuine creates — the `create_*_label` and attachment
- * tools — are plain writes rather than destructive.
- */
-const LINEAR_CLASSIFICATION = {
-    tools: {
-        // Issues
-        list_issues: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list issues data without changing workspace state.",
-        },
-        get_issue: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get issue data without changing workspace state.",
-        },
-        list_issue_statuses: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list issue statuses data without changing workspace state.",
-        },
-        get_issue_status: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get issue status data without changing workspace state.",
-        },
-        list_issue_labels: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list issue labels data without changing workspace state.",
-        },
-        save_issue: { verdict: "destructive", reason: UPSERT },
-        create_issue_label: {
-            "verdict": "write",
-            "reason": "Creates Linear state through create_issue_label; the reviewed operation only appends.",
-        },
-        // Projects
-        list_projects: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list projects data without changing workspace state.",
-        },
-        get_project: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get project data without changing workspace state.",
-        },
-        list_project_labels: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list project labels data without changing workspace state.",
-        },
-        save_project: { verdict: "destructive", reason: UPSERT },
-        // Milestones
-        list_milestones: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list milestones data without changing workspace state.",
-        },
-        get_milestone: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get milestone data without changing workspace state.",
-        },
-        save_milestone: { verdict: "destructive", reason: UPSERT },
-        // Initiatives
-        list_initiatives: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list initiatives data without changing workspace state.",
-        },
-        get_initiative: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get initiative data without changing workspace state.",
-        },
-        list_initiative_labels: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list initiative labels data without changing workspace state.",
-        },
-        save_initiative: { verdict: "destructive", reason: UPSERT },
-        create_initiative_label: {
-            "verdict": "write",
-            "reason": "Creates Linear state through create_initiative_label; the reviewed operation only appends.",
-        },
-        // Cycles
-        list_cycles: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list cycles data without changing workspace state.",
-        },
-        // Comments
-        list_comments: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list comments data without changing workspace state.",
-        },
-        save_comment: { verdict: "destructive", reason: UPSERT },
-        delete_comment: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through delete_comment.",
-        },
-        // Documents
-        list_documents: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list documents data without changing workspace state.",
-        },
-        get_document: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get document data without changing workspace state.",
-        },
-        save_document: { verdict: "destructive", reason: UPSERT },
-        // Teams and users
-        list_teams: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list teams data without changing workspace state.",
-        },
-        get_team: { "verdict": "read", "reason": "Reads existing Linear get team data without changing workspace state." },
-        list_users: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list users data without changing workspace state.",
-        },
-        get_user: { "verdict": "read", "reason": "Reads existing Linear get user data without changing workspace state." },
-        get_workspace: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get workspace data without changing workspace state.",
-        },
-        // Templates
-        list_templates: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list templates data without changing workspace state.",
-        },
-        get_template: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get template data without changing workspace state.",
-        },
-        // Status updates
-        get_status_updates: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get status updates data without changing workspace state.",
-        },
-        save_status_update: { verdict: "destructive", reason: UPSERT },
-        delete_status_update: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through delete_status_update.",
-        },
-        // Releases
-        list_release_pipelines: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list release pipelines data without changing workspace state.",
-        },
-        list_releases: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list releases data without changing workspace state.",
-        },
-        get_release: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get release data without changing workspace state.",
-        },
-        list_release_notes: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list release notes data without changing workspace state.",
-        },
-        get_release_note: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get release note data without changing workspace state.",
-        },
-        save_release: { verdict: "destructive", reason: UPSERT },
-        save_release_note: { verdict: "destructive", reason: UPSERT },
-        // Code review
-        list_diffs: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list diffs data without changing workspace state.",
-        },
-        get_diff: { "verdict": "read", "reason": "Reads existing Linear get diff data without changing workspace state." },
-        get_diff_threads: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get diff threads data without changing workspace state.",
-        },
-        save_diff_comment: { verdict: "destructive", reason: UPSERT },
-        resolve_diff_thread: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through resolve_diff_thread.",
-        },
-        delete_diff_comment: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through delete_diff_comment.",
-        },
-        submit_diff_review: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through submit_diff_review.",
-        },
-        merge_diff: { "verdict": "destructive", "reason": "Changes or removes existing Linear state through merge_diff." },
-        // Attachments
-        get_attachment: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get attachment data without changing workspace state.",
-        },
-        prepare_attachment_upload: {
-            verdict: "write",
-            reason: "Mints an upload URL: a side effect, but it changes no existing record.",
-        },
-        create_attachment_from_upload: {
-            "verdict": "write",
-            "reason": "Creates Linear state through create_attachment_from_upload; the reviewed operation only appends.",
-        },
-        create_attachment: {
-            "verdict": "write",
-            "reason": "Creates Linear state through create_attachment; the reviewed operation only appends.",
-        },
-        delete_attachment: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through delete_attachment.",
-        },
-        // Explicit issue access.
-        share_issue: {
-            verdict: "destructive",
-            reason: "Changes who can see an existing issue.",
-        },
-        unshare_issue: {
-            verdict: "destructive",
-            reason: "Changes who can see an existing issue.",
-        },
-        // Agent skills
-        list_agent_skills: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list agent skills data without changing workspace state.",
-        },
-        get_agent_skill: {
-            "verdict": "read",
-            "reason": "Reads existing Linear get agent skill data without changing workspace state.",
-        },
-        // Documentation search
-        search_documentation: {
-            "verdict": "read",
-            "reason": "Reads existing Linear search documentation data without changing workspace state.",
-        },
-        // Customer requests (plan-gated)
-        list_customers: {
-            "verdict": "read",
-            "reason": "Reads existing Linear list customers data without changing workspace state.",
-        },
-        save_customer: { verdict: "destructive", reason: UPSERT },
-        delete_customer: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through delete_customer.",
-        },
-        save_customer_need: { verdict: "destructive", reason: UPSERT },
-        delete_customer_need: {
-            "verdict": "destructive",
-            "reason": "Changes or removes existing Linear state through delete_customer_need.",
-        },
-        // Markdown helper.
-        extract_images: {
-            verdict: "read",
-            reason: "Reads images out of content it is handed and touches no workspace state; the hosted server ships it annotated readOnlyHint: true and idempotentHint: true.",
-        },
-    },
-};
-/**
- * Connection-independent conventions. The access note and purpose lead the
- * rendered guide; deployment instructions follow it.
- */
-/** The closed options linear() accepts, checked against LinearOptions. */
-const LINEAR_OPTIONS = optionsOf()({
-    ...PROVIDER_COMMON,
-    ...keys("access"),
-    auth: REMOTE_MCP_AUTH,
-});
-/** A maintained Linear hosted-MCP connection. */
-export const linear = defineProvider({
-    name: "linear",
-    title: "Linear",
-    kind: "mcp",
-    readme: "Linear",
-    bundle: { "baselineGzip": 127244, "maxGzip": 187244 },
-    skill,
-    options: LINEAR_OPTIONS,
-    classify: LINEAR_CLASSIFICATION,
-    create(id, options, provider) {
-        const access = options.access;
-        if (access !== "read-write" && access !== "read-only") {
-            throw new Error(`linear("${id}") requires access "read-write" or "read-only".`);
-        }
-        // Leads the guide because discovery summarizes a connector by its first
-        // content line: whether this connection can write at all is the one thing
-        // an agent must know before it opens the guide, and `search_tools` shows
-        // the summary without the description.
-        const accessNote = access === "read-only"
-            ? "Read-only connection: bound to Linear's read-only endpoint, whose token is scope-limited downstream, so every write fails at Linear regardless of arguments. Route writes to a connector configured for read-write access."
-            : "Read-write connection: treat every `save_`, `create_`, `delete_`, `resolve_`, `submit_`, and `merge_` operation as a write. Connecta classifies the maintained writes explicitly, and a read-only endpoint refuses them. Unknown tools without an explicit, uncontradicted read annotation fail closed.";
-        return remoteMcp(id, {
-            url: LINEAR_MCP_ENDPOINTS[access],
-            ...provider.connectorOptions,
-            // The title is what browse-time discovery renders; a read-only
-            // connection says so there rather than only in a description the caller
-            // may not see.
-            title: options.title ?? (access === "read-only" ? "Linear (read-only)" : "Linear"),
-            description: access === "read-only"
-                ? `Linear issue tracking and project planning (read-only) — ${options.purpose}`
-                : `Linear issue tracking and project planning — ${options.purpose}`,
-            // Linear's MCP endpoint takes an API key the same way it takes an OAuth
-            // token — `Authorization: Bearer <yourtoken>` — so only the slot copy is
-            // provider-specific and the bearer framing default stands. The
-            // bare-header convention belongs to Linear's GraphQL API, not to this
-            // endpoint.
-            auth: withCredentialDefaults(options.auth ?? { type: "oauth" }, {
-                credential: {
-                    label: "Personal API key",
-                    description: "A Linear personal API key. It carries the issuing user's full workspace access and is stored encrypted; the read-only endpoint still limits what it can reach.",
-                    placeholder: "lin_api_…",
-                },
-            }),
-            requireHttps: true,
-            classify: provider.classify,
-            usageGuide: provider.usageGuide({
-                context: [accessNote, `Workspace purpose: ${options.purpose}`],
-                // Explicit rather than derived. The derived summary would truncate the
-                // access note mid-sentence at 120 characters, and the one thing a
-                // browsing agent must not get wrong is whether this connection can
-                // write at all ([#342](https://github.com/zackbart/connecta/issues/342)).
-                // Not `required`: Linear's own schemas describe each call correctly;
-                // the guide adds cross-tool sequence advice worth reading before a
-                // write, not before every read.
-                summary: access === "read-only"
-                    ? "Read-only: every write fails at Linear. Id resolution, upsert semantics, and cursor paging."
-                    : "Read-write. Id resolution, `save_*` upsert semantics, plan-gated areas, and cursor paging.",
-            }),
-        });
-    },
-});
-/**
- * The reviewed classification in the legacy manifest form.
- *
- * @deprecated Read `linear.definition.classify` instead. This alias is derived
- * from it and retained for existing public imports.
- */
-export const LINEAR_VETTED_CATALOG = reviewedCatalog(linear.definition.classify, 'defineProvider("linear")');

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

@@ -1,8 +0,0 @@
-// Generated by scripts/generate-providers.mjs; do not edit.
-export const skill = {
-    "content": "- Issue arguments use `state`, not `status`. Resolve team-specific states through `list_issue_statuses` and use the value format required by the live input schema.\n- Resolve identity before acting. `list_teams`, `list_users`, `list_projects`, `list_issue_statuses`, and `list_issue_labels` return the ids that create and update arguments expect; do not guess a team, status, label, or assignee id.\n- Issues carry a human identifier like `ENG-123` — team key, dash, number — alongside a UUID. Use the identifier the request gave you and resolve it with `get_issue` or `list_issues` when a tool wants an id; never fabricate an identifier or renumber one.\n- `save_*` tools are upserts: omit the record id to create, supply it to update in place. Read the record first when you mean to update, and send only the fields you intend to change — an upsert overwrites what you restate.\n- Labels are the exception to that naming: `create_issue_label` and `create_initiative_label` only ever create.\n- Projects, milestones, and initiatives nest: initiatives contain projects, projects contain milestones and issues, and cycles are per-team time boxes. Scope a search by team or project rather than listing the workspace and filtering afterwards.\n- List tools paginate with a cursor. Thread the returned cursor for the next page instead of raising the page size, and reduce pages inside `execute_code` before returning them.\n- This workspace's catalog is not the whole product. Customer requests, releases, and code review are plan- and feature-gated, so search the catalog for what this connector actually exposes rather than assuming a tool exists.\n- Linear meters the underlying API per user per hour, shared with everything else that credential does. Reuse discovery results within a run and avoid speculative fan-out.\n- An `auth_required` failure means this connector's Linear authorization is missing or expired: run `authorize_connector` for this connector id, then retry the same call unchanged.",
-    "instructionsHeading": "Workspace instructions",
-    "fragments": {
-        "content": "- Issue arguments use `state`, not `status`. Resolve team-specific states through `list_issue_statuses` and use the value format required by the live input schema.\n- Resolve identity before acting. `list_teams`, `list_users`, `list_projects`, `list_issue_statuses`, and `list_issue_labels` return the ids that create and update arguments expect; do not guess a team, status, label, or assignee id.\n- Issues carry a human identifier like `ENG-123` — team key, dash, number — alongside a UUID. Use the identifier the request gave you and resolve it with `get_issue` or `list_issues` when a tool wants an id; never fabricate an identifier or renumber one.\n- `save_*` tools are upserts: omit the record id to create, supply it to update in place. Read the record first when you mean to update, and send only the fields you intend to change — an upsert overwrites what you restate.\n- Labels are the exception to that naming: `create_issue_label` and `create_initiative_label` only ever create.\n- Projects, milestones, and initiatives nest: initiatives contain projects, projects contain milestones and issues, and cycles are per-team time boxes. Scope a search by team or project rather than listing the workspace and filtering afterwards.\n- List tools paginate with a cursor. Thread the returned cursor for the next page instead of raising the page size, and reduce pages inside `execute_code` before returning them.\n- This workspace's catalog is not the whole product. Customer requests, releases, and code review are plan- and feature-gated, so search the catalog for what this connector actually exposes rather than assuming a tool exists.\n- Linear meters the underlying API per user per hour, shared with everything else that credential does. Reuse discovery results within a run and avoid speculative fan-out.\n- An `auth_required` failure means this connector's Linear authorization is missing or expired: run `authorize_connector` for this connector id, then retry the same call unchanged."
-    }
-};

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

@@ -1,57 +0,0 @@
-import { type RemoteMcpAuth } from "../../connectors/remote-mcp.js";
-import type { ConnectorCallAdmissionPolicy } from "../../types.js";
-export type MixpanelRegion = "us" | "eu" | "in";
-export declare const MIXPANEL_MCP_ENDPOINTS: Readonly<Record<MixpanelRegion, string>>;
-interface MixpanelCommonOptions {
-    /**
-     * Human-readable display name; defaults to "Mixpanel (<region>)". The region
-     * rides the title because a project lives in exactly one residency and
-     * discovery shows the title before anything else.
-     */
-    title?: string;
-    /** Downstream auth ownership. Defaults to one shared deployment grant. */
-    authScope?: "shared" | "personal";
-    /** Who should use this account and for what decisions. */
-    purpose: string;
-    /**
-     * Data residency region, selecting the matching official endpoint. A wrong
-     * region answers empty rather than wrong, which reads as an empty project.
-     */
-    region?: MixpanelRegion;
-    /** Account-specific conventions appended to the maintained provider guide. */
-    instructions?: string;
-    /** Connector-specific inline result limit; omit to inherit the deployment. */
-    maxResultBytes?: number;
-    /**
-     * Optional per-runtime policy. API mode defaults to 60 calls/hour and five
-     * concurrent calls across all tools and projects. MCP mode has no default:
-     * its per-user hourly quota cannot be modeled by one per-runtime counter.
-     */
-    callAdmission?: ConnectorCallAdmissionPolicy;
-}
-/** The default hosted MCP connection. Existing auth configurations still work. */
-export interface MixpanelMcpOptions extends MixpanelCommonOptions {
-    via?: "mcp";
-    /**
-     * OAuth by default; static headers support Mixpanel service accounts, and
-     * `{ type: "credential" }` takes the same service account as an
-     * operator-managed `username:secret` that Connecta frames for the endpoint.
-     */
-    auth?: RemoteMcpAuth;
-    defaultProjectId?: never;
-}
-/** REST APIs using an operator-managed username:secret service account. */
-export interface MixpanelApiOptions extends MixpanelCommonOptions {
-    via: "api";
-    auth: {
-        type: "credential";
-    };
-    /** Fills an omitted project_id. Explicit ids still reach other granted projects. */
-    defaultProjectId?: number;
-}
-export type MixpanelOptions = MixpanelMcpOptions | MixpanelApiOptions;
-/** Mixpanel hosted MCP by default, or service-account REST with via: "api". */
-export declare const mixpanel: import("../../provider.js").ProviderFactory<MixpanelOptions>;
-/** @deprecated Read `mixpanel.definition.classify` instead. Kept for existing imports. */
-export declare const MIXPANEL_VETTED_CATALOG: import("../../catalog-drift.js").VettedCatalog;
-export {};