@shipstatic/ship 2.2.0-beta.7 → 2.2.0-beta.9

package/README.md

@@ -48,6 +48,7 @@ const ship = new Ship({ token: 'ship-...' });
 ```bash
 ship ./dist                                        # Deploy (shortcut)
 ship ./dist --domain www.example.com               # Deploy and serve it there
+ship ./dist --ttl 1h                               # Expires in an hour
 ship ./dist --label production --label v1.0.0      # Deploy with labels
 ship deployments list
 ship deployments list --limit 20                   # Page size; a hint shows the next cursor
@@ -106,7 +107,7 @@ ship.domains.set('www.münchen.de');    // → Unicode supported
 ### Tokens
 
 ```bash
-ship tokens create --ttl 3600 --label ci
+ship tokens create --ttl 30d --label ci            # Or 3600, 90s, 1h — one grammar
 ship tokens list
 ship tokens get <token>
 ship tokens delete <token>
@@ -153,6 +154,27 @@ open https://$(ship ./dist -q)
 ship deployments list -q | xargs -I{} ship deployments delete {} -q
 ```
 
+### Ephemeral deployments
+
+```bash
+ship ./dist --ttl 1h          # gone in an hour
+ship ./dist --ttl 7d          # a week-long preview
+ship ./dist --ttl 3600        # bare seconds work too
+```
+
+The platform reclaims the deployment when the time is up. Seconds, or a
+`<n><unit>` duration (`s`/`m`/`h`/`d`) — the same grammar `ship tokens create
+--ttl` uses. Bounded at one year.
+
+Two rules, both refused before anything uploads. It **needs a token**: an
+anonymous deployment already expires on the platform's own schedule, so there
+is no deployer to choose a different one. And it **cannot be combined with
+`--domain`**: a domain is a commitment and a deadline is its opposite, so the
+API refuses to point a domain at a deployment that expires.
+
+To keep something longer, deploy it again — there is no way to extend a
+deployment's life, and no way to shorten it after the fact.
+
 `--domain` is the same two calls as one command:
 
 ```bash
@@ -192,6 +214,7 @@ Available on `ship <path>` and `ship deployments upload`:
 | `--domain <domain>` | Serve this deployment at that domain — creates or repoints it. Needs a token |
 | `--label <label>` | Add label (repeatable) |
 | `--password <password>` | Password-protect this deployment (6–128 chars) |
+| `--ttl <duration>` | Expire this deployment after that long — `3600`, `90s`, `30m`, `1h`, `7d`. Needs a token; cannot be combined with `--domain` |
 | `--no-path-detect` | Disable automatic path optimization |
 | `--no-spa-detect` | Disable automatic SPA detection |
 
@@ -255,6 +278,7 @@ own `signal` (`AbortSignal.timeout(ms)`), which is never retried past.
 ship.deploy(input, {
   labels?: string[],
   password?: string,          // Password-protect the deployment (6–128 chars)
+  ttl?: number,               // Seconds until it expires (needs a token; max 1 year)
   signal?: AbortSignal,       // Abort to cancel the deploy
   pathDetect?: boolean,       // Auto-optimize paths (default: true)
   spaDetect?: boolean,        // Auto-detect SPA (default: true)
@@ -262,6 +286,17 @@ ship.deploy(input, {
 });
 ```
 
+#### Expiring deployments
+
+Pass `ttl` in **seconds** and the platform reclaims the deployment when the time is up — 1 second to one year. The wire carries the duration and the API stamps `expires` against its own clock, so the answer says when:
+
+```typescript
+const result = await ship.deploy('./dist', { ttl: 3600 });
+// result.expires → unix seconds, one hour after result.created
+```
+
+Needs a credential — an anonymous deployment already expires on the platform's own schedule. And a deployment carrying a ttl cannot be linked to a domain: the API refuses, which is what stops a domain pointing at something that is about to be reclaimed. There is no way to extend or shorten a deployment after the fact; redeploy instead.
+
 #### Password protection
 
 Pass `password` (6–128 characters) to gate the deployment behind a prompt. Visitors are asked for the password before they can view the site, including on any custom domains pointing at it. To remove protection, redeploy without a password.

package/SKILL.md

@@ -43,6 +43,27 @@ Without credentials, deployments are public and expire in 3 days. **Always show
 
 The deployment ID **is** the URL hostname. Use the full ID (e.g. `happy-cat-abc1234.shipstatic.com`) as the argument to all other commands. The site lives at `https://<deployment>`.
 
+### Deployments that clean themselves up
+
+```bash
+ship ./dist --ttl 1h      # gone in an hour
+ship ./dist --ttl 7d      # a week-long preview
+```
+
+For a preview nobody needs to keep — a draft, a diff, a one-off render. The
+platform reclaims it when the time is up, so nothing accumulates in the user's
+account and nobody has to remember to delete it. Seconds or a `<n><unit>`
+duration (`s`/`m`/`h`/`d`), up to a year.
+
+**It needs a token.** Without one the deploy is anonymous and already expires
+in 3 days on the platform's own schedule — there is no deployer to choose a
+different lifetime, and the CLI refuses before uploading anything. **It cannot
+be combined with `--domain`**, because a domain must not point at something
+about to be reclaimed.
+
+The response's `expires` is the answer, in unix seconds — read it there rather
+than computing it, since the platform stamps it against its own clock.
+
 ### Parsing output
 
 ```bash
@@ -238,6 +259,7 @@ List commands return `{"<resource>s": [...], "cursor": null}`. A non-null `curso
 ```bash
 ship ./dist                          # Deploy (shortcut)
 ship ./dist --domain <name>          # Deploy and serve it at that domain
+ship ./dist --ttl 1h                 # Expires in an hour (needs a token)
 ship deployments upload <path>       # Deploy (explicit)
 ship deployments list                # List all
 ship deployments get <deployment>    # Details
@@ -265,7 +287,7 @@ ship domains delete <name>            # Delete
 ship whoami                           # Account info
 ship ping                             # Connectivity check
 ship tokens create                    # New deploy token (shown once)
-ship tokens create --ttl 3600         # With expiry (seconds)
+ship tokens create --ttl 30d          # With expiry — 3600, 90s, 1h, 30d
 ship tokens list                      # List tokens
 ship tokens get <token>               # Details for one token
 ship tokens delete <token>            # Delete (revokes immediately)
@@ -281,6 +303,7 @@ ship tokens delete <token>            # Delete (revokes immediately)
 | `--domain <domain>` | Deploy and serve it there — creates or repoints. Needs a token |
 | `--label <label>` | Set label (repeatable, replaces all) |
 | `--password <pwd>` | Password-protect deployment (6–128 chars) |
+| `--ttl <duration>` | Expire after that long — `3600`, `90s`, `1h`, `7d`. Needs a token; not with `--domain` |
 | `--no-path-detect` | Skip build output auto-detection |
 | `--no-spa-detect` | Skip SPA rewrite auto-configuration |
 | `--no-color` | Disable colors |
@@ -295,6 +318,8 @@ ship tokens delete <token>            # Delete (revokes immediately)
 | `not found` | No such resource | Verify the ID/name |
 | `path does not exist` | Bad deploy path | Check file/directory |
 | `invalid domain name` | Not a subdomain | Use `www.example.com`, not `example.com` |
+| `--ttl sets an expiry, which needs a token` | `--ttl` without credentials | Set an API key, or drop `--ttl` |
+| `--ttl and --domain cannot be combined` | Both flags given | A domain cannot point at an expiring deployment — pick one |
 | `<resource> limit reached` | Plan caps hit (deployments, domains) | Suggest upgrading the plan; do not retry |
 | `Account has been deleted` / `Account terminated` | Account is gone | Stop; the account cannot deploy |
 | `DNS information is only available for external domains` | DNS op on internal domain | Only custom domains need DNS |

package/THIRD-PARTY-LICENSES.md

@@ -5,7 +5,7 @@ Their copyright notices travel with that copy, and are reproduced here in
 full. This file is GENERATED from the build's own metafile — edit the
 bundle, not this list.
 
-## @shipstatic/types 2.7.0-beta.3
+## @shipstatic/types 2.7.0-beta.4
 
 License: MIT
 
@@ -160,62 +160,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
 ```
 
-## form-data-encoder 4.1.0
-
-License: MIT
-
-```
-The MIT License (MIT)
-
-Copyright (c) 2021-present Nick K.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-```
-
-## formdata-node 6.0.3
-
-License: MIT
-
-```
-The MIT License (MIT)
-
-Copyright (c) 2017-present Nick K.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-```
-
 ## junk 4.0.1
 
 License: MIT

package/dist/browser.d.ts

@@ -671,6 +671,12 @@ declare const DEPLOY_FIELDS: {
     readonly VIA: "via";
     /** Plaintext password — the API hashes it server-side. */
     readonly PASSWORD: "password";
+    /**
+     * Requested lifetime in SECONDS — a duration, never an instant. The API
+     * computes and stores the expiry, so the wire carries no client clock.
+     * See {@link validateTtl}.
+     */
+    readonly TTL: "ttl";
     /** @internal Server-processing flag — first-party `/upload` only. */
     readonly BUILD: "build";
     /** @internal Server-processing flag — first-party `/upload` only. */
@@ -1259,6 +1265,47 @@ declare function validateApiUrl(apiUrl: string): void;
  * Example: "happy-cat-abc1234.shipstatic.com"
  */
 declare function isDeployment(input: string): boolean;
+/**
+ * The envelope a requested lifetime must fit — one word, one grammar, wherever
+ * the platform lets a caller choose how long something lives.
+ *
+ * Two resources wear it: `TokenCreateOptions.ttl` and
+ * `DeploymentUploadOptions.ttl`. It lives here rather than on the server by
+ * the format-vs-policy rule — a client can decide offline whether a duration
+ * is well-formed, and the API rejects the same value the same way. What is
+ * NOT here is any per-plan ceiling: no such policy exists, and one delivered
+ * speculatively through `/limits` would be an owner for a decision nobody has
+ * made.
+ */
+declare const TTL_CONSTRAINTS: {
+    /**
+     * Shortest requestable lifetime, in seconds. One rather than zero: a
+     * deployment that expires the instant it is created is not a shorter lease,
+     * it is a deploy that was never live, and `0` is how an unset variable
+     * arrives.
+     */
+    readonly MIN_SECONDS: 1;
+    /** Longest requestable lifetime, in seconds — one year. */
+    readonly MAX_SECONDS: number;
+};
+/**
+ * Validate a requested lifetime in SECONDS and return it, or `undefined` when
+ * none was asked for.
+ *
+ * **A duration, never an instant.** The caller says how long; the server owns
+ * what time it is and stamps the expiry — so a client's clock, however wrong,
+ * cannot shorten or extend a lease. That is the tokens precedent, and it is
+ * why this rule measures a count of seconds rather than checking a timestamp
+ * against `now`.
+ *
+ * Fractions are refused rather than rounded: a caller who wrote `1.5` meant
+ * something the wire cannot carry, and silently choosing `1` or `2` for them
+ * is a decision the platform has no standing to make.
+ *
+ * Single source of truth shared by the API (the tokens route and the deploy
+ * schema), the SDK's request boundary, and the CLI's parser.
+ */
+declare function validateTtl(value: unknown): number | undefined;
 /**
  * Request payload for SPA check endpoint
  */
@@ -1391,6 +1438,27 @@ interface DeploymentUploadOptions {
      * into missing analytics rather than an error. See {@link DeploymentVia}.
      */
     via?: DeploymentViaType;
+    /**
+     * Seconds until this deployment expires; omit for one that never does.
+     *
+     * The platform reclaims it when the time is up — an ephemeral deployment,
+     * chosen by the deployer rather than by the identity. The same word and the
+     * same grammar as {@link TokenCreateOptions.ttl}, bounded by
+     * {@link TTL_CONSTRAINTS}.
+     *
+     * **Requires a credential.** An anonymous deploy has no deployer, and the
+     * platform owns anonymous lifetime as policy
+     * ({@link PUBLIC_DEPLOYMENT_TTL_SECONDS}) — so a ttl on one is refused
+     * rather than honoured or ignored.
+     *
+     * **A deployment carrying one cannot be linked to a domain.** A domain is a
+     * commitment and a deadline is its opposite; the API refuses the link, which
+     * is what keeps the reaper from tearing a live domain's target away.
+     *
+     * Immutable, like every other field of a deployment: to keep something
+     * longer, redeploy.
+     */
+    ttl?: number;
     /**
      * Optional password that protects this deployment.
      *
@@ -1829,14 +1897,6 @@ interface DeploymentOptions extends DeploymentUploadOptions {
     spaDetect?: boolean;
 }
 type ApiDeployOptions = Omit<DeploymentOptions, 'pathDetect'>;
-/**
- * Prepared request body for deployment.
- * Created by platform-specific code, consumed by HTTP client.
- */
-interface DeployBody {
-    body: FormData | ArrayBuffer;
-    headers: Record<string, string>;
-}
 /**
  * Context passed to the deploy body creator — everything that becomes a
  * form field alongside the files themselves.
@@ -1860,6 +1920,11 @@ interface DeployBodyContext {
      * characters. Whitespace is preserved verbatim — significant.
      */
     password?: string;
+    /**
+     * Requested lifetime in SECONDS — a duration, never an instant, bounded by
+     * `TTL_CONSTRAINTS`. The API stamps the expiry against its own clock.
+     */
+    ttl?: number;
     /** @internal Server-side processing flags. */
     flags?: {
         build?: boolean;
@@ -1869,11 +1934,6 @@ interface DeployBodyContext {
     /** @internal reCAPTCHA proof for the anonymous human deploy channel (/upload). */
     captcha?: string;
 }
-/**
- * Function that creates a deploy request body from files.
- * Implemented differently for Node.js and Browser.
- */
-type DeployBodyCreator = (files: StaticFile[], context?: DeployBodyContext) => Promise<DeployBody>;
 /** Standard `fetch` signature — the type of the `fetch` client option. */
 type Fetch = typeof fetch;
 /**
@@ -2071,28 +2131,72 @@ declare class SimpleEvents {
     emit<K extends keyof ShipEvents>(event: K, ...args: ShipEvents[K]): void;
 }
 
-/**
- * @file HTTP client for Ship API.
- */
-
 interface ApiHttpOptions extends ShipClientOptions {
     /** Resolves the credential slot per request — async so token providers can mint/refresh. */
     getAuthHeaders: () => Record<string, string> | Promise<Record<string, string>>;
-    createDeployBody: DeployBodyCreator;
 }
-declare class ApiHttp extends SimpleEvents {
+interface RequestResult<T> {
+    data: T;
+    status: number;
+}
+/**
+ * The deploy's CARRIAGE — the two facts about a deploy that are transport's
+ * rather than the deployment resource's.
+ *
+ * The numbers are transport's because a budget for how long to wait on a wire
+ * is nothing else, and the endpoint is transport's because `deployEndpoint` is
+ * a client option that redirects the route. The CHOICE between the two
+ * ceilings is the resource's, because only it knows that `build`/`prerender`
+ * wait on work the server does after the upload lands.
+ */
+interface DeployTransport {
+    /** `/deployments`, or `/upload` where the `@internal` option redirects it. */
+    readonly endpoint: string;
+    /** The ordinary deploy ceiling. */
+    readonly timeout: number;
+    /** The ceiling when the server will also build. */
+    readonly buildTimeout: number;
+}
+/**
+ * What a resource may ask of the transport: carry this request, and tell me
+ * what came back.
+ *
+ * This interface is the whole seam. `resources.ts` states WHICH request — the
+ * path, the verb, the body, the response type — and hands it here; nothing
+ * above this line knows the base URL, the credential, the retry policy or the
+ * event vocabulary, and nothing below knows what a domain is.
+ */
+interface Transport {
+    request<T>(path: string, options: ShipRequestInit, operationName: string, timeoutMs?: number): Promise<T>;
+    requestWithStatus<T>(path: string, options: ShipRequestInit, operationName: string): Promise<RequestResult<T>>;
+    readonly deploy: DeployTransport;
+}
+/**
+ * A request as THIS client composes one.
+ *
+ * Identical to `RequestInit` but for the headers, which are narrowed from the
+ * DOM's three-shaped `HeadersInit` to the one shape every call site here
+ * actually builds. That narrowing is load-bearing twice over: `mergeHeaders`
+ * used to reach its record through an `as` cast, and `hasIdempotencyKey` used
+ * to walk all three shapes to find a key that only ever arrives in one of
+ * them. Narrowing at RUNTIME instead would have turned an unreachable case
+ * into a SILENT no-retry — a deploy that quietly stopped replaying because
+ * someone handed the transport a `Headers`. Here that is a compile error.
+ */
+type ShipRequestInit = Omit<RequestInit, 'headers'> & {
+    headers?: Record<string, string>;
+};
+declare class ApiHttp extends SimpleEvents implements Transport {
     private readonly apiUrl;
     private readonly getAuthHeadersCallback;
     private readonly session;
     private readonly caller;
     private readonly timeout;
     private readonly maxRetries;
-    private readonly deployTimeout;
-    private readonly deployBuildTimeout;
     private readonly fetch;
-    private readonly createDeployBody;
-    private readonly deployEndpoint;
     private globalHeaders;
+    /** @see DeployTransport — the carriage facts the deployment resource reads. */
+    readonly deploy: DeployTransport;
     constructor(options: ApiHttpOptions);
     /**
      * Set global headers included in every request.
@@ -2131,7 +2235,13 @@ declare class ApiHttp extends SimpleEvents {
      * is one that may be sent twice.
      */
     private isRetryable;
-    /** Did this request carry the header that makes a repeat safe? */
+    /**
+     * Did this request carry the header that makes a repeat safe?
+     *
+     * Case-insensitively, because HTTP field names are — the CLI's env tier and
+     * the SDK option both spell it canonically, but a caller composing headers
+     * by hand is entitled not to.
+     */
     private hasIdempotencyKey;
     /**
      * One attempt: headers, timeout signal, the `request`/`response` events, and
@@ -2143,51 +2253,56 @@ declare class ApiHttp extends SimpleEvents {
      */
     private attemptOnce;
     /**
-     * Simple request - returns data only
+     * Send it; resolve what came back.
+     *
+     * Takes a PATH, not a URL: the base is this client's and nothing above needs
+     * to know it. Twenty-two call sites wrote `${this.apiUrl}${API_PATHS.X}` by
+     * hand before the endpoints moved out, which is twenty-two chances to
+     * assemble it differently.
      */
-    private request;
+    request<T>(path: string, options: ShipRequestInit, operationName: string, timeoutMs?: number): Promise<T>;
     /**
-     * Request with status - returns data and HTTP status code
+     * The same, plus the HTTP status — for the one operation where the status IS
+     * the answer: a domain upsert says create-or-update in its 201/200 and
+     * nowhere else in the response.
      */
-    private requestWithStatus;
+    requestWithStatus<T>(path: string, options: ShipRequestInit, operationName: string): Promise<RequestResult<T>>;
     private mergeHeaders;
     private createTimeoutSignal;
     private safeClone;
     private parseResponse;
-    deploy(files: StaticFile[], options?: ApiDeployOptions): Promise<DeploymentCreateResponse>;
-    listDeployments(options?: ListOptions): Promise<DeploymentListResponse>;
-    getDeployment(id: string): Promise<Deployment>;
-    updateDeploymentLabels(id: string, labels: string[]): Promise<Deployment>;
-    deleteDeployment(id: string): Promise<DeploymentDeleteResponse>;
-    setDomain(name: string, deployment?: string, labels?: string[]): Promise<DomainSetResult>;
-    listDomains(options?: ListOptions): Promise<DomainListResponse>;
-    getDomain(name: string): Promise<Domain>;
-    deleteDomain(name: string): Promise<DomainDeleteResponse>;
-    verifyDomain(name: string): Promise<DomainVerifyResponse>;
-    getDomainDns(name: string): Promise<DomainDnsResponse>;
-    getDomainRecords(name: string): Promise<DomainRecordsResponse>;
-    getDomainShare(name: string): Promise<DomainShareResponse>;
-    validateDomain(name: string): Promise<DomainValidateResponse>;
-    createToken(ttl?: number, labels?: string[]): Promise<TokenCreateResponse>;
-    listTokens(options?: ListOptions): Promise<TokenListResponse>;
-    deleteToken(token: string): Promise<TokenDeleteResponse>;
-    getToken(token: string): Promise<Token>;
-    getAccount(): Promise<AccountGetResponse>;
-    getLimits(): Promise<PlatformLimits>;
-    ping(): Promise<PingResponse>;
-    checkSPA(files: StaticFile[], _options?: ApiDeployOptions): Promise<boolean>;
 }
 
 /**
- * Ship SDK resource factory functions.
+ * @file The SDK's vocabulary — every request it can make, stated once.
+ *
+ * A resource method IS its endpoint: the path, the verb, the body, the
+ * response type. It hands that to the transport, which knows how to carry a
+ * request and nothing about what one means.
+ *
+ * **These were two layers until 2026-08-12.** `ApiHttp` carried eighteen
+ * endpoint methods and every factory below wrapped one of them 1:1 —
+ * `get: async (name) => getApi().getDomain(name)` — because this SDK mirrors
+ * the wire one method per endpoint BY DESIGN (see CLAUDE.md, "Recorded
+ * absences"). That design is exactly what made the second layer a restatement
+ * rather than an adapter: the two could not diverge without one of them being
+ * wrong. Folding DOWN rather than up is what keeps the public grouping and the
+ * transport separate, which was the whole point of having two files.
+ *
+ * The `*Resource` interfaces come from `@shipstatic/types` and did not move.
+ * They are the published contract; this file is how it is met.
  */
 
 /**
  * Shared context for all resource factories.
+ *
+ * A factory receives the callbacks it needs and nothing else — which is what
+ * lets `getApi()` be a THUNK rather than an instance: the transport is built
+ * once in the constructor, but reading it lazily is what keeps the resources
+ * constructible before it exists and swappable in tests.
  */
 interface ResourceContext {
-    getApi: () => ApiHttp;
-    ensureInit: () => Promise<void>;
+    getApi: () => Transport;
 }
 /**
  * Extended context for deployment resource.
@@ -2236,7 +2351,6 @@ declare abstract class Ship$1 {
     private credential;
     constructor(options?: ShipClientOptions);
     protected abstract processInput(input: DeployInput, options: DeploymentOptions): Promise<StaticFile[]>;
-    protected abstract getDeployBodyCreator(): DeployBodyCreator;
     /**
      * Lazy initialization — fetches platform limits (file size / count caps) once,
      * on the first API call. Subsequent calls reuse the resolved promise.
@@ -2601,23 +2715,26 @@ declare function validateDeployFile(input: FileRuleInput, limits: PlatformLimits
 declare function pluralize(count: number, singular: string, plural: string, includeCount?: boolean): string;
 
 /**
- * @file Browser-specific file utilities for the Ship SDK.
- * Provides helpers for processing browser files into deploy-ready objects.
+ * @file The browser half of the deploy pipeline: reading paths off `File`s.
  *
- * Two modes:
- * - **Deploy** (default): Full validation pipeline — security, extensions, sizes, counts.
- * - **Server-processed** (build/prerender): Source files destined for server-side build.
- *   Junk filtering and MD5 checksums only — the build service validates the output.
+ * Everything after is shared (`shared/core/deploy-files.ts`) — path
+ * optimization, junk filtering, the platform's rules, the checksums. What is
+ * genuinely browser here is one line: a directory drop carries
+ * `webkitRelativePath`, a file picker does not.
  *
- * Both modes share: environment check → extract paths → optimize paths → filter junk → MD5.
+ * There is no size to look up and no content to fetch, because a `File`
+ * already is both. That is the whole of this platform's collection step, and
+ * it is why the seam the Node side needs (`size` before `read()`) costs
+ * nothing on this one.
  */
 
 /**
  * Processes browser files into an array of StaticFile objects ready for deploy.
- * Calculates MD5, filters junk files, validates sizes, and applies path optimization.
  *
- * For server-processed uploads (build/prerender), client-side deploy validation is
- * skipped — the build service produces and validates the actual deployment output.
+ * For server-processed uploads (`build`/`prerender`), the shared processor
+ * skips deploy validation — the build service produces and validates the
+ * actual deployment output. Those flags are `@internal` and this is their only
+ * platform: `web/my` and `web/www` set them through `/upload`.
  *
  * @param browserFiles - File[] to process for deploy.
  * @param options - Processing options including pathDetect for automatic path optimization.
@@ -2666,7 +2783,6 @@ declare class Ship extends Ship$1 {
      */
     deploy(input: File[], options?: DeploymentOptions): Promise<DeploymentCreateResponse>;
     protected processInput(input: DeployInput, options: DeploymentOptions): Promise<StaticFile[]>;
-    protected getDeployBodyCreator(): DeployBodyCreator;
 }
 
-export { API_KEY, API_PATHS, AUTH_BASE_PATH, type Account, type AccountDeleteResponse, type AccountGetResponse, type AccountKeyResponse, type AccountOverrides, AccountPlan, type AccountPlanType, type AccountResource, type AccountUsage, type Activity, type ActivityEvent, type ActivityListResponse, type ActivityMeta, type ApiDeployOptions, ApiHttp, type ApiHttpOptions, AuthMethod, type AuthMethodType, type BillingCancelResponse, type BillingStatus, CALLER, type CheckoutSession, DEFAULT_API, DEPLOYMENT_CONFIG_FILENAME, DEPLOY_FIELDS, DEPLOY_TOKEN, type DeployBody, type DeployBodyContext, type DeployBodyCreator, type DeployFile, type DeployInput, type Deployment, type DeploymentCreateResponse, type DeploymentDeleteResponse, type DeploymentListResponse, type DeploymentOptions, type DeploymentResource, type DeploymentResourceContext, type DeploymentSetOptions, DeploymentStatus, type DeploymentStatusType, type DeploymentUploadOptions, DeploymentVia, type DeploymentViaType, type DnsLookup, type DnsProvider, type DnsRecord, type DnsRecordType, type Domain, type DomainDeleteResponse, type DomainDnsResponse, type DomainListResponse, type DomainRecordsResponse, type DomainResource, type DomainSetOptions, type DomainSetResult, type DomainShareResponse, DomainStatus, type DomainStatusType, type DomainValidateResponse, type DomainVerifyResponse, type ErrorResponse, ErrorType, type ExecutionEnvironment, FileValidationStatus as FILE_VALIDATION_STATUS, type Fetch, type FileValidationResult, FileValidationStatus, type FileValidationStatusType, IDEMPOTENCY_KEY_CONSTRAINTS, JUNK_DIRECTORIES, LABEL_CONSTRAINTS, LABEL_PATTERN, type LabelsResponse, type ListOptions, type ListResponse, type MD5Result, MY_API_KEY_URL, OAuthScope, type OAuthScopeType, PASSWORD_CONSTRAINTS, PUBLIC_DEPLOYMENT_TTL_SECONDS, type PingResponse, type PlatformLimits, type ResourceContext, SHIP_ENV, type SPACheckDebug, type SPACheckRequest, type SPACheckResponse, SPA_CHECK_CONSTRAINTS, SPA_DEFAULT_CONFIG, type SetupInstructionsResponse, Ship, type ShipClientOptions, ShipError, type ShipEvents, type StaticFile, type Token, type TokenCreateOptions, type TokenCreateResponse, type TokenDeleteResponse, TokenKind, type TokenKindType, type TokenListResponse, type TokenProvider, type TokenResource, UNBUILT_PROJECT_MARKERS, UNSAFE_FILENAME_CHARS, type UploadedFile, type UserVisibleActivityEvent, type ValidatableFile, type ValidationIssue, WEB_FILE_ACCEPT, __setTestEnvironment, allValidFilesReady, assertShipJsonSyntax, calculateMD5, classifyToken, createAccountResource, createDeploymentResource, createDomainResource, createTokenResource, Ship as default, deserializeLabels, extractSubdomain, filterJunk, formatFileSize, generateDeploymentUrl, generateDomainUrl, getENV, getValidFiles, hasUnbuiltMarker, hasUnsafeChars, isBlockedExtension, isCustomDomain, isDeployment, isPlatformDomain, isShipError, normalizeVia, optimizeDeployPaths, pluralize, processFilesForBrowser, serializeLabels, validateApiKey, validateApiUrl, validateCaller, validateDeployFile, validateDeployPath, validateDeployToken, validateFileName, validateFiles, validateIdempotencyKey, validatePassword, validateToken };
+export { API_KEY, API_PATHS, AUTH_BASE_PATH, type Account, type AccountDeleteResponse, type AccountGetResponse, type AccountKeyResponse, type AccountOverrides, AccountPlan, type AccountPlanType, type AccountResource, type AccountUsage, type Activity, type ActivityEvent, type ActivityListResponse, type ActivityMeta, type ApiDeployOptions, ApiHttp, type ApiHttpOptions, AuthMethod, type AuthMethodType, type BillingCancelResponse, type BillingStatus, CALLER, type CheckoutSession, DEFAULT_API, DEPLOYMENT_CONFIG_FILENAME, DEPLOY_FIELDS, DEPLOY_TOKEN, type DeployBodyContext, type DeployFile, type DeployInput, type DeployTransport, type Deployment, type DeploymentCreateResponse, type DeploymentDeleteResponse, type DeploymentListResponse, type DeploymentOptions, type DeploymentResource, type DeploymentResourceContext, type DeploymentSetOptions, DeploymentStatus, type DeploymentStatusType, type DeploymentUploadOptions, DeploymentVia, type DeploymentViaType, type DnsLookup, type DnsProvider, type DnsRecord, type DnsRecordType, type Domain, type DomainDeleteResponse, type DomainDnsResponse, type DomainListResponse, type DomainRecordsResponse, type DomainResource, type DomainSetOptions, type DomainSetResult, type DomainShareResponse, DomainStatus, type DomainStatusType, type DomainValidateResponse, type DomainVerifyResponse, type ErrorResponse, ErrorType, type ExecutionEnvironment, FileValidationStatus as FILE_VALIDATION_STATUS, type Fetch, type FileValidationResult, FileValidationStatus, type FileValidationStatusType, IDEMPOTENCY_KEY_CONSTRAINTS, JUNK_DIRECTORIES, LABEL_CONSTRAINTS, LABEL_PATTERN, type LabelsResponse, type ListOptions, type ListResponse, type MD5Result, MY_API_KEY_URL, OAuthScope, type OAuthScopeType, PASSWORD_CONSTRAINTS, PUBLIC_DEPLOYMENT_TTL_SECONDS, type PingResponse, type PlatformLimits, type RequestResult, type ResourceContext, SHIP_ENV, type SPACheckDebug, type SPACheckRequest, type SPACheckResponse, SPA_CHECK_CONSTRAINTS, SPA_DEFAULT_CONFIG, type SetupInstructionsResponse, Ship, type ShipClientOptions, ShipError, type ShipEvents, type ShipRequestInit, type StaticFile, TTL_CONSTRAINTS, type Token, type TokenCreateOptions, type TokenCreateResponse, type TokenDeleteResponse, TokenKind, type TokenKindType, type TokenListResponse, type TokenProvider, type TokenResource, type Transport, UNBUILT_PROJECT_MARKERS, UNSAFE_FILENAME_CHARS, type UploadedFile, type UserVisibleActivityEvent, type ValidatableFile, type ValidationIssue, WEB_FILE_ACCEPT, __setTestEnvironment, allValidFilesReady, assertShipJsonSyntax, calculateMD5, classifyToken, createAccountResource, createDeploymentResource, createDomainResource, createTokenResource, Ship as default, deserializeLabels, extractSubdomain, filterJunk, formatFileSize, generateDeploymentUrl, generateDomainUrl, getENV, getValidFiles, hasUnbuiltMarker, hasUnsafeChars, isBlockedExtension, isCustomDomain, isDeployment, isPlatformDomain, isShipError, normalizeVia, optimizeDeployPaths, pluralize, processFilesForBrowser, serializeLabels, validateApiKey, validateApiUrl, validateCaller, validateDeployFile, validateDeployPath, validateDeployToken, validateFileName, validateFiles, validateIdempotencyKey, validatePassword, validateToken, validateTtl };