@jokerized/decksmith 0.3.1 → 0.3.2

package/dist/types/deck/player-element.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/types/deck/player.d.ts

@@ -0,0 +1,37 @@
+/** One stop, as a host sees it. */
+export interface PlayerStop {
+    i: number;
+    label: string;
+    notes?: string;
+}
+export declare class DecksmithPlayer extends HTMLElement {
+    #private;
+    static observedAttributes: string[];
+    /** Every stop the deck reported, empty until `ds-ready`. */
+    get stops(): PlayerStop[];
+    /** Where the deck is now. */
+    get at(): number;
+    /** Whether the deck answered the handshake. */
+    get connected(): boolean;
+    connectedCallback(): void;
+    disconnectedCallback(): void;
+    attributeChangedCallback(name: string, was: string | null, now: string | null): void;
+    next(): void;
+    prev(): void;
+    go(at: number): void;
+    play(on?: boolean): void;
+}
+/**
+ * Register the element, once.
+ *
+ * GUARDED AND PARAMETERISED because `customElements.define` throws on a
+ * duplicate name, and a host page that imports this twice — two bundlers, or a
+ * hot reload — should get a no-op rather than an exception that takes the page
+ * down. The tag is an argument so a consumer whose page already owns
+ * `decksmith-player` can mount it under another name.
+ *
+ * NOT called at import time. A module with a side effect cannot be imported for
+ * its types, and `player-element.ts` exists precisely so the side-effecting
+ * entry point is a separate file a consumer opts into.
+ */
+export declare function define(tag?: string): void;

package/dist/types/deck/protocol.d.ts

@@ -0,0 +1,80 @@
+/**
+ * What a host page and a deck say to each other.
+ *
+ * ONE FILE, IMPORTED BY BOTH ENDS, so `tsc` checks the sender against the
+ * receiver. The alternative — a string literal in the runtime and a matching one
+ * in the element — is two copies of a contract that drift the first time a field
+ * is added, and the drift is invisible because `postMessage` takes `any` and a
+ * message nobody understands is simply ignored.
+ *
+ * WHY A BRIDGE AT ALL, rather than hosting the deck in the page. A deck is a
+ * whole document with its own fonts, GSAP, KaTeX, a vendored player and a ready
+ * gate, and `frameOf` in runtime.ts can only reach a SAME-ORIGIN frame — it
+ * returns null otherwise and the runtime merely warns, so a deck served from
+ * another origin would navigate perfectly and paint nothing, silently. Keeping
+ * the frame keeps that same-origin pair inside one directory, where it is always
+ * true, and makes the host link `postMessage`, which does not care about origin.
+ *
+ * VERSION COUPLING IS THE HAZARD. Every deck published before this existed has
+ * no listener, and a deck is a static artifact that outlives the tool that made
+ * it. So silence is a SUPPORTED state, not an error: the element times out, says
+ * so with a distinct code, and leaves the deck usable — it is still a deck in a
+ * frame, and its own keyboard still works.
+ */
+/** The channel name, on every message in both directions. */
+export declare const CHANNEL = "decksmith-deck";
+/** Sent by the host once the frame has loaded, to open the conversation. */
+export interface Hello {
+    channel: typeof CHANNEL;
+    type: "hello";
+}
+/**
+ * The deck's answer, and the only message that establishes the host's origin.
+ *
+ * NOTHING IS POSTED TO "*" AFTER THIS. A stop carries the slide's speaker
+ * notes, and any page on the internet can put a deck in a frame — posting
+ * wildcard would hand an arbitrary framer the presenter's notes. The origin is
+ * taken from the `hello` event and every later message is addressed to it.
+ */
+export interface Ready {
+    channel: typeof CHANNEL;
+    type: "ready";
+    /** Every stop the deck can land on, in order. */
+    stops: {
+        i: number;
+        label: string;
+        notes?: string;
+    }[];
+    /** Where it is now. */
+    at: number;
+}
+/** Where the deck landed, after any move. */
+export interface Stopped {
+    channel: typeof CHANNEL;
+    type: "stop";
+    at: number;
+    total: number;
+    label: string;
+    notes?: string;
+    playing: boolean;
+}
+/** What a host may ask for. Deliberately small: everything else is a deck concern. */
+export type Command = {
+    channel: typeof CHANNEL;
+    type: "next";
+} | {
+    channel: typeof CHANNEL;
+    type: "prev";
+} | {
+    channel: typeof CHANNEL;
+    type: "go";
+    at: number;
+} | {
+    channel: typeof CHANNEL;
+    type: "play";
+    on: boolean;
+};
+export type FromDeck = Ready | Stopped;
+export type ToDeck = Hello | Command;
+/** A message from us, rather than from anything else sharing the window. */
+export declare function isOurs(data: unknown): data is FromDeck | ToDeck;

package/dist/types/deck/runtime.d.ts

@@ -57,3 +57,39 @@ export declare function parseHash(hash: string): Pos | null;
  * longer emit falls back to its slide rather than to nothing.
  */
 export declare function findStop(stops: readonly Stop[], pos: Pos): number;
+interface Player extends HTMLElement {
+    ready?: boolean;
+    seek: (t: number) => void;
+    pause?: () => void;
+}
+/** Only what we call on a GSAP timeline. */
+interface Seekable {
+    seek: (t: number) => void;
+}
+interface Frame {
+    doc: Document;
+    timelines: Record<string, Seekable>;
+}
+/**
+ * The composition, reached through the player's iframe.
+ *
+ * Same-origin only, which means a deck must be served over http — opening
+ * `deck.html` from the filesystem gives the iframe an opaque origin and we
+ * cannot drive it. `present()` says so out loud rather than rendering blank.
+ */
+export declare function frameOf(player: Player): Frame | null;
+/** One player-page video, keyed in the island by the scene that draws its still. */
+export interface ClipSpec {
+    /** Already in embeddable form — `embedUrl` in src/pack/media.ts did that at build time. */
+    url: string;
+    /** The figure's caption. It titles the frame, which is all a screen reader gets. */
+    title: string;
+}
+/**
+ * Read the island, defensively, for the same reason `parseNarration` is
+ * defensive: a deck built before this existed has no island, and one built by a
+ * newer emitter may carry fields this reader has never heard of. Neither may do
+ * anything worse than leave the poster alone.
+ */
+export declare function parseClips(json: string | null | undefined): Record<string, ClipSpec>;
+export {};

package/dist/types/emit/archetypes/claim-figure.d.ts

@@ -1,9 +1,2 @@
-/**
- * A claim from the source, shown next to the figure that backs it.
- *
- * The layout is chosen from the figure's own aspect ratio rather than being a
- * parameter: EXPERIMENT-002 full-bled a 1.98-aspect figure and pushed its
- * caption 200px off-canvas. Only a genuine strip earns the full width.
- */
 import type { Emitter } from "../kit.js";
 export declare const claimFigure: Emitter<"claim-figure">;

package/dist/types/emit/kit.d.ts

@@ -137,6 +137,39 @@ export interface EmitContext {
      * `hyperframes lint` rejects it (`unscoped_gsap_selector`).
      */
     sid: string;
+    /**
+     * WHERE THIS SCENE BEGINS ON THE DECK'S OWN CLOCK, in seconds, ALREADY ROUNDED
+     * to invariant 10's three places — the identical number the scene wrapper
+     * publishes as `data-start`. Write it; do not round it again, because two
+     * roundings of one number is how a byte moves.
+     *
+     * Everything else an archetype emits is scene-relative, and that is the right
+     * default: an emitter that knew where it sat in the deck would be an emitter a
+     * cut could invalidate. ONE thing is not expressible that way. A `<video>` is
+     * timed by the RUNTIME, not by this scene's timeline, and the runtime reads
+     * `data-start` as an ABSOLUTE composition second — so a clip that declares a
+     * scene-relative start is seeked into a window that has already passed.
+     *
+     * MEASURED, because the alternative looked right on paper. hyperframes'
+     * compiler injects `data-start="0" data-hf-auto-start=""` into a media tag
+     * that declares no timing, and its runtime resolves that marker against the
+     * enclosing `[data-composition-id]`, which is exactly this scene — so the
+     * marker ought to have been enough. Rendered at 0.8.27, on a two-beat deck
+     * whose clip is red for 2s, green for 2s then blue for 2s and whose second
+     * scene starts at 7s: with the marker the plate is BLUE at composition 9.5s,
+     * 10.5s and 12.5s — the clip's last frame, frozen, because the render placed
+     * it at second 0 and it had ended before the scene began. With `data-start="7"`
+     * the same frames are green, green, blue: clip seconds 2.5, 3.5 and 5.5. Every
+     * gate is green over both.
+     *
+     * OPTIONAL, because the shell is not the only caller: an archetype test calls
+     * `emitScene` with a context it builds by hand, and twelve of the thirteen
+     * emitters have no use for this. The one that does refuses by name when it is
+     * missing rather than inventing a second, i.e. wrong, clock. `planCut` passes
+     * a provisional 0 for the same reason it passes provisional scene ids — its
+     * pass exists to measure holds, and every scene it emits is thrown away.
+     */
+    start: number;
 }
 /**
  * A value in a GSAP vars payload that is JavaScript rather than data.

package/dist/types/images/providers.d.ts

@@ -82,11 +82,20 @@ export declare function codexImages(opts?: CodexImagesOptions): ImageProvider;
  * something better draws it. Same request, same bytes.
  */
 export declare function drawSvg(req: ImageRequest): string;
-/** The size the tool wrote into its own SVG. `imageSize` is raster-only on purpose. */
-export declare function svgSize(bytes: Buffer): {
-    width: number;
-    height: number;
-};
+/**
+ * The size an SVG declares, for `sizeOf` in ./illustrate.ts and for anything
+ * else that already imports this module.
+ *
+ * It USED to live here, as a regex for `viewBox="0 0 %d %d"` over the first 200
+ * bytes — four integers, no units, no preamble — which is exactly the SVG
+ * `drawSvg` above writes and nothing else. Figure ingest needs to measure an SVG
+ * a stranger wrote, so the reader was generalised and moved to src/source/assets.ts
+ * beside the other formats. It moved THERE rather than staying here because
+ * that module imports nothing but node and the schemas: the reverse would put
+ * the Codex runner and this file's OpenAI adapter on the import path of every
+ * source parse, for two integers.
+ */
+export { svgSize } from "../source/assets.js";
 /** The last rung. Pure, so it cannot fail, so `illustrate` always finishes. */
 export declare function toolSvg(): ImageProvider;
 /**

package/dist/types/index.d.ts

@@ -8,12 +8,25 @@ import { type Format, type Source, type Storyboard } from "./types.js";
  */
 export { parseMarkdown } from "./source/markdown.js";
 export type { ParseOptions } from "./source/markdown.js";
+/**
+ * A web page in, a markdown document and a directory of files out — the step
+ * BEFORE `parseMarkdown`, not a replacement for it. Separate because it needs a
+ * browser and the network, which `parseMarkdown` deliberately does not.
+ *
+ * `attachClips` is exported with it because a harvest is not finished without
+ * it: the markdown dialect has no way to say `kind: "clip"`, so a page's videos
+ * come back beside the document and this is what puts them into the source. It
+ * runs BEFORE `fetchFigures`, which passes a clip through untouched.
+ */
+export { attachClips, harvest, toMarkdown } from "./source/harvest.js";
+export type { Block, Harvested, HarvestedClip, HarvestOptions } from "./source/harvest.js";
 /**
  * Figures referenced by URL, downloaded beside the source. Separate from
  * `parseMarkdown` because it touches the network and a server may want to fetch
  * through its own client instead.
  */
 export { fetchFigures } from "./source/assets.js";
+export { fetchGuarded, isBlockedAddress } from "./net/fetch.js";
 /**
  * Subset a CJK webfont over the glyphs a deck actually renders. Exported
  * because invariant 9 — a font stack naming a family the bundle does not

package/dist/types/mcp/tools.d.ts

@@ -90,6 +90,7 @@ export declare const estimateSchema: z.ZodObject<{
 export declare const createSchema: z.ZodObject<{
     document_path: z.ZodOptional<z.ZodString>;
     document_text: z.ZodOptional<z.ZodString>;
+    document_url: z.ZodOptional<z.ZodString>;
     settings: z.ZodOptional<z.ZodObject<{
         format: z.ZodOptional<z.ZodEnum<{
             [x: string]: string;
@@ -221,6 +222,25 @@ export declare function deckTools(opts: McpOptions): {
             state: import("../server/queue.js").StepState;
         }[];
         log: string[];
+    } | {
+        harvest_warnings: string[];
+        next: string;
+        deck_path?: string | undefined;
+        slides?: number | undefined;
+        duration_seconds?: number | undefined;
+        warnings?: string[] | undefined;
+        storyboard_path: string;
+        error?: import("../server/errors.js").JobError | undefined;
+        job_id: string;
+        state: import("../server/queue.js").JobState;
+        stage: import("../server/queue.js").Stage | undefined;
+        queue_position: number | undefined;
+        elapsed_seconds: number;
+        steps: {
+            name: import("../server/queue.js").Stage;
+            state: import("../server/queue.js").StepState;
+        }[];
+        log: string[];
     }>;
     /** Poll, blocking up to `wait_seconds` for the job to move on. */
     status(input: z.infer<typeof statusSchema>): Promise<{

package/dist/types/net/fetch.d.ts

@@ -0,0 +1,81 @@
+/**
+ * The one guarded door out of this process for a URL somebody else chose.
+ *
+ * Two holes made this file. `src/source/assets.ts` fetched a figure with a bare
+ * `fetch(src)` — no timeout, no size cap, no idea what came back. And
+ * `src/server/pipeline.ts` grew an SSRF pre-check, `reachable()`, which resolves
+ * the hostname, refuses the private ranges, and then hands the URL to `fetch`,
+ * which resolves it again. A pre-check the socket never honours stops the naive
+ * class and nothing else: a public host that 302s to 169.254.169.254 walks
+ * straight past it, because the address that was checked is not the address that
+ * got connected to.
+ *
+ * WHY THIS IS node:http/node:https AND NOT `fetch`. Exactly one reason, and it
+ * is the reason the file exists: `fetch` gives no way to say "connect to THIS
+ * address". `http.request` takes a `lookup`, so the address this module
+ * validated is the address the socket opens, and the second DNS answer that
+ * would have been a rebinding attack is never asked for. Everything else here —
+ * the manual redirect walk, the streaming cap, the timeout, the content-type
+ * check — could have been written over `fetch`. The pin could not, and
+ * pipeline.ts's own comment named that gap and called it unclosable. It was
+ * closable; it just needed a different client.
+ *
+ * WHAT IS STILL OPEN, because a guard that oversells itself is worse than none:
+ *  - Resolution is `dns.lookup`, the OS resolver, so `/etc/hosts` and any local
+ *    override are honoured. That is deliberate — it is how this machine resolves
+ *    every other name — but it does mean a poisoned hosts file is trusted.
+ *  - A hostname with several A records is refused if ANY of them is blocked, and
+ *    the socket is pinned to the first. That is stricter than a browser and is
+ *    the intended trade: a round-robin where one member is internal is not a
+ *    host this process wants to talk to at all.
+ *  - Nothing here bounds how many of these run at once. The caller owns that.
+ */
+export declare function isBlockedAddress(ip: string): string | null;
+export interface GuardOptions {
+    /**
+     * Cap on the body, applied to DECODED bytes — see `readCapped` and `decode`
+     * for the two places it is enforced and why it takes both.
+     */
+    maxBytes: number;
+    /** Whole-call budget: DNS, connect, every hop, and reading the body. */
+    timeoutMs: number;
+    /**
+     * Refuse unless the response's bare media type matches. Matched against the
+     * type WITHOUT its parameters, so `/^image\//` and `/^text\/html$/` both do
+     * what they look like against `text/html; charset=utf-8`.
+     */
+    accept?: RegExp;
+    /**
+     * Extra request headers, lowercased on the way in. `authorization` and
+     * `cookie` are dropped the moment a redirect changes origin.
+     */
+    headers?: Record<string, string>;
+    /**
+     * TEST SEAM, and the only way to point this at a server on this machine.
+     *
+     * It exempts loopback from the address block and lifts the 80/443 rule, which
+     * together is exactly what it takes to drive a `node:http` server on an
+     * ephemeral port through this module's real code path — see test/net.test.ts,
+     * which is the only caller. It relaxes NOTHING else: link-local, the private
+     * ranges, the non-http schemes, the hop cap, the size cap, the timeout and the
+     * content-type check all still apply, which is what makes those tests evidence
+     * about the guard rather than about a bypass of it. Nothing in src passes it.
+     */
+    allowLoopback?: boolean;
+}
+export interface Fetched {
+    bytes: Buffer;
+    /** The `Content-Type` header as sent, parameters and all — a caller decoding
+     * text needs the charset, and dropping it here would lose it for good. */
+    contentType: string;
+    /** The URL the bytes actually came from, after redirects. What a caller must
+     * resolve relative links against, and what it should cache under. */
+    url: string;
+}
+/**
+ * Fetch `url`, refusing loudly at the first thing that looks wrong.
+ *
+ * Every refusal names the URL, what was wrong with it, and what to do; a caller
+ * surfacing `err.message` to a user is giving them something actionable.
+ */
+export declare function fetchGuarded(url: string, opts: GuardOptions): Promise<Fetched>;

package/dist/types/pack/media.d.ts

@@ -37,6 +37,18 @@ export interface MediaPlan {
 }
 /** A player URL is one whose host is in the list, or a subdomain of one. */
 export declare function isEmbed(url: string): boolean;
+/**
+ * Every origin an embed can come from, deduped.
+ *
+ * DERIVED FROM THE RULES ABOVE RATHER THAN RESTATED BESIDE THEM, because the
+ * served deck's `frame-src` names exactly this list (src/server/http.ts): a host
+ * added here and forgotten there is a frame the browser refuses, and CSP refuses
+ * it the way CSP refuses everything — an empty rectangle and a line in a console
+ * nobody has open.
+ */
+export declare const EMBED_ORIGINS: readonly string[];
+/** The embeddable form of a player page, or undefined when we cannot say. */
+export declare function embedUrl(url: string): string | undefined;
 /**
  * The final policy for one asset.
  *

package/dist/types/plan/prompt.d.ts

@@ -48,6 +48,7 @@ export declare const SYSTEM: string;
  *
  * The figure block carries two facts beyond the caption — the section the image
  * sat under and the prose that refers to it — because a planner that cannot see
- * the picture has nothing else to decide what the picture is FOR.
+ * the picture has nothing else to decide what the picture is FOR. A clip carries
+ * one more: what the deck can actually show of it, which is a still.
  */
 export declare function renderSource(source: Source): string;

package/dist/types/server/pipeline.d.ts

@@ -1,21 +1,44 @@
-import { type ImageProvider, type Runner } from "../index.js";
+import { type HarvestOptions, type ImageProvider, type Runner, type Source } from "../index.js";
 import type { JobOptions } from "./options.js";
 import type { JobHandle, JobResult, Stage } from "./queue.js";
 import { type Upload } from "./upload.js";
 export interface PipelineInput {
-    upload: Upload;
+    /**
+     * The document that arrived, when a file was posted. Exactly one of this and
+     * `url` is set — `parseSubmission` is what guarantees it, and `ingest` refuses
+     * loudly rather than guessing if a direct caller hands it both or neither.
+     */
+    upload?: Upload;
+    /** The page to harvest, when a URL was posted instead of a file. */
+    url?: string;
     options: JobOptions;
     /**
      * Whether a figure named by an http(s) URL may be downloaded.
      *
-     * OFF by default, and that is a security decision, not a performance one. The
-     * document is a stranger's; `![](http://169.254.169.254/latest/meta-data/)` is
-     * a request this process would make from inside the network it runs in, and a
-     * hostname allowlist does not close it because DNS can answer differently the
-     * second time. Off, the figure is dropped and named in the warnings. On (the
-     * owner's own box, own papers), it is fetched with a count and a timeout.
+     * ON by default — src/server/main.ts sets `DECKSMITH_FETCH_FIGURES` to true —
+     * because a paper's markdown links its images and a deck that silently drops
+     * them is not the deck anyone asked for. The flag is therefore NOT the guard;
+     * `guardFigures` below is, and it refuses any URL resolving to a private,
+     * loopback or link-local address before the fetch is attempted.
+     *
+     * When it is on, the fetch itself is `fetchGuarded` in src/net/fetch.ts by way
+     * of `fetchFigures`: a 32 MB streaming cap and a 20s whole-call timeout at the
+     * socket, with the connection PINNED to the address that was validated. That
+     * last part is what closed the DNS-rebinding hole an earlier version of this
+     * comment called unclosable. `MAX_REMOTE_FIGURES` below is the count.
+     *
+     * Off, a remote figure is dropped and named in the warnings.
      */
     fetchRemoteFigures: boolean;
+    /**
+     * Caps for the harvest of `url`, overriding `HARVEST_LIMITS`.
+     *
+     * TEST SEAM, the same shape as `imageChain` and `run` below. It is the only
+     * way to point a harvest at a `node:http` server on loopback, which is what
+     * test/server.test.ts needs to drive this path with no network. Nothing in
+     * src/ sets it, so production always gets `HARVEST_LIMITS` exactly.
+     */
+    harvest?: HarvestOptions;
     /**
      * The rungs `illustrate` draws through. A test injects the tool's own SVG and
      * nothing else; absent, the stage resolves its providers from the environment
@@ -33,3 +56,23 @@ export interface PipelineInput {
 /** Which rows the step list should have, decided before anything runs. */
 export declare function stagesFor(options: JobOptions): Stage[];
 export declare function runPipeline(job: JobHandle, input: PipelineInput): Promise<JobResult>;
+/**
+ * Rewrite every figure's `src` to something safe to read, or drop the figure.
+ *
+ * `fetchFigures` does `readFile(src)` for anything that is not an http URL, and
+ * `src` is whatever the document's markdown said. A document containing
+ * `![](../../../../etc/ssh/ssh_host_rsa_key)` would otherwise have this process
+ * read it — the image sniffer rejects it a moment later, but the read already
+ * happened and the error message quotes the path. So relative paths are resolved
+ * inside the upload directory and confined there, and everything else is dropped
+ * unless remote fetching has been deliberately switched on.
+ *
+ * Dropped figures leave before the planner sees the source, so no beat can cite
+ * one and `assertRefsResolve` has nothing to fail on.
+ *
+ * EXPORTED FOR ITS TEST, like `safeUrlPath` and `parseRange` in ./http.ts. Its
+ * warnings are the only evidence of which rule fired, and they do not reach a
+ * `JobHandle` — so reading them through a whole `runPipeline` is impossible and
+ * the alternative was to leave the guard untested.
+ */
+export declare function guardFigures(source: Source, root: string, allowRemote: boolean, warnings: string[]): Promise<Source>;

package/dist/types/server/upload.d.ts

@@ -2,9 +2,10 @@
  * What arrives on the socket, treated as hostile.
  *
  * Three jobs, in order: get the bytes off the wire without letting the sender
- * choose how much memory we spend, turn them into a file and a set of fields,
- * and — if the file is a zip — get its contents onto disk without letting an
- * entry name decide where "onto disk" is.
+ * choose how much memory we spend, turn them into a `Submission` — a file or a
+ * URL, never both and never neither, plus the option fields — and, if the file
+ * is a zip, get its contents onto disk without letting an entry name decide
+ * where "onto disk" is.
  *
  * Everything here is pure except `readBody`, which is why the zip half can be
  * tested against an actually malicious archive with no server running.
@@ -44,7 +45,30 @@ export interface Upload {
     fields: Record<string, string>;
 }
 /**
- * multipart/form-data, with no dependency.
+ * What one POST carries: a document, or the address of one.
+ *
+ * A union rather than two optional fields on one record, because "exactly one of
+ * these" IS the rule, and a shape that can hold both — or neither — is a shape
+ * every reader downstream has to re-check. `parseSubmission` is the last place
+ * that can still answer the client, so both refusals live there and nothing
+ * after it asks the question again.
+ *
+ * `fields` is on both arms because the option fields belong to the REQUEST, and a
+ * URL submission has them just as an upload does. On the file arm it is the very
+ * same object as `upload.fields`, not a copy — read either; `Upload` keeps its
+ * own reference because src/mcp/tools.ts builds one without ever seeing a form.
+ */
+export type Submission = {
+    kind: "file";
+    upload: Upload;
+    fields: Record<string, string>;
+} | {
+    kind: "url";
+    url: string;
+    fields: Record<string, string>;
+};
+/**
+ * multipart/form-data, with no dependency, and the exactly-one rule enforced.
  *
  * `new Response(body, { headers }).formData()` is undici's parser, which ships
  * in Node — measured against a hand-built body with a filename containing a
@@ -52,7 +76,7 @@ export interface Upload {
  * with the right bytes. It throws a bare TypeError on a malformed body, which
  * is not a sentence anyone can act on, so it is translated here.
  */
-export declare function parseMultipart(body: Buffer, contentType: string): Promise<Upload>;
+export declare function parseSubmission(body: Buffer, contentType: string): Promise<Submission>;
 /** A zip starts "PK". Asked before unzipping so a PDF reads as a PDF. */
 export declare function looksLikeZip(bytes: Uint8Array): boolean;
 /**

package/dist/types/source/assets.d.ts

@@ -1,11 +1,84 @@
 import { type Source } from "../types.js";
-/** Fetch every figure into `dir`, rewrite `src` to the local name, measure it. */
-export declare function fetchFigures(source: Source, dir: string): Promise<Source>;
 /**
- * Intrinsic size from the file header. Just enough PNG/JPEG/GIF to answer the
- * one question layout asks — four field reads do not justify a dependency.
+ * Fetch every figure into `dir`, rewrite `src` to the local name, measure it.
+ *
+ * A figure that cannot be fetched, cannot be measured, or cannot be represented
+ * is DROPPED and named in `warnings` — the same shape `guardFigures` in
+ * src/server/pipeline.ts already uses for the figures it refuses to fetch at
+ * all. The reason is what the caller is: a whole ingest. A paper with eleven
+ * figures and one dead CDN link is still the deck someone asked for, and before
+ * this the dead link ended the run with `unrecognised image header` and no
+ * indication of which figure had produced it.
+ *
+ * `warnings` is an out-parameter rather than a second return value so the two
+ * callers that do not collect them (`decksmith ingest`, and the pipeline's own
+ * call) keep compiling unchanged, and so a caller that does collect them can
+ * pass the SAME array it already threads through `guardFigures` and have both
+ * sets of drops read as one list. Omit it and the drops go to stderr instead —
+ * dropping a figure only stops being an improvement over aborting if somebody
+ * is told which figure went.
+ */
+export declare function fetchFigures(source: Source, dir: string, warnings?: string[]): Promise<Source>;
+/** Every format this reads. Also every format a page is likely to serve a figure in. */
+export type ImageFormat = "png" | "jpeg" | "gif" | "webp" | "avif" | "svg";
+/**
+ * The format the bytes claim to be, from the header alone.
+ *
+ * Exported and separate from `imageSize` because two callers ask two different
+ * questions of the same eight bytes: what to name the file, and how to measure
+ * it. Keeping them one function is how a file ends up named after the reader
+ * that happened to succeed.
+ */
+export declare function sniffFormat(b: Buffer): ImageFormat | undefined;
+/**
+ * Intrinsic size from the file header, for every format a page may hand us.
+ *
+ * PNG, JPEG and GIF were enough while a source was a markdown file with its own
+ * images beside it. A URL is not: a page today serves WebP for the photograph,
+ * AVIF for the hero and SVG for the diagram, and a reader that knows three
+ * formats measures the other three as "unrecognised" and drops them.
+ *
+ * Still no dependency for this. Each reader below is a handful of field reads
+ * against a published header layout, and the alternative is a decoder that
+ * pulls in the whole pixel pipeline to answer two integers.
+ *
+ * It THROWS rather than returning zeros, and the message names what it saw.
+ * `figureSchema` requires a positive int, so a zero would not be caught here at
+ * all — it would surface much later as `width: too small` against a figure id,
+ * with nothing to say which URL had produced it.
  */
 export declare function imageSize(b: Buffer): {
     width: number;
     height: number;
 };
+/**
+ * The size an SVG declares, in CSS pixels.
+ *
+ * Two callers: figure ingest above, and `sizeOf` in src/images/illustrate.ts
+ * through the re-export in src/images/providers.ts, where this used to live as a
+ * regex for `viewBox="0 0 %d %d"` over the first 200 bytes. That was honest for
+ * the SVG the tool draws itself and wrong for everything else, because a real
+ * SVG opens with a licence comment above the root element, spells the viewBox
+ * with floats, writes `width="640px"`, or carries no viewBox at all.
+ *
+ * `width`/`height` win when BOTH resolve to an absolute length, because that is
+ * the intrinsic size a browser would use. The viewBox is the fallback, and it is
+ * also the right answer for the very common `width="100%"`: a percentage is a
+ * fraction of a viewport this pipeline has not created yet, so it is deliberately
+ * left unresolved rather than read as 100 pixels.
+ *
+ * CHECKED against the browser that draws these: 60 real SVGs off this machine
+ * measured here and loaded in Chrome, and all 60 agree with `naturalWidth` and
+ * `naturalHeight` to the pixel. Two deliberate divergences remain. A fractional
+ * viewBox is rounded, where Chrome's own rounding differs by up to a pixel in
+ * either direction (300.5 → 300, 300.4 → 299, 99.9 → 100), which is a ratio
+ * unchanged in the third decimal. And an SVG declaring NEITHER a size nor a
+ * viewBox is refused rather than given the 300x150 a browser hands a replaced
+ * element with no intrinsic size: that default is a CSS fallback, not a fact
+ * about the picture, and everything downstream frames the figure against the box
+ * recorded here.
+ */
+export declare function svgSize(bytes: Buffer): {
+    width: number;
+    height: number;
+};