nomoreide 0.2.0 → 0.3.2

package/dist/core/providers/deploy-provider.d.ts

@@ -1,327 +0,0 @@
-/**
- * The contract a deploy platform implements — Vercel today, Cloudflare and
- * Netlify next.
- *
- * Every method here already existed on `VercelManager` with the same arguments;
- * this is a rename plus four deliberate neutralizations, each of which is a
- * place the abstraction would otherwise leak on provider #2:
- *
- * 1. **Build settings are a list, not fields.** `VercelProject` hard-codes
- *    seven; Cloudflare's set differs and an IaaS provider has none.
- * 2. **Deployment state carries `rawState`.** The vendor's own word survives
- *    normalization, so the first provider whose states don't map cleanly does
- *    not force a contract change.
- * 3. **Build and runtime log lines are one type.** They answer different
- *    questions but have the same shape, and a provider may serve only one.
- * 4. **Writes are a named action list, not fixed methods.** See
- *    {@link DeployProviderActions}.
- *
- * The read-safe / write-capable split from `git-manager`/`git-actions` and
- * `db-peek`/`db-write` is preserved exactly: {@link DeployProvider} contains
- * nothing that changes what is deployed, and {@link DeployProviderActions} is a
- * separate object resolved separately and never exposed as an MCP tool.
- */
-import type { ProviderApiSpec } from "./egress.js";
-import type { ProviderStrings } from "./strings.js";
-/** Signed-in account. ← `VercelViewer` */
-export interface ProviderAccount {
-    id: string;
-    username: string;
-    name?: string | null;
-    email?: string | null;
-    avatar?: string | null;
-}
-/** A team / org / account within the provider. ← `VercelTeam` */
-export interface ProviderScope {
-    id: string;
-    slug: string;
-    name: string | null;
-}
-/** A project's Git connection, when it was imported from a repository. */
-export interface ProviderProjectLink {
-    type: string;
-    org?: string;
-    repo?: string;
-    productionBranch?: string;
-}
-/**
- * One build setting.
- *
- * `value: null` means "not overridden" — the provider is using the framework's
- * own default — which is a meaningful state and distinct from the setting being
- * *absent from the array*, which means "not read". Vercel's list endpoint omits
- * settings that its single-project endpoint fills in, and the settings panel
- * relies on telling those two apart.
- */
-export interface ProviderSetting {
-    key: string;
-    label: string;
-    value: string | null;
-}
-/** ← `VercelProject` */
-export interface ProviderProject {
-    id: string;
-    name: string;
-    framework?: string | null;
-    updatedAt?: number;
-    link?: ProviderProjectLink;
-    settings: ProviderSetting[];
-}
-/**
- * Normalized deployment state, chosen to be the intersection that drives an
- * icon and a filter. Anything finer belongs in `rawState`.
- */
-export type ProviderDeploymentState = "queued" | "building" | "ready" | "error" | "canceled" | "blocked" | "deleted";
-/** ← `VercelDeployment` */
-export interface ProviderDeployment {
-    id: string;
-    name: string;
-    /**
-     * The deployment's hostname, **without a scheme** — consumers prefix
-     * `https://`. Vercel returns it this way; Cloudflare returns a full URL and
-     * its adapter strips the scheme.
-     */
-    url: string | null;
-    /** Drives the icon and the filter. */
-    state: ProviderDeploymentState;
-    /** The vendor's own word for the state, shown in the UI detail. */
-    rawState: string;
-    /** `production` / `staging`; null is a preview deployment. */
-    target: string | null;
-    createdAt: number;
-    readyAt?: number;
-    /** True while this deployment serves the project's production alias. */
-    isCurrentProduction?: boolean;
-    creator?: {
-        username?: string;
-        email?: string;
-    };
-    meta: {
-        branch?: string;
-        sha?: string;
-        commitMessage?: string;
-        commitAuthor?: string;
-    };
-    inspectorUrl?: string;
-}
-export interface ProviderDeploymentDetail extends ProviderDeployment {
-    aliases: string[];
-    buildingAt?: number;
-    errorMessage?: string;
-}
-/**
- * A line of build or runtime output. ← `VercelBuildLogLine` + `VercelRuntimeLogLine`
- *
- * Merged because the two differ only in what `level` holds and whether a
- * request is attached, and a provider may serve one without the other.
- */
-export interface ProviderLogLine {
-    id: string;
-    createdAt: number;
-    kind: "build" | "runtime";
-    /** `stdout` / `stderr` / `command` for build lines; `error` / `warning` / `info` for runtime. */
-    level: string;
-    text: string;
-    source?: string;
-    /** Runtime lines only — which request produced this line. */
-    request?: {
-        method?: string;
-        path?: string;
-        statusCode?: number;
-    };
-}
-/**
- * A project environment variable, with its value deliberately absent.
- *
- * Listing answers "is this key set, and where" — the question a failed deploy
- * actually raises. The value is a separate, explicitly-requested read (see
- * {@link DeployProvider.getEnvValue}), so merely opening the tab never puts a
- * secret on the wire. ← `VercelEnvVar`
- */
-export interface ProviderEnvVar {
-    id: string;
-    key: string;
-    /** `production` / `preview` / `development`. ← Vercel's `target` */
-    environments: string[];
-    /** `encrypted` / `plain` / `system` / `secret`. */
-    type: string;
-    /** Set when the variable is scoped to one preview branch. */
-    gitBranch?: string | null;
-    comment?: string | null;
-    createdAt?: number;
-    updatedAt?: number;
-}
-export interface ProviderDomainVerification {
-    type: string;
-    domain: string;
-    value: string;
-    reason?: string;
-}
-/** ← `VercelDomain` */
-export interface ProviderDomain {
-    name: string;
-    apexName?: string;
-    verified: boolean;
-    /** Set when the domain is a redirect rather than a served alias. */
-    redirect?: string | null;
-    gitBranch?: string | null;
-    createdAt?: number;
-    updatedAt?: number;
-    /** Outstanding DNS records the user must add, when unverified. */
-    verification: ProviderDomainVerification[];
-}
-/**
- * Optional reads. Declared in the manifest's `capabilities` so the generic view
- * can hide a tab rather than render one that errors.
- */
-export type DeployCapability = "projects" | "deployments" | "buildLogs" | "runtimeLogs" | "env" | "domains";
-/** The read-safe half. Nothing here changes what is deployed. */
-export interface DeployProvider {
-    account(): Promise<ProviderAccount>;
-    listScopes(): Promise<ProviderScope[]>;
-    listProjects(opts?: {
-        search?: string;
-        repoUrl?: string;
-        limit?: number;
-    }): Promise<ProviderProject[]>;
-    getProject(id: string): Promise<ProviderProject>;
-    listDeployments(opts: {
-        projectId: string;
-        target?: "production" | "preview";
-        limit?: number;
-    }): Promise<ProviderDeployment[]>;
-    getDeployment(id: string): Promise<ProviderDeploymentDetail>;
-    buildLogs(id: string, limit?: number): Promise<ProviderLogLine[]>;
-    /** Returns [] when the account's plan lacks them, rather than throwing. */
-    runtimeLogs?(id: string, limit?: number): Promise<ProviderLogLine[]>;
-    /** Values deliberately absent — see {@link ProviderEnvVar}. */
-    listEnv?(projectId: string): Promise<ProviderEnvVar[]>;
-    /** The one door for reading a secret. */
-    getEnvValue?(projectId: string, envId: string): Promise<string>;
-    listDomains?(projectId: string): Promise<ProviderDomain[]>;
-}
-export interface DeployActionInput {
-    deploymentId: string;
-    /** Required by actions that address the project rather than the deployment. */
-    projectId?: string;
-    /**
-     * The deployment's own name and environment, read before the call and passed
-     * through by actions that recreate it. Vercel's redeploy needs both, or a
-     * production retry silently comes back as a preview.
-     */
-    name?: string;
-    target?: string | null;
-    /** Recorded by providers that accept a reason (Vercel's rollback). */
-    description?: string;
-}
-export interface DeployActionResult {
-    /** Set when the action created a new deployment, as `redeploy` does. */
-    deployment?: {
-        id: string;
-        url: string | null;
-    };
-}
-/**
- * The write-capable half — dashboard-only, never an MCP tool.
- *
- * **Why `run(action, …)` rather than `redeploy()`/`cancel()`/`promote()`/
- * `rollback()`:** promote-vs-rollback is Vercel-specific vocabulary (Vercel
- * records a rollback, with its reason, on a different endpoint from a forward
- * promotion). Cloudflare has "retry" and "rollback" but no "promote"; Netlify
- * has "publish". Fixing four method names into the contract would bake in one
- * vendor's words. The names a provider actually offers, and which of them
- * change what production serves, are declared in its manifest instead.
- */
-export interface DeployProviderActions {
-    run(action: string, input: DeployActionInput): Promise<DeployActionResult>;
-    createEnv?(projectId: string, input: {
-        key: string;
-        value: string;
-        environments: string[];
-        type?: "encrypted" | "plain";
-    }): Promise<ProviderEnvVar>;
-    updateEnv?(projectId: string, envId: string, input: {
-        value?: string;
-        environments?: string[];
-    }): Promise<ProviderEnvVar>;
-    deleteEnv?(projectId: string, envId: string): Promise<void>;
-}
-/**
- * The vendor-specific inputs to project resolution — the only two things in
- * that three-tier ladder that are not generic.
- */
-export interface DeployProviderHooks {
-    /** Normalizes a git remote into the URL the vendor keys projects by. */
-    repoUrl(remoteUrl: string): string | null;
-    /**
-     * The file the vendor's CLI writes on `link`. Vercel:
-     * `{ path: ".vercel/project.json", field: "projectId" }`. Providers without
-     * one simply skip that tier.
-     */
-    linkFile?: {
-        path: string;
-        field: string;
-    };
-}
-/**
- * The declarative half of a provider — everything a generic view needs in
- * order to render it without knowing which provider it is.
- *
- * Plain data because this is what a provider manifest carries. `strings` and
- * `auth` join it when the registry lands; today it holds what already exists.
- */
-export interface DeployProviderManifest {
-    id: string;
-    name: string;
-    kind: "deploy";
-    /**
-     * This provider's own words, per locale — its action labels, their toasts and
-     * confirmations, and what it calls a scope (`scope.label`: "Team" for Vercel,
-     * "Account" for Cloudflare).
-     *
-     * Here rather than in the host's `i18n/en.ts` because the provider, not the
-     * host, determines which keys exist: `actions` is a free list of vendor
-     * vocabulary, so the host cannot hold a catalogue entry for a word it has
-     * never seen. See `providers/strings.ts`.
-     */
-    strings: ProviderStrings;
-    /**
-     * How this provider can be connected.
-     *
-     * The generic setup screen cannot otherwise know whether to offer "sign in
-     * with browser": Vercel has all three sources, while Cloudflare has no
-     * registration endpoint for `providers/oauth.ts` to mint a client against, so
-     * offering it there is a button that can only fail. This is a fact about each
-     * provider's *current* wiring rather than a permanent one — see
-     * `cloudflare-auth.ts` — which is exactly why it is declared per provider
-     * instead of inferred. Kept in step with the `ProviderAuthSpec` by
-     * `test/provider-routes.test.ts`.
-     */
-    authSources: ("cli" | "stored" | "oauth")[];
-    capabilities: DeployCapability[];
-    /**
-     * Whether a scope must be chosen before anything can be read at all.
-     *
-     * Cloudflare addresses every Pages URL as `/accounts/<id>/…`, so without an
-     * account id there is no request to make; Vercel's personal scope is a real
-     * resting state, so "no scope" is normal there. The switcher needs the
-     * difference because a scope list can come back empty for a perfectly good
-     * token — enumerating Cloudflare accounts needs `Account Settings: Read`,
-     * which a Pages token has no reason to carry — and the two providers want
-     * opposite things in that case: Vercel, nothing; Cloudflare, a way to enter
-     * the id by hand rather than a dead end.
-     */
-    requiresScope?: boolean;
-    /** Action names accepted by {@link DeployProviderActions.run}. */
-    actions: string[];
-    /** The subset of `actions` that changes what production serves; the UI confirms these first. */
-    productionAffecting: string[];
-    /**
-     * The egress allowlist — every host this provider may reach.
-     *
-     * Enforced, not documented: the provider's registry entry mints its client
-     * with `createProviderFetch(manifest)`, and a request to any other host throws
-     * before it is sent. See `providers/egress.ts`.
-     */
-    api: ProviderApiSpec;
-}

package/dist/core/providers/deploy-provider.js

@@ -1,25 +0,0 @@
-/**
- * The contract a deploy platform implements — Vercel today, Cloudflare and
- * Netlify next.
- *
- * Every method here already existed on `VercelManager` with the same arguments;
- * this is a rename plus four deliberate neutralizations, each of which is a
- * place the abstraction would otherwise leak on provider #2:
- *
- * 1. **Build settings are a list, not fields.** `VercelProject` hard-codes
- *    seven; Cloudflare's set differs and an IaaS provider has none.
- * 2. **Deployment state carries `rawState`.** The vendor's own word survives
- *    normalization, so the first provider whose states don't map cleanly does
- *    not force a contract change.
- * 3. **Build and runtime log lines are one type.** They answer different
- *    questions but have the same shape, and a provider may serve only one.
- * 4. **Writes are a named action list, not fixed methods.** See
- *    {@link DeployProviderActions}.
- *
- * The read-safe / write-capable split from `git-manager`/`git-actions` and
- * `db-peek`/`db-write` is preserved exactly: {@link DeployProvider} contains
- * nothing that changes what is deployed, and {@link DeployProviderActions} is a
- * separate object resolved separately and never exposed as an MCP tool.
- */
-export {};
-//# sourceMappingURL=deploy-provider.js.map

package/dist/core/providers/deploy-provider.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"deploy-provider.js","sourceRoot":"","sources":["../../../src/core/providers/deploy-provider.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG"}

package/dist/core/providers/egress.d.ts

@@ -1,58 +0,0 @@
-/**
- * The provider egress boundary — a `fetch` scoped to a provider's declared
- * `api.hosts`.
- *
- * §6 of `docs/plans/2026-08-13-provider-registry-design.md` calls `api.hosts`
- * "the security boundary", and §11 records that the boundary existed only in
- * prose: all three managers called global `fetch` directly. This is the module
- * that makes it real, and it is gate item 3 of the freeze decision.
- *
- * **Why it matters even while every provider is in-tree.** A provider
- * necessarily receives credentials and runs inside the daemon — the same
- * process holding GitHub tokens, `db-write.ts` access and process-spawn
- * ability. In-tree the code is reviewed and the egress auditable, so this buys
- * documentation rather than protection. The moment a provider is *downloaded*,
- * it is the entire barrier. Landing it now means the three in-tree providers
- * prove the shape before anything third-party depends on it.
- *
- * **The hole it closes today.** All three `xRequest` helpers accept an absolute
- * URL (`path.startsWith("http")`) and skip the base URL entirely. That escape
- * exists for pagination cursors, and it is exactly what provider code would use
- * to send an `Authorization`-bearing request anywhere it liked. The allowlist is
- * checked against the *final* URL, so the escape no longer escapes.
- */
-/**
- * The egress allowlist a provider manifest declares.
- *
- * Hosts are matched **exactly** — no wildcards, deliberately. Every vendor here
- * has a customer-controlled subdomain space (`*.vercel.app`, `*.pages.dev`), so
- * a pattern like `*.vercel.com` reads as a convenience while quietly admitting
- * hosts the vendor does not control. A provider that genuinely needs a second
- * host lists the second host.
- */
-export interface ProviderApiSpec {
-    /** Bare hostnames, no scheme and no path: `["api.vercel.com"]`. */
-    hosts: string[];
-}
-/** A `fetch` that can only reach one provider's declared hosts. */
-export type ProviderFetch = (url: string | URL, init?: RequestInit) => Promise<Response>;
-/**
- * A refused request. Distinct from every `*ApiError` because nothing was sent —
- * there is no status and no vendor to blame, only a provider asking for
- * something its manifest does not declare.
- */
-export declare class ProviderEgressError extends Error {
-    readonly providerId: string;
-    readonly url: string;
-    constructor(message: string, providerId: string, url: string);
-}
-/**
- * A `fetch` for one provider, refusing anything its manifest does not declare.
- *
- * Takes the manifest rather than a bare host list so the id in an error message
- * and the allowlist it was checked against cannot drift apart.
- */
-export declare function createProviderFetch(manifest: {
-    id: string;
-    api: ProviderApiSpec;
-}, base?: ProviderFetch): ProviderFetch;

package/dist/core/providers/egress.js

@@ -1,124 +0,0 @@
-/**
- * The provider egress boundary — a `fetch` scoped to a provider's declared
- * `api.hosts`.
- *
- * §6 of `docs/plans/2026-08-13-provider-registry-design.md` calls `api.hosts`
- * "the security boundary", and §11 records that the boundary existed only in
- * prose: all three managers called global `fetch` directly. This is the module
- * that makes it real, and it is gate item 3 of the freeze decision.
- *
- * **Why it matters even while every provider is in-tree.** A provider
- * necessarily receives credentials and runs inside the daemon — the same
- * process holding GitHub tokens, `db-write.ts` access and process-spawn
- * ability. In-tree the code is reviewed and the egress auditable, so this buys
- * documentation rather than protection. The moment a provider is *downloaded*,
- * it is the entire barrier. Landing it now means the three in-tree providers
- * prove the shape before anything third-party depends on it.
- *
- * **The hole it closes today.** All three `xRequest` helpers accept an absolute
- * URL (`path.startsWith("http")`) and skip the base URL entirely. That escape
- * exists for pagination cursors, and it is exactly what provider code would use
- * to send an `Authorization`-bearing request anywhere it liked. The allowlist is
- * checked against the *final* URL, so the escape no longer escapes.
- */
-/**
- * A refused request. Distinct from every `*ApiError` because nothing was sent —
- * there is no status and no vendor to blame, only a provider asking for
- * something its manifest does not declare.
- */
-export class ProviderEgressError extends Error {
-    providerId;
-    url;
-    constructor(message, providerId, url) {
-        super(message);
-        this.providerId = providerId;
-        this.url = url;
-        this.name = "ProviderEgressError";
-    }
-}
-/**
- * A redirect chain is followed by hand so that every hop is checked.
- *
- * The default `redirect: "follow"` would let an allowlisted host bounce a
- * credential-bearing request to an unlisted one, and open redirects on vendor
- * APIs are common enough that this is not a theoretical concern. Each hop goes
- * back through the allowlist; the cap stops a redirect loop from hanging a
- * dashboard request.
- */
-const MAX_REDIRECTS = 5;
-/** Read at call time, not at module load, so a test's `vi.stubGlobal` still wins. */
-const globalFetch = (url, init) => fetch(url, init);
-/**
- * A `fetch` for one provider, refusing anything its manifest does not declare.
- *
- * Takes the manifest rather than a bare host list so the id in an error message
- * and the allowlist it was checked against cannot drift apart.
- */
-export function createProviderFetch(manifest, base = globalFetch) {
-    const { id } = manifest;
-    const allowed = new Set(manifest.api.hosts.map((host) => host.trim().toLowerCase()));
-    const send = async (input, init, hop) => {
-        const url = assertAllowed(id, allowed, input);
-        // `manual` so a 3xx comes back as a response to inspect rather than being
-        // followed past the allowlist.
-        const response = await base(url, { ...init, redirect: "manual" });
-        const location = redirectTarget(response);
-        if (!location)
-            return response;
-        if (hop >= MAX_REDIRECTS) {
-            throw new ProviderEgressError(`Provider "${id}" was redirected more than ${MAX_REDIRECTS} times from ${url.href}.`, id, url.href);
-        }
-        return send(new URL(location, url), afterRedirect(init, response.status), hop + 1);
-    };
-    return (input, init) => send(input, init, 0);
-}
-/** The URL a response redirects to, or null when it is not a redirect. */
-function redirectTarget(response) {
-    if (response.status < 300 || response.status > 399)
-        return null;
-    return response.headers.get("location");
-}
-/**
- * How a request changes across a redirect, per the Fetch standard: 303 always
- * becomes a GET, 301/302 turn a POST into one, and 307/308 preserve both method
- * and body.
- */
-function afterRedirect(init, status) {
-    const method = (init?.method ?? "GET").toUpperCase();
-    const downgrades = status === 303 || ((status === 301 || status === 302) && method === "POST");
-    if (!downgrades)
-        return init;
-    const { body: _body, ...rest } = init ?? {};
-    return { ...rest, method: "GET" };
-}
-/** Hosts that cannot leave the machine, and so need no transport encryption. */
-function isLoopback(hostname) {
-    return hostname === "127.0.0.1" || hostname === "localhost" || hostname === "[::1]" || hostname === "::1";
-}
-/** The check itself. Throws before anything is sent, so a refused call leaks nothing. */
-function assertAllowed(providerId, allowed, input) {
-    let url;
-    try {
-        url = input instanceof URL ? input : new URL(String(input));
-    }
-    catch {
-        throw new ProviderEgressError(`Provider "${providerId}" asked for a URL that is not absolute: ${String(input)}`, providerId, String(input));
-    }
-    // Every provider API is HTTPS, and the schemes this rules out are the
-    // interesting ones: `file:` reads the disk, `data:` smuggles a payload past a
-    // host check, and `http:` puts a token on the wire in clear text.
-    //
-    // The one exception is a loopback host, which is only ever reachable because
-    // `providerApiBase()` accepted an override naming one — and a request that
-    // never leaves the loopback interface is not on a wire to be read. Narrowing
-    // it to loopback is what keeps this from becoming a general `http:` opening.
-    if (url.protocol !== "https:" && !(url.protocol === "http:" && isLoopback(url.hostname))) {
-        throw new ProviderEgressError(`Provider "${providerId}" may only use https, not ${url.protocol.replace(":", "")}: ${url.href}`, providerId, url.href);
-    }
-    if (!allowed.has(url.hostname.toLowerCase())) {
-        throw new ProviderEgressError(`Provider "${providerId}" is not allowed to reach ${url.hostname}. ` +
-            `Its manifest declares: ${[...allowed].join(", ") || "no hosts"}.`, providerId, url.href);
-    }
-    return url;
-}
-//# sourceMappingURL=egress.js.map

package/dist/core/providers/egress.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"egress.js","sourceRoot":"","sources":["../../../src/core/providers/egress.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AAmBH;;;;GAIG;AACH,MAAM,OAAO,mBAAoB,SAAQ,KAAK;IAG1B;IACA;IAHlB,YACE,OAAe,EACC,UAAkB,EAClB,GAAW;QAE3B,KAAK,CAAC,OAAO,CAAC,CAAC;QAHC,eAAU,GAAV,UAAU,CAAQ;QAClB,QAAG,GAAH,GAAG,CAAQ;QAG3B,IAAI,CAAC,IAAI,GAAG,qBAAqB,CAAC;IACpC,CAAC;CACF;AAED;;;;;;;;GAQG;AACH,MAAM,aAAa,GAAG,CAAC,CAAC;AAExB,qFAAqF;AACrF,MAAM,WAAW,GAAkB,CAAC,GAAG,EAAE,IAAI,EAAE,EAAE,CAAC,KAAK,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;AAEnE;;;;;GAKG;AACH,MAAM,UAAU,mBAAmB,CACjC,QAA8C,EAC9C,OAAsB,WAAW;IAEjC,MAAM,EAAE,EAAE,EAAE,GAAG,QAAQ,CAAC;IACxB,MAAM,OAAO,GAAG,IAAI,GAAG,CAAC,QAAQ,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC;IAErF,MAAM,IAAI,GAAG,KAAK,EAAE,KAAmB,EAAE,IAA6B,EAAE,GAAW,EAAE,EAAE;QACrF,MAAM,GAAG,GAAG,aAAa,CAAC,EAAE,EAAE,OAAO,EAAE,KAAK,CAAC,CAAC;QAC9C,0EAA0E;QAC1E,+BAA+B;QAC/B,MAAM,QAAQ,GAAG,MAAM,IAAI,CAAC,GAAG,EAAE,EAAE,GAAG,IAAI,EAAE,QAAQ,EAAE,QAAQ,EAAE,CAAC,CAAC;QAElE,MAAM,QAAQ,GAAG,cAAc,CAAC,QAAQ,CAAC,CAAC;QAC1C,IAAI,CAAC,QAAQ;YAAE,OAAO,QAAQ,CAAC;QAC/B,IAAI,GAAG,IAAI,aAAa,EAAE,CAAC;YACzB,MAAM,IAAI,mBAAmB,CAC3B,aAAa,EAAE,8BAA8B,aAAa,eAAe,GAAG,CAAC,IAAI,GAAG,EACpF,EAAE,EACF,GAAG,CAAC,IAAI,CACT,CAAC;QACJ,CAAC;QACD,OAAO,IAAI,CAAC,IAAI,GAAG,CAAC,QAAQ,EAAE,GAAG,CAAC,EAAE,aAAa,CAAC,IAAI,EAAE,QAAQ,CAAC,MAAM,CAAC,EAAE,GAAG,GAAG,CAAC,CAAC,CAAC;IACrF,CAAC,CAAC;IAEF,OAAO,CAAC,KAAK,EAAE,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;AAC/C,CAAC;AAED,0EAA0E;AAC1E,SAAS,cAAc,CAAC,QAAkB;IACxC,IAAI,QAAQ,CAAC,MAAM,GAAG,GAAG,IAAI,QAAQ,CAAC,MAAM,GAAG,GAAG;QAAE,OAAO,IAAI,CAAC;IAChE,OAAO,QAAQ,CAAC,OAAO,CAAC,GAAG,CAAC,UAAU,CAAC,CAAC;AAC1C,CAAC;AAED;;;;GAIG;AACH,SAAS,aAAa,CAAC,IAA6B,EAAE,MAAc;IAClE,MAAM,MAAM,GAAG,CAAC,IAAI,EAAE,MAAM,IAAI,KAAK,CAAC,CAAC,WAAW,EAAE,CAAC;IACrD,MAAM,UAAU,GAAG,MAAM,KAAK,GAAG,IAAI,CAAC,CAAC,MAAM,KAAK,GAAG,IAAI,MAAM,KAAK,GAAG,CAAC,IAAI,MAAM,KAAK,MAAM,CAAC,CAAC;IAC/F,IAAI,CAAC,UAAU;QAAE,OAAO,IAAI,CAAC;IAC7B,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,GAAG,IAAI,EAAE,GAAG,IAAI,IAAI,EAAE,CAAC;IAC5C,OAAO,EAAE,GAAG,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,CAAC;AACpC,CAAC;AAED,gFAAgF;AAChF,SAAS,UAAU,CAAC,QAAgB;IAClC,OAAO,QAAQ,KAAK,WAAW,IAAI,QAAQ,KAAK,WAAW,IAAI,QAAQ,KAAK,OAAO,IAAI,QAAQ,KAAK,KAAK,CAAC;AAC5G,CAAC;AAED,yFAAyF;AACzF,SAAS,aAAa,CAAC,UAAkB,EAAE,OAAoB,EAAE,KAAmB;IAClF,IAAI,GAAQ,CAAC;IACb,IAAI,CAAC;QACH,GAAG,GAAG,KAAK,YAAY,GAAG,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC;IAC9D,CAAC;IAAC,MAAM,CAAC;QACP,MAAM,IAAI,mBAAmB,CAC3B,aAAa,UAAU,2CAA2C,MAAM,CAAC,KAAK,CAAC,EAAE,EACjF,UAAU,EACV,MAAM,CAAC,KAAK,CAAC,CACd,CAAC;IACJ,CAAC;IAED,sEAAsE;IACtE,8EAA8E;IAC9E,kEAAkE;IAClE,EAAE;IACF,6EAA6E;IAC7E,2EAA2E;IAC3E,6EAA6E;IAC7E,6EAA6E;IAC7E,IAAI,GAAG,CAAC,QAAQ,KAAK,QAAQ,IAAI,CAAC,CAAC,GAAG,CAAC,QAAQ,KAAK,OAAO,IAAI,UAAU,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC,EAAE,CAAC;QACzF,MAAM,IAAI,mBAAmB,CAC3B,aAAa,UAAU,6BAA6B,GAAG,CAAC,QAAQ,CAAC,OAAO,CAAC,GAAG,EAAE,EAAE,CAAC,KAAK,GAAG,CAAC,IAAI,EAAE,EAChG,UAAU,EACV,GAAG,CAAC,IAAI,CACT,CAAC;IACJ,CAAC;IAED,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,EAAE,CAAC;QAC7C,MAAM,IAAI,mBAAmB,CAC3B,aAAa,UAAU,6BAA6B,GAAG,CAAC,QAAQ,IAAI;YAClE,0BAA0B,CAAC,GAAG,OAAO,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,UAAU,GAAG,EACpE,UAAU,EACV,GAAG,CAAC,IAAI,CACT,CAAC;IACJ,CAAC;IAED,OAAO,GAAG,CAAC;AACb,CAAC"}

package/dist/core/providers/host-bridge.d.ts

@@ -1,20 +0,0 @@
-import type { ConfigStore } from "../config-store.js";
-import type { HostSshTarget } from "./host-provider.js";
-/**
- * Every connected host provider's instances, as SSH targets.
- *
- * This is the bridge §7 of the design plan was written for: the servers list
- * the user already has gains a row per provider instance, and everything
- * downstream — `probeSshServer`, `readRemoteHostMetrics`, the terminal route,
- * the remote service runner — keeps working against a plain
- * `SshServerDefinition` without knowing a provider exists.
- *
- * **Never throws.** A provider that is not connected, whose token has expired,
- * or whose API is down contributes nothing; the user's hand-registered and
- * `~/.ssh/config` hosts must still list. A provider outage is not a reason for
- * the servers page to go blank, and there is nowhere in that page's shape to
- * report one.
- */
-export declare function hostProviderSshTargets(configStore: ConfigStore): Promise<HostSshTarget[]>;
-/** Drops the cache so the next read reflects a change we just made. */
-export declare function invalidateHostSshTargets(): void;

package/dist/core/providers/host-bridge.js

@@ -1,57 +0,0 @@
-import { hostProviders } from "./registry.js";
-/**
- * Every connected host provider's instances, as SSH targets.
- *
- * This is the bridge §7 of the design plan was written for: the servers list
- * the user already has gains a row per provider instance, and everything
- * downstream — `probeSshServer`, `readRemoteHostMetrics`, the terminal route,
- * the remote service runner — keeps working against a plain
- * `SshServerDefinition` without knowing a provider exists.
- *
- * **Never throws.** A provider that is not connected, whose token has expired,
- * or whose API is down contributes nothing; the user's hand-registered and
- * `~/.ssh/config` hosts must still list. A provider outage is not a reason for
- * the servers page to go blank, and there is nowhere in that page's shape to
- * report one.
- */
-export async function hostProviderSshTargets(configStore) {
-    const cached = readCache();
-    if (cached)
-        return cached;
-    const perProvider = await Promise.all(hostProviders.map(async (provider) => {
-        try {
-            const { provider: client } = await provider.context(configStore);
-            const instances = await client.listInstances();
-            return instances
-                .map((instance) => client.toSshTarget(instance))
-                .filter((target) => target !== null);
-        }
-        catch {
-            return [];
-        }
-    }));
-    const targets = perProvider.flat();
-    cache = { at: Date.now(), targets };
-    return targets;
-}
-/**
- * How long a provider's instance list is reused.
- *
- * The servers view reloads on an interval *and* on every window focus, and each
- * reload would otherwise be one API call per connected provider. Instances do
- * not change on a human timescale, so a short window trades staleness nobody
- * notices for not being rate-limited by the vendor. Power actions clear it
- * explicitly, which is the one case where the delay would be visible.
- */
-const CACHE_TTL_MS = 30_000;
-let cache = null;
-function readCache() {
-    if (!cache || Date.now() - cache.at >= CACHE_TTL_MS)
-        return null;
-    return cache.targets;
-}
-/** Drops the cache so the next read reflects a change we just made. */
-export function invalidateHostSshTargets() {
-    cache = null;
-}
-//# sourceMappingURL=host-bridge.js.map

package/dist/core/providers/host-bridge.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"host-bridge.js","sourceRoot":"","sources":["../../../src/core/providers/host-bridge.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,aAAa,EAAE,MAAM,eAAe,CAAC;AAE9C;;;;;;;;;;;;;;GAcG;AACH,MAAM,CAAC,KAAK,UAAU,sBAAsB,CAC1C,WAAwB;IAExB,MAAM,MAAM,GAAG,SAAS,EAAE,CAAC;IAC3B,IAAI,MAAM;QAAE,OAAO,MAAM,CAAC;IAE1B,MAAM,WAAW,GAAG,MAAM,OAAO,CAAC,GAAG,CACnC,aAAa,CAAC,GAAG,CAAC,KAAK,EAAE,QAAQ,EAAE,EAAE;QACnC,IAAI,CAAC;YACH,MAAM,EAAE,QAAQ,EAAE,MAAM,EAAE,GAAG,MAAM,QAAQ,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC;YACjE,MAAM,SAAS,GAAG,MAAM,MAAM,CAAC,aAAa,EAAE,CAAC;YAC/C,OAAO,SAAS;iBACb,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,MAAM,CAAC,WAAW,CAAC,QAAQ,CAAC,CAAC;iBAC/C,MAAM,CAAC,CAAC,MAAM,EAA2B,EAAE,CAAC,MAAM,KAAK,IAAI,CAAC,CAAC;QAClE,CAAC;QAAC,MAAM,CAAC;YACP,OAAO,EAAE,CAAC;QACZ,CAAC;IACH,CAAC,CAAC,CACH,CAAC;IAEF,MAAM,OAAO,GAAG,WAAW,CAAC,IAAI,EAAE,CAAC;IACnC,KAAK,GAAG,EAAE,EAAE,EAAE,IAAI,CAAC,GAAG,EAAE,EAAE,OAAO,EAAE,CAAC;IACpC,OAAO,OAAO,CAAC;AACjB,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,YAAY,GAAG,MAAM,CAAC;AAE5B,IAAI,KAAK,GAAoD,IAAI,CAAC;AAElE,SAAS,SAAS;IAChB,IAAI,CAAC,KAAK,IAAI,IAAI,CAAC,GAAG,EAAE,GAAG,KAAK,CAAC,EAAE,IAAI,YAAY;QAAE,OAAO,IAAI,CAAC;IACjE,OAAO,KAAK,CAAC,OAAO,CAAC;AACvB,CAAC;AAED,uEAAuE;AACvE,MAAM,UAAU,wBAAwB;IACtC,KAAK,GAAG,IAAI,CAAC;AACf,CAAC"}