@vornrun/connector-sdk 0.6.1 → 0.7.0-beta.10

package/dist/index.d.ts

@@ -1,272 +1,7 @@
+import { C as ConnectorDefinition, b as Connector, c as ConnectorConfig, T as TriggerDefinition, P as PollContext, d as PollOutcome, e as ConnectorItem, N as NormalizedItem, f as PostReceiveOp, A as ActionRequest, B as BundleRequest, a as BundleOutput, g as CheckFinding } from './packaging-DFTuP4fr.js';
+export { h as ActionContext, i as ActionDefinition, j as ActionInputField, k as ActionInputOption, l as ActionInputType, m as ActionOutputField, n as AuthRung, o as CHECK_OWNERS, p as CheckCode, q as CheckOptions, r as ConformanceRun, s as ConnectionSetup, t as ConnectorAuth, u as ConnectorConfigField, v as ConnectorHarness, w as ConnectorIcon, x as ConnectorManifest, y as ConnectorVerification, D as DedupeStrategy, z as DefaultWorkflow, F as FetchContext, H as HarnessOptions, M as MANIFEST_TOOL, E as MAX_PACK_BYTES, G as MAX_POLL_PAGES, I as MockCall, J as MockRoute, K as MockRouteMissError, L as MockRun, O as OPTIONS_TOOL, Q as OptionsContext, R as OptionsLoader, S as PREFLIGHT_TOOL, U as PaginationStrategy, V as PollPage, W as PreflightResult, X as ResilientFetchOptions, Y as RetryPolicy, Z as RunActionOptions, _ as RunPollOptions, $ as StatusSuggestion, a0 as backoffMs, a1 as bundleDependencyFindings, a2 as checkConnector, a3 as connectionSetup, a4 as connectorManifest, a5 as createConnectorHarness, a6 as drainPoll, a7 as esbuildBundle, a8 as escapedMockHttp, a9 as formatFindings, aa as lifecycleScriptFindings, ab as pollToolName, ac as readNearestPackageJson, ad as resilientFetch, ae as retryAfterMs, af as runAction, ag as runConformance, ah as runOptions, ai as runPoll, aj as withMockHttp } from './packaging-DFTuP4fr.js';
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 
-/**
- * Author-facing types for Vorn connectors.
- *
- * A connector written with this SDK runs as an ordinary MCP stdio server, so
- * it is shared as a normal npm package and installed by pointing a Vorn
- * connection at `npx -y <package>`. Nothing about the host app has to change
- * to accept a new connector.
- */
-/** A raw item as the author's code returns it. Only id and title are required. */
-interface ConnectorItem {
-    /** Stable upstream identity. Vorn dedupes on this, so it must not change. */
-    externalId: string | number;
-    title: string;
-    url?: string;
-    description?: string;
-    /** Raw upstream status (`open`, `Active`, `In Progress`, …). */
-    status?: string;
-    labels?: string[];
-    assignee?: string;
-    /**
-     * When the item last changed. Vorn advances its poll cursor from this field,
-     * so it must be monotonic per item and comparable as an ISO 8601 string.
-     * Defaults to poll time when omitted.
-     */
-    updatedAt?: string | Date;
-    /** Extra fields to expose to workflow templates as `{{trigger.item.<key>}}`. */
-    data?: Record<string, unknown>;
-}
-/** A connector item after normalization. This is the exact JSON Vorn sees. */
-interface NormalizedItem extends Record<string, unknown> {
-    externalId: string;
-    title: string;
-    url: string;
-    description: string;
-    status: string;
-    labels: string[];
-    updatedAt: string;
-    assignee?: string;
-}
-/** Declares a value the connector needs at runtime, read from the environment. */
-interface ConnectorConfigField {
-    key: string;
-    label: string;
-    /** Environment variable the value is read from. Defaults to CONSTANT_CASE(key). */
-    env?: string;
-    required?: boolean;
-    /** Secrets are stored encrypted by Vorn and never printed by the CLI. */
-    secret?: boolean;
-    description?: string;
-    default?: string;
-}
-type ConnectorConfig = Record<string, string | undefined>;
-interface PollContext {
-    config: ConnectorConfig;
-    /**
-     * Lower bound the host asked for, when it was able to supply one. Treat it
-     * as a hint: returning older items is safe because Vorn dedupes, but
-     * returning fewer than everything after `since` loses events.
-     */
-    since?: string;
-    /** Opaque cursor previously returned by this trigger, when supplied. */
-    cursor?: string;
-    /** Upper bound on items to return in one page. */
-    limit?: number;
-    /** Injectable clock so tests are deterministic. */
-    now(): string;
-}
-interface PollOutcome {
-    items: ConnectorItem[];
-    nextCursor?: string;
-    hasMore?: boolean;
-}
-/**
- * How the SDK decides which fetched items are new.
- *
- * - `timestamp` — for sources that expose a reliable "last changed" field and
- *   can filter on it. Handles the boundary case where several items share the
- *   newest timestamp, which is the classic source of both duplicates and
- *   silently dropped items.
- * - `lastItem` — for feeds that return newest-first with no dependable
- *   timestamp. The cursor is the newest id already delivered.
- */
-type DedupeStrategy = 'timestamp' | 'lastItem';
-/**
- * What a declarative trigger's `fetch` receives. Deliberately smaller than
- * {@link PollContext}: cursor encoding, ordering, windowing and de-duplication
- * are the SDK's job, so the author only has to answer "what is there now?".
- */
-interface FetchContext {
-    config: ConnectorConfig;
-    /**
-     * With `dedupe: 'timestamp'`, everything changed at or after this instant is
-     * worth returning. Absent on the very first poll. Returning a little too
-     * much is safe — the SDK drops what was already delivered.
-     */
-    since?: string;
-    /**
-     * With `dedupe: 'lastItem'`, the newest id already delivered. Absent on the
-     * very first poll. Return the feed newest-first and the SDK will stop there.
-     */
-    lastItemId?: string;
-    /** Upper bound on items worth returning in one call. */
-    limit?: number;
-    /** Injectable clock so tests are deterministic. */
-    now(): string;
-}
-/**
- * What an upstream state should become when an item is imported as a task.
- *
- * A suggestion, not a rule: it seeds the connection form, and the person
- * setting it up can change it. Without any, everything a connector imports
- * lands as `todo` regardless of whether it was closed a year ago.
- */
-interface StatusSuggestion {
-    /** The value the connector reports in `ConnectorItem.status`. */
-    upstream: string;
-    suggestedLocal: 'todo' | 'in_progress' | 'in_review' | 'done' | 'cancelled';
-}
-/**
- * The workflow to create when a connection is made.
- *
- * A connector that fires on a schedule is useless until something polls it, and
- * expecting every person to build that workflow by hand is how a connection
- * ends up configured and silent. Seeded workflows are ordinary, visible and
- * editable — the schedule is a starting point, not a fixed rule.
- */
-interface DefaultWorkflow {
-    name: string;
-    defaultCronFromMinutes: number;
-}
-interface TriggerBase {
-    /** Event key, e.g. `workItemCreated`. Becomes the `poll_<type>` MCP tool. */
-    type: string;
-    label: string;
-    description?: string;
-    /** Seeds the connection's status mapping; the person setting it up owns it. */
-    statusMapping?: StatusSuggestion[];
-    /** Seeds a polling workflow when a connection is created. */
-    defaultWorkflow?: DefaultWorkflow;
-    /**
-     * Representative items. `vorn-connector check` replays these through the
-     * real dedupe pipeline, so a connector can be verified before anyone has
-     * credentials for it.
-     */
-    sample?: ConnectorItem[];
-}
-/**
- * A trigger is either declarative or hand-written, never both — expressed as a
- * union so the invalid combinations are a type error at authoring time rather
- * than a throw when the connector is first loaded.
- */
-type TriggerDefinition = TriggerBase & ({
-    /**
-     * Declarative polling: return what the source has and let the SDK
-     * handle cursors and de-duplication.
-     */
-    dedupe: DedupeStrategy;
-    fetch(context: FetchContext): Promise<ConnectorItem[]> | ConnectorItem[];
-    poll?: never;
-} | {
-    /**
-     * Full control over cursors and paging. Use only when the source's
-     * paging cannot be expressed as "give me everything since X".
-     */
-    poll(context: PollContext): Promise<PollOutcome> | PollOutcome;
-    dedupe?: never;
-    fetch?: never;
-});
-interface ActionInputField {
-    key: string;
-    label: string;
-    type?: 'string' | 'number' | 'boolean';
-    required?: boolean;
-    description?: string;
-}
-/**
- * A field the action is known to return. Declaring these is optional — extra
- * keys always pass through — but declared fields show up in Vorn's variable
- * autocomplete as `{{steps.<action>.<key>}}`.
- */
-interface ActionOutputField {
-    key: string;
-    type?: 'string' | 'number' | 'boolean';
-    description?: string;
-}
-interface ActionContext {
-    config: ConnectorConfig;
-    now(): string;
-}
-interface ActionDefinition {
-    /** Action key, e.g. `closeWorkItem`. Becomes an MCP tool of the same name. */
-    type: string;
-    label: string;
-    description?: string;
-    /**
-     * Whether repeating the call with the same arguments is safe. Surfaced in
-     * the MCP tool description, because an agent retrying a failed step has no
-     * other way to know whether it is about to create a second issue.
-     */
-    idempotent?: boolean;
-    inputs?: ActionInputField[];
-    outputs?: ActionOutputField[];
-    run(args: Record<string, unknown>, context: ActionContext): Promise<Record<string, unknown> | void> | Record<string, unknown> | void;
-}
-/**
- * A connector's own glyph, so an installed connector is recognizable in a list
- * rather than sharing one generic icon with every other one.
- *
- * Path data only — deliberately not markup. Vorn draws these itself as
- * `<path d="...">` inside an `<svg>` it owns, so a connector cannot inject
- * elements, scripts or external references into the app rendering it.
- */
-interface ConnectorIcon {
-    /** Defaults to `0 0 24 24`. */
-    viewBox?: string;
-    /** SVG path `d` data, drawn with `fill="currentColor"` so it inherits color. */
-    paths: string[];
-}
-/**
- * What a connector reports about its own readiness.
- *
- * `message` is shown to the user verbatim, so it should say what to do rather
- * than what went wrong — "run `gh auth login`" beats "not authenticated".
- */
-interface PreflightResult {
-    ok: boolean;
-    message?: string;
-}
-interface ConnectorDefinition {
-    /** Stable connector id, e.g. `azure-devops`. */
-    id: string;
-    name: string;
-    version?: string;
-    description?: string;
-    icon?: ConnectorIcon;
-    config?: ConnectorConfigField[];
-    triggers?: TriggerDefinition[];
-    actions?: ActionDefinition[];
-    /**
-     * Whether this connector could work right now, asked before anyone waits on
-     * a poll.
-     *
-     * A connector whose credentials come from config fields does not need this:
-     * a missing field is already a visible, nameable error. One that borrows an
-     * external tool's login — `gh auth login`, `az login` — has no field to be
-     * missing, so without this the first sign that the tool is absent or signed
-     * out is a poll failing some minutes after the connection was saved.
-     *
-     * Answer `ok: false` with a message saying what to do about it. Throwing is
-     * equivalent — the server catches it and reports the same shape with the
-     * error's message — so there is one result for a caller to read and no
-     * behaviour riding on which you choose. Prefer returning when the state is
-     * one you recognise, because then you get to write the sentence.
-     *
-     * Absent means there is nothing to check, which is not the same answer as a
-     * check that passed.
-     */
-    preflight?(): Promise<PreflightResult> | PreflightResult;
-}
-/** A validated definition. Every accessor below is guaranteed non-null. */
-interface Connector extends ConnectorDefinition {
-    readonly version: string;
-    readonly config: ConnectorConfigField[];
-    readonly triggers: TriggerDefinition[];
-    readonly actions: ActionDefinition[];
-}
-
 /** Environment variable a config field reads from, e.g. `apiToken` → `API_TOKEN`. */
 declare function envNameFor(key: string, explicit?: string): string;
 /**
@@ -285,36 +20,6 @@ declare function defineConnector(definition: ConnectorDefinition): Connector;
  */
 declare function resolveConfig(connector: Connector, env?: NodeJS.ProcessEnv): ConnectorConfig;
 
-interface CheckFinding {
-    /** `error` means the connector will misbehave in Vorn; `warn` is advisory. */
-    level: 'error' | 'warn';
-    code: string;
-    /** Which part of the connector the finding is about. */
-    target: string;
-    message: string;
-}
-interface CheckOptions {
-    /**
-     * Poll every trigger against the real source. Off by default, so a check
-     * runs on declared `sample` items and the definition alone.
-     */
-    live?: boolean;
-    /** Credentials, required by `live`. */
-    config?: ConnectorConfig;
-    now?: () => string;
-}
-/**
- * Check a connector against the contract Vorn relies on.
- *
- * The point is a feedback loop: a connector — hand-written or generated — can
- * be verified before it is ever installed, catching the failures that are
- * otherwise invisible until duplicate tasks show up in someone's inbox days
- * later.
- */
-declare function checkConnector(connector: Connector, options?: CheckOptions): Promise<CheckFinding[]>;
-/** Render findings for a terminal. Returns an empty string when all clear. */
-declare function formatFindings(findings: CheckFinding[]): string;
-
 /**
  * Run a declarative trigger: call the author's `fetch`, then apply the chosen
  * dedupe strategy.
@@ -341,114 +46,88 @@ declare function normalizeItem(item: ConnectorItem, polledAt: string): Normalize
  */
 declare function normalizeItems(items: ConnectorItem[], polledAt: string): NormalizedItem[];
 
-interface PollPage {
-    items: NormalizedItem[];
-    nextCursor?: string;
-    hasMore: boolean;
-}
-interface RunPollOptions {
-    config?: ConnectorConfig;
-    since?: string;
-    cursor?: string;
-    limit?: number;
-    now?: () => string;
+/** The value at a dotted path, or undefined if any step is missing. */
+declare function valueAt(value: unknown, path: string): unknown;
+/** Run a response through the declared ops, left to right. */
+declare function applyPostReceive(value: unknown, ops: PostReceiveOp[] | undefined): unknown;
+
+interface RequestScope {
+    args: Record<string, unknown>;
+    config: ConnectorConfig;
 }
-/** Longest chain of pages `drainPoll` will follow before calling it a bug. */
-declare const MAX_POLL_PAGES = 1000;
 /**
- * Run one poll page and normalize it. Shared by the MCP server, the CLI and
- * the test harness so all three observe exactly what Vorn will observe.
+ * How a substituted value is written into its surroundings.
+ *
+ * A value's meaning depends on where it lands: a path segment has to be
+ * escaped, a header has characters it may not contain at all. Passing that
+ * decision in means the substitution is made safe once, here, instead of by
+ * every author who interpolates an argument.
  */
-declare function runPoll(connector: Connector, triggerType: string, options?: RunPollOptions): Promise<PollPage>;
+type Substitution = (value: string, source: 'args' | 'config') => string;
 /**
- * Follow `hasMore` to the end of a trigger's backlog. Mirrors how Vorn drains
- * a connector, including its refusal to follow a cursor that does not move —
- * so an author sees the infinite loop in a unit test instead of in the app.
+ * Resolve `{{args.x}}` and `{{config.y}}` inside a value.
+ *
+ * A whole-string placeholder keeps the referenced value's own type, so a body
+ * can carry a number or an object; a placeholder among other text is rendered
+ * into the string. An unset reference resolves to `undefined` on its own and to
+ * the empty string when it is part of a larger one, which is what lets an
+ * optional argument simply not appear.
+ *
+ * With a `substitute`, every resolved value passes through it — including a
+ * whole-string one, which then arrives as text rather than keeping its type,
+ * because a place that needs escaping is a place that holds a string.
  */
-declare function drainPoll(connector: Connector, triggerType: string, options?: RunPollOptions): Promise<NormalizedItem[]>;
-interface RunActionOptions {
-    config?: ConnectorConfig;
-    now?: () => string;
+declare function resolveTemplates(value: unknown, scope: RequestScope, substitute?: Substitution): unknown;
+interface ResolvedRequest {
+    url: string;
+    method: string;
+    headers: Record<string, string>;
+    body?: string;
 }
-/**
- * Run an action with its declared inputs validated and coerced. Vorn renders
- * every action argument as a template string, so numbers and booleans arrive
- * as text and have to be converted back here.
- */
-declare function runAction(connector: Connector, actionType: string, args: Record<string, unknown>, options?: RunActionOptions): Promise<Record<string, unknown>>;
-
-/** MCP tool name a trigger is served under. */
-declare function pollToolName(triggerType: string): string;
-/** Tool that reports the connector's manifest and setup hints. */
-declare const MANIFEST_TOOL = "vorn_connector_manifest";
-/**
- * Tool that reports whether the connector can run right now. Present only when
- * the connector declares a `preflight`, so its absence means "nothing to
- * check" rather than "check passed".
- */
-declare const PREFLIGHT_TOOL = "vorn_connector_preflight";
-interface ConnectionSetup {
-    connectorId: string;
-    triggerType: string;
-    /** Values to paste into Vorn's MCP connection form. */
-    filters: {
-        pollTool: string;
-        itemsPath: 'items';
-        idField: 'externalId';
-        timestampField: 'updatedAt';
-        titleField: 'title';
-        urlField: 'url';
-        cursorArg: 'cursor';
-        cursorPath: 'nextCursor';
-    };
-    /** Environment variable names the connector reads. */
-    env: Array<{
-        name: string;
-        required: boolean;
-        secret: boolean;
-        description?: string;
-    }>;
+/** Build the exact call a declared request makes, with its templates resolved. */
+declare function resolveRequest(request: ActionRequest, scope: RequestScope): ResolvedRequest;
+interface SendOptions {
+    fetchImpl: typeof fetch;
 }
 /**
- * Describe how to wire one trigger into a Vorn MCP connection.
+ * The action's result, as Vorn stores it.
  *
- * Every SDK connector normalizes to the same field names, so this mapping is
- * fixed; it is generated rather than documented so a rename in the SDK cannot
- * drift away from the setup instructions users copy. `cursorArg` hands the
- * connector back its own cursor each poll, which is what lets its dedupe
- * strategy — rather than Vorn's timestamp comparison — decide what is new.
- */
-declare function connectionSetup(connector: Connector, triggerType: string): ConnectionSetup;
-interface ConnectorManifest {
-    id: string;
-    name: string;
-    version: string;
-    description?: string;
-    icon?: ConnectorIcon;
-    triggers: Array<{
-        type: string;
-        label: string;
-        description?: string;
-        /** Seeds a connection's status mapping; absent when the connector was silent. */
-        statusMapping?: StatusSuggestion[];
-        /** Seeds the polling workflow created with the connection. */
-        defaultWorkflow?: DefaultWorkflow;
-        setup: ConnectionSetup;
-    }>;
-    actions: Array<{
-        type: string;
-        label: string;
-        description?: string;
-        inputs: Array<{
-            key: string;
-            label: string;
-            type: string;
-            required: boolean;
-        }>;
-    }>;
-}
-/** Full machine-readable description of a connector, served over MCP and printed by the CLI. */
-declare function connectorManifest(connector: Connector): ConnectorManifest;
+ * A step's output is a record, so a response that is a list becomes `items` —
+ * the name the rest of this SDK already uses for one — and any other bare
+ * value becomes `result`.
+ */
+declare function asOutput(value: unknown): Record<string, unknown>;
+/** Longest chain of pages a declared request will follow before calling it a bug. */
+declare const MAX_REQUEST_PAGES = 100;
+/** The URL of the next page, as a paged HTTP API states it in its `Link` header. */
+declare function nextLink(header: string | null): string | undefined;
+/** Run a declared request end to end: resolve, send, follow its pages, reshape. */
+declare function executeRequest(request: ActionRequest, postReceive: PostReceiveOp[] | undefined, scope: RequestScope, options: SendOptions): Promise<Record<string, unknown>>;
+
+interface PackOptions {
+    /** Module specifier the connector was loaded from, bundled as the pack entry. */
+    entry: string;
+    /** Directory the `.vorn.tgz` is written to; defaults to the working directory. */
+    outDir?: string;
+    /** Directory module specifiers resolve from; defaults to the working directory. */
+    resolveDir?: string;
+    /** SDK specifier the generated stdio entry imports; overridden in tests. */
+    sdkModule?: string;
+    /** Size ceiling for the written archive; defaults to `MAX_PACK_BYTES`. */
+    maxBytes?: number;
+    /** Replaced in tests so packing does not shell out to a bundler. */
+    bundle?(request: BundleRequest): Promise<BundleOutput>;
+}
+interface PackResult {
+    findings: CheckFinding[];
+    /** Absolute path of the written pack; absent when a gate failed. */
+    file?: string;
+    bytes?: number;
+}
+/** File name Vorn recognizes as a connector pack. */
+declare function packFileName(connector: Connector): string;
+/** The entry is generated, not the author's bin, so every pack launches alike. */
+declare function packConnector(connector: Connector, options: PackOptions): Promise<PackResult>;
 
 interface ConnectorServerOptions {
     /** Resolved connector configuration. Defaults to reading `process.env`. */
@@ -467,28 +146,34 @@ declare function createConnectorServer(connector: Connector, options?: Connector
 /** Serve a connector on stdio. This is the one line a connector's bin needs. */
 declare function serveConnector(connector: Connector, options?: ConnectorServerOptions): Promise<void>;
 
-interface HarnessOptions {
-    config?: ConnectorConfig;
-    /** Fixed clock, so `updatedAt` defaults and cursors are deterministic. */
-    now?: () => string;
-}
-interface ConnectorHarness {
-    poll(triggerType: string, options?: RunPollOptions): Promise<PollPage>;
-    drain(triggerType: string, options?: RunPollOptions): Promise<NormalizedItem[]>;
-    execute(actionType: string, args?: Record<string, unknown>): Promise<Record<string, unknown>>;
-    manifest(): ConnectorManifest;
-    /**
-     * Poll repeatedly the way Vorn does — carrying the newest `updatedAt`
-     * forward as the watermark — and return only items a real installation
-     * would treat as new. Catches the classic connector bug where a poll
-     * ignores its lower bound and re-delivers the same backlog forever.
-     */
-    pollTwice(triggerType: string, options?: RunPollOptions): Promise<NormalizedItem[]>;
-}
 /**
- * Run a connector in-process, exactly as the MCP server would, without
- * spawning anything. Authors get real assertions in a plain unit test.
+ * The files a new connector starts as.
+ *
+ * A connector is mostly boilerplate — a package that builds, an entry that
+ * serves, a definition, a test that proves it without a network — and getting
+ * that boilerplate right is the slowest part of writing the interesting bit.
+ * Generating it means every connector starts from the same shape, which is
+ * also the shape `check` and `pack` expect to find.
+ *
+ * The files are returned rather than written so the decision of what to write
+ * stays testable, and the writing stays in the CLI.
  */
-declare function createConnectorHarness(connector: Connector, harnessOptions?: HarnessOptions): ConnectorHarness;
+interface ScaffoldOptions {
+    id: string;
+    /** Defaults to the id in title case. */
+    name?: string;
+    description?: string;
+    /** Emit the shape the connectors repository expects of a package inside it. */
+    repoConventions?: boolean;
+}
+interface ScaffoldFile {
+    /** Relative to the directory the connector is created in. */
+    path: string;
+    contents: string;
+}
+/** `acme-tickets` → `Acme Tickets`, so a generated name reads like a name. */
+declare function titleCase(id: string): string;
+/** Every file a new connector starts with, ready to build, check and pack. */
+declare function scaffoldFiles(options: ScaffoldOptions): ScaffoldFile[];
 
-export { type ActionContext, type ActionDefinition, type ActionInputField, type CheckFinding, type CheckOptions, type ConnectionSetup, type Connector, type ConnectorConfig, type ConnectorConfigField, type ConnectorDefinition, type ConnectorHarness, type ConnectorIcon, type ConnectorItem, type ConnectorManifest, type ConnectorServerOptions, type DedupeStrategy, type DefaultWorkflow, type FetchContext, type HarnessOptions, MANIFEST_TOOL, MAX_POLL_PAGES, type NormalizedItem, PREFLIGHT_TOOL, type PollContext, type PollOutcome, type PollPage, type PreflightResult, type RunActionOptions, type RunPollOptions, type StatusSuggestion, type TriggerDefinition, checkConnector, connectionSetup, connectorManifest, createConnectorHarness, createConnectorServer, defineConnector, drainPoll, envNameFor, formatFindings, normalizeItem, normalizeItems, pollToolName, pollWithDedupe, resolveConfig, runAction, runPoll, serveConnector };
+export { ActionRequest, BundleOutput, BundleRequest, CheckFinding, Connector, ConnectorConfig, ConnectorDefinition, ConnectorItem, type ConnectorServerOptions, MAX_REQUEST_PAGES, NormalizedItem, type PackOptions, type PackResult, PollContext, PollOutcome, PostReceiveOp, type RequestScope, type ResolvedRequest, type ScaffoldFile, type ScaffoldOptions, type Substitution, TriggerDefinition, applyPostReceive, asOutput, createConnectorServer, defineConnector, envNameFor, executeRequest, nextLink, normalizeItem, normalizeItems, packConnector, packFileName, pollWithDedupe, resolveConfig, resolveRequest, resolveTemplates, scaffoldFiles, serveConnector, titleCase, valueAt };