@antiphony/shared 0.4.0 → 0.5.0

package/dist/cjs/index.d.cts

@@ -11,11 +11,20 @@ export { ReportedErrorEvent, buildReportedErrorEvent, reportError } from './obse
 /**
  * Audio hygiene / enrichment processing (B5).
  *
- * Antiphony can, when the calling app opts in, run two pieces of audio
- * processing on a post's audio: **transcription** (machine transcript, the
- * `dev.antiphony.audio.transcript` enrichment) and **denoise** (a cleaned
- * audio variant for playback). Both are OFF by default — the app asks for
- * them per post via `CreateAudioPostRequest.processing`.
+ * Antiphony can, when the calling app opts in, run audio processing on a
+ * post's audio. Four stages, classified on two axes (see
+ * `specs/enrichment-pipeline.md`):
+ *
+ *  - **Byte-mutating** (`denoise`, `trim`) produce new audio. They compose in
+ *    order into a SINGLE processed variant — trimmed-and-denoised audio is one
+ *    artifact, not two — addressed by `processedBlobCid`.
+ *  - **Derived** (`transcribe`, `waveform`) are pure analysis over the final
+ *    variant and modify no audio. Because they are a function of the variant,
+ *    recomputation is always the correct response to their input changing.
+ *
+ * Every stage is OFF by default — the app asks for them per post via
+ * `CreateAudioPostRequest.processing`, or after the fact via the `processing`
+ * opt-in on `PATCH /api/v1/posts/{postId}`.
  *
  * The work runs asynchronously (outside the create request), so a post
  * carries a mutable `processing` state that starts `pending` and settles to
@@ -23,6 +32,11 @@ export { ReportedErrorEvent, buildReportedErrorEvent, reportError } from './obse
  * it is NOT part of the canonical lexicon record and never enters the record
  * CID (like `kind` and `threadParticipants`), so processing can update it
  * without changing the post's content address.
+ *
+ * That immutability is why stage OUTPUT lives here rather than on the embed:
+ * `embed.audio.ref.$link`, `embed.durationMs`, and `embed.waveform` are inside
+ * the CID and can never be rewritten. The read-time view resolves per field
+ * between the record's canonical values and the variant values below.
  */
 /**
  * Per-stage status.
@@ -30,64 +44,271 @@ export { ReportedErrorEvent, buildReportedErrorEvent, reportError } from './obse
  *  - `ready`    — completed.
  *  - `failed`   — attempted and errored.
  *  - `skipped`  — requested but this deployment has no provider for it.
+ *
+ * A stage returning to `pending` after having been `ready` is NORMAL, not a
+ * regression: a byte-mutating stage completing invalidates derived artifacts,
+ * which are then recomputed. Clients treat any `pending` stage as "still
+ * working", which already covers this.
  */
 declare const ProcessingStageStatusSchema: z.ZodEnum<["pending", "ready", "failed", "skipped"]>;
 type ProcessingStageStatus = z.infer<typeof ProcessingStageStatusSchema>;
 /**
- * What the calling app opts into, on `CreateAudioPostRequest`. Both default
+ * The stage names, in the order a multi-stage request runs them:
+ * denoise → trim → (transcribe, waveform).
+ *
+ * All byte-mutating stages run first; the two derived stages then consume the
+ * final variant and are mutually independent. Denoise precedes trim
+ * deliberately — silence detection keys off a noise floor, so on noisy input
+ * the "silence" is not actually quiet and trim under-cuts.
+ */
+declare const PROCESSING_STAGES: readonly ["denoise", "trim", "transcribe", "waveform"];
+declare const ProcessingStageSchema: z.ZodEnum<["denoise", "trim", "transcribe", "waveform"]>;
+type ProcessingStage = z.infer<typeof ProcessingStageSchema>;
+/** Stages that produce new audio bytes, composing into one processed variant. */
+declare const BYTE_MUTATING_STAGES: readonly ["denoise", "trim"];
+/** Stages that are pure analysis over the final variant, modifying no audio. */
+declare const DERIVED_STAGES: readonly ["transcribe", "waveform"];
+/**
+ * What the calling app opts into, on `CreateAudioPostRequest`. All default
  * off; only `true` values request a stage.
  */
 declare const ProcessingRequestSchema: z.ZodObject<{
     transcribe: z.ZodOptional<z.ZodBoolean>;
     denoise: z.ZodOptional<z.ZodBoolean>;
+    trim: z.ZodOptional<z.ZodBoolean>;
+    waveform: z.ZodOptional<z.ZodBoolean>;
+    /**
+     * Whether a completed byte-mutating stage should invalidate and recompute
+     * the derived artifacts that describe the old audio. Defaults to **true**
+     * — a transcript of superseded audio is wrong, not merely stale.
+     *
+     * `false` opts out, for an app that would rather keep the existing
+     * transcript than pay to regenerate it. It does NOT name a stage, so a
+     * request carrying only `reprocess` requests no work.
+     */
+    reprocess: z.ZodOptional<z.ZodBoolean>;
 }, "strip", z.ZodTypeAny, {
-    transcribe?: boolean | undefined;
     denoise?: boolean | undefined;
-}, {
+    trim?: boolean | undefined;
     transcribe?: boolean | undefined;
+    waveform?: boolean | undefined;
+    reprocess?: boolean | undefined;
+}, {
     denoise?: boolean | undefined;
+    trim?: boolean | undefined;
+    transcribe?: boolean | undefined;
+    waveform?: boolean | undefined;
+    reprocess?: boolean | undefined;
 }>;
 type ProcessingRequest = z.infer<typeof ProcessingRequestSchema>;
 /**
- * Stored processing state on the post record (storage-layer; not in the CID).
- * A stage key is present iff that stage was requested. `denoisedBlobCid`
- * points at the cleaned audio variant once denoise completes — the record's
- * own `embed.audio.ref.$link` stays the ORIGINAL CID (immutable content
- * address); only the read-time view swaps playback to the cleaned variant.
+ * Per-stage status across all stages — the shape shared by the stored state,
+ * the hydrated view, and the resolved-initial-state handoff between the route
+ * and the service. A key is present iff that stage was requested.
+ */
+declare const ProcessingStageMapSchema: z.ZodObject<{
+    transcribe: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    denoise: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    trim: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    waveform: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+}, "strip", z.ZodTypeAny, {
+    denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
+}, {
+    denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
+}>;
+type ProcessingStageMap = z.infer<typeof ProcessingStageMapSchema>;
+/**
+ * An opt-in request resolved against a deployment's capabilities: the initial
+ * per-stage state plus the settings the async worker needs to honour it.
+ *
+ * `reprocess` is carried here — and persisted — rather than passed to the
+ * worker as an argument, because the request that asks for the work and the
+ * pass that performs it are separated by a queue (step 8). Written on every
+ * request including the default, because the stored state is MERGED onto —
+ * absent means true only for posts written before this field existed.
+ */
+declare const ResolvedProcessingSchema: z.ZodObject<{
+    transcribe: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    denoise: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    trim: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    waveform: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+} & {
+    reprocess: z.ZodOptional<z.ZodBoolean>;
+}, "strip", z.ZodTypeAny, {
+    denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    reprocess?: boolean | undefined;
+}, {
+    denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    reprocess?: boolean | undefined;
+}>;
+type ResolvedProcessing = z.infer<typeof ResolvedProcessingSchema>;
+/**
+ * Stored processing state on the post record (storage-layer; not in the CID):
+ * the per-stage statuses plus the output of the stages themselves.
+ *
+ * The variant fields below all exist for the same reason — their canonical
+ * counterparts live inside the record CID and cannot be updated:
+ *
+ *  - `processedBlobCid` ↔ `embed.audio.ref.$link`
+ *  - `processedMimeType` ↔ `embed.audio.mimeType` (providers may transcode)
+ *  - `processedDurationMs` ↔ `embed.durationMs` (trim changes duration)
+ *  - `waveformPeaks` ↔ `embed.waveform` (the client's peaks describe the original)
  */
 declare const ProcessingStateSchema: z.ZodObject<{
     transcribe: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
     denoise: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
-    /** Content CID of the denoised audio variant, once `denoise === 'ready'`. */
-    denoisedBlobCid: z.ZodOptional<z.ZodString>;
+    trim: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    waveform: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+} & {
+    reprocess: z.ZodOptional<z.ZodBoolean>;
+} & {
+    /**
+     * Content CID of the processed audio variant — the composed output of every
+     * byte-mutating stage that has completed. The record's own
+     * `embed.audio.ref.$link` stays the ORIGINAL CID (immutable content
+     * address); only the read-time view swaps playback to this variant.
+     */
+    processedBlobCid: z.ZodOptional<z.ZodString>;
+    /**
+     * MIME type of the processed variant. Present because providers may
+     * TRANSCODE — the ElevenLabs Voice Isolator returns MP3 regardless of what
+     * it is given — so the variant's type cannot be assumed to match
+     * `embed.audio.mimeType`. Anything reading the variant's bytes must use
+     * this, not the embed's.
+     */
+    processedMimeType: z.ZodOptional<z.ZodString>;
+    /**
+     * Duration of the processed variant, when a byte-mutating stage changed it
+     * (i.e. trim). Absent when the variant's duration matches the original.
+     */
+    processedDurationMs: z.ZodOptional<z.ZodNumber>;
+    /**
+     * Peaks for the processed variant, once the `waveform` stage completes.
+     * Same normalization and bounds as `embed.waveform` (0–100, max 1000), so
+     * a view can never carry a larger payload than the record allows.
+     */
+    waveformPeaks: z.ZodOptional<z.ZodArray<z.ZodNumber, "many">>;
+    /**
+     * When the current runner's exclusive claim on this post expires.
+     *
+     * Queue delivery is at-least-once, so the same job can arrive twice and
+     * run CONCURRENTLY. `process()` is idempotent under sequential retry — it
+     * acts on `pending` and re-does nothing already settled — but two passes
+     * interleaved is a different failure: both read the same `pending` state,
+     * both bill the provider for the same stage, and both write
+     * `processedBlobCid`, so the surviving variant is whichever finished last
+     * and the other's blob is orphaned.
+     *
+     * A runner claims this field transactionally before doing any work and
+     * clears it when finished; a second runner finding it unexpired declines
+     * and returns. It is an EXPIRY, not a boolean lock, because the holder can
+     * die mid-run (instance recycled, process killed) with no chance to
+     * release — a plain flag would strand the post permanently, where a lapsed
+     * lease lets the next delivery pick it up.
+     *
+     * Internal, like the variant fields above: `toProcessingView` projects
+     * stages only, so this never reaches a client.
+     */
+    leaseUntil: z.ZodOptional<z.ZodEffects<z.ZodUnion<[z.ZodType<unknown, z.ZodTypeDef, unknown>, z.ZodString, z.ZodNumber, z.ZodDate]>, Date, unknown>>;
     updatedAt: z.ZodEffects<z.ZodUnion<[z.ZodType<unknown, z.ZodTypeDef, unknown>, z.ZodString, z.ZodNumber, z.ZodDate]>, Date, unknown>;
 }, "strip", z.ZodTypeAny, {
     updatedAt: Date;
-    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
     denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
-    denoisedBlobCid?: string | undefined;
-}, {
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
     transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    reprocess?: boolean | undefined;
+    processedBlobCid?: string | undefined;
+    processedMimeType?: string | undefined;
+    processedDurationMs?: number | undefined;
+    waveformPeaks?: number[] | undefined;
+    leaseUntil?: Date | undefined;
+}, {
     denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
-    denoisedBlobCid?: string | undefined;
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    reprocess?: boolean | undefined;
+    processedBlobCid?: string | undefined;
+    processedMimeType?: string | undefined;
+    processedDurationMs?: number | undefined;
+    waveformPeaks?: number[] | undefined;
+    leaseUntil?: unknown;
     updatedAt?: unknown;
 }>;
 type ProcessingState = z.infer<typeof ProcessingStateSchema>;
 /**
  * The processing status surfaced on the hydrated view — the per-stage status
- * only (no internal storage fields). Absent when no processing was requested.
- * Clients treat any `pending` stage as "still working".
+ * only (no internal storage fields: variant CID, duration, peaks, timestamps).
+ * Absent when no processing was requested.
  */
 declare const ProcessingViewSchema: z.ZodObject<{
     transcribe: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
     denoise: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    trim: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
+    waveform: z.ZodOptional<z.ZodEnum<["pending", "ready", "failed", "skipped"]>>;
 }, "strip", z.ZodTypeAny, {
-    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
     denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
-}, {
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
     transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
+}, {
     denoise?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    trim?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    transcribe?: "pending" | "ready" | "failed" | "skipped" | undefined;
+    waveform?: "pending" | "ready" | "failed" | "skipped" | undefined;
 }>;
 type ProcessingView = z.infer<typeof ProcessingViewSchema>;
+/**
+ * Project the stored state onto the view — drops every internal field.
+ *
+ * Derived from `PROCESSING_STAGES` rather than listing the stages by hand, so
+ * a stage added to the set cannot be silently omitted from the view (which
+ * would leave clients unable to tell "not requested" from "in progress").
+ */
+declare function toProcessingView(state: ProcessingState): ProcessingView;
+/** The record's own audio fields — canonical, inside the CID, never rewritten. */
+interface CanonicalAudioFields {
+    blobCid: string;
+    durationMs?: number;
+    waveform?: number[];
+}
+/**
+ * Resolve the audio fields a reader should see: canonical from the record,
+ * variant from `ProcessingState` wherever processing has superseded it.
+ *
+ * The three fields have to move together. Peaks are rendered ACROSS a duration
+ * and a duration describes a specific set of bytes, so serving a processed URL
+ * beside the original duration puts a scrubber out of alignment with the audio
+ * under it — the failure this function exists to prevent.
+ *
+ * Resolution is not a uniform `??` per field, because the state's fields do not
+ * all mean the same thing when absent:
+ *
+ *  - `processedDurationMs` absent is DEFINED as "the variant's duration equals
+ *    the original" (denoise transcodes without retiming), so falling back to
+ *    the record there is correct, not a guess.
+ *  - `waveformPeaks` carries no such guarantee. Recompute marks the stage
+ *    `pending` without clearing the field, so between a variant change and the
+ *    recomputed peaks landing it holds peaks for the SUPERSEDED variant. Hence
+ *    the status gate rather than a presence check.
+ *
+ * Peaks do not key off `processedBlobCid`: `waveform` always runs over the
+ * final variant, so when it is `ready` its peaks describe whatever playback
+ * resolves to here, variant or original alike.
+ */
+declare function resolveAudioVariant(canonical: CanonicalAudioFields, state: ProcessingState | undefined): CanonicalAudioFields;
 
-export { type ProcessingRequest, ProcessingRequestSchema, type ProcessingStageStatus, ProcessingStageStatusSchema, type ProcessingState, ProcessingStateSchema, type ProcessingView, ProcessingViewSchema };
+export { BYTE_MUTATING_STAGES, type CanonicalAudioFields, DERIVED_STAGES, PROCESSING_STAGES, type ProcessingRequest, ProcessingRequestSchema, type ProcessingStage, type ProcessingStageMap, ProcessingStageMapSchema, ProcessingStageSchema, type ProcessingStageStatus, ProcessingStageStatusSchema, type ProcessingState, ProcessingStateSchema, type ProcessingView, ProcessingViewSchema, type ResolvedProcessing, ResolvedProcessingSchema, resolveAudioVariant, toProcessingView };

package/dist/cjs/types/audio.cjs

@@ -46,21 +46,85 @@ var FirestoreTimestampSchema = zod.z.union([
   return date;
 });
 var ProcessingStageStatusSchema = zod.z.enum(["pending", "ready", "failed", "skipped"]);
+var PROCESSING_STAGES = ["denoise", "trim", "transcribe", "waveform"];
+zod.z.enum(PROCESSING_STAGES);
 zod.z.object({
   transcribe: zod.z.boolean().optional(),
-  denoise: zod.z.boolean().optional()
+  denoise: zod.z.boolean().optional(),
+  trim: zod.z.boolean().optional(),
+  waveform: zod.z.boolean().optional(),
+  /**
+   * Whether a completed byte-mutating stage should invalidate and recompute
+   * the derived artifacts that describe the old audio. Defaults to **true**
+   * — a transcript of superseded audio is wrong, not merely stale.
+   *
+   * `false` opts out, for an app that would rather keep the existing
+   * transcript than pay to regenerate it. It does NOT name a stage, so a
+   * request carrying only `reprocess` requests no work.
+   */
+  reprocess: zod.z.boolean().optional()
 });
-var ProcessingStateSchema = zod.z.object({
+var ProcessingStageMapSchema = zod.z.object({
   transcribe: ProcessingStageStatusSchema.optional(),
   denoise: ProcessingStageStatusSchema.optional(),
-  /** Content CID of the denoised audio variant, once `denoise === 'ready'`. */
-  denoisedBlobCid: zod.z.string().optional(),
-  updatedAt: FirestoreTimestampSchema
+  trim: ProcessingStageStatusSchema.optional(),
+  waveform: ProcessingStageStatusSchema.optional()
 });
-var ProcessingViewSchema = zod.z.object({
-  transcribe: ProcessingStageStatusSchema.optional(),
-  denoise: ProcessingStageStatusSchema.optional()
+var ResolvedProcessingSchema = ProcessingStageMapSchema.extend({
+  reprocess: zod.z.boolean().optional()
+});
+var ProcessingStateSchema = ResolvedProcessingSchema.extend({
+  /**
+   * Content CID of the processed audio variant — the composed output of every
+   * byte-mutating stage that has completed. The record's own
+   * `embed.audio.ref.$link` stays the ORIGINAL CID (immutable content
+   * address); only the read-time view swaps playback to this variant.
+   */
+  processedBlobCid: zod.z.string().optional(),
+  /**
+   * MIME type of the processed variant. Present because providers may
+   * TRANSCODE — the ElevenLabs Voice Isolator returns MP3 regardless of what
+   * it is given — so the variant's type cannot be assumed to match
+   * `embed.audio.mimeType`. Anything reading the variant's bytes must use
+   * this, not the embed's.
+   */
+  processedMimeType: zod.z.string().optional(),
+  /**
+   * Duration of the processed variant, when a byte-mutating stage changed it
+   * (i.e. trim). Absent when the variant's duration matches the original.
+   */
+  processedDurationMs: zod.z.number().int().min(0).optional(),
+  /**
+   * Peaks for the processed variant, once the `waveform` stage completes.
+   * Same normalization and bounds as `embed.waveform` (0–100, max 1000), so
+   * a view can never carry a larger payload than the record allows.
+   */
+  waveformPeaks: zod.z.array(zod.z.number().int().min(0).max(100)).max(1e3).optional(),
+  /**
+   * When the current runner's exclusive claim on this post expires.
+   *
+   * Queue delivery is at-least-once, so the same job can arrive twice and
+   * run CONCURRENTLY. `process()` is idempotent under sequential retry — it
+   * acts on `pending` and re-does nothing already settled — but two passes
+   * interleaved is a different failure: both read the same `pending` state,
+   * both bill the provider for the same stage, and both write
+   * `processedBlobCid`, so the surviving variant is whichever finished last
+   * and the other's blob is orphaned.
+   *
+   * A runner claims this field transactionally before doing any work and
+   * clears it when finished; a second runner finding it unexpired declines
+   * and returns. It is an EXPIRY, not a boolean lock, because the holder can
+   * die mid-run (instance recycled, process killed) with no chance to
+   * release — a plain flag would strand the post permanently, where a lapsed
+   * lease lets the next delivery pick it up.
+   *
+   * Internal, like the variant fields above: `toProcessingView` projects
+   * stages only, so this never reaches a client.
+   */
+  leaseUntil: FirestoreTimestampSchema.optional(),
+  updatedAt: FirestoreTimestampSchema
 });
+var ProcessingViewSchema = ProcessingStageMapSchema;
 
 // types/audio.ts
 var StrongRefSchema = zod.z.object({
@@ -96,20 +160,34 @@ var TimedTranscriptSchema = zod.z.object({
 });
 var AudioEmbedViewSchema = zod.z.object({
   $type: zod.z.literal("dev.antiphony.embed.audio#view"),
+  /**
+   * `url`, `durationMs` and `waveform` are RESOLVED, not copied: once
+   * processing has produced an audio variant they describe that variant
+   * rather than the bytes the client uploaded. They always agree with one
+   * another — a duration and a set of peaks are only meaningful against the
+   * audio `url` actually points at.
+   *
+   * A client that stored `durationMs` at upload time should therefore expect
+   * it to change (trim removes leading/trailing silence), and should render
+   * these three as a set rather than caching them independently. The record's
+   * originals are immutable and unaffected; this is a read-time resolution.
+   */
   url: zod.z.string().url(),
   durationMs: zod.z.number().int().min(0).optional(),
-  // `alt`/`waveform` are copied from the stored embed; keep the same bounds
-  // so a view can never carry a larger payload than the record allows.
+  // `alt` is copied from the stored embed; keep the same bounds so a view can
+  // never carry a larger payload than the record allows.
   alt: zod.z.string().max(1e4).optional(),
   waveform: zod.z.array(zod.z.number().int().min(0).max(100)).max(1e3).optional(),
   /** Lifted from the transcript enrichment record; absent until transcription completes. */
   transcript: TimedTranscriptSchema.optional(),
   /**
-   * Per-stage audio-processing status (transcribe / denoise), when the app
-   * opted into processing on create. Absent otherwise. A `pending` stage
-   * means the client should poll (or re-render) for the result. When
-   * `denoise === 'ready'`, `url` above already resolves to the cleaned
-   * audio variant. See `types/processing.ts`.
+   * Per-stage audio-processing status (denoise / trim / transcribe /
+   * waveform), when the app opted into processing. Absent otherwise. A
+   * `pending` stage means the client should poll (or re-render) for the
+   * result — including a stage that returns to `pending` after having been
+   * `ready`, which is how a recompute surfaces. Once a byte-mutating stage
+   * completes, `url`/`durationMs`/`waveform` above already resolve to the
+   * processed audio variant. See `types/processing.ts`.
    */
   processing: ProcessingViewSchema.optional()
 });