Skip to content

fix(transcribe): meetings transcribe answers the shared call_transcription_report shape - #42

Merged
leemour merged 1 commit into
mainfrom
fix/transcription-report-parity
Nov 17, 2026
Merged

leemour merged 1 commit into
mainfrom
fix/transcription-report-parity

Conversation

@leemour

@leemour leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member

Task

beeline, b24 and pbx answer the same call_transcription_report. The family audit (same-entity-schema, WC-OUT-11) requires one shape. b24's old shape (the same as pbx's) blocked beeline's pull requests; b24 moved to beeline's shape in WireCatLabs/bitrix24-cli#145. pbx is not on npm yet, so the audit does not see it, but it would block once published.

Why

WC-OUT-13: a length of time is milliseconds in a _ms key, and a stored thing is named by ref.

What

Field Before Now (= beeline, b24)
audio time audio_seconds (rounded) audio_ms
failed[] meeting, reason, message meeting, ref, reason, message
no recording without_recording count failed[] with recording.missing (already in src/reasons.ts)

Breaking for callers, so the fragment is under "Changed — may break callers". No release in this PR.

Testing

pnpm typecheck, pnpm lint, full vitest run (190 passed), pnpm docs:check, pnpm contracts:check, pnpm generate:check.

🤖 Generated with Claude Code

…ption_report shape

beeline, b24 and pbx all answer `call_transcription_report`, and the family
audit (WC-OUT-11) requires one schema per shared entity. b24 moved to beeline's
shape in WireCatLabs/bitrix24-cli#145 after its old shape blocked beeline's
pull requests; pbx had the same old shape and would block once on npm.

Per WC-OUT-13 (durations in `_ms`, stored things named by `ref`):

- `audio_ms` replaces the rounded `audio_seconds`;
- each `failed` item has its `ref` (`meeting:<account>/<id>`);
- a call with no recording is listed under `failed` as `recording.missing`,
  a reason pbx already declares; `without_recording` is gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit 854c885 into main Nov 17, 2026
16 checks passed
@leemour leemour mentioned this pull request Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant