@aventurevc/api-schemas 0.8.371 → 0.8.373

package/dist/entity/sitemap.d.ts

@@ -1,6 +1,6 @@
 import { z } from "zod/v4";
 /**
- * Sub-route eligibility GATE for sitemap.xml emission, not a write receipt. Each boolean is true only when the underlying rows EXIST AND every entity that sub-route renders (this entity and any counterpart, e.g. the acquired/acquirer company behind `hasAcquisitions`) currently passes publication visibility (not hidden, on sitemap). A `false` flag when you know the data exists means an unmet visibility prerequisite -- publish the hidden entity -- confirmed against the owning command-side read; it is an active gate result, not refresh lag, and a flag being `false` says nothing succeeded-and-is-fine. Served from a materialized projection (`mv_entity_sitemap_url_slots`) refreshed asynchronously, so a `true` flag can trail a gate that was just satisfied, but a successful write alone does not flip any flag.
+ * Sub-route eligibility GATE for sitemap.xml emission, not a write receipt. Each boolean is true only when the underlying rows EXIST AND every entity that sub-route renders (this entity and any counterpart, e.g. the acquired/acquirer company behind `hasAcquisitions`) currently passes publication visibility (not hidden, on sitemap). Served from the materialized projection `mv_entity_sitemap_url_slots`, which the `sitemap-boundaries-refresh` job rebuilds on `app.materialized-view-refresh.sitemap-boundaries.interval` and which skips write-driven requests within its `min-success-interval` of the last performed refresh. A `false` flag whose qualifying write is newer than that refresh (the `Last-Modified` time that sitemap reads report) is refresh lag that clears on the next performed refresh; polling sooner changes nothing. A `false` flag whose write is older than that refresh is the gate result: an unmet visibility prerequisite -- publish the hidden entity -- confirmed against the owning command-side read.
  *
  * @openapiSchema EntitySitemap
  * @endpoint GET /v1/entities

package/dist/entity/sitemap.js

@@ -1,7 +1,7 @@
 // LLM AGENTS MAY NOT EDIT THIS FILE UNDER ANY CIRCUMSTANCES. DO NOT EDIT - generated from Kotlin data classes via OpenAPI. Edit the backend owner and run: make docs-openapi && make docs-zod
 import { z } from "zod/v4";
 /**
- * Sub-route eligibility GATE for sitemap.xml emission, not a write receipt. Each boolean is true only when the underlying rows EXIST AND every entity that sub-route renders (this entity and any counterpart, e.g. the acquired/acquirer company behind `hasAcquisitions`) currently passes publication visibility (not hidden, on sitemap). A `false` flag when you know the data exists means an unmet visibility prerequisite -- publish the hidden entity -- confirmed against the owning command-side read; it is an active gate result, not refresh lag, and a flag being `false` says nothing succeeded-and-is-fine. Served from a materialized projection (`mv_entity_sitemap_url_slots`) refreshed asynchronously, so a `true` flag can trail a gate that was just satisfied, but a successful write alone does not flip any flag.
+ * Sub-route eligibility GATE for sitemap.xml emission, not a write receipt. Each boolean is true only when the underlying rows EXIST AND every entity that sub-route renders (this entity and any counterpart, e.g. the acquired/acquirer company behind `hasAcquisitions`) currently passes publication visibility (not hidden, on sitemap). Served from the materialized projection `mv_entity_sitemap_url_slots`, which the `sitemap-boundaries-refresh` job rebuilds on `app.materialized-view-refresh.sitemap-boundaries.interval` and which skips write-driven requests within its `min-success-interval` of the last performed refresh. A `false` flag whose qualifying write is newer than that refresh (the `Last-Modified` time that sitemap reads report) is refresh lag that clears on the next performed refresh; polling sooner changes nothing. A `false` flag whose write is older than that refresh is the gate result: an unmet visibility prerequisite -- publish the hidden entity -- confirmed against the owning command-side read.
  *
  * @openapiSchema EntitySitemap
  * @endpoint GET /v1/entities
@@ -53,7 +53,7 @@ import { z } from "zod/v4";
  * @contractRole canonical
  */
 export const EntitySitemapSchema = z.object({
-    /** Whether `/companies/<slug>/acquisitions` should be emitted. True only when an acquisition relationship exists AND both the acquired and acquirer entities are publicly visible. A confirmed acquisition relationship row with this flag `false` (or with `entities acquisitions list` returning zero rows) means a counterpart entity is still hidden -- publish it -- it is a visibility gate, not list lag. */
+    /** Whether `/companies/<slug>/acquisitions` should be emitted. True only when an acquisition relationship exists AND both the acquired and acquirer entities are publicly visible. A confirmed acquisition relationship row older than the projection's last refresh with this flag `false` (or with `entities acquisitions list` returning zero rows) means a counterpart entity is still hidden -- publish it; a newer row is refresh lag (see `EntitySitemap`). */
     hasAcquisitions: z.boolean().default(false).optional(),
     /** Whether the profile Analysis sub-route should be emitted. */
     hasAnalysis: z.boolean(),

package/dist/lookup/job-mutation.js

@@ -9,7 +9,7 @@ const LookupJobMutationSchemaDefinition = z.object({
     mention: z.array(LookupMentionSchema).optional(),
     /** POST /v1/lookup/mentions only: true answers each name with only its name, mentionType, failureReason, and identification status, stage, match, officialUrl, and detail: no entity or person rows and empty candidate and duplicate lists. Defaults to false, the full answer. */
     omitRecords: z.boolean().optional(),
-    /** Id of a stored source document whose text is the article; send it alone. Only POST /v1/lookup/mentions reads it, and only for accounts with editing rights. */
+    /** Id of a stored source document whose text is the article; send it alone. A durable source read (Prefer respond-async, source-read) accepts any signed-in user's own captured PDF; a live read needs editing rights. */
     sourceDocumentId: z.uuid().nullish(),
     /** aVenture news id of the article; an id that names no stored article is an error. */
     sourceNewsId: z.int().nullish(),

package/dist/lookup/job.d.ts

@@ -2314,11 +2314,13 @@ declare const LookupJobSchemaDefinition: z.ZodObject<{
         faviconUrl: z.ZodOptional<z.ZodNullable<z.ZodString>>;
         kind: z.ZodOptional<z.ZodNullable<z.ZodUnion<readonly [z.ZodEnum<{
             ARTICLE: "ARTICLE";
+            DOCUMENT: "DOCUMENT";
             POST: "POST";
             PROFILE: "PROFILE";
         }>, z.ZodString]> & {
             enum: {
                 ARTICLE: "ARTICLE";
+                DOCUMENT: "DOCUMENT";
                 POST: "POST";
                 PROFILE: "PROFILE";
             };

package/dist/lookup/source-kind.d.ts

@@ -1,6 +1,6 @@
 import { z } from "zod/v4";
 /**
- * What a lookup's source is, so a client names it while it loads: a news article, a LinkedIn or X post, or a supplied profile. An unknown future kind reads as a generic source.
+ * What a lookup's source is, so a client names it while it loads: a news article, a LinkedIn or X post, a supplied profile, or the caller's own captured document (sourceDocumentId). An unknown future kind reads as a generic source.
  *
  * @openapiSchema LookupSourceKind
  * @endpoint GET /v1/lookup-jobs/{jobId}
@@ -13,11 +13,13 @@ import { z } from "zod/v4";
  */
 export declare const LookupSourceKindSchema: z.ZodUnion<readonly [z.ZodEnum<{
     ARTICLE: "ARTICLE";
+    DOCUMENT: "DOCUMENT";
     POST: "POST";
     PROFILE: "PROFILE";
 }>, z.ZodString]> & {
     enum: {
         ARTICLE: "ARTICLE";
+        DOCUMENT: "DOCUMENT";
         POST: "POST";
         PROFILE: "PROFILE";
     };

package/dist/lookup/source-kind.js

@@ -1,8 +1,8 @@
 // LLM AGENTS MAY NOT EDIT THIS FILE UNDER ANY CIRCUMSTANCES. DO NOT EDIT - generated from Kotlin data classes via OpenAPI. Edit the backend owner and run: make docs-openapi && make docs-zod
 import { z } from "zod/v4";
-const LookupSourceKindSchemaKnownMembers = z.enum(["ARTICLE", "POST", "PROFILE"]);
+const LookupSourceKindSchemaKnownMembers = z.enum(["ARTICLE", "POST", "PROFILE", "DOCUMENT"]);
 /**
- * What a lookup's source is, so a client names it while it loads: a news article, a LinkedIn or X post, or a supplied profile. An unknown future kind reads as a generic source.
+ * What a lookup's source is, so a client names it while it loads: a news article, a LinkedIn or X post, a supplied profile, or the caller's own captured document (sourceDocumentId). An unknown future kind reads as a generic source.
  *
  * @openapiSchema LookupSourceKind
  * @endpoint GET /v1/lookup-jobs/{jobId}

package/dist/lookup/source-read.d.ts

@@ -1,6 +1,6 @@
 import { z } from "zod/v4";
 /**
- * Source context and honest reading activity for a shared article, post, or profile.
+ * Source context and honest reading activity for a shared article, post, profile, or the caller's own captured document.
  *
  * @openapiSchema LookupSourceRead
  * @endpoint GET /v1/lookup-jobs/{jobId}
@@ -22,11 +22,13 @@ export declare const LookupSourceReadSchema: z.ZodObject<{
     faviconUrl: z.ZodOptional<z.ZodNullable<z.ZodString>>;
     kind: z.ZodOptional<z.ZodNullable<z.ZodUnion<readonly [z.ZodEnum<{
         ARTICLE: "ARTICLE";
+        DOCUMENT: "DOCUMENT";
         POST: "POST";
         PROFILE: "PROFILE";
     }>, z.ZodString]> & {
         enum: {
             ARTICLE: "ARTICLE";
+            DOCUMENT: "DOCUMENT";
             POST: "POST";
             PROFILE: "PROFILE";
         };

package/dist/lookup/source-read.js

@@ -4,7 +4,7 @@ import { JobEnqueueSchema } from "../job/enqueue.js";
 import { LookupSourceKindSchema } from "./source-kind.js";
 import { LookupSourceReadPhaseSchema } from "./source-read-phase.js";
 /**
- * Source context and honest reading activity for a shared article, post, or profile.
+ * Source context and honest reading activity for a shared article, post, profile, or the caller's own captured document.
  *
  * @openapiSchema LookupSourceRead
  * @endpoint GET /v1/lookup-jobs/{jobId}

package/dist/mention/lookup.d.ts

@@ -1940,11 +1940,13 @@ declare const MentionLookupSchemaDefinition: z.ZodObject<{
         faviconUrl: z.ZodOptional<z.ZodNullable<z.ZodString>>;
         kind: z.ZodOptional<z.ZodNullable<z.ZodUnion<readonly [z.ZodEnum<{
             ARTICLE: "ARTICLE";
+            DOCUMENT: "DOCUMENT";
             POST: "POST";
             PROFILE: "PROFILE";
         }>, z.ZodString]> & {
             enum: {
                 ARTICLE: "ARTICLE";
+                DOCUMENT: "DOCUMENT";
                 POST: "POST";
                 PROFILE: "PROFILE";
             };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aventurevc/api-schemas",
-  "version": "0.8.371",
+  "version": "0.8.373",
   "private": false,
   "description": "Zod v4 schemas and TypeScript types for the aVenture API.",
   "license": "Apache-2.0",