@omelhorsite/sdk 0.13.0 → 0.16.0

package/dist/types/resources/quotas.d.ts

@@ -19,8 +19,9 @@
  *   what is stored RIGHT NOW and only falls when something is deleted; waiting
  *   does not give it back.
  * - **Anonymous callers get a shorter list.** Without a credential the server
- *   answers with the daily resources only, counted per IP, because an
- *   anonymous caller has no file tree and no music library. Never index the
+ *   answers with the daily tool resources only, counted per IP, because an
+ *   anonymous caller has no file tree, no music library and no way to reach
+ *   a model or the search engines. Never index the
  *   array by position - look the resource up by name, or use
  *   {@link quotaFor}, which returns `undefined` rather than lying.
  *
@@ -44,14 +45,16 @@ import type { RequestOptions } from "../types";
  * widened to `string` on purpose, so an unknown name arrives as data rather
  * than as a type error in a client nobody has rebuilt.
  */
-export declare const QUOTA_RESOURCES: readonly ["vocal_separation_seconds", "transcription_seconds", "caption_seconds", "jumpstyle_edits", "storage_nodes", "music_storage_bytes"];
+export declare const QUOTA_RESOURCES: readonly ["vocal_separation_seconds", "transcription_seconds", "caption_seconds", "jumpstyle_edits", "storage_nodes", "music_storage_bytes", "llm_requests", "llm_cost_microusd", "search_requests"];
 /** One of {@link QUOTA_RESOURCES}. */
 export type QuotaResource = (typeof QUOTA_RESOURCES)[number];
 /**
  * What the numbers count. `"seconds"` of media, `"count"` of whole things
- * (edits, files and folders), `"bytes"` of stored media.
+ * (edits, files and folders, model calls, searches), `"bytes"` of stored
+ * media, `"microusd"` of model spend (millionths of a US dollar, so
+ * `200_000` is 0.20 USD).
  */
-export type QuotaUnit = "seconds" | "count" | "bytes";
+export type QuotaUnit = "seconds" | "count" | "bytes" | "microusd";
 /**
  * `"daily"` spends and resets at midnight, server time. `"total"` is what is
  * stored right now and only falls when something is deleted.

package/dist/types/resources/search.d.ts

@@ -103,8 +103,44 @@ export interface SearchResponse {
     /** Whether asking for `page + 1` is likely to return anything. */
     readonly has_more: boolean;
 }
+/** Longer values answer `400`. */
+export declare const SEARCH_PAGE_MAX_URL_LENGTH = 2000;
+/** `maxChars` outside this range answers `400`. */
+export declare const SEARCH_PAGE_MIN_CHARS = 200;
+export declare const SEARCH_PAGE_MAX_CHARS = 20000;
+export interface SearchPageInput {
+    /** A public `http(s)` URL. Private, loopback and link-local addresses answer `422`. */
+    readonly url: string;
+    /** How much text to return, {@link SEARCH_PAGE_MIN_CHARS} to {@link SEARCH_PAGE_MAX_CHARS}; defaults to 8000. */
+    readonly maxChars?: number;
+}
+/** The readable part of one page: scripts, navigation, footers and forms stripped. */
+export interface SearchPage {
+    /** Where the page was actually read from, after redirects. */
+    readonly url: string;
+    readonly host: string;
+    /** Plain text, at most 200 characters; empty when the page has no title. */
+    readonly title: string;
+    /** Plain text, whitespace collapsed, cut at `maxChars`. Never empty: a page with nothing readable is a `422`. */
+    readonly text: string;
+}
 /** The `search` namespace, reachable as `oms.search`. */
 export declare class SearchNamespace extends Resource {
+    /**
+     * `GET /search/page` - reads one public web page and returns its main text.
+     * The natural follow-up to {@link query}: search first, then read the hits
+     * worth reading in full.
+     *
+     * Only `http` and `https`, only public addresses, at most three redirects,
+     * and pages that are not HTML or text are refused. The server keeps the
+     * answer for ten minutes, so reading the same page twice is cheap.
+     *
+     * @throws {OmsApiError} 400 for a missing or overlong URL or a `maxChars`
+     *   out of range; 401 without a credential; 422 with `error: "unreadable"`
+     *   and a `message` saying why (private address, not HTML, unreachable,
+     *   HTTP error, nothing readable); 429 above 60 reads a minute.
+     */
+    readPage(input: SearchPageInput, options?: RequestOptions): Promise<SearchPage>;
     /**
      * `GET /search` - runs one search and returns one page of merged results.
      *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omelhorsite/sdk",
-  "version": "0.13.0",
+  "version": "0.16.0",
   "description": "TypeScript SDK for the omelhorsite API. Isolate-safe: no node builtins, no environment access, no stdout.",
   "type": "module",
   "license": "UNLICENSED",

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

@@ -1,230 +0,0 @@
-/** Intel stories: the analysed, grouped, scored output. */
-import { Resource } from "../../../http";
-import type { ListParams } from "../../../listing";
-import type { Id, Paginated, RequestOptions, Timestamp } from "../../../types";
-import type { IntelArticleCategory, IntelReportKind } from "./types";
-/**
- * A story: several raw items about the same event, grouped, scored and
- * categorised by the analysis pipeline.
- *
- * This is the shape an INDEX row has. `GET /intel_articles/:id` renders
- * `:extended`, which is this plus four more keys - see
- * {@link IntelArticleDetail}. The detail is always a superset, never a
- * different record.
- */
-export interface IntelArticle {
-    readonly id: Id;
-    readonly created_at: Timestamp;
-    readonly updated_at: Timestamp;
-    /** Headline the model wrote. Nullable: the column has no `NOT NULL`. */
-    readonly title: string | null;
-    /** One-paragraph summary. Nullable for the same reason. */
-    readonly summary: string | null;
-    /**
-     * 0-10, validated `only_integer, in: 0..10`. The buckets the dashboard uses
-     * are in {@link IntelStats.by_importance} and they are NOT evenly spaced:
-     * >=9 critical, 7-8 high, 5-6 medium, 3-4 low, <3 noise.
-     */
-    readonly importance: number;
-    /** See {@link IntelArticleCategory}. `null` when unclassified. */
-    readonly category: IntelArticleCategory | null;
-    /**
-     * Free-form tags. The column defaults to `[]`, but it is nullable, so a row
-     * written before the default landed can still hand you `null`. Do not map
-     * over it without a guard.
-     */
-    readonly tags: string[] | null;
-    /**
-     * The `og:image` of one of the story's sources, stored RAW and uncompressed
-     * - it points at whatever news site published it, not at this API. Render it
-     * through {@link intelArticleImageUrl} rather than directly; that helper
-     * explains the trade it makes.
-     */
-    readonly image_url: string | null;
-    /**
-     * Whether the web-search enrichment pass has run on this story.
-     *
-     * `false` is not a failure, it is a queue position: `AnalyzeUserJob` enriches
-     * at most three stories per run, only those at or above
-     * {@link IntelConfig.enrich_min_importance}, and only while
-     * {@link IntelConfig.web_search} is on. A low-importance story stays `false`
-     * for ever, by design.
-     */
-    readonly enriched: boolean;
-    /** When the story was first built. */
-    readonly first_seen_at: Timestamp;
-    /** Touched every time a new item joins the story. This is the "recency" clock. */
-    readonly last_seen_at: Timestamp;
-    /**
-     * How many raw items back this story.
-     *
-     * Costs one COUNT query per row on the listing. A page of 500 stories is
-     * 500 extra queries. This is the reason to keep `pageSize` modest on
-     * {@link IntelArticlesNamespace.list}.
-     */
-    readonly n_sources: number;
-}
-/** One raw item cited by a story, as `:extended` inlines it. */
-export interface IntelArticleSourceRef {
-    /** Id of the {@link IntelItem}. Fetch the full row with `items.get(id)`. */
-    readonly id: Id;
-    /** Name of the {@link IntelSource} the item came from, or `null` if it was deleted. */
-    readonly source_name: string | null;
-    readonly title: string | null;
-    readonly url: string | null;
-    readonly published_at: Timestamp | null;
-}
-/**
- * A story related to this one, as `:extended` inlines it.
- *
- * "Related" is not "duplicate": duplicates are merged during dedup and never
- * become two rows. `IntelArticleLink` is an undirected edge between two
- * DISTINCT stories, which is why {@link relation} is one label describing the
- * pair rather than a direction.
- */
-export interface IntelRelatedArticleRef {
-    readonly id: Id;
-    readonly title: string | null;
-    readonly importance: number;
-    readonly category: IntelArticleCategory | null;
-    /** Free text the model wrote for the edge, e.g. a pattern name. Nullable. */
-    readonly relation: string | null;
-}
-/** A report this story appears in, as `:extended` inlines it. Newest period first. */
-export interface IntelArticleReportRef {
-    readonly id: Id;
-    readonly kind: IntelReportKind;
-    readonly title: string | null;
-    readonly period_end: Timestamp;
-}
-/**
- * `GET /intel_articles/:id` - the `:extended` view.
- *
- * Four keys the listing does not carry, and all four are joins run inline:
- * `sources` walks `intel_items`, `related` walks the link table in
- * BOTH directions, `reports` orders the report join by `period_end`. There is
- * no paging on any of them, so a story that has been running for a week can
- * inline a lot of rows.
- */
-export interface IntelArticleDetail extends IntelArticle {
-    /** The long body. `null` until the enrichment pass writes one. */
-    readonly details: string | null;
-    /** Every raw item behind the story. Length matches {@link IntelArticle.n_sources}. */
-    readonly sources: IntelArticleSourceRef[];
-    /** Stories linked to this one. `[]` when the linker found nothing. */
-    readonly related: IntelRelatedArticleRef[];
-    /** Reports that cited this story, newest period first. */
-    readonly reports: IntelArticleReportRef[];
-}
-/** Filter columns of `GET /intel_articles`, on top of {@link BASE_FILTER_COLUMNS}. */
-export declare const INTEL_ARTICLE_FILTER_COLUMNS: readonly ["title", "summary", "category", "importance", "enriched"];
-/** Filters for {@link IntelArticlesNamespace.list}. */
-export interface ListIntelArticlesParams extends ListParams<(typeof INTEL_ARTICLE_FILTER_COLUMNS)[number]> {
-    /**
-     * Free-text search over `title`, `summary` AND `details`.
-     *
-     * A TOP-LEVEL parameter, not a `search` key: the controller reads
-     * `params[:q]` itself, which is why it can reach `details` (a column that is
-     * not in `search_params` at all) and why an unknown-filter 400 cannot
-     * happen for it.
-     *
-     * Three ways it differs from {@link ListParams.search}:
-     *
-     * - it is **accent-SENSITIVE**. The controller does `LOWER(col) LIKE
-     *   LOWER(term)`, with no unaccenting, while the list DSL's `search` strips
-     *   accents on both sides. `"policia"` will not find `"polícia"` here.
-     * - `%` and `_` in your term are **not escaped**. The controller wraps the
-     *   term as `"%#{q}%"` and binds it, so a term containing `%` is a wildcard,
-     *   not a literal percent sign. Not an injection - it is a bound parameter -
-     *   but a surprise. Strip them if you are passing user input through.
-     * - it is an unanchored `LIKE` over three text columns with no index, so it
-     *   is a sequential scan of your stories. Fine for thousands, not for
-     *   millions.
-     */
-    readonly q?: string;
-    /**
-     * Keep only stories at or above this importance. Also top-level.
-     *
-     * Sent through Ruby's `String#to_i`, which does NOT raise: `"high"` becomes
-     * `0` and the filter silently matches everything. Pass a number and let the
-     * SDK stringify it.
-     */
-    readonly minImportance?: number;
-    /**
-     * `"recent"` orders by `last_seen_at` descending. Anything else - including
-     * omitting it - orders by `importance` descending, then `last_seen_at`
-     * descending. There is no third value and no ascending variant.
-     *
-     * If you ALSO pass {@link PageParams.order}, both apply and yours wins: the
-     * controller appends its ordering after the list DSL has applied
-     * `modifiers[order]`, so your column becomes the primary sort key and the
-     * controller's becomes the tie-breaker. That is the opposite of what the
-     * parameter names suggest.
-     */
-    readonly sort?: "recent" | "importance";
-}
-/**
- * `GET /intel_articles` and friends: the stories the pipeline built.
- *
- * Read-only plus a delete. There is no create and no update route -
- * `IntelArticle#creatable_by?` and `#updatable_by?` both return `false`
- * unconditionally, and the route is `only: [:index, :show, :destroy]`. Stories
- * come from `Intel::ArticleBuilder`, never from a client.
- */
-export declare class IntelArticlesNamespace extends Resource {
-    /**
-     * `GET /intel_articles` - your stories, most important first.
-     *
-     * Ordering is the controller's, not yours by default: `importance DESC,
-     * last_seen_at DESC`, or `last_seen_at DESC` alone with `sort: "recent"`.
-     * See {@link ListIntelArticlesParams.sort} for what happens when you pass
-     * `order` as well - it is not what the names imply.
-     *
-     * Filter keys this controller declares for `search` / `exactSearch`:
-     * `title`, `summary`, `category`, `importance`, `enriched`, plus the
-     * inherited `id`, `created_at`, `updated_at`. Anything else is
-     * `400 "Unknown search filter: x"` - fail-closed, never a wider result. The
-     * free-text and importance filters are top-level instead: `q` and
-     * `minImportance`.
-     *
-     * **Cost.** Every row runs its own `COUNT` for
-     * {@link IntelArticle.n_sources}. Keep `pageSize` in the tens, not at 500.
-     *
-     * The response carries an `ETag` and can answer `304` - except when
-     * `random` is set, which short-circuits `resources_stale?`.
-     *
-     * @throws {OmsAuthError} 401 when anonymous.
-     * @throws {OmsApiError} 403 `"Intel access is restricted."` for a signed-in
-     *   account outside the allowlist; 400 for an unrecognised filter key.
-     */
-    list(params?: ListIntelArticlesParams, options?: RequestOptions): Promise<Paginated<IntelArticle>>;
-    /**
-     * `GET /intel_articles/:id` - one story with its body, its sources, its
-     * related stories and the reports that cited it.
-     *
-     * The `:extended` view, so it is a strict superset of the listing row. All
-     * four extras are inlined without paging; see {@link IntelArticleDetail}.
-     *
-     * @throws {OmsApiError} 404 `"Resource not found"` when the id is not one of
-     *   yours - the lookup is `viewable_by(Current.user).find_by(id:)`, so
-     *   somebody else's story is indistinguishable from a typo, which is the
-     *   point.
-     */
-    get(id: Id, options?: RequestOptions): Promise<IntelArticleDetail>;
-    /**
-     * `DELETE /intel_articles/:id` - drops a story. `204`, empty body.
-     *
-     * The story's links to items are removed with it (`dependent: :destroy` on
-     * `intel_article_sources`), but the {@link IntelItem} rows themselves SURVIVE
-     * - they belong to the source, not to the story. They are also still marked
-     * `processed_at`, so deleting a story does not make the pipeline rebuild it.
-     * This is a hide, not an undo.
-     *
-     * @throws {OmsApiError} 404 when the story is not yours. 401
-     *   `"You are not authorized to destroy this resource"` cannot happen here -
-     *   `destroyable_by?` is `user == self.user` and the lookup already scoped it
-     *   - but note the API's habit of answering 401 rather than 403 for a failed
-     *   authorisation check, which the scripts routes DO hit.
-     */
-    delete(id: Id, options?: RequestOptions): Promise<void>;
-}

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>;
-}