@omelhorsite/sdk 0.15.1 → 0.17.0

package/dist/types/resources/content/intel/config.d.ts

@@ -1,135 +0,0 @@
-/** Intel config: the per-user pipeline settings. */
-import { Resource } from "../../../http";
-import type { Id, RequestOptions, Timestamp } from "../../../types";
-/**
- * The only keys {@link IntelConfig.prompts} accepts.
- *
- * Any other key fails the whole `PATCH` with
- * `400 "Prompts unknown keys: <the offenders>"`. A key that is present but
- * empty is not the same as an absent one: absent means "use the platform
- * default", present-and-empty means the pipeline gets an empty prompt.
- */
-export declare const INTEL_PROMPT_KEYS: readonly ["build", "enrich_plan", "enrich_actors", "enrich_synth", "report"];
-/** One overridable prompt in the analysis pipeline. */
-export type IntelPromptKey = (typeof INTEL_PROMPT_KEYS)[number];
-/**
- * The per-user knobs on the analysis pipeline. One row per user, created on
- * demand - see {@link IntelConfigNamespace.get}.
- */
-export interface IntelConfig {
-    readonly id: Id;
-    readonly created_at: Timestamp;
-    readonly updated_at: Timestamp;
-    /**
-     * Free text telling the classifier what "important" means for you. `null`
-     * falls back to the platform default. This is the single highest-leverage
-     * field here: everything else is a threshold applied to the score this
-     * produces.
-     */
-    readonly rubric: string | null;
-    /**
-     * Prompt overrides, keyed by {@link IntelPromptKey}. `{}` means "platform
-     * defaults everywhere"; a key present means that one stage is overridden.
-     *
-     * Nullable at the database level even though it defaults to `{}`.
-     */
-    readonly prompts: Partial<Record<IntelPromptKey, string>> | null;
-    /** LLM for the story-building pass. `null` uses the platform default. */
-    readonly build_model: string | null;
-    /** LLM for report generation. `null` uses the platform default. */
-    readonly report_model: string | null;
-    /** Stories below this importance are left out of reports. 0-10, default 4. */
-    readonly report_min_importance: number;
-    /**
-     * Stories below this importance are never web-enriched. 0-10, default 6.
-     *
-     * Lowering it does not enrich the backlog quickly: the job does three
-     * stories per run, highest importance first.
-     */
-    readonly enrich_min_importance: number;
-    /**
-     * Master switch for the enrichment pass. `false` leaves every story at
-     * `enriched: false` and `details: null` for ever.
-     */
-    readonly web_search: boolean;
-    /**
-     * How many {@link IntelSource} rows you may own. 1-500, default 50.
-     *
-     * Enforced on CREATE only (`validate :within_source_quota, on: :create`), so
-     * lowering it below your current count does not delete anything - it just
-     * stops the next create with `400 "Source limit reached (N)"`.
-     */
-    readonly max_sources: number;
-}
-/**
- * Arguments for {@link IntelConfigNamespace.update}.
- *
- * Every key is optional and only the keys you send are written -
- * `assign_attributes` over a permitted hash - so this is a genuine partial
- * update, unlike {@link UpdateIntelSourceInput.config}.
- */
-export interface UpdateIntelConfigInput {
-    readonly rubric?: string | null;
-    /**
-     * REPLACES the whole prompts object. Same trap as
-     * {@link UpdateIntelSourceInput.config}: it is one JSON column, so a partial
-     * object drops the keys you left out. Spread the current value.
-     *
-     * Only {@link INTEL_PROMPT_KEYS} are accepted; anything else fails the whole
-     * request with a 400 naming the offenders.
-     */
-    readonly prompts?: Partial<Record<IntelPromptKey, string>>;
-    readonly buildModel?: string | null;
-    readonly reportModel?: string | null;
-    /** 0-10. Outside the range is a 400, not a clamp. */
-    readonly reportMinImportance?: number;
-    /** 0-10. Outside the range is a 400, not a clamp. */
-    readonly enrichMinImportance?: number;
-    readonly webSearch?: boolean;
-    /** 1-500. Outside the range is a 400, not a clamp. */
-    readonly maxSources?: number;
-}
-/**
- * `/intel_config` - the per-user pipeline settings.
- *
- * A Rails SINGULAR resource (`resource :intel_config`), so the path has no id
- * and there is no listing: `GET /intel_config` and `PATCH /intel_config` are
- * the whole surface. Both act on the caller's own row and there is no way to
- * address anybody else's.
- */
-export declare class IntelConfigNamespace extends Resource {
-    /**
-     * `GET /intel_config` - your settings.
-     *
-     * **This read WRITES.** The controller calls `IntelConfig.for(Current.user)`,
-     * which is `find_or_create_by!`, so a first call inserts the row with the
-     * column defaults and returns it. Consequences worth knowing: it is not safe
-     * to fire at high frequency (two concurrent first calls race on the unique
-     * index and one raises), the response is a `200` even when it just created
-     * something, and `created_at` on a "read" can be now.
-     *
-     * @throws {OmsApiError} 403 `"Intel access is restricted."` outside the
-     *   allowlist - checked before the row is created, so a refused caller does
-     *   not leave a row behind.
-     */
-    get(options?: RequestOptions): Promise<IntelConfig>;
-    /**
-     * `PATCH /intel_config` - changes settings. Answers with the whole row.
-     *
-     * A genuine partial update for the scalar fields, and a whole-object replace
-     * for `prompts` - see {@link UpdateIntelConfigInput.prompts}.
-     *
-     * The route also accepts `PUT`, and it means exactly the same thing: Rails
-     * maps both onto `update` and the controller does not read the verb. There is
-     * no "replace the whole config" call.
-     *
-     * Failures are a `400` whose body is ONE sentence, not a field map:
-     * `ApplicationRecord#error_messages` is `errors.full_messages.to_sentence`,
-     * so several violations arrive joined by commas and "and". Parse it for
-     * humans, not for code.
-     *
-     * @throws {OmsApiError} 400 for a threshold outside `0..10`, a `max_sources`
-     *   outside `1..500`, or a `prompts` key outside {@link INTEL_PROMPT_KEYS}.
-     */
-    update(input: UpdateIntelConfigInput, options?: RequestOptions): Promise<IntelConfig>;
-}

package/dist/types/resources/content/intel/index.d.ts

@@ -1,53 +0,0 @@
-/** The `intel` namespace and everything under it. */
-import { type ApiClient, Resource } from "../../../http";
-import { IntelArticlesNamespace } from "./articles";
-import { IntelConfigNamespace } from "./config";
-import { IntelItemsNamespace } from "./items";
-import { IntelReportsNamespace } from "./reports";
-import { IntelScriptsNamespace } from "./scripts";
-import { IntelSourcesNamespace } from "./sources";
-import { IntelStatsNamespace } from "./stats";
-export * from "./articles";
-export * from "./config";
-export * from "./items";
-export * from "./reports";
-export * from "./scripts";
-export * from "./sources";
-export * from "./stats";
-export * from "./types";
-/**
- * The `intel` namespace, reachable as `oms.content.intel`.
- *
- * A tour of the data model, because the names do not give it away:
- *
- * 1. a {@link IntelScript} knows HOW to fetch one kind of feed;
- * 2. an {@link IntelSource} is that script plus its settings - a feed you
- *    actually follow;
- * 3. polling a source writes {@link IntelItem} rows: raw, unprocessed, one per
- *    thing the feed published;
- * 4. the analysis pipeline groups items into {@link IntelArticle} stories,
- *    scores them against your {@link IntelConfig} rubric, enriches the
- *    important ones and links related ones together;
- * 5. {@link IntelReport} digests summarise a closed time window of stories.
- *
- * Only steps 1 and 2 are yours to write. Everything from step 3 on is produced
- * by background jobs and is read-only over HTTP - a delete is the only mutation
- * you get, and it is a hide, not an undo.
- */
-export declare class IntelNamespace extends Resource {
-    /** Stories: the analysed, grouped, scored output. Read plus delete. */
-    readonly articles: IntelArticlesNamespace;
-    /** Generated digests over closed time windows. Read plus delete. */
-    readonly reports: IntelReportsNamespace;
-    /** The feeds you follow. Full CRUD, plus a manual run. */
-    readonly sources: IntelSourcesNamespace;
-    /** The fetchers. Full CRUD over yours; the built-ins are read-only. */
-    readonly scripts: IntelScriptsNamespace;
-    /** The raw material behind the stories. Read plus delete. */
-    readonly items: IntelItemsNamespace;
-    /** Your rubric, thresholds and prompt overrides. */
-    readonly config: IntelConfigNamespace;
-    /** Dashboard counters, in one expensive call. */
-    readonly stats: IntelStatsNamespace;
-    constructor(http: ApiClient);
-}

package/dist/types/resources/content/intel/items.d.ts

@@ -1,91 +0,0 @@
-/** Intel items: the raw material behind the stories. */
-import { Resource } from "../../../http";
-import type { ListParams } from "../../../listing";
-import type { Id, Paginated, RequestOptions, Timestamp } from "../../../types";
-/**
- * A raw item, exactly as a script returned it.
- *
- * Written only by `Intel::FetchSourceJob`; over HTTP it is read-only plus a
- * delete. Items are the substrate the stories are built from - the story never
- * copies the body, it points here.
- */
-export interface IntelItem {
-    readonly id: Id;
-    readonly created_at: Timestamp;
-    readonly updated_at: Timestamp;
-    /** Which source produced it. */
-    readonly intel_source_id: Id;
-    /**
-     * The script's own id for this item, unique per source. This is the
-     * de-duplication key: a second poll that returns the same `external_id` does
-     * not create a second row.
-     */
-    readonly external_id: string;
-    readonly title: string | null;
-    /** The body the script extracted. Can be large; a listing carries all of it. */
-    readonly content: string | null;
-    readonly url: string | null;
-    readonly author: string | null;
-    /** Publication time as the feed reported it, not as we saw it. */
-    readonly published_at: Timestamp | null;
-    /** When the poll that produced this item ran. Never null. */
-    readonly fetched_at: Timestamp;
-}
-/** Filter columns of `GET /intel_items`, on top of {@link BASE_FILTER_COLUMNS}. */
-export declare const INTEL_ITEM_FILTER_COLUMNS: readonly ["intel_source_id", "external_id", "title", "content", "url"];
-/** Filters for {@link IntelItemsNamespace.list}. */
-export interface ListIntelItemsParams extends ListParams<(typeof INTEL_ITEM_FILTER_COLUMNS)[number]> {
-    /** Only items produced by one source. Sent as `exact_search[intel_source_id]`. */
-    readonly sourceId?: Id;
-}
-/**
- * `/intel_items` - the raw material.
- *
- * Read-only plus a delete: `creatable_by?` and `updatable_by?` are hard `false`
- * and the route is `only: [:index, :show, :destroy]`. Items are written by
- * `Intel::FetchSourceJob` and by nothing else.
- *
- * It is here because the stories only carry a citation stub
- * ({@link IntelArticleSourceRef}) and this is the only way to read the body
- * behind one.
- */
-export declare class IntelItemsNamespace extends Resource {
-    /**
-     * `GET /intel_items` - raw items, newest first.
-     *
-     * **Heavy.** Every row carries {@link IntelItem.content} in full - the whole
-     * article text a script scraped - and there is no lighter view. The SDK
-     * defaults to a page of 25 for that reason; raising it is how you get a
-     * multi-megabyte response.
-     *
-     * Declared filters: `intel_source_id`, `external_id`, `title`, `content`,
-     * `url`, plus the inherited three. Note `processed_at` is NOT among them and
-     * is not on the payload either, so there is no way to list only the
-     * unprocessed items - {@link IntelStats.totals.pending_items} is the only
-     * window onto that backlog.
-     *
-     * The controller sets no ordering; the SDK sends `created_at:desc`.
-     */
-    list(params?: ListIntelItemsParams, options?: RequestOptions): Promise<Paginated<IntelItem>>;
-    /**
-     * `GET /intel_items/:id` - one raw item.
-     *
-     * There are no `:extended` extras, so this is the same shape a listing row
-     * has. Use it to expand one {@link IntelArticleSourceRef} without
-     * pulling a page of bodies.
-     *
-     * @throws {OmsApiError} 404 when the item is not yours.
-     */
-    get(id: Id, options?: RequestOptions): Promise<IntelItem>;
-    /**
-     * `DELETE /intel_items/:id`. `204`, empty body.
-     *
-     * Rarely what you want. The item's `external_id` uniqueness is what stops the
-     * next poll re-fetching it, so deleting one invites it straight back on the
-     * following run - and if the story built from it survives, you get a second
-     * citation of the same thing. Delete the SOURCE, or leave items alone.
-     *
-     * @throws {OmsApiError} 404 when the item is not yours.
-     */
-    delete(id: Id, options?: RequestOptions): Promise<void>;
-}

package/dist/types/resources/content/intel/reports.d.ts

@@ -1,108 +0,0 @@
-/** Intel reports: generated digests over closed time windows. */
-import { Resource } from "../../../http";
-import type { ListParams } from "../../../listing";
-import type { Id, Json, Paginated, RequestOptions, Timestamp } from "../../../types";
-import type { IntelArticleCategory, IntelReportKind } from "./types";
-/** A story as a report inlines it. Four keys, no summary and no body. */
-export interface IntelReportArticleRef {
-    readonly id: Id;
-    readonly title: string | null;
-    readonly importance: number;
-    readonly category: IntelArticleCategory | null;
-}
-/**
- * A generated report over one closed time window.
- *
- * The index shape. `GET /intel_reports/:id` adds three keys - see
- * {@link IntelReportDetail}.
- *
- * There is at most ONE report per `(user, kind, period_end)`: the migration
- * puts a unique index on that triple precisely so a re-run of
- * `GenerateReportJob` cannot mint a duplicate. Windows are the last CLOSED
- * period, computed by `IntelReport.last_window`, so a `"day"` report covers
- * yesterday and never the day in progress.
- */
-export interface IntelReport {
-    readonly id: Id;
-    readonly created_at: Timestamp;
-    readonly updated_at: Timestamp;
-    /** Which window: see {@link INTEL_REPORT_KINDS}. */
-    readonly kind: IntelReportKind;
-    /** Title the model wrote. Nullable. */
-    readonly title: string | null;
-    /** Start of the window, inclusive. */
-    readonly period_start: Timestamp;
-    /** End of the window, exclusive. Also the sort key of the listing. */
-    readonly period_end: Timestamp;
-    /** LLM that wrote it, as configured at generation time. Nullable. */
-    readonly model: string | null;
-}
-/** `GET /intel_reports/:id` - the `:extended` view. */
-export interface IntelReportDetail extends IntelReport {
-    /** The report body, usually Markdown. `null` if generation failed halfway. */
-    readonly content: string | null;
-    /**
-     * Whatever the generator chose to record about the run. A free-form JSON
-     * object with no schema on either side, defaulting to `{}` - which is why it
-     * is typed as a bag rather than as fields. Read it defensively.
-     */
-    readonly stats: Record<string, Json> | null;
-    /** The stories the report covered, most important first. */
-    readonly articles: IntelReportArticleRef[];
-}
-/** Filter columns of `GET /intel_reports`, on top of {@link BASE_FILTER_COLUMNS}. */
-export declare const INTEL_REPORT_FILTER_COLUMNS: readonly ["kind"];
-/** Filters for {@link IntelReportsNamespace.list}. */
-export interface ListIntelReportsParams extends ListParams<(typeof INTEL_REPORT_FILTER_COLUMNS)[number]> {
-    /**
-     * Narrow to one window, e.g. `"day"`. Sent as `exact_search[kind]`, so it is
-     * equality rather than a prefix match - `"6h"` will not also match `"6hx"`.
-     *
-     * Passing it through {@link ListParams.search} instead would be a
-     * partial match and would work too; `kind` is on this controller's
-     * `search_params` allowlist. Equality is what you want.
-     */
-    readonly kind?: IntelReportKind;
-}
-/**
- * `GET /intel_reports` - the generated digests.
- *
- * Read-only plus a delete, for the same reason as the stories: reports come
- * from `Intel::GenerateReportJob`. There is no way to ask for one to be
- * generated over HTTP.
- */
-export declare class IntelReportsNamespace extends Resource {
-    /**
-     * `GET /intel_reports` - your reports, newest window first.
-     *
-     * `period_end DESC` is applied by the controller; as with the stories, a
-     * `order` of your own becomes the PRIMARY key and this becomes the
-     * tie-breaker.
-     *
-     * `kind` is the only declared filter beyond the inherited three. Use
-     * {@link ListIntelReportsParams.kind}, which sends it as an exact match.
-     *
-     * @throws {OmsApiError} 403 `"Intel access is restricted."` outside the
-     *   allowlist.
-     */
-    list(params?: ListIntelReportsParams, options?: RequestOptions): Promise<Paginated<IntelReport>>;
-    /**
-     * `GET /intel_reports/:id` - the report with its body and its stories.
-     *
-     * @throws {OmsApiError} 404 when the report is not yours.
-     */
-    get(id: Id, options?: RequestOptions): Promise<IntelReportDetail>;
-    /**
-     * `DELETE /intel_reports/:id`. `204`, empty body.
-     *
-     * The stories it cited are untouched - only the join rows go.
-     *
-     * A deleted report can come back: `GenerateReportJob` is keyed by the unique
-     * `(user, kind, period_end)` index, and deleting the row frees that key, so
-     * the next dispatcher pass over the same window will regenerate it. Delete a
-     * report to re-run it, not to suppress it.
-     *
-     * @throws {OmsApiError} 404 when the report is not yours.
-     */
-    delete(id: Id, options?: RequestOptions): Promise<void>;
-}

package/dist/types/resources/content/intel/stats.d.ts

@@ -1,105 +0,0 @@
-/** Intel stats: the dashboard counters. */
-import { Resource } from "../../../http";
-import type { RequestOptions } from "../../../types";
-/** One category bucket of {@link IntelStats}. */
-export interface IntelCategoryCount {
-    readonly category: string;
-    /** Named `c`, not `count`. */
-    readonly c: number;
-}
-/** One day of the {@link IntelStats} histogram. */
-export interface IntelDayCount {
-    /** `YYYY-MM-DD`, from Postgres `DATE(last_seen_at)`. Not a full timestamp. */
-    readonly day: string;
-    readonly c: number;
-}
-/**
- * The importance histogram, with the backend's own Portuguese bucket names.
- *
- * The boundaries are hard-coded server-side and are not
- * configurable: `critico` >=9, `alta` 7-8, `media` 5-6, `baixa` 3-4, `ruido`
- * <3. Note they are NOT the same thresholds as
- * {@link IntelConfig.report_min_importance} or
- * {@link IntelConfig.enrich_min_importance} - those are yours, these are the
- * dashboard's.
- */
-export interface IntelImportanceBuckets {
-    readonly critico: number;
-    readonly alta: number;
-    readonly media: number;
-    readonly baixa: number;
-    readonly ruido: number;
-}
-/** Row counts on the {@link IntelStats} answer. */
-export interface IntelStatsTotals {
-    /** Stories you own. */
-    readonly articles: number;
-    /**
-     * **Not the number of feeds you have configured.** This counts the
-     * story-to-item POINTER rows, so this is "how many citations exist across
-     * all my stories" and it grows without bound as
-     * stories accumulate. If you want the number of configured sources, read the
-     * length of {@link IntelSourcesNamespace.list}. The name is the backend's and
-     * the SDK does not rename it, but do not put it under a "Sources" label.
-     */
-    readonly sources: number;
-    readonly reports: number;
-    /** Raw items you own, processed or not. */
-    readonly items: number;
-    /**
-     * Items the analysis pipeline has not consumed yet (`processed_at IS NULL`).
-     *
-     * The one number worth watching: a figure that climbs and never falls means
-     * the pipeline is not running - most often because `Intel::LlmClient` is
-     * disabled for want of an API key, in which case `AnalysisDispatcherJob`
-     * returns immediately and silently.
-     */
-    readonly pending_items: number;
-}
-/**
- * `GET /intel_stats` - counters for the intel dashboard.
- *
- * Not a record: it has no `id`, no timestamps and no `:extended` view.
- */
-export interface IntelStats {
-    readonly totals: IntelStatsTotals;
-    /**
-     * Categories by story count, descending. Stories with a `null` category are
-     * EXCLUDED, so these do not sum to `totals.articles`.
-     */
-    readonly by_category: IntelCategoryCount[];
-    /**
-     * The last 30 days by `last_seen_at`, ascending.
-     *
-     * Sparse: a day with no activity is simply ABSENT, not present with zero.
-     * Fill the gaps before plotting or the line will lie about its own x-axis.
-     */
-    readonly by_day: IntelDayCount[];
-    readonly by_importance: IntelImportanceBuckets;
-    /** Stories touched in the last 24 hours. */
-    readonly last24h: number;
-}
-/** `/intel_stats` - the dashboard counters. One route, one verb. */
-export declare class IntelStatsNamespace extends Resource {
-    /**
-     * `GET /intel_stats` - every counter the intel dashboard shows, in one call.
-     *
-     * Also a Rails singular resource, so the path is `/intel_stats` with no id
-     * despite the plural spelling.
-     *
-     * **Cost, and the reason not to poll this.** The controller does
-     * `articles.pluck(:importance)` - it loads the importance of EVERY story you
-     * own into Ruby memory to build {@link IntelStats.by_importance} - and then
-     * runs five more aggregate queries beside it. There is no cache, no `ETag`
-     * (the hand-written action never calls `stale?`, unlike every list in this
-     * file) and therefore no `304`. Cost grows linearly with your story count for
-     * ever. Fetch it on a dashboard open, not on a timer.
-     *
-     * Read {@link IntelStatsTotals.sources} before you label it: it does not
-     * count your feeds.
-     *
-     * @throws {OmsApiError} 403 `"Intel access is restricted."` outside the
-     *   allowlist.
-     */
-    get(options?: RequestOptions): Promise<IntelStats>;
-}

package/dist/types/resources/content/intel/types.d.ts

@@ -1,86 +0,0 @@
-/** Vocabulary shared across the intel families. */
-/**
- * ## Access: this is effectively a one-user feature
- *
- * Every intel route is gated by a fixed allowlist of one handle plus admins.
- * So: anonymous is `401`, any other signed-in account is
- * `403 "Intel access is restricted."`, and no amount of correct request
- * shaping changes that. Do not build a shared feature on it, and do not
- * treat a 403 here as a bug in the caller.
- *
- * An OAuth access token is `403 {"error":"insufficient_scope"}` on every
- * route below. Session credential only.
- *
- * ## Ids are STRINGS here
- *
- * Articles, reports, sources, scripts, items and the config row all carry
- * opaque string ids, unlike blogs, notifications, jokes and Space Invaders
- * games, whose ids are integers. Nothing in intel is ever a number you can
- * compare or sort by.
- *
- * ## Ceilings
- *
- * None of their own. Every route rides the general bucket: 600 requests per
- * minute for an authenticated caller. Two of them are still expensive and are
- * documented as such - {@link IntelStatsNamespace.get} and
- * {@link IntelSourcesNamespace.run}.
- */
-/** Categories a story can carry. `null` when the classifier declined to pick one. */
-export declare const INTEL_ARTICLE_CATEGORIES: readonly ["incidente", "politica", "comunidade", "sociedade", "internacional", "economia", "outro"];
-/**
- * A story's category.
- *
- * Widened with `string & {}` deliberately: the list is a Ruby constant that a
- * migration can extend without the SDK noticing, and a `switch` that fails to
- * compile on a new category is worse than one that falls through to a default.
- * The backend DOES validate inclusion, so a value outside the list can only
- * mean the constant moved.
- */
-export type IntelArticleCategory = (typeof INTEL_ARTICLE_CATEGORIES)[number] | (string & {});
-/** Report windows a report can cover. */
-export declare const INTEL_REPORT_KINDS: readonly ["6h", "day", "week", "month"];
-/** Which window a report covers. */
-export type IntelReportKind = (typeof INTEL_REPORT_KINDS)[number] | (string & {});
-/**
- * Base of the third-party image proxy {@link intelArticleImageUrl} builds on.
- *
- * `wsrv.nl` is a free public image CDN. It is NOT this API and NOT our
- * infrastructure.
- */
-export declare const INTEL_IMAGE_PROXY_BASE_URL = "https://wsrv.nl/";
-/** Knobs for {@link intelArticleImageUrl}. */
-export interface IntelImageOptions {
-    /** Target width in pixels. Default 480. Height follows the aspect ratio. */
-    readonly width?: number;
-    /** Quality, 1-100. Default 45 - low on purpose; these are thumbnails. */
-    readonly quality?: number;
-}
-/**
- * Builds a resized, re-compressed URL for {@link IntelArticle.image_url}.
- *
- * Pure string building, no request, isolate-safe. Returns `""` for a story with
- * no image so it can be dropped straight into an `<img src>` without a
- * conditional - though a real client should test the field and render nothing.
- *
- * ## What this actually does, and why you might not want it
- *
- * `image_url` is the raw `og:image` of a news site: full size, arbitrary
- * format, arbitrary weight, and served from that site's own host. Nothing in
- * this API resizes it. This helper routes it through `wsrv.nl`, a free public
- * image CDN, which fetches the origin image and hands back a width-limited
- * WebP.
- *
- * The trade is explicit and it is not the SDK's to make silently:
- *
- * - the ORIGIN URL is sent to a third party in a query string, so wsrv.nl
- *   learns which article your user is looking at, and so does anyone reading
- *   the request. There is no credential involved - the images are public - but
- *   it is still a referrer-shaped leak;
- * - availability is theirs, not ours. A wsrv.nl outage is a page of broken
- *   images, and there is no fallback in the URL;
- * - `&we` asks it not to enlarge images smaller than `width`.
- *
- * If neither trade suits you, use {@link IntelArticle.image_url} directly and
- * size it in CSS.
- */
-export declare function intelArticleImageUrl(imageUrl: string | null | undefined, options?: IntelImageOptions): string;