dashboard: a completed recurring meeting shows no transcript once the next occurrence's row exists

[DmitriyG228]

Defect. The dashboard meeting page fetches the transcript by platform/native_meeting_id (/transcripts/{platform}/{native_id}?meeting_id=…). That endpoint ignores meeting_id and resolves the newest row for that native id. For a recurring meeting, calendar auto-join creates next week's scheduled row minutes after the call ends, so the completed meeting's page renders the empty newer row.

Reproduced on prod, 2026-09-01. Meeting 27493 (DNA Dev Check-in, zoom 92446951537, completed 18:43Z) has 271 transcript segments in Postgres. Row 27499 (same zoom id, scheduled, 0 segments) was created 19:16Z. The page calls the native-id endpoint and receives 27499 → "No transcript yet".

Fix. Dashboard commit c23ef2f6 = the July 23 exact-row fix eecd9acf cherry-picked onto the deployed base fa667cd1: when the internal id is known, fetch /transcripts/by-id/{id} (live in prod meeting-api + gateway). Falls back to the native route otherwise. Two vitest cases pass.

Rung. Image vexaai/dashboard:v01223-rc6-by-id-c23ef2f6 (sha256:5421f253…) published; adoption PR Vexa-ai/vexa-platform#392 open; prod delivery goes through the channel entry seq-13 under the deliver session (no break-glass — founder ruling 2026-09-01).

Finding on the side. The dashboard's source is on no main: the deployed base fa667cd1 lives on codex/1150-dashboard-calendar; #1183 (retain hosted source in OSS main) and #1246 (attested build path) are still open, so V-est-7 cannot be proven for any dashboard rebuild until they land.

[DmitriyG228]

Rung: in production, machine-verified. Entry seq-13 pinned to prod at 23:00Z on the founder's word (DmitriyG228/vexa-stations#10). The dashboard pod runs vexaai/dashboard@sha256:e9ae120a… (built from 1a7d21a9, PR #1387); the served bundle contains the transcripts/by-id fetch. Post-pin cluster conformance CONFORMS 6/6 against the entry. Station proof before the pin: on a throwaway stack at prod digests, the old image rendered 0 of 12 seeded segments for a completed meeting shadowed by a newer scheduled row, the new image rendered 12 of 12 by exact row (record: vexa-stations/channels/vexa-internal/stations/estate-seq13/).

Remaining rung — verified by them: the founder reloading https://dashboard.vexa.ai/meetings/27493 and seeing its 271 segments. This issue closes on that word. #1387 stays open for the source lane (rights tick pending; the dashboard has no main — #1183).

[DmitriyG228]

Delivered and verified by the founder. Founder, 2026-09-01 ~23:20Z: "now it renders zoom" on https://dashboard.vexa.ai/meetings/27493. Prod: entry seq-13 (sha256:79ada079…), chart 0.1.0-estate.20260829.7, dashboard vexaai/dashboard@sha256:e9ae120a… from 1a7d21a9 (#1387); post-pin conformance 6/6; receipt vexa-stations/channels/vexa-internal/receipts/2026-09-01-seq13-delivered.md.

The same report carried "no audio playback" on that page. That is a separate defect, not this fix: meeting 27493 has no recording at all (no data.recordings, no chunks), while 254 of 285 meetings completed in the last 7 days do. Filed on its own.