[tang-vu]

Why this matters

ODS Talk users can save the conversation displayed in their current tab as Markdown or structured JSON, without making a new inference request or uploading the transcript elsewhere.

Current public-beta integration

Updated this original export PR onto current public-beta. The exporter reads visible message text/role/status, omits the welcome message, attachment file payloads and retry metadata, disables while sending/recording, and releases its temporary object URL after download. Error text retains its error status rather than being presented as a successful answer.

Overlap check

Searched open/closed Talk export PRs and ODSTalk/TalkExport paths. This is the existing canonical transcript-export PR, not a new variant. Beta's streaming, attachment and cancellation changes remain intact; exporting does not alter their transport or lifecycle.

Validation

• npm test -- --maxWorkers=2 src/components/TalkExport.test.jsx src/pages/ODSTalk.test.jsx: 18 passed. The object-URL lifecycle assertion was then added and its focused test passed again.
• Rendered ODSTalk tests download both formats without another request. Export component regression verifies busy gating, JSON field allowlist, Unicode, error status, attachment exclusion, filename and URL revocation.
• Focused ESLint has zero errors; focused pre-commit and diff check passed.
• Batch baseline dashboard 1,232 tests/build and Linux smoke/simulation passed. Existing full make gate/BATS environment/fixture failures remain disclosed. Real browser download and mobile recording behavior were not exercised live.

Tradeoffs and rollback

This exports text from the current tab, not server history or attachment files. Downloaded text can contain sensitive conversation content and is owned by the user. Markdown preserves authored text rather than sanitizing its meaning. Revert removes export UI with no server migration or restart. Ready for independent review, not approval to merge.

Follow-up regression receipt

Head 61e79d893acc1c8fe766bbd576f7dc9fc39f1e13 keeps export disabled while generation is busy. Focused export/page suites: 18 passed. Three invalid Latin-1 fixture bytes in the pre-existing ODSTalk test were converted to the equivalent UTF-8 character; the rest of the file and line endings were preserved. This is a fixture encoding repair, not a production transcript rewrite.

Final beta-batch receipt — 2026-09-16

Candidate: 61e79d893acc1c8fe766bbd576f7dc9fc39f1e13. GitHub check audit at 11:07:47 UTC: 37 successful, 4 skipped, 0 failed, 0 pending, matching this exact head; OPEN, public-beta base, Ready (not Draft). Skipped checks are not counted as passed tests.

The combined integration head, 5b9877184ceab0751c6c9fe3564c73303e78f0a3, contains all 30 exact candidate heads on public-beta 3c186f3f12ba21dad7b7266ec5449393529abb00. At this exact final SHA: full dashboard 171 files / 1,274 tests passed; full dashboard API 3,124 passed, 2 skipped; advice boundary suite 23 passed; Bark request/legacy-empty cases 9 passed; changed-file secret/key/size hooks and diff check passed. Shell-only hooks had no matching changed files.

Additional combined checks ran at predecessor 28adf1aa5c0710d3c0de13df7870629e24977fec: Token Spy 130 passed, 1 skipped; CLI contracts 16 passed; real backup/restore round trip passed; Open Interpreter HTTP/runner cases 4 passed; make lint smoke simulate, frontend lint (zero errors, 624 warnings) and production build passed. The only final-head differences are two test files (advice dialog fixtures and Bark's empty-text expectation); production files are identical. These results are not live GPU/model or service rollout qualification.

Qualified merge order: #5490 → #5494 → #5495 → #3848 → #3846 → #3845 → #3844 → #3843 → #3841 → #3838 → #3837 → #3836 → #3835 → #3834 → #3809 → #3808 → #3807 → #3806 → #3804 → #3803 → #3802 → #3801 → #3800 → #3712 → #3711 → #3710 → #3709 → #3708 → #3852 → #3849. Branches are independently useful. Shared-file merging required only preserving the union of four adjacent Makefile registrations: provider-probe redirects, healthcheck error-body, Milvus persistence and healthcheck latency. Production code in these 30 merged without manual conflict resolution. External advice/Bark overlaps have separate pairwise receipts in #5494/#3808. Recheck the combined tree if other shared-file PRs land first; do not drop test registrations.

Full release qualification remains not green: baseline make gate fails a no-sudo Docker fallback fixture; 5 of 428 BATS cases fail in this environment; all-files private-key scanning flags two pre-existing dummy-key fixtures. No checks were disabled. CI success and Ready status do not replace independent human review, especially for auth backups and Milvus data migration. No upstream merge or deployment was performed.

[Lightheartdevs]

Thanks for this contribution. public-beta was promoted into main on 2026-09-24 and no longer receives changes, so we're closing pull requests that target it. This isn't a judgment on the change itself. If it's still needed, please rebase onto main and open a focused PR. See #7253 for details and the contribution policy.