5 Commits

Include renames

Author	SHA1	Message	Date
Lotus CIandClaude Opus 4.8	d71d8d6799	chore(lotus): fix stale denoise flag docs + prep 0.20.1-lotus.2 ... The in-source ML denoiser is gated on lotusDenoiseSource (see lotusDenoise.ts gate), not the legacy build-time shim flag lotusDenoise=ml. Correct the two stale references (lotusDenoise.ts JSDoc + InCallView.tsx comment) to lotusDenoiseSource=1. Bump the embedded package to 0.20.1-lotus.2 for the next publish and update the CI comment: the checked-in version now tracks the intended release, while a pushed tag still wins (npm version "$TAG" overwrites at publish time). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-01 23:56:28 -04:00
Lotus CIandClaude Opus 4.8	29592fbb18	lotus(#1): fix restart-silence (A7), 48kHz ctx; protocol + CI hardening ... Denoise deep-review (CRITICAL): restart() read opts.audioContext, which LiveKit does NOT pass on restart — so reconnect (the A7 scenario) and mic device-switch threw after stopping the old track, leaving the mic SILENT (A7 reintroduced). Fix: - Processor owns a dedicated 48kHz AudioContext (sapphi worklets require 48kHz; H1), reused across restart, closed on destroy. - restart() never throws and never leaves a stopped track on the sender: builds the new graph first, then disposes the old; on failure degrades to RAW mic audio rather than silence. - Cache wasm per URL (no re-fetch each reconnect); gate threshold default -45 and accept an explicit 0 (M2); document the cross-repo asset contract. Protocol audit: - Non-silent warning when an unsupported denoise model (dtln/deepfilternet) is requested instead of silent rnnoise fallback (F3). - Correct the call_state enum comment (immediate error-reply, not 10s) (F2). Build/CI audit: - Stamp VITE_APP_VERSION in CI; document the vX.Y.Z-lotus.N version scheme. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-30 00:15:59 -04:00
Lotus CIandClaude Opus 4.8	39377fb6e1	ci: drop actions/upload-artifact@v4 (incompatible with Gitea runner) ... upload-artifact@v4 needs GitHub's artifact backend, which the Gitea act_runner doesn't implement — it failed the build job with exit 1 even though build:embedded + smoke-check passed. The publish job rebuilds from source, so the artifact was only a convenience. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-29 22:49:15 -04:00
Lotus CIandClaude Opus 4.8	b1fed78283	ci: stage embedded dist into embedded/web/dist before publish ... build:embedded outputs to repo-root dist/; the publish job and smoke-check expected embedded/web/dist (the publish template's files entry), which was never created in CI — so a tagged publish would fail its smoke-check or ship an empty tarball. Copy dist -> embedded/web/dist in both jobs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-29 22:45:20 -04:00
Lotus CIandClaude Opus 4.8	229b54b3b7	Lotus fork: rename embedded package + add Gitea CI ... - embedded/web/package.json: publish as @lotusguild/element-call-embedded from our Gitea fork (repository URL updated). - .gitea/workflows/ci.yml: build the embedded bundle on PR/push to lotus; publish to the Gitea npm registry on a v* tag. Linux-only (web bundle). Based on upstream element-call v0.20.1 (2d74c48). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-29 22:16:45 -04:00