test livekit-client 2.9.1

.eslintrc.cjs

@@ -0,0 +1,54 @@
+const COPYRIGHT_HEADER = `/*
+Copyright %%CURRENT_YEAR%% New Vector Ltd.
+
+SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
+Please see LICENSE in the repository root for full details.
+*/
+
+`;
+
+module.exports = {
+  plugins: ["matrix-org", "rxjs"],
+  extends: [
+    "plugin:matrix-org/react",
+    "plugin:matrix-org/a11y",
+    "plugin:matrix-org/typescript",
+    "prettier",
+    "plugin:rxjs/recommended",
+  ],
+  parserOptions: {
+    ecmaVersion: "latest",
+    sourceType: "module",
+    project: ["./tsconfig.json"],
+  },
+  env: {
+    browser: true,
+    node: true,
+  },
+  rules: {
+    "matrix-org/require-copyright-header": ["error", COPYRIGHT_HEADER],
+    "jsx-a11y/media-has-caption": "off",
+    // We should use the js-sdk logger, never console directly.
+    "no-console": ["error"],
+    "react/display-name": "error",
+    // Encourage proper usage of Promises:
+    "@typescript-eslint/no-floating-promises": "error",
+    "@typescript-eslint/no-misused-promises": "error",
+    "@typescript-eslint/promise-function-async": "error",
+    "@typescript-eslint/require-await": "error",
+    "@typescript-eslint/await-thenable": "error",
+    // To help ensure that we get proper vite/rollup lazy loading (e.g. for matrix-js-sdk):
+    "@typescript-eslint/consistent-type-imports": [
+      "error",
+      { fixStyle: "inline-type-imports" },
+    ],
+    // To encourage good usage of RxJS:
+    "rxjs/no-exposed-subjects": "error",
+    "rxjs/finnish": "error",
+  },
+  settings: {
+    react: {
+      version: "detect",
+    },
+  },
+};

.githooks/pre-commit

@@ -1,9 +0,0 @@
-#!/usr/bin/env bash
-
-# Checks if there currently is linking configured. Informs the user to disable linking before committing.
-
-PNPMFILE=.pnpmfile.cjs
-if test -f "$PNPMFILE"; then
-  echo "[pnpm-linker] The pre-commit hook detected $PNPMFILE which implies you have linked packages in your pnpm-lock.yaml. Run pnpm links:off and commit again. See also linking.md."
-  exit 1
-fi

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,46 +0,0 @@
-<!-- Thanks for submitting a PR! Please read CONTRIBUTING.md before you start. -->
-
-> [!IMPORTANT]
-> **Features and UI changes require a pre-approved issue.**
-> Every PR must have a linked issue
-> that a maintainer has reviewed and approved **before you started writing code**.
-> PRs that don't meet this requirement will not be reviewed.
-> See [CONTRIBUTING.md](https://github.com/element-hq/element-call/blob/main/CONTRIBUTING.md) for ElementCall decided for this approach.
-
-## Content
-
-<!-- Describe shortly what has been changed -->
-
-## Motivation and context
-
-<!-- Provide a link to the pre-approved issue, or explain the context for a bug fix -->
-
-## Screenshots / GIFs
-
-<!--
-
-You can use a table like this to show a before/after comparison.
-Uncomment the markdown table below and fill in the last line:
-
-|Before|After|
-|-|-|
-|||
-
--->
-
-## Tests
-
-<!-- Explain how you tested your changes -->
-
-- Step 1
-- Step 2
-- Step ...
-
-## Checklist
-
-- [ ] A linked, pre-approved issue exists for this feature or UI change.
-- [ ] I have read [CONTRIBUTING.md](https://github.com/element-hq/element-call/blob/main/CONTRIBUTING.md) in full.
-- [ ] Pull request includes screenshots or videos for any UI changes.
-- [ ] Tests written for new code (and existing touched code where feasible).
-- [ ] Linter and other CI checks pass.
-- [ ] I have licensed the changes to Element by completing the [Contributor License Agreement (CLA)](https://cla-assistant.io/element-hq/element-call)

.github/labels.yml

@@ -1,253 +0,0 @@
-- name: "A-1:1"
-  description: "Calls between two people"
-  color: "bfd4f2"
-- name: "A-Big-Grid"
-  description: "The freedom layout system used for >12 participants"
-  color: "bfd4f2"
-- name: "A-Developer-Experience"
-  description: "Workflow of developing: building, linting, debugging, profiling, etc."
-  color: "c5def5"
-- name: "A-E2EE"
-  description: "End-to-end encryption"
-  color: "bfd4f2"
-- name: "A-Embedded"
-  description: "Using the app embedded within other Matrix clients (as a widget)"
-  color: "bfd4f2"
-- name: "A-Feedback-Reporting"
-  description: "Reporting process for bugs, debug logs (rageshakes), suggestions"
-  color: "bfd4f2"
-- name: "A-Freedom"
-  description: "Freedom layout, where participants can be rearranged and resized"
-  color: "bfd4f2"
-- name: "A-Handset"
-  description: "Audio playback through the earpiece of a phone. Also known as 'earpiece mode' or 'handset mode'."
-  color: "bfd4f2"
-- name: "A-Huddle"
-  description: "Ad-hoc calls in a room notifying others"
-  color: "bfd4f2"
-- name: "A-Lobby"
-  description: "The page before joining a call"
-  color: "bfd4f2"
-- name: "A-Login"
-  color: "bfd4f2"
-- name: "A-Matrix2.0"
-  description: "Issues relating to the Matrix 2.0 / MSC4143 work, such as sticky events and multi-sfu"
-  color: "bfd4f2"
-- name: "A-Media-Devices"
-  color: "BFD4F2"
-- name: "A-Media-Quality"
-  description: "Distortions or glitches in audio/video"
-  color: "bfd4f2"
-- name: "A-Meeting"
-  description: "Scheduled call on the calendar"
-  color: "bfd4f2"
-- name: "A-Mobile"
-  description: "Using the app on a mobile device"
-  color: "bfd4f2"
-- name: "A-Moderation"
-  description: "Access to calls and powers within calls"
-  color: "bfd4f2"
-- name: "A-Performance"
-  color: "bfd4f2"
-- name: "A-Reactions"
-  color: "bfd4f2"
-- name: "A-Registration"
-  color: "bfd4f2"
-- name: "A-Screen-Sharing"
-  color: "bfd4f2"
-- name: "A-SDK"
-  description: "SDK for building MatrixRTC + LiveKit widgets"
-  color: "c5def5"
-- name: "A-Settings"
-  color: "bfd4f2"
-- name: "A-SFU"
-  description: "Routing calls through a selective forwarding unit"
-  color: "bfd4f2"
-- name: "A-Signaling"
-  description: "Call signaling"
-  color: "bfd4f2"
-- name: "A-Simulcast"
-  description: "Automatic selection of variable video resolutions"
-  color: "bfd4f2"
-- name: "A-SPA"
-  description: "Standalone application accessed via call links"
-  color: "bfd4f2"
-- name: "A-Spatial-Audio"
-  description: "Directional audio based on where a speaker appears on screen"
-  color: "bfd4f2"
-- name: "A-Speech-Enhancement"
-  description: "Techniques to enhance the intelligibility of speech in calls"
-  color: "c5def5"
-- name: "A-Split-Grid"
-  description: "The freedom layout system used for ≤12 participants"
-  color: "bfd4f2"
-- name: "A-Spotlight"
-  description: "Spotlight layout, where the active speaker is foregrounded"
-  color: "bfd4f2"
-- name: "A-Telemetry-Posthog"
-  description: "Share opt in usage data for optimizing the app via posthog"
-  color: "bfd4f2"
-- name: "A-Testing"
-  description: "Integration tests, unit tests, etc."
-  color: "bfd4f2"
-- name: "A-Video-Rooms"
-  description: "Rooms reserved exclusively for calling"
-  color: "bfd4f2"
-- name: "A-Walkie-Talkie"
-  description: "Walkie-talkie / PTT (push-to-talk) mode"
-  color: "bfd4f2"
-- name: "A11y"
-  description: "Accessibility"
-  color: "4ADEC0"
-- name: "backport-candidate"
-  description: "Something that is a candidate for backport to a particular release branch"
-  color: "0B8D85"
-- name: "customer-retainer"
-  color: "F44A5F"
-- name: "dependencies"
-  description: "Pull requests that update a dependency file"
-  color: "0366d6"
-- name: "development build"
-  description: "runs yarn build process in development mode"
-  color: "1d76db"
-- name: "Discord"
-  description: "Use case familiar to Discord users"
-  color: "3670d2"
-- name: "docker build"
-  description: "Creates a docker image for this PR"
-  color: "0e8a16"
-- name: "EPIC"
-  color: "5319E7"
-- name: "good first issue"
-  description: "Good for newcomers"
-  color: "7057ff"
-- name: "Help Wanted"
-  description: "Community contributions are welcome!"
-  color: "159818"
-- name: "I18n"
-  description: "Internationalisation"
-  color: "d4c5f9"
-- name: "O-Frequent"
-  description: "Affects or can be seen by most users regularly or impacts most users' first experience"
-  color: "0052CC"
-- name: "O-Occasional"
-  description: "Affects or can be seen by some users regularly or most users rarely"
-  color: "1D76DB"
-- name: "O-Uncommon"
-  description: "Most users are unlikely to come across this or unexpected workflow"
-  color: "C5DEF5"
-- name: "p1"
-  description: "Must fix/implement before this is usable as a product"
-  color: "D93F0B"
-- name: "p2"
-  description: "Should fix/implement, but not at the expense of p1s"
-  color: "FBCA04"
-- name: "p3"
-  description: "Could fix/implement when time allows"
-  color: "0E8A16"
-- name: "PR-Breaking-Change"
-  description: "A Pull request that changes EC in a way that is incompatible to the previous version."
-  color: "D93F0B"
-- name: "PR-Bug-Fix"
-  description: "Release note category. A PR that fixes a bug."
-  color: "C2E0C6"
-- name: "PR-Developer-Experience"
-  description: "Release note category. A PR that does not change EC but improves working with the repository."
-  color: "C2E0C6"
-- name: "PR-Documentation"
-  description: "Release note category. A PR that improves the documentation."
-  color: "C2E0C6"
-- name: "PR-Feature"
-  description: "Release note category. A PR that introduces a new user facing feature."
-  color: "C2E0C6"
-- name: "PR-Improvement"
-  description: "Release note category. A PR that improves EC's performance or stability."
-  color: "C2E0C6"
-- name: "PR-Task"
-  description: "Release note category. A PR that is hidden from release note."
-  color: "C2E0C6"
-- name: "Privacy"
-  color: "f41192"
-- name: "Roadmap"
-  color: "57457E"
-- name: "S-Critical"
-  description: "Prevents work, causes data loss and/or has no workaround"
-  color: "bd0026"
-- name: "S-Major"
-  description: "Severely degrades major functionality or product features, with no satisfactory workaround"
-  color: "fc4e2a"
-- name: "S-Minor"
-  description: "Impairs non-critical functionality or suitable workarounds exist"
-  color: "feb24c"
-- name: "S-Tolerable"
-  description: "Low/no impact on users"
-  color: "ffeda0"
-- name: "Security"
-  color: "b3e5fc"
-- name: "storybook build"
-  description: "Build and deploy the storybook frontend to netlify."
-  color: "45cd61"
-- name: "T-Defect"
-  description: "Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems"
-  color: "98e6ae"
-- name: "T-Enhancement"
-  description: "New features, changes in functionality, performance boosts, user-facing improvements"
-  color: "98e6ae"
-- name: "T-Other"
-  description: "Questions, user support, anything else"
-  color: "98e6ae"
-- name: "T-Task"
-  description: "Refactoring, enabling or disabling functionality, other engineering tasks"
-  color: "98e6ae"
-- name: "X-Blocked"
-  description: "Cannot be merged due to external dependencies"
-  color: "ff7979"
-- name: "X-Cannot-Reproduce"
-  description: "Needs reproduction steps"
-  color: "ff7979"
-- name: "X-Needs-Design"
-  description: "May require input from the design team"
-  color: "ff7979"
-- name: "X-Needs-Info"
-  description: "This issue is blocked awaiting information from the reporter"
-  color: "ff7979"
-- name: "X-Needs-Investigation"
-  color: "ff7979"
-- name: "X-Needs-Product"
-  description: "More input needed from the Product team"
-  color: "ff7979"
-- name: "X-Regression"
-  color: "ff7979"
-- name: "X-Release-Blocker"
-  color: "ff7979"
-- name: "X-Spec-Changes"
-  description: "May require spec changes"
-  color: "ff7979"
-- name: "X-Won't-Fix"
-  description: "This will not be worked on"
-  color: "ff7979"
-- name: "Z-Community-Testing"
-  description: "Issues found during the community testing sessions"
-  color: "efefef"
-- name: "Z-Could"
-  color: "ededed"
-- name: "Z-Design"
-  color: "ededed"
-- name: "Z-Flaky-Test"
-  color: "aaaaaa"
-- name: "Z-Media-Failure"
-  description: "Someone's audio or video isn't coming through"
-  color: "ededed"
-- name: "Z-Must"
-  color: "ededed"
-- name: "Z-Platform-Specific"
-  color: "ededed"
-- name: "Z-Power-Users"
-  color: "ededed"
-- name: "Z-ProductPolish"
-  color: "aaaaaa"
-- name: "Z-Should"
-  color: "ededed"
-- name: "Z-Splitbrain"
-  description: "Someone who should be on the call isn't showing up"
-  color: "ededed"

.github/release.yml

@@ -1,30 +0,0 @@
-changelog:
-  categories:
-    - title: 🛠 Breaking Changes
-      labels:
-        - PR-Breaking-Change
-    - title: ✨ Features
-      labels:
-        - PR-Feature
-    - title: 🙌 Improvements
-      labels:
-        - PR-Improvement
-    - title: 📄 Documentation
-      labels:
-        - PR-Documentation
-    - title: 🐛 Bugfixes
-      labels:
-        - PR-Bug-Fix
-    - title: 💾 Developer Experience
-      labels:
-        - PR-Developer-Experience
-    - title: Others
-      labels:
-        - "*"
-      exclude:
-        labels:
-          - PR-Task
-          - dependencies
-    - title: 👒 Dependencies
-      labels:
-        - dependencies

.github/workflows/blocked.yaml

@@ -1,16 +1,7 @@
 name: Prevent blocked
 on:
-  # zizmor: ignore[dangerous-triggers]
-  # Reason: This workflow does not checkout code or use secrets.
-  # It only reads labels to set a failure status on the PR.
-  pull_request_target:
-    types: [opened, labeled, unlabeled, synchronize]
-
-permissions:
-  pull-requests: read
-  # Required to fail the check on the PR
-  statuses: write
-
+  pull_request:
+    types: [opened, labeled, unlabeled]
 jobs:
   prevent-blocked:
     name: Prevent blocked
@@ -19,7 +10,7 @@ jobs:
       pull-requests: read
     steps:
       - name: Add notice
-        uses: actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b # v7
+        uses: actions/github-script@v7
         if: contains(github.event.pull_request.labels.*.name, 'X-Blocked')
         with:
           script: |

.github/workflows/build-and-publish-docker.yaml

@@ -20,16 +20,13 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       contents: write # required to upload release asset
-      packages: write # needed for publishing packages to GHCR
-      id-token: write # needed for login into tailscale with GitHub OIDC Token
+      packages: write
     steps:
       - name: Check it out
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          persist-credentials: false
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
 
       - name: 📥 Download artifact
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        uses: actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806 # v4
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           run-id: ${{ inputs.artifact_run_id }}
@@ -37,64 +34,24 @@ jobs:
           path: dist
 
       - name: Log in to container registry
-        uses: docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9 # v3.7.0
+        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Connect to Tailscale
-        uses: tailscale/github-action@306e68a486fd2350f2bfc3b19fcd143891a4a2d8 # v4
-        if: github.event_name != 'pull_request'
-        with:
-          oauth-client-id: ${{ secrets.TS_OAUTH_CLIENT_ID }}
-          audience: ${{ secrets.TS_AUDIENCE }}
-          tags: tag:github-actions
-
-      - name: Compute vault jwt role name
-        id: vault-jwt-role
-        if: github.event_name != 'pull_request'
-        run: |
-          echo "role_name=github_service_management_$( echo "${{ github.repository }}" | sed -r 's|[/-]|_|g')" | tee -a "$GITHUB_OUTPUT"
-
-      - name: Get team registry token
-        id: import-secrets
-        uses: hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b # v3
-        if: github.event_name != 'pull_request'
-        with:
-          url: https://vault.infra.ci.i.element.dev
-          role: ${{ steps.vault-jwt-role.outputs.role_name }}
-          path: service-management/github-actions
-          jwtGithubAudience: https://vault.infra.ci.i.element.dev
-          method: jwt
-          secrets: |
-            services/voip-repositories/secret/data/oci.element.io username | OCI_USERNAME ;
-            services/voip-repositories/secret/data/oci.element.io password | OCI_PASSWORD ;
-
-      - name: Login to oci.element.io Registry
-        uses: docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9 # v3
-        if: github.event_name != 'pull_request'
-        with:
-          registry: oci-push.vpn.infra.element.io
-          username: ${{ steps.import-secrets.outputs.OCI_USERNAME }}
-          password: ${{ steps.import-secrets.outputs.OCI_PASSWORD }}
-
       - name: Extract metadata (tags, labels) for Docker
         id: meta
-        uses: docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051 # v5.10.0
+        uses: docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804 # v5.7.0
         with:
-          images: |
-            ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
-            oci-push.vpn.infra.element.io/element-call
-          tags: ${{ inputs.docker_tags }}
-          labels: |
-            org.opencontainers.image.licenses=AGPL-3.0-only OR LicenseRef-Element-Commercial
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          tags: ${{ inputs.docker_tags}}
 
       - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f # v3.12.0
+        uses: docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2 # v3.10.0
 
       - name: Build and push Docker image
-        uses: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8 # v6.19.2
+        uses: docker/build-push-action@471d1dc4e07e5cdedd4c2171150001c434f0b7a4 # v6.15.0
         with:
           context: .
           platforms: linux/amd64,linux/arm64

.github/workflows/build-element-call.yaml

@@ -7,13 +7,8 @@ on:
         type: string
       package:
         type: string # This would ideally be a `choice` type, but that isn't supported yet
-        description: The package type to be built. Must be one of 'full', 'embedded', or 'sdk'
+        description: The package type to be built. Must be one of 'full' or 'embedded'
         required: true
-      build_mode:
-        type: string # This would ideally be a `choice` type, but that isn't supported yet
-        description: The build mode for vite. Must be either 'development' or 'production'
-        required: false
-        default: production
     secrets:
       SENTRY_ORG:
         required: true
@@ -32,21 +27,28 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+      - name: Yarn cache
+        uses: actions/setup-node@1d0ff469b7ec7b3cb9d8673fde0c81c44821de2a # v4
         with:
-          persist-credentials: false
-      - name: Enable Corepack
-        run: corepack enable
-      - name: pnpm cache
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
-        with:
-          cache: "pnpm"
+          cache: "yarn"
           node-version-file: ".node-version"
       - name: Install dependencies
-        # ignore-pnpmfile should never be commited. Make CI crash if it happened (`pnpmfileChecksum` is present)
-        run: "pnpm install --frozen-lockfile --ignore-pnpmfile"
-      - name: Build Element Call
-        run: pnpm run build:"$PACKAGE":"$BUILD_MODE"
+        run: "yarn install --frozen-lockfile"
+      - name: Build full version
+        if: ${{ inputs.package == 'full' }}
+        run: "yarn run build:full"
+        env:
+          SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
+          SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
+          SENTRY_URL: ${{ secrets.SENTRY_URL }}
+          SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
+          VITE_APP_VERSION: ${{ inputs.vite_app_version }}
+          NODE_OPTIONS: "--max-old-space-size=4096"
+      - name: Build embedded
+        if: ${{ inputs.package == 'embedded' }}
+        run: "yarn run build:embedded"
         env:
           SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
           SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
@@ -55,10 +57,8 @@ jobs:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
           VITE_APP_VERSION: ${{ inputs.vite_app_version }}
           NODE_OPTIONS: "--max-old-space-size=4096"
-          PACKAGE: ${{ inputs.package }}
-          BUILD_MODE: ${{ inputs.build_mode }}
       - name: Upload Artifact
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
+        uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # v4
         with:
           name: build-output-${{ inputs.package }}
           path: dist

.github/workflows/build.yaml

@@ -5,8 +5,16 @@ on:
       - synchronize
       - opened
       - labeled
+    paths-ignore:
+      - ".github/ISSUE_TEMPLATE/**"
+      - ".github/CODEOWNERS"
+      - "docs/**"
   push:
-    branches: [main]
+    branches: [livekit, full-mesh]
+    paths-ignore:
+      - ".github/ISSUE_TEMPLATE/**"
+      - ".github/CODEOWNERS"
+      - "docs/**"
 jobs:
   build_full_element_call:
     # Use the full package vite build
@@ -14,7 +22,6 @@ jobs:
     with:
       package: full
       vite_app_version: ${{ github.event.release.tag_name || github.sha }}
-      build_mode: ${{ github.event_name == 'pull_request' && contains(github.event.pull_request.labels.*.name, 'development build') && 'development' || 'production' }}
     secrets:
       SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
       SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
@@ -22,8 +29,8 @@ jobs:
       SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
       CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
   deploy_develop:
-    # Deploy main branch to call.element.dev after build completes
-    if: github.ref == 'refs/heads/main'
+    # Deploy livekit branch to call.element.dev after build completes
+    if: github.ref == 'refs/heads/livekit'
     needs: build_full_element_call
     runs-on: ubuntu-latest
     steps:
@@ -43,15 +50,13 @@ jobs:
                 }
             })
   docker_for_develop:
-    # Build docker and publish docker for main branch after build completes
-    if: github.ref == 'refs/heads/main'
+    # Build docker and publish docker for livekit branch after build completes
+    if: github.ref == 'refs/heads/livekit'
     needs: build_full_element_call
     permissions:
       contents: write
       packages: write
-      id-token: write
     uses: ./.github/workflows/build-and-publish-docker.yaml
-    secrets: inherit
     with:
       artifact_run_id: ${{ github.run_id }}
       docker_tags: |
@@ -64,52 +69,9 @@ jobs:
     with:
       package: embedded
       vite_app_version: ${{ github.event.release.tag_name || github.sha }}
-      build_mode: ${{ github.event_name == 'pull_request' && contains(github.event.pull_request.labels.*.name, 'development build') && 'development' || 'production' }}
     secrets:
       SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
       SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
       SENTRY_URL: ${{ secrets.SENTRY_URL }}
       SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
       CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
-
-  build_sdk_element_call:
-    # Use the embedded package vite build
-    uses: ./.github/workflows/build-element-call.yaml
-    with:
-      package: sdk
-      vite_app_version: ${{ github.event.release.tag_name || github.sha }}
-      build_mode: ${{ github.event_name == 'pull_request' && contains(github.event.pull_request.labels.*.name, 'development build') && 'development' || 'production' }}
-    secrets:
-      SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
-      SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
-      SENTRY_URL: ${{ secrets.SENTRY_URL }}
-      SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
-      CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
-
-  build_storybook:
-    name: Build Storybook
-    if: contains(github.event.pull_request.labels.*.name, 'storybook build')
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          persist-credentials: false
-      - name: Enable Corepack
-        run: corepack enable
-      - name: pnpm cache
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
-        with:
-          cache: "pnpm"
-          node-version-file: ".node-version"
-      - name: Install dependencies
-        run: "pnpm install --frozen-lockfile --ignore-pnpmfile"
-      - name: Build Storybook
-        run: pnpm run build-storybook
-      - name: Upload Artifact
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
-        with:
-          name: build-output-storybook
-          path: storybook-static
-          # We'll only use this in a triggered job, then we're done with it
-          retention-days: 1

.github/workflows/changelog-label.yml

@@ -1,22 +0,0 @@
-name: PR changelog label
-
-on:
-  # zizmor: ignore[dangerous-triggers]
-  # This is safe because we do not use actions/checkout or execute untrusted code.
-  # Using pull_request_target is necessary to allow status writes for PRs from forks.
-  pull_request_target:
-    types: [labeled, unlabeled, opened, synchronize]
-
-permissions:
-  pull-requests: read
-  statuses: write
-
-jobs:
-  pr-changelog-label:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: yogevbd/enforce-label-action@a3c219da6b8fa73f6ba62b68ff09c469b3a1c024 # 2.2.2
-        with:
-          REQUIRED_LABELS_ANY: "PR-Bug-Fix,PR-Documentation,PR-Task,PR-Feature,PR-Improvement,PR-Developer-Experience,dependencies,PR-Breaking-Change"
-          REQUIRED_LABELS_ANY_DESCRIPTION: "Select at least one 'PR-' label"
-          BANNED_LABELS: "banned"

.github/workflows/deploy-to-netlify.yaml

@@ -14,10 +14,6 @@ on:
       deployment_ref:
         required: true
         type: string
-      package:
-        required: true
-        type: string
-        description: Which package to deploy - 'full', 'embedded', 'sdk', or 'storybook'
       artifact_run_id:
         required: false
         type: string
@@ -43,46 +39,34 @@ jobs:
         with:
           step: start
           token: ${{ secrets.GITHUB_TOKEN }}
-          env: ${{ inputs.package}}
+          env: Netlify
           ref: ${{ inputs.deployment_ref }}
           desc: |
             Do you trust the author of this PR? Maybe this build will steal your keys or give you malware.
             Exercise caution. Use test accounts.
 
       - name: 📥 Download artifact
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        uses: actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806 # v4
         with:
           github-token: ${{ secrets.ELEMENT_BOT_TOKEN }}
           run-id: ${{ inputs.artifact_run_id }}
-          name: build-output-${{ inputs.package }}
+          name: build-output-full
           path: webapp
 
       - name: Add redirects file
         # We fetch from github directly as we don't bother checking out the repo
-        # Not needed for storybook deployments
-        if: inputs.package != 'storybook'
         run: curl -s https://raw.githubusercontent.com/element-hq/element-call/main/config/netlify_redirects > webapp/_redirects
 
       - name: Add config file
-        # Not needed for storybook deployments
-        if: inputs.package != 'storybook'
-        run: |
-          if [ "${INPUTS_PACKAGE}" = "full" ]; then
-            curl -s "https://raw.githubusercontent.com/${INPUTS_PR_HEAD_FULL_NAME}/${INPUTS_PR_HEAD_REF}/config/config_netlify_preview.json" > webapp/config.json
-          else
-            curl -s "https://raw.githubusercontent.com/${INPUTS_PR_HEAD_FULL_NAME}/${INPUTS_PR_HEAD_REF}/config/config_netlify_preview_sdk.json" > webapp/config.json
-          fi
-        env:
-          INPUTS_PACKAGE: ${{ inputs.package }}
-          INPUTS_PR_HEAD_FULL_NAME: ${{ inputs.pr_head_full_name }}
-          INPUTS_PR_HEAD_REF: ${{ inputs.pr_head_ref }}
+        run: curl -s "https://raw.githubusercontent.com/${{ inputs.pr_head_full_name }}/${{ inputs.pr_head_ref }}/config/config_netlify_preview.json" > webapp/config.json
+
       - name: ☁️ Deploy to Netlify
         id: netlify
         uses: nwtgck/actions-netlify@4cbaf4c08f1a7bfa537d6113472ef4424e4eb654 # v3.0
         with:
           publish-dir: webapp
           deploy-message: "Deploy from GitHub Actions"
-          alias: ${{ inputs.package == 'sdk' && format('pr{0}-sdk', inputs.pr_number) || inputs.package == 'storybook' && format('pr{0}-storybook', inputs.pr_number) || format('pr{0}', inputs.pr_number) }}
+          alias: pr${{ inputs.pr_number }}
         env:
           NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
           NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}

.github/workflows/lint.yaml

@@ -2,31 +2,26 @@ name: Lint, format & type check
 on:
   pull_request: {}
 jobs:
-  lint:
+  prettier:
     name: Lint, format & type check
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+      - name: Yarn cache
+        uses: actions/setup-node@1d0ff469b7ec7b3cb9d8673fde0c81c44821de2a # v4
         with:
-          persist-credentials: false
-      - name: Enable Corepack
-        run: corepack enable
-      - name: pnpm cache
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
-        with:
-          cache: "pnpm"
+          cache: "yarn"
           node-version-file: ".node-version"
       - name: Install dependencies
-        # ignore-pnpmfile should never be commited. Make CI crash if it happened (`pnpmfileChecksum` is present)
-        run: "pnpm install --frozen-lockfile --ignore-pnpmfile"
-      - name: Formatting
-        run: "pnpm run format:check"
+        run: "yarn install --frozen-lockfile"
+      - name: Prettier
+        run: "yarn run prettier:check"
       - name: i18n
-        run: "pnpm run i18n:check"
-      - name: Lint
-        run: "pnpm run lint:oxlint"
+        run: "yarn run i18n:check"
+      - name: ESLint
+        run: "yarn run lint:eslint"
       - name: Type check
-        run: "pnpm run lint:types"
+        run: "yarn run lint:types"
       - name: Dead code analysis
-        run: "pnpm run lint:knip"
+        run: "yarn run lint:knip"

.github/workflows/playwright.yml

@@ -0,0 +1,33 @@
+name: Playwright Tests
+on:
+  pull_request: {}
+  push:
+    branches: [livekit, full-mesh]
+jobs:
+  test:
+    timeout-minutes: 10
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          cache: "yarn"
+          node-version-file: ".node-version"
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+      - name: Install Playwright Browsers
+        run: yarn playwright install --with-deps
+      - name: Run backend components
+        run: |
+          docker compose -f playwright-backend-docker-compose.yml up -d
+          docker ps
+      - name: Copy config file
+        run: cp config/config.devenv.json public/config.json
+      - name: Run Playwright tests
+        run: yarn playwright test
+      - uses: actions/upload-artifact@v4
+        if: ${{ !cancelled() }}
+        with:
+          name: playwright-report
+          path: playwright-report/
+          retention-days: 3

.github/workflows/pr-deploy.yaml

@@ -1,7 +1,5 @@
 name: Deploy previews for PRs
 on:
-  # zizmor: ignore[dangerous-triggers]
-  # Reason: This is now restricted to internal PRs only using the 'if' condition below.
   workflow_run:
     workflows: ["Build"]
     types:
@@ -9,14 +7,7 @@ on:
 
 jobs:
   prdetails:
-    # Logic:
-    # 1. Build must be successful
-    # 2. Event must be a pull_request
-    # 3. Head repository must be the SAME as the base repository (No Forks!)
-    if: >
-      github.event.workflow_run.conclusion == 'success' &&
-      github.event.workflow_run.event == 'pull_request' &&
-      github.event.workflow_run.head_repository.full_name == github.repository
+    if: ${{ github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event == 'pull_request' }}
     runs-on: ubuntu-latest
     outputs:
       pr_number: ${{ steps.prdetails.outputs.pr_id }}
@@ -29,7 +20,7 @@ jobs:
           owner: ${{ github.event.workflow_run.head_repository.owner.login }}
           branch: ${{ github.event.workflow_run.head_branch }}
 
-  netlify-full:
+  netlify:
     needs: prdetails
     permissions:
       deployments: write
@@ -40,42 +31,6 @@ jobs:
       pr_head_full_name: ${{ github.event.workflow_run.head_repository.full_name }}
       pr_head_ref: ${{ needs.prdetails.outputs.pr_data_json && fromJSON(needs.prdetails.outputs.pr_data_json).head.ref }}
       deployment_ref: ${{ needs.prdetails.outputs.pr_data_json && fromJSON(needs.prdetails.outputs.pr_data_json).head.sha || github.ref || github.head_ref }}
-      package: full
-    secrets:
-      ELEMENT_BOT_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}
-      NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
-      NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}
-
-  netlify-sdk:
-    needs: prdetails
-    permissions:
-      deployments: write
-    uses: ./.github/workflows/deploy-to-netlify.yaml
-    with:
-      artifact_run_id: ${{ github.event.workflow_run.id || github.run_id }}
-      pr_number: ${{ needs.prdetails.outputs.pr_number }}
-      pr_head_full_name: ${{ github.event.workflow_run.head_repository.full_name }}
-      pr_head_ref: ${{ needs.prdetails.outputs.pr_data_json && fromJSON(needs.prdetails.outputs.pr_data_json).head.ref }}
-      deployment_ref: ${{ needs.prdetails.outputs.pr_data_json && fromJSON(needs.prdetails.outputs.pr_data_json).head.sha || github.ref || github.head_ref }}
-      package: sdk
-    secrets:
-      ELEMENT_BOT_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}
-      NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
-      NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}
-
-  netlify-storybook:
-    needs: prdetails
-    if: ${{ needs.prdetails.outputs.pr_data_json && contains(fromJSON(needs.prdetails.outputs.pr_data_json).labels.*.name, 'storybook build') }}
-    permissions:
-      deployments: write
-    uses: ./.github/workflows/deploy-to-netlify.yaml
-    with:
-      artifact_run_id: ${{ github.event.workflow_run.id || github.run_id }}
-      pr_number: ${{ needs.prdetails.outputs.pr_number }}
-      pr_head_full_name: ${{ github.event.workflow_run.head_repository.full_name }}
-      pr_head_ref: ${{ needs.prdetails.outputs.pr_data_json && fromJSON(needs.prdetails.outputs.pr_data_json).head.ref }}
-      deployment_ref: ${{ needs.prdetails.outputs.pr_data_json && fromJSON(needs.prdetails.outputs.pr_data_json).head.sha || github.ref || github.head_ref }}
-      package: storybook
     secrets:
       ELEMENT_BOT_TOKEN: ${{ secrets.ELEMENT_BOT_TOKEN }}
       NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
@@ -87,9 +42,7 @@ jobs:
     permissions:
       contents: write
       packages: write
-      id-token: write
     uses: ./.github/workflows/build-and-publish-docker.yaml
-    secrets: inherit
     with:
       artifact_run_id: ${{ github.event.workflow_run.id || github.run_id }}
       docker_tags: |

.github/workflows/publish-embedded-packages.yaml

@@ -1,328 +0,0 @@
-name: Build & publish embedded packages for releases
-
-on:
-  release:
-    types: [published]
-  pull_request:
-    types:
-      - synchronize
-      - opened
-      - labeled
-  push:
-    branches: [main]
-
-jobs:
-  versioning:
-    name: Versioning
-    runs-on: ubuntu-latest
-    outputs:
-      DRY_RUN: ${{ steps.dry_run.outputs.DRY_RUN }}
-      PREFIXED_VERSION: ${{ steps.prefixed_version.outputs.PREFIXED_VERSION }}
-      UNPREFIXED_VERSION: ${{ steps.unprefixed_version.outputs.UNPREFIXED_VERSION }}
-      TAG: ${{ steps.tag.outputs.TAG }}
-    steps:
-      - name: Calculate VERSION
-        # Safely store dynamic values in environment variables
-        # to prevent shell injection (template-injection)
-        run: |
-          # The logic is executed within the shell using the env variables
-          if [ "$EVENT_NAME" = "release" ]; then
-            echo "VERSION=$RELEASE_TAG" >> "$GITHUB_ENV"
-          else
-            echo "VERSION=v0.0.0-pre.0" >> "$GITHUB_ENV"
-          fi
-        env:
-          RELEASE_TAG: ${{ github.event.release.tag_name }}
-          EVENT_NAME: ${{ github.event_name }}
-      - id: dry_run
-        name: Set DRY_RUN
-        # We perform a dry run for all events except releases.
-        # This is to help make sure that we notice if the packaging process has become
-        # broken ahead of a release.
-        run: echo "DRY_RUN=${{ github.event_name != 'release' }}" >> "$GITHUB_OUTPUT"
-      - id: prefixed_version
-        name: Set PREFIXED_VERSION
-        run: echo "PREFIXED_VERSION=${VERSION}" >> "$GITHUB_OUTPUT"
-      - id: unprefixed_version
-        name: Set UNPREFIXED_VERSION
-        # This just strips the leading character
-        run: echo "UNPREFIXED_VERSION=${VERSION:1}" >> "$GITHUB_OUTPUT"
-      - id: tag
-        # latest = a proper release
-        # other = anything else
-        name: Set tag
-        run: |
-          if [[ "${VERSION}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
-            echo "TAG=latest" >> "$GITHUB_OUTPUT"
-          elif [[ "${VERSION}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+\-rc\.[0-9]+$ ]]; then
-            echo "TAG=rc" >> "$GITHUB_OUTPUT"
-          else
-            echo "TAG=other" >> "$GITHUB_OUTPUT"
-          fi
-
-  build_element_call:
-    needs: versioning
-    uses: ./.github/workflows/build-element-call.yaml
-    with:
-      vite_app_version: embedded-${{ needs.versioning.outputs.PREFIXED_VERSION }}
-      package: embedded
-    secrets:
-      SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
-      SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
-      SENTRY_URL: ${{ secrets.SENTRY_URL }}
-      SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
-
-  publish_tarball:
-    needs: [build_element_call, versioning]
-    if: always()
-    name: Publish tarball
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write # required to upload release asset
-    steps:
-      - name: Determine filename
-        run: echo "FILENAME_PREFIX=element-call-embedded-${NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION}" >> "$GITHUB_ENV"
-        env:
-          NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION: ${{ needs.versioning.outputs.UNPREFIXED_VERSION }}
-      - name: 📥 Download built element-call artifact
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          run-id: ${{ github.event.workflow_run.id || github.run_id }}
-          name: build-output-embedded
-          path: ${{ env.FILENAME_PREFIX}}
-      - name: Create Tarball
-        run: tar --numeric-owner -cvzf ${FILENAME_PREFIX}.tar.gz ${FILENAME_PREFIX}
-      - name: Create Checksum
-        run: find ${FILENAME_PREFIX} -type f -print0 | sort -z | xargs -0 sha256sum | tee ${FILENAME_PREFIX}.sha256
-      - name: Upload
-        if: ${{ needs.versioning.outputs.DRY_RUN == 'false' }}
-        uses: softprops/action-gh-release@3bb12739c298aeb8a4eeaf626c5b8d85266b0e65 # v2
-        with:
-          files: |
-            ${{ env.FILENAME_PREFIX }}.tar.gz
-            ${{ env.FILENAME_PREFIX }}.sha256
-
-  publish_npm:
-    needs: [build_element_call, versioning]
-    if: always()
-    name: Publish NPM
-    runs-on: ubuntu-latest
-    outputs:
-      ARTIFACT_VERSION: ${{ steps.artifact_version.outputs.ARTIFACT_VERSION }}
-    permissions:
-      contents: read
-      id-token: write # Allow npm to authenticate as a trusted publisher
-    steps:
-      - name: Checkout
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          persist-credentials: false
-
-      - name: 📥 Download built element-call artifact
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          run-id: ${{ github.event.workflow_run.id || github.run_id }}
-          name: build-output-embedded
-          path: embedded/web/dist
-
-      # n.b. We don't enable corepack here because we are using plain npm
-      - name: Setup node
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
-        with:
-          node-version-file: .node-version
-          registry-url: "https://registry.npmjs.org"
-
-      - name: Publish npm
-        working-directory: embedded/web
-        run: |
-          npm version ${NEEDS_VERSIONING_OUTPUTS_PREFIXED_VERSION} --no-git-tag-version
-          echo "ARTIFACT_VERSION=$(jq '.version' --raw-output package.json)" >> "$GITHUB_ENV"
-          npm publish --provenance --access public --tag ${NEEDS_VERSIONING_OUTPUTS_TAG} ${{ needs.versioning.outputs.DRY_RUN == 'true' && '--dry-run' || '' }}
-        env:
-          NEEDS_VERSIONING_OUTPUTS_PREFIXED_VERSION: ${{ needs.versioning.outputs.PREFIXED_VERSION }}
-          NEEDS_VERSIONING_OUTPUTS_TAG: ${{ needs.versioning.outputs.TAG }}
-
-      - id: artifact_version
-        name: Output artifact version
-        run: echo "ARTIFACT_VERSION=${ARTIFACT_VERSION}" >> "$GITHUB_OUTPUT"
-
-  publish_android:
-    needs: [build_element_call, versioning]
-    if: always()
-    name: Publish Android AAR
-    runs-on: ubuntu-latest
-    outputs:
-      ARTIFACT_VERSION: ${{ steps.artifact_version.outputs.ARTIFACT_VERSION }}
-    permissions:
-      contents: read
-    steps:
-      - name: Checkout
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          persist-credentials: false
-
-      - name: 📥 Download built element-call artifact
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          run-id: ${{ github.event.workflow_run.id || github.run_id }}
-          name: build-output-embedded
-          path: embedded/android/lib/src/main/assets/element-call
-
-      - name: ☕️ Setup Java
-        uses: actions/setup-java@c1e323688fd81a25caa38c78aa6df2d33d3e20d9 # v4
-        with:
-          distribution: "temurin"
-          java-version: "17"
-
-      - name: Get artifact version
-        # Anything that is not a final release will be tagged as a snapshot
-        run: |
-          if [[ "${NEEDS_VERSIONING_OUTPUTS_TAG}" == "latest" ]]; then
-            echo "ARTIFACT_VERSION=${NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION}" >> "$GITHUB_ENV"
-          elif [[ "${NEEDS_VERSIONING_OUTPUTS_TAG}" == "rc" ]]; then
-            echo "ARTIFACT_VERSION=${NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION}" >> "$GITHUB_ENV"
-          else
-            echo "ARTIFACT_VERSION=${NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION}-SNAPSHOT" >> "$GITHUB_ENV"
-          fi
-        env:
-          NEEDS_VERSIONING_OUTPUTS_TAG: ${{ needs.versioning.outputs.TAG }}
-          NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION: ${{ needs.versioning.outputs.UNPREFIXED_VERSION }}
-
-      - name: Set version string
-        run: sed -i "s/0.0.0/${ARTIFACT_VERSION}/g" embedded/android/lib/src/main/kotlin/io/element/android/call/embedded/Version.kt
-
-      - name: Publish AAR
-        working-directory: embedded/android
-        env:
-          EC_VERSION: ${{ env.ARTIFACT_VERSION }}
-          ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.MAVEN_RELEASE_USERNAME }}
-          ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.MAVEN_RELEASE_PASSWORD }}
-          ORG_GRADLE_PROJECT_signingInMemoryKey: ${{ secrets.GPG_SIGNING_KEY }}
-          ORG_GRADLE_PROJECT_signingInMemoryKeyPassword: ${{ secrets.GPG_SIGNING_KEY_PASSWORD }}
-        run: ./gradlew publishToMavenCentral --no-daemon ${{ needs.versioning.outputs.DRY_RUN == 'true' && '--dry-run' || '' }}
-
-      - id: artifact_version
-        name: Output artifact version
-        run: echo "ARTIFACT_VERSION=${ARTIFACT_VERSION}" >> "$GITHUB_OUTPUT"
-
-  publish_ios:
-    needs: [build_element_call, versioning]
-    if: always()
-    name: Publish SwiftPM Library
-    runs-on: ubuntu-latest
-    outputs:
-      ARTIFACT_VERSION: ${{ steps.artifact_version.outputs.ARTIFACT_VERSION }}
-    permissions:
-      contents: read
-    steps:
-      - name: Checkout
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          path: element-call
-          persist-credentials: false
-
-      - name: 📥 Download built element-call artifact
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          run-id: ${{ github.event.workflow_run.id || github.run_id }}
-          name: build-output-embedded
-          path: element-call/embedded/ios/Sources/dist
-
-      - name: Checkout element-call-swift
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          repository: element-hq/element-call-swift
-          path: element-call-swift
-          persist-credentials: false
-
-      - name: Copy files
-        run: rsync -a --delete --exclude .git element-call/embedded/ios/ element-call-swift
-
-      - name: Get artifact version
-        run: echo "ARTIFACT_VERSION=${NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION}" >> "$GITHUB_ENV"
-        env:
-          NEEDS_VERSIONING_OUTPUTS_UNPREFIXED_VERSION: ${{ needs.versioning.outputs.UNPREFIXED_VERSION }}
-
-      - name: Set version string
-        run: sed -i "s/0.0.0/${ARTIFACT_VERSION}/g" element-call-swift/Sources/EmbeddedElementCall/EmbeddedElementCall.swift
-
-      - name: Test build
-        working-directory: element-call-swift
-        run: swift build
-
-      - name: Commit and tag
-        working-directory: element-call-swift
-        run: |
-          git config --global user.email "ci@element.io"
-          git config --global user.name "Element CI"
-          git add -A
-          git commit -am "Release ${NEEDS_VERSIONING_OUTPUTS_PREFIXED_VERSION}"
-          git tag -a ${ARTIFACT_VERSION} -m "${GITHUB_EVENT_RELEASE_HTML_URL}"
-        env:
-          NEEDS_VERSIONING_OUTPUTS_PREFIXED_VERSION: ${{ needs.versioning.outputs.PREFIXED_VERSION }}
-          GITHUB_EVENT_RELEASE_HTML_URL: ${{ github.event.release.html_url }}
-
-      - name: Push
-        if: ${{ needs.versioning.outputs.DRY_RUN == 'false' }}
-        working-directory: element-call-swift
-        run: |
-          git push "https://x-access-token:${SWIFT_RELEASE_TOKEN}@github.com/element-hq/element-call-swift.git" --tags
-        env:
-          SWIFT_RELEASE_TOKEN: ${{ secrets.SWIFT_RELEASE_TOKEN }}
-
-      - id: artifact_version
-        name: Output artifact version
-        run: echo "ARTIFACT_VERSION=${ARTIFACT_VERSION}" >> "$GITHUB_OUTPUT"
-
-  release_notes:
-    needs: [versioning, publish_npm, publish_android, publish_ios]
-    if: always()
-    name: Update release notes
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write # to update release notes
-    steps:
-      - name: Log versions
-        run: |
-          echo "NPM: ${NEEDS_PUBLISH_NPM_OUTPUTS_ARTIFACT_VERSION}"
-          echo "Android: ${NEEDS_PUBLISH_ANDROID_OUTPUTS_ARTIFACT_VERSION}"
-          echo "iOS: ${NEEDS_PUBLISH_IOS_OUTPUTS_ARTIFACT_VERSION}"
-        env:
-          NEEDS_PUBLISH_NPM_OUTPUTS_ARTIFACT_VERSION: ${{ needs.publish_npm.outputs.ARTIFACT_VERSION }}
-          NEEDS_PUBLISH_ANDROID_OUTPUTS_ARTIFACT_VERSION: ${{ needs.publish_android.outputs.ARTIFACT_VERSION }}
-          NEEDS_PUBLISH_IOS_OUTPUTS_ARTIFACT_VERSION: ${{ needs.publish_ios.outputs.ARTIFACT_VERSION }}
-      - name: Add release notes
-        if: ${{ needs.versioning.outputs.DRY_RUN == 'false' }}
-        uses: softprops/action-gh-release@3bb12739c298aeb8a4eeaf626c5b8d85266b0e65 # v2
-        with:
-          append_body: true
-          body: |
-
-            ## Embedded packages
-
-            This release includes the following embedded packages that allow Element Call to be used as an embedded widget
-            within another application.
-
-            ### NPM
-
-            ```
-            npm install @element-hq/element-call-embedded@${{ needs.publish_npm.outputs.ARTIFACT_VERSION }}
-            ```
-
-            ### Android AAR
-
-            ```
-            dependencies {
-              implementation 'io.element.android:element-call-embedded:${{ needs.publish_android.outputs.ARTIFACT_VERSION }}'
-            }
-            ```
-
-            ### SwiftPM
-
-            ```
-            .package(url: "https://github.com/element-hq/element-call-swift.git", from: "${{ needs.publish_ios.outputs.ARTIFACT_VERSION }}")
-            ```

.github/workflows/publish.yaml

@@ -1,85 +1,66 @@
-name: Build & publish full packages for releases
+name: Build & publish images to the package registry for releases
 
 on:
   release:
     types: [published]
 
 env:
-  VERSION: ${{ github.event.release.tag_name }}
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
 
 jobs:
   build_element_call:
+    if: ${{ github.event_name == 'release' }}
     uses: ./.github/workflows/build-element-call.yaml
     with:
       package: full
-      vite_app_version: ${{ github.event.release.tag_name }} # Using ${{ env.VERSION }} here doesn't work
+      vite_app_version: ${{ github.event.release.tag_name || github.sha }}
     secrets:
       SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
       SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
       SENTRY_URL: ${{ secrets.SENTRY_URL }}
       SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
-
   publish_tarball:
     needs: build_element_call
     if: always()
     name: Publish tarball
     runs-on: ubuntu-latest
+    outputs:
+      unix_time: ${{steps.current-time.outputs.unix_time}}
     permissions:
       contents: write # required to upload release asset
       packages: write
     steps:
-      - name: Determine filename
-        run: echo "FILENAME_PREFIX=element-call-${VERSION:1}" >> "$GITHUB_ENV"
-      - name: 📥 Download built element-call artifact
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+      - name: Get current time
+        id: current-time
+        run: echo "unix_time=$(date +'%s')" >> $GITHUB_OUTPUT
+      - name: 📥 Download artifact
+        uses: actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806 # v4
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           run-id: ${{ github.event.workflow_run.id || github.run_id }}
           name: build-output-full
-          path: ${{ env.FILENAME_PREFIX }}
+          path: dist
       - name: Create Tarball
-        run: tar --numeric-owner --transform "s/dist/${FILENAME_PREFIX}/" -cvzf ${FILENAME_PREFIX}.tar.gz ${FILENAME_PREFIX}
-      - name: Create Checksum
-        run: find ${FILENAME_PREFIX} -type f -print0 | sort -z | xargs -0 sha256sum | tee ${FILENAME_PREFIX}.sha256
+        env:
+          TARBALL_VERSION: ${{ github.event.release.tag_name || github.sha }}
+        run: |
+          tar --numeric-owner --transform "s/dist/element-call-${TARBALL_VERSION}/" -cvzf element-call-${TARBALL_VERSION}.tar.gz dist
       - name: Upload
-        uses: softprops/action-gh-release@3bb12739c298aeb8a4eeaf626c5b8d85266b0e65 # v2
+        uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # v4.6.1
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
         with:
-          files: |
-            ${{ env.FILENAME_PREFIX }}.tar.gz
-            ${{ env.FILENAME_PREFIX }}.sha256
-
+          path: "./element-call-*.tar.gz"
   publish_docker:
-    needs: build_element_call
+    needs: publish_tarball
     if: always()
-    name: Publish docker
     permissions:
       contents: write
       packages: write
-      id-token: write
     uses: ./.github/workflows/build-and-publish-docker.yaml
-    secrets: inherit
     with:
       artifact_run_id: ${{ github.event.workflow_run.id || github.run_id }}
       docker_tags: |
         type=sha,format=short,event=branch
-        type=raw,value=${{ github.event.release.tag_name }}
-        type=raw,value=latest
-      # Like before, using ${{ env.VERSION }} above doesn't work
-  add_docker_release_note:
-    needs: publish_docker
-    name: Add docker release note
-    runs-on: ubuntu-latest
-    steps:
-      - name: Add release note
-        uses: softprops/action-gh-release@3bb12739c298aeb8a4eeaf626c5b8d85266b0e65 # v2
-        with:
-          append_body: true
-          body: |
-            ## Docker full package
-            Element Call is available as a Docker image from the [GitHub Container Registry](https://github.com/element-hq/element-call/pkgs/container/element-call).
-
-            The image provides a full build of Element Call that can be used both in standalone and as a widget (on a remote URL).
-
-            ```
-            docker pull ghcr.io/element-hq/element-call:${{ env.VERSION }}
-            ```
+        type=semver,pattern=v{{version}}

.github/workflows/sync-labels.yml

@@ -1,23 +0,0 @@
-name: Sync labels
-on:
-  workflow_dispatch: {}
-
-  push:
-    branches:
-      - main
-    paths:
-      - .github/labels.yml
-      - .github/workflows/sync-labels.yml
-
-permissions: {} # We use LABEL_SYNC_GITHUB_TOKEN instead
-
-jobs:
-  sync-labels:
-    uses: element-hq/element-meta/.github/workflows/sync-labels.yml@7f2f93fb9b52ece7a0998f60e64862aa203c1746
-    with:
-      LABELS: |
-        .github/labels.yml
-      DELETE: true
-      WET: true
-    secrets:
-      ELEMENT_BOT_TOKEN: ${{ secrets.LABEL_SYNC_GITHUB_TOKEN }}

.github/workflows/test-netlify.yaml

@@ -1,48 +0,0 @@
-# Triggers after the playwright tests have finished,
-# taking the artifact and uploading it to Netlify for easier viewing
-name: Upload End to End Test report to Netlify
-on:
-  # Privilege escalation necessary to publish to Netlify
-  # 🚨 We must not execute any checked out code here.
-  workflow_run: # zizmor: ignore[dangerous-triggers]
-    workflows: ["Test"]
-    types:
-      - completed
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.workflow_run.head_branch || github.run_id }}
-  cancel-in-progress: ${{ github.event.workflow_run.event == 'pull_request' }}
-
-permissions: {}
-
-jobs:
-  report:
-    if: github.event.workflow_run.conclusion != 'cancelled'
-    name: Report results
-    runs-on: ubuntu-24.04
-    environment: Netlify
-    permissions:
-      statuses: write
-      deployments: write
-      actions: read
-    steps:
-      - name: Download HTML report
-        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          run-id: ${{ github.event.workflow_run.id }}
-          name: html-report
-          path: playwright-report
-
-      - name: 📤 Deploy to Netlify
-        uses: matrix-org/netlify-pr-preview@9805cd123fc9a7e421e35340a05e1ebc5dee46b5 # v3
-        with:
-          path: playwright-report
-          owner: ${{ github.event.workflow_run.head_repository.owner.login }}
-          branch: ${{ github.event.workflow_run.head_branch }}
-          revision: ${{ github.event.workflow_run.head_sha }}
-          token: ${{ secrets.NETLIFY_AUTH_TOKEN }}
-          site_id: ${{ secrets.NETLIFY_SITE_ID }}
-          desc: Playwright Report
-          deployment_env: EndToEndTests
-          prefix: "e2e-"

.github/workflows/test.yaml

@@ -1,90 +1,28 @@
-name: Test
+name: Run unit tests
 on:
   pull_request: {}
   push:
-    branches: [main]
+    branches: [livekit, full-mesh]
 jobs:
   vitest:
-    name: Run unit tests
+    name: Run vitest tests
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
+      - name: Yarn cache
+        uses: actions/setup-node@1d0ff469b7ec7b3cb9d8673fde0c81c44821de2a # v4
         with:
-          persist-credentials: false
-      - name: Enable Corepack
-        run: corepack enable
-      - name: pnpm cache
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
-        with:
-          cache: "pnpm"
+          cache: "yarn"
           node-version-file: ".node-version"
       - name: Install dependencies
-        # ignore-pnpmfile should never be commited. Make CI crash if it happened (`pnpmfileChecksum` is present)
-        run: "pnpm install --frozen-lockfile --ignore-pnpmfile"
-      - name: Get Playwright version
-        run: echo "PLAYWRIGHT_VERSION=$(pnpm list @playwright/test --depth=0 --json | jq -r '.[0].devDependencies["@playwright/test"].version')" >> $GITHUB_ENV
-      - name: Cache Playwright binaries
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
-        id: playwright-cache
-        with:
-          path: |
-            ~/.cache/ms-playwright
-          key: ${{ runner.os }}-playwright-${{ env.PLAYWRIGHT_VERSION }}
-      - name: Install Playwright binaries
-        if: steps.playwright-cache.outputs.cache-hit != 'true'
-        run: pnpm playwright install --with-deps
+        run: "yarn install --frozen-lockfile"
       - name: Vitest
-        run: "pnpm run test:coverage"
+        run: "yarn run test:coverage"
       - name: Upload to codecov
-        uses: codecov/codecov-action@fb8b3582c8e4def4969c97caa2f19720cb33a72f # v7
+        uses: codecov/codecov-action@0565863a31f2c772f9f0395002a31e3f06189574 # v5
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
         with:
           flags: unittests
           fail_ci_if_error: true
-  playwright:
-    name: Run end-to-end tests
-    timeout-minutes: 60
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          persist-credentials: false
-      - name: Enable Corepack
-        run: corepack enable
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
-        with:
-          cache: "pnpm"
-          node-version-file: ".node-version"
-      - name: Install dependencies
-        # ignore-pnpmfile should never be commited. Make CI crash if it happened (`pnpmfileChecksum` is present)
-        run: pnpm install --frozen-lockfile --ignore-pnpmfile
-      - name: Get Playwright version
-        run: echo "PLAYWRIGHT_VERSION=$(pnpm list @playwright/test --depth=0 --json | jq -r '.[0].devDependencies["@playwright/test"].version')" >> $GITHUB_ENV
-      - name: Cache Playwright binaries
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
-        id: playwright-cache
-        with:
-          path: |
-            ~/.cache/ms-playwright
-          key: ${{ runner.os }}-playwright-${{ env.PLAYWRIGHT_VERSION }}
-      - name: Install Playwright binaries
-        if: steps.playwright-cache.outputs.cache-hit != 'true'
-        run: pnpm playwright install --with-deps
-      - name: Run backend components
-        run: |
-          docker compose -f docker-compose-dev.yml -f docker-compose-playwright.yml pull
-          docker compose -f docker-compose-dev.yml -f docker-compose-playwright.yml up -d
-          docker ps
-      - name: Run Playwright tests
-        env:
-          USE_DOCKER: 1
-        run: pnpm exec playwright test
-      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
-        if: ${{ !cancelled() }}
-        with:
-          name: html-report
-          path: playwright-report
-          if-no-files-found: error
-          retention-days: 4

.github/workflows/translations-download.yaml

@@ -13,21 +13,15 @@ jobs:
 
     steps:
       - name: Checkout the code
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          persist-credentials: false
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
 
-      - name: Enable Corepack
-        run: corepack enable
-
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
+      - uses: actions/setup-node@1d0ff469b7ec7b3cb9d8673fde0c81c44821de2a # v4
         with:
-          cache: "pnpm"
+          cache: "yarn"
           node-version-file: ".node-version"
 
       - name: Install Deps
-        # ignore-pnpmfile should never be commited. Make CI crash if it happened (`pnpmfileChecksum` is present)
-        run: "pnpm install --frozen-lockfile --ignore-pnpmfile"
+        run: "yarn install --frozen-lockfile"
 
       - name: Prune i18n
         run: "rm -R locales"
@@ -40,17 +34,12 @@ jobs:
       - name: Fix the owner of the downloaded files
         run: "sudo chown runner:docker -R locales"
 
-      # Localazy doesn't write file contents in the same order that i18next-cli's
-      # extractor uses. We re-run the extractor after downloading to fix the order.
-      - name: i18n
-        run: pnpm i18n
-
-      - name: Formatting
-        run: pnpm format
+      - name: Prettier
+        run: yarn prettier:format
 
       - name: Create Pull Request
         id: cpr
-        uses: peter-evans/create-pull-request@22a9089034f40e5a961c8808d113e2c98fb63676 # v7.0.11
+        uses: peter-evans/create-pull-request@dd2324fc52d5d43c699a5636bcf19fceaa70c284 # v7.0.7
         with:
           token: ${{ secrets.ELEMENT_BOT_TOKEN }}
           branch: actions/localazy-download
@@ -58,7 +47,7 @@ jobs:
           title: Localazy Download
           commit-message: Translations updates
           labels: |
-            PR-Task
+            T-Task
 
       - name: Enable automerge
         run: gh pr merge --merge --auto "$PR_NUMBER"

.github/workflows/translations-upload.yaml

@@ -2,7 +2,7 @@ name: Upload translation files to Localazy
 on:
   push:
     branches:
-      - main
+      - livekit
     paths-ignore:
       - ".github/**"
 
@@ -14,9 +14,7 @@ jobs:
 
     steps:
       - name: Checkout the code
-        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
-        with:
-          persist-credentials: false
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
 
       - name: Upload
         uses: localazy/upload@27e6b5c0fddf4551596b42226b1c24124335d24a # v1

.github/workflows/zizmor.yml

@@ -1,23 +0,0 @@
-name: GitHub Actions Security Analysis with zizmor 🌈
-
-on:
-  push:
-    branches: ["main", "full-mesh"]
-  pull_request: {}
-
-permissions: {}
-
-jobs:
-  zizmor:
-    name: Run zizmor 🌈
-    runs-on: ubuntu-latest
-    permissions:
-      security-events: write # Required for upload-sarif (used by zizmor-action) to upload SARIF files.
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
-        with:
-          persist-credentials: false
-
-      - name: Run zizmor 🌈
-        uses: zizmorcore/zizmor-action@192e21d79ab29983730a13d1382995c2307fbcaa # v0.5.7

.gitignore

@@ -8,36 +8,11 @@ dist-ssr
 .idea/
 public/config.json
 backend/synapse_tmp/*
-backend/synapse_tmp_othersite/*
 /coverage
-
-# Transient agent scratch files
-/agent-workspace/
-config.json
-
-# Yarn
 yarn-error.log
-/.pnp.*
-/.yarn/*
-!/.yarn/patches
-!/.yarn/plugins
-!/.yarn/releases
-!/.yarn/sdks
-!/.yarn/versions
-# old yarn based linking
-/.links.yaml
-/.links.disabled.yaml
-/.links.temp-disabled.yaml
-# pnpm based linking
-/.links.cjs
-/.links.disabled.cjs
-/.links.temp-disabled.cjs
 
 # Playwright
 /test-results/
 /playwright-report/
 /blob-report/
 /playwright/.cache/
-
-*storybook.log
-storybook-static

.node-version

@@ -1 +1 @@
-24
+22

.oxfmtrc.json

@@ -1,6 +0,0 @@
-{
-  "$schema": "./node_modules/oxfmt/configuration_schema.json",
-  "printWidth": 80,
-  "sortPackageJson": false,
-  "ignorePatterns": ["pnpm-lock.yaml", "node_modules", "dist", "FEATURES_SPEC"]
-}

.oxlintrc.json

@@ -1,165 +0,0 @@
-{
-  "$schema": "./node_modules/oxlint/configuration_schema.json",
-  "plugins": [
-    "eslint",
-    "import",
-    "jsdoc",
-    "jsx-a11y",
-    "promise",
-    "react",
-    "typescript",
-    "unicorn",
-    "vitest"
-  ],
-  "jsPlugins": [
-    "eslint-plugin-storybook",
-    "eslint-plugin-element-call"
-    // TODO: Re-enable once oxlint supports lint rules that rely on TypeScript type-awareness.
-    // "eslint-plugin-rxjs"
-  ],
-  "categories": {
-    "correctness": "error",
-    "perf": "error"
-  },
-  "options": {
-    "denyWarnings": true,
-    "typeAware": true
-  },
-  "env": {
-    "builtin": true
-  },
-  "rules": {
-    "element-call/copyright-header": [
-      "error",
-      "/*\nCopyright %%CURRENT_YEAR%% Element Creations Ltd.\n\nSPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial\nPlease see LICENSE in the repository root for full details.\n*/\n\n"
-    ],
-    "element-call/no-observablescope-leak": "error",
-    "element-call/no-top-level-logger-get-child": "error",
-    "jsdoc/empty-tags": "error",
-    "jsdoc/check-property-names": "error",
-    "jsdoc/require-param-description": "warn",
-    "react/display-name": "error",
-    // TODO: These React Compiler-based rules joined oxlint's correctness
-    // category in v1.81 and flag many pre-existing patterns, including hooks
-    // like useLatest/useInitial/useReactiveState that intentionally access
-    // refs during render. Re-evaluate them when adopting the React Compiler.
-    "react/immutability": "off",
-    "react/no-deriving-state-in-effects": "off",
-    "react/preserve-manual-memoization": "off",
-    "react/refs": "off",
-    "react/set-state-in-effect": "off",
-    "react/static-components": "off",
-    "react/use-memo": "off",
-    // TODO: Re-enable once oxlint supports lint rules that rely on TypeScript type-awareness.
-    // "rxjs/no-exposed-subjects": "error",
-    // "rxjs/finnish": [
-    //   "error",
-    //   {
-    //     "names": {
-    //       "^this$": false
-    //     }
-    //   }
-    // ],
-    "no-restricted-imports": [
-      "error",
-      {
-        "patterns": [
-          {
-            "group": [
-              "matrix-widget-api/src",
-              "matrix-widget-api/src/",
-              "matrix-widget-api/src/**",
-              "matrix-widget-api/lib",
-              "matrix-widget-api/lib/",
-              "matrix-widget-api/lib/**"
-            ],
-            "message": "Please use matrix-widget-api instead"
-          },
-          {
-            "group": [
-              "matrix-js-sdk/src",
-              "matrix-js-sdk/src/",
-              "matrix-js-sdk/src/**",
-              "matrix-js-sdk/lib",
-              "matrix-js-sdk/lib/",
-              "matrix-js-sdk/lib/index"
-            ],
-            "message": "Please use matrix-js-sdk instead"
-          }
-        ]
-      }
-    ],
-    "typescript/no-floating-promises": "error",
-    "typescript/no-misused-promises": "error",
-    "typescript/promise-function-async": "error",
-    "typescript/require-await": "error",
-    "typescript/await-thenable": "error",
-    // To help ensure that we get proper vite/rollup lazy loading (e.g. for matrix-js-sdk).
-    "typescript/consistent-type-imports": [
-      "error",
-      {
-        "fixStyle": "inline-type-imports"
-      }
-    ],
-    // TODO: These had to be disabled in the eslint -> oxlint migration. Would be nice to
-    // enable them in future or at least document why we're disabling them.
-    "eslint/no-await-in-loop": "off",
-    "eslint/no-unused-vars": ["error", { "args": "none" }],
-    "import/default": "off",
-    "jsdoc/check-tag-names": "off",
-    "jsx-a11y/prefer-tag-over-role": "off",
-    "promise/no-callback-in-promise": "off",
-    "react/jsx-key": "off",
-    "react/jsx-no-constructed-context-values": "off",
-    "react/no-array-index-key": "off",
-    "react/no-children-prop": "off",
-    "react/no-object-type-as-default-prop": "off",
-    "typescript/no-misused-spread": "off",
-    "typescript/no-useless-default-assignment": "off",
-    "typescript/restrict-template-expressions": "off",
-    "typescript/unbound-method": "off",
-    "vitest/expect-expect": "off",
-    "vitest/no-conditional-expect": "off",
-    "vitest/no-disabled-tests": "off",
-    "vitest/require-mock-type-parameters": "off",
-    "vitest/require-to-throw-message": "off"
-  },
-  "overrides": [
-    {
-      "files": ["src/*/**"],
-      "rules": {
-        // In application code we should use the js-sdk logger, never console directly.
-        "no-console": "error"
-      }
-    },
-    {
-      "files": [
-        "**/*.test.ts",
-        "**/*.test.tsx",
-        "**/test.ts",
-        "**/test.tsx",
-        "**/test-**"
-      ],
-      "rules": {
-        // Tests often initialize an ObservableScope in an outer scope in
-        // beforeEach, which is not actually a problem
-        "element-call/no-observablescope-leak": "off",
-        "jsdoc/empty-tags": "off",
-        "jsdoc/check-property-names": "off",
-        "jsdoc/require-param-description": "off",
-        "jsx-a11y/media-has-caption": "off"
-        // TODO: Enable once oxlint supports them.
-        // "jsdoc/check-values": "off",
-        // "jsdoc/check-param-names": "off",
-        // "jsdoc/no-types": "off",
-      }
-    },
-    {
-      "files": ["playwright/**"],
-      "rules": {
-        // Playwright as a `use` function that has nothing to do with React hooks.
-        "react-hooks/rules-of-hooks": "off"
-      }
-    }
-  ]
-}

.prettierignore

@@ -0,0 +1,2 @@
+node_modules
+dist

.prettierrc.json

@@ -0,0 +1 @@
+{}

.storybook/main.ts

@@ -1,36 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import type { StorybookConfig } from "@storybook/react-vite";
-
-const config: StorybookConfig = {
-  stories: ["../src/**/*.mdx", "../src/**/*.stories.@(js|jsx|mjs|ts|tsx)"],
-  addons: ["@storybook/addon-docs", "@storybook/addon-vitest"],
-  framework: "@storybook/react-vite",
-  // THIS IS IMPORTANT
-  // vitest runs without Vite's normal dependency optimization, so we need to manually include the polyfills for the stories to work.
-  // otherwise we will get: new dependencies optimized: ...
-  // and
-  // ```
-  // [vitest] Vite unexpectedly reloaded a test. This may cause tests to fail, lead to flaky behaviour or duplicated test runs.
-  // For a stable experience, please add mentioned dependencies to your config's `optimizeDeps.include` field manually.
-  // ```
-  // which breaks the storybook ci on the first and only run.
-  viteFinal(config) {
-    config.optimizeDeps = {
-      ...config.optimizeDeps,
-      include: [
-        ...(config.optimizeDeps?.include ?? []),
-        "vite-plugin-node-polyfills/shims/buffer",
-        "vite-plugin-node-polyfills/shims/global",
-        "vite-plugin-node-polyfills/shims/process",
-      ],
-    };
-    return config;
-  },
-};
-export default config;

.storybook/manager.ts

@@ -1,31 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import { create } from "storybook/theming";
-import { addons } from "storybook/manager-api";
-
-addons.setConfig({
-  theme: create({
-    base: "light",
-    colorPrimary: "#1b1d22",
-    colorSecondary: "#0467dd",
-
-    // Typography
-    fontBase: '"Inter", sans-serif',
-    fontCode: '"Inconsolata", monospace',
-
-    // Text colors
-    textColor: "#1b1d22",
-    appBg: "#ffffff",
-    barBg: "#ffffff",
-
-    brandTitle: "Element Call",
-    brandUrl: "https://element.io/",
-    brandImage: "/src/icons/Logo.svg",
-    brandTarget: "_self",
-  }),
-});

.storybook/preview.tsx

@@ -1,58 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import type { Preview } from "@storybook/react-vite";
-import { TooltipProvider } from "@vector-im/compound-web";
-import { logger } from "matrix-js-sdk/lib/logger";
-
-import EN from "../locales/en/app.json";
-import { initReactI18next } from "react-i18next";
-import { i18n } from "../src/utils/i18n";
-import "../src/index.css";
-
-// Bare-minimum i18n config.
-// Unlike the app, stories register the instance as react-i18next's default
-// rather than wrapping every story in an <I18nextProvider>.
-i18n
-  .use(initReactI18next)
-  .init({
-    lng: "en",
-    fallbackLng: "en",
-    supportedLngs: ["en"],
-    // We embed the translations, so that it never needs to fetch
-    resources: {
-      en: {
-        translation: EN,
-      },
-    },
-    interpolation: {
-      escapeValue: false, // React has built-in XSS protections
-    },
-  })
-  .catch((e) => logger.warn("Failed to init i18n for stories", e));
-
-const preview: Preview = {
-  parameters: {
-    layout: "centered",
-    controls: {
-      matchers: {
-        color: /(background|color)$/i,
-        date: /Date$/i,
-      },
-    },
-  },
-  tags: ["autodocs"],
-  decorators: [
-    (Story) => (
-      <TooltipProvider>
-        <Story />
-      </TooltipProvider>
-    ),
-  ],
-};
-
-export default preview;

AGENTS.md

@@ -1,52 +0,0 @@
-# AGENTS.md — Element Call
-
-MatrixRTC (MSC4143) + LiveKit video calling, shipped standalone, as a widget in
-Element Web and Element X, as embedded packages, and as a React component in a
-host's page. It is the MatrixRTC reference implementation.
-
-## Non-negotiables
-
-- Features and UI changes need a pre-approved issue. No issue, no review.
-- Exactly one `PR-*` label per PR. CI enforces it; it drives the changelog.
-- New behaviour ships with unit tests, a story if it renders, and an e2e spec if it
-  is user-facing. All three.
-- Reuse an existing component. If you genuinely cannot, say so in the PR body and
-  name what you rejected — never add a new one silently.
-- Nothing reads the page. No `window.location`, `document.body`, `window.inner*`,
-  `@media`, global `i18next` or the `widget` global — take it from a provider.
-- The change works standalone, as a widget and as a component. Say what you checked.
-- Every gate below is green before you push.
-- Hand off after the first implementation, before the quality pass. Commit when the
-  user confirms direction, not before.
-
-## Read before you
-
-| …                                | …                                                          |
-| -------------------------------- | ---------------------------------------------------------- |
-| start a task of any size         | [docs/agents/workflow.md](docs/agents/workflow.md)         |
-| touch call logic or a view model | [docs/agents/architecture.md](docs/agents/architecture.md) |
-| write any code                   | [docs/agents/code-style.md](docs/agents/code-style.md)     |
-| write a test, story or e2e spec  | [docs/agents/testing.md](docs/agents/testing.md)           |
-| open a PR                        | [CONTRIBUTING.md](CONTRIBUTING.md)                         |
-| implement from a feature spec    | [FEATURES_SPEC/AGENTS.md](FEATURES_SPEC/AGENTS.md)         |
-
-## Gates
-
-```sh
-pnpm lint            # tsc, oxlint, knip, component externals
-pnpm format          # oxfmt
-pnpm test            # vitest: unit and storybook projects
-pnpm i18n:check
-```
-
-`knip` fails on dead code; a file deliberately inert ahead of its consumer goes in
-`knip.ts` `ignoreFiles` with a reason.
-
-## A good PR
-
-- One slice, under ~400 changed lines, green on its own, linked to its issue.
-- View model + marble tests, thin view, a story per state, an e2e spec.
-- Any new shared component called out explicitly, with why nothing existing fit.
-- Template filled for real: what, why, before/after screenshots, repro steps.
-- Branch `<handle>/<topic>`. Plain imperative commit subjects, no prefixes.
-- Once review starts, fix forward. Never force-push a regeneration over a review.

CONTRIBUTING.md

@@ -1,71 +1,3 @@
 # Contributing code to Element
 
 Element follows the same pattern as the [matrix-js-sdk](https://github.com/matrix-org/matrix-js-sdk/blob/develop/CONTRIBUTING.md).
-
-# Contributing to Element Call
-
-Element Call is a native Matrix video conferencing application built on
-[MatrixRTC (MSC4143)](https://github.com/matrix-org/matrix-spec-proposals/pull/4143)
-and [LiveKit](https://livekit.io/). It runs in multiple deployment contexts — as a
-standalone web app and as a widget embedded in Element Web, Element X iOS, and
-Element X Android. It is also the primary R&D foundation for MatrixRTC, which means
-its architecture, maintainability, and flexibility are held to a high standard.
-
-We welcome contributions from the community. This document explains how to
-contribute effectively so that both you and the maintainers get the best outcome.
-
-## Issue First Policy
-
-> [!IMPORTANT]
-> Before writing a single line of code for a new feature or UI change, you **must**
-> open an issue and have the approach agreed with the maintainers.
->
-> **We will not review or merge feature or UI pull requests that arrive without a
-> corresponding, pre-approved issue.**
-
-This is not gatekeeping — it's how we prevent wasted effort on both sides. Element
-Call must work correctly across multiple deployment contexts and meet specific product
-and design requirements. It is also a fast-moving codebase that underpins ongoing
-MatrixRTC development. A PR that looks reasonable in isolation can easily conflict
-with in-progress work, planned architecture changes, or design decisions that haven't
-been publicly documented yet.
-
-The issue is where we resolve all of that **before** anyone writes code.
-
-**Bug fixes** are no exception — most confirmed bugs should already have an issue anyways, existing issues that are marked as bugs have an implicit maintainer approval. If the solution for the bug is controversial it is highly recommended to discuss the approach in the issue before opening a PR.
-
-## Contribution Workflow
-
-1. **Open an issue** using the [Enhancement request](https://github.com/element-hq/element-call/issues/new?template=enhancement.yml) template.
-2. **Wait for feedback.** A maintainer will comment on the issue **within two weeks**. The use case and approach will get dicussed.
-   This may involve questions, suggestions, or a request to adjust scope.
-   This also allows to bring design and product into the loop before code gets created.
-3. **Get a green light.** Wait for explicit approval from a maintainer before starting
-   implementation.
-4. **Implement.** Write the code against the agreed approach.
-5. **Open a PR.** Link to the issue in your PR description and satisfy the checklist
-   in the PR template.
-
-## Code Quality
-
-Element Call moves fast and the codebase must stay clean and maintainable.
-
-- **Take responsibility for AI-generated code.** AI tools can be a useful aid, but we expect all the generated code to be understood and reasoned about by the contributor. Questions by the maintainers should be answered without just forwarding them to AI. The maintainers also have access to AI tools. If your contribution is just transporting messages between LLM <-> maintaines all our time is better used if the maintainers decide to interact with AI for this specific problem by themselves.
-- **Think across deployment contexts.** Changes must work correctly in both standalone
-  and widget modes. Consider how your change interacts with Element Web, Element X
-  iOS, and Element X Android.
-- **Write tests.** New functionality should be covered by tests. Where it is feasible,
-  existing uncovered code touched by your PR should also gain tests.
-
-## Contributor License Agreement
-
-All contributors must sign the
-[Element Contributor License Agreement](https://cla-assistant.io/element-hq/element-call)
-before their contribution can be merged. The CLA assistant bot will prompt you
-automatically when you open a PR.
-
-## Getting Help
-
-The best place to ask questions about Element Call development is the MatrixRTC room:
-
-**[#matrixRtc:matrix.org](https://matrix.to/#/#matrixrtc:matrix.org)**

Dockerfile

@@ -6,7 +6,7 @@ COPY ./dist /dist
 WORKDIR /dist/assets
 RUN gzip -k ../index.html *.js *.map *.css *.wasm *-app-*.json 
 
-FROM nginxinc/nginx-unprivileged:alpine-slim
+FROM nginxinc/nginx-unprivileged:alpine
 
 COPY --from=builder ./dist /app
 

FEATURES_SPEC/2026-09_Audio_Quick_Menu.md

@@ -1,356 +0,0 @@
----
-status: implement
-blocked_from: null
-title: Audio quick menu
-owner: fkwp
-signoff:
-  eng: ok
-  design: ok
-  product: ok
-experiment_ref: fkwp/feature/audio_quick_menu_exploration
-base: 029622f07b44f58f8a84e7e167e5b66374479b63
-repos: [element-call]
-specs: []
-supersedes: []
-superseded_by: null
----
-
-## Problem
-
-- `MediaMuteAndSwitchButton` populates its menu from `audioInput.available$` only. On
-  desktop, audio output is reachable only through `SettingsModal` → audio tab, which covers
-  the call view; the footer's `audioOutputSwitcher$` is an earpiece/loudspeaker toggle that
-  only materialises for controlled (mobile) devices.
-- No input-level indicator exists anywhere in the app: a participant cannot tell whether the
-  selected microphone captures sound without unmuting and asking another participant.
-- `soundEffectVolume` is adjustable only in `SettingsModal`, which replaces the call view.
-- `DeviceSelection` renders nothing when `available.size <= 1`, and `AudioOutput.available$`
-  is emptied on Safari, so those users get no indication of where call audio is going.
-- The in-call chevron is suppressed off desktop and in PiP via `disableDeviceSwitcher$`
-  (`CallFooterViewModel`), while `createLobbyFooterViewModel` passes `constant(false)`; the
-  two surfaces already disagree about when the menu exists.
-
-## Decisions
-
-- D1 — The level indicator captures from the microphone only while the menu is open, muted or
-  not — bounds the capture and the microphone-in-use indicator to a deliberate user action
-  while still answering "is my microphone working?" before unmuting.
-- D2 — The menu appears both before joining and during a call — pre-join is where a device
-  check matters most, in-call is where the settings detour costs most.
-- D3 — Before joining, the full menu appears on every platform, including mobile; during a
-  call it stays web/desktop only — the pre-join chevron already exists everywhere, so
-  suppressing sections there would be new work for no user gain.
-- D4 — Sound-effects volume appears in the menu and stays in settings, both reading and
-  writing one stored value — no migration, and neither audience loses the control it knows.
-- D5 — Where the audio output cannot be changed, the menu still shows the active output as a
-  non-selectable row — knowing where audio goes is useful even when it cannot be redirected.
-- D6 — The menu carries no disclosure that the microphone is sampled while muted — mute state
-  and the operating system's microphone-in-use indicator are independent of each other.
-- D7 — A microphone producing no signal shows an idle indicator; one held exclusively by
-  another application shows a greyed-out indicator — two distinguishable states, the second
-  rare on current operating systems.
-- D8 — A denied microphone permission shows a hint rather than a silent idle indicator —
-  silence is otherwise indistinguishable from a broken microphone.
-- D9 — The level indicator is focusable and announces its state to a screen reader while
-  focused — it is the one control in the menu with no non-visual equivalent.
-- D10 — No numeric latency target for the level indicator; it must move visibly while the
-  person is still speaking — perceived latency is not critical for a presence check.
-- D11 — Only the device lists scroll; the menu's heading and the sound-effect slider stay
-  in place — a list longer than the screen otherwise carries both out of view.
-- D12 — The level indicator belongs to the microphone group and stays visible while that
-  group is on screen, rather than sitting with the output controls — pinned next to the
-  sound-effect slider it reads as one of them.
-- D13 — Keyboard navigation marks the current item with a border, pointer use marks it with
-  a background and no border — the menu moves focus to whatever the pointer is over, so
-  without the distinction both appear at once.
-
-## Acceptance criteria
-
-Test names are the anchor; tests are created with exactly these names.
-
-- AC1 [FR-001] — The chevron beside the microphone button opens a menu headed "Audio controls".
-  - check: `pnpm vitest run --project=unit -t "audio menu is headed Audio controls"`
-- AC2 [FR-002] — The menu lists every available microphone, marks the active one, and selecting
-  another switches input without closing the menu.
-  - check: `pnpm vitest run --project=unit -t "audio menu switches microphone and stays open"`
-- AC3 [FR-003] — The menu lists every available audio output, marks the active one, and
-  selecting another switches output without closing the menu.
-  - check: `pnpm vitest run --project=unit -t "audio menu switches audio output and stays open"`
-- AC4 [FR-004] — The menu renders a separator between the microphone, speaker and
-  sound-effects groups.
-  - check: `pnpm vitest run --project=unit -t "audio menu separates microphone speaker and sound effects groups"`
-- AC5 [FR-005] — With exactly one audio output available, the speaker group still names the
-  active output and offers no selectable row.
-  - check: `pnpm vitest run --project=unit -t "audio menu shows single audio output as non-selectable"`
-- AC6 [FR-005] — In a browser that does not permit choosing an audio output, the speaker group
-  names the active output and offers no selectable row.
-  - check: manual, on Safari: join a call, open the microphone chevron, confirm the speaker
-    group names the output in use and that no row responds to a click.
-- AC7 [FR-006] — An output selected in the menu is shown as active in settings, and an output
-  selected in settings is shown as active in the menu.
-  - check: `pnpm vitest run --project=unit -t "audio output selection is shared between menu and settings"`
-- AC8 [FR-007] — While the menu is open, the level indicator's reported level follows the
-  signal level of the selected microphone.
-  - check: `pnpm vitest run --project=unit -t "level indicator follows the microphone signal level"`
-- AC9 [FR-008] — The level indicator responds to the microphone signal while the participant
-  is muted.
-  - check: `pnpm vitest run --project=unit -t "level indicator responds while muted"`
-- AC10 [FR-009] — Opening the menu starts capturing from the selected microphone; closing it
-  stops the capture.
-  - check: `pnpm vitest run --project=unit -t "audio menu starts capture on open and stops on close"`
-- AC11 [internal] — No microphone capture started by the menu outlives the menu, including
-  when the menu is closed while a device switch is in flight.
-  - check: `pnpm vitest run --project=unit -t "menu capture is released when closed during a device switch"`
-- AC12 [FR-010] — Selecting a different microphone re-points the level indicator at it without
-  closing the menu.
-  - check: `pnpm vitest run --project=unit -t "level indicator follows a microphone change"`
-- AC13 [FR-011] — A selected microphone that produces no signal leaves the indicator in its
-  idle state and produces no error.
-  - check: `pnpm vitest run --project=unit -t "level indicator stays idle for a silent microphone"`
-- AC14 [FR-018] — With microphone permission denied, the menu shows a hint in place of the
-  idle indicator.
-  - check: `pnpm vitest run --project=unit -t "audio menu hints when microphone permission is denied"`
-- AC15 [D7] — When the selected microphone cannot be opened because another application holds
-  it, the indicator renders in a greyed-out state.
-  - check: `pnpm vitest run --project=storybook -t "Microphone Unavailable"`, which reads
-    the greying a browser applies. The unit test
-    `-t "level indicator greys out when the microphone is unavailable"` covers the state
-    the stylesheet keys off, and cannot fail on the greying itself.
-- AC16 [FR-012] — Moving the sound-effects slider changes the level at which the next sound
-  effect plays.
-  - check: `pnpm vitest run --project=unit -t "sound effects volume from the menu applies to the next effect"`
-- AC17 [FR-013] — Sound-effects volume set in the menu is shown in settings and vice versa.
-  - check: `pnpm vitest run --project=unit -t "sound effects volume is shared between menu and settings"`
-- AC18 [FR-014] — The full menu is present before joining on every platform, and during a call
-  on web and desktop.
-  - check: `pnpm vitest run --project=unit -t "audio menu is present pre-join on every platform"`
-- AC19 [FR-015] — During a call on mobile, the microphone chevron offers no menu.
-  - check: `pnpm test:playwright --project=mobile -g "no audio menu during a call on mobile"`
-- AC20 [FR-016] — Every control in the menu — device rows, level indicator and sound-effects
-  slider — is reachable and operable from the keyboard alone.
-  - check: `pnpm vitest run --project=unit -t "audio menu is fully operable from the keyboard"`
-- AC21 [FR-017] — The level indicator takes focus and announces its current state to a screen
-  reader while focused.
-  - check: manual, with VoiceOver active: open the menu, tab to the level indicator, speak,
-    confirm the announced state changes with the signal.
-- AC22 [D11] — With more devices than fit on screen, the heading and the sound-effect slider
-  stay visible while the device lists scroll.
-  - check: `pnpm vitest run --project=storybook -t "With Many Devices"`, which measures the
-    layout in a browser with the device count fixed. The unit test
-    `-t "audio menu keeps its title and volume slider out of the scrolling area"` and the
-    e2e `-g "audio menu stays inside a short window"` cover the structure and the window
-    bound; neither can fail on layout alone.
-- AC23 [D12] — The level indicator stays with the microphone list and never sits among the
-  output controls.
-  - check: `pnpm vitest run --project=unit -t "level indicator stays with the microphone list rather than the speakers"`
-- AC24 [D13] — Moving through the menu by keyboard marks the current item with a border;
-  moving over it with a pointer marks it with a background and no border.
-  - check: `pnpm test:playwright --project=chromium --project=firefox -g "the focus border follows the keyboard and not the pointer"`
-- AC25 [SC-001] — Selecting an output from the menu during a call leaves the other
-  participants visible throughout.
-  - check: `pnpm test:playwright --project=chromium -g "audio menu leaves participants visible while switching output"`
-- AC26 [SC-002] — In a real browser with the menu open, sound at the microphone moves the
-  level indicator.
-  - check: `pnpm test:playwright --project=chromium --project=firefox -g "level indicator moves with microphone input"`
-- AC27 [SC-003] — Every menu control is reachable and operable by keyboard alone in
-  Chromium and Firefox.
-  - check: `pnpm test:playwright --project=chromium --project=firefox -g "audio menu is keyboard operable in a real browser"`
-- AC28 [review: #4254] — With no microphone present, the menu names the absence in place
-  of the level indicator, rather than an indicator at rest.
-  - check: `pnpm vitest run --project=unit -t "audio menu says when there is no microphone"`
-
-## Rejected alternatives
-
-- Driving the level meter from the microphone track the call already publishes — the
-  track is muted exactly when the user is muted, so the meter reads flat in the one
-  situation it exists for (D1, FR-008). A capture of its own is what makes a muted
-  check possible.
-- Gating the audio menu on there being more than one microphone, as the chevron did
-  before — leaves no menu at all where there are no input devices to list but an
-  output section is still worth showing, which is the pre-join case on iOS (D3).
-- Naming the sound-effects slider with `aria-label` — the shared slider takes its
-  accessible name from its tooltip, so the label was overridden and the control
-  announced itself as "50%". The tooltip text now carries the control's name.
-- Bounding the height of the menu as a whole — keeps it on screen, but scrolls the
-  heading away with the device list, which is what the bound was meant to prevent (D11).
-- Pinning the level meter beside the sound-effect slider — always visible, but read as
-  one of the output controls rather than as a reading of the microphone (D12).
-- Letting the level meter scroll with the microphone list — on a machine with many
-  devices it is off screen for most of the interaction (D12).
-- Fixed-width meter bars spread across the row — all leftover width lands in the gaps,
-  so the bars read as thin lines separated by wide spaces. The bars share the row
-  instead, and the gap and bar count together set their thickness.
-
-## Measurements
-
-- Unit suite: ≥ 771 passing, 0 failing, ≥ 98 files (method: `pnpm vitest run --project=unit`
-  on the experiment branch rebased onto `base`, 2026-09-10; measured 771 / 0 / 98, 9 skipped).
-- SC-001: holds (method: manual, owner, 2026-09-10 — output switched from the microphone
-  chevron menu during a call; the other participants stayed visible throughout).
-- SC-002: holds (method: manual, owner, 2026-09-10 — menu open, speaking, muted and
-  unmuted; the level indicator moved while still speaking).
-- SC-003: holds (method: manual, owner, 2026-09-10 — every menu control reached and
-  operated by keyboard alone on the supported desktop browsers).
-- Not measured: what the meter's second concurrent capture costs alongside the call's own
-  — CPU of the second capture, analyser and per-frame poll during a call, and any glitch
-  on the call's own track when the capture opens or closes.
-
-## Out of scope
-
-- The in-call chevron on mobile (`platform` `android` / `ios`), which stays suppressed by
-  `disableDeviceSwitcher$` — FR-015. The lobby chevron is in scope on every platform
-  (FR-014), so whatever `audioOutput.available$` reports there — including the
-  speaker/earpiece entries of `AndroidControlledAudioOutput` / `IOSControlledAudioOutput` —
-  is rendered by the same menu.
-- The iOS native audio-device picker button (`showNativeAudioDevicePicker`); it stays in
-  `SettingsModal`.
-- The camera chevron menu and the background-blur toggle it carries.
-- PiP layout; the menu stays suppressed there.
-- An output test tone or "play test sound" affordance.
-- Noise suppression, echo cancellation and gain controls.
-- Restructuring the settings dialog beyond keeping the sound-effects slider in place.
-
-## Open questions
-
-None.
-
-## Slicing plan
-
-Re-derived 2026-09-10 against head 029622f (see Drift log). Owner decision 2026-09-10: the
-feature lands as one PR into `fkwp/feature/audio_quick_menu`, one commit per slice, each
-commit building and passing the unit suite on its own. Order follows story priority: US1
-(P1) first, US2 (P2) second, US3 (P3) third; FR-014's pre-join surface last. Both footers
-read one `MediaDevices` helper, so slice 1 lights the menu up on either surface and slice 5
-is what holds it there.
-
-1. Audio menu: "Audio controls" heading, microphone and speaker groups, active output as
-   a non-selectable row where it cannot be changed, outputs derived in
-   `CallFooterViewModel` — covers AC1, AC2, AC3, AC5, AC6, AC7, AC25 — depends on: none
-2. Level meter component and its capture hook, unused until slice 3 — covers AC8, AC11,
-   AC13, AC15 — depends on: none
-3. Level meter in the microphone group: capture bound to the menu being open, placement
-   with the microphone list, keyboard and pointer focus states — covers AC9, AC10, AC12,
-   AC14, AC23, AC24, AC26 — depends on: 1, 2
-4. Sound-effects volume in the menu, with only the device lists scrolling — covers AC4,
-   AC16, AC17, AC20, AC21, AC22, AC27 — depends on: 3
-5. Surface coverage: the menu reaches every platform before joining and stays gated to
-   desktop during a call — covers AC18, AC19 — depends on: 4
-
-## Drift log
-
-### 2026-09-10 — drift check (base 029622f → head 029622f)
-- `origin/main` is at `base`; `base..head` is empty. Every file and symbol named in
-  `## Problem`, `## Measurements` and the provisional slicing plan exists unchanged; no
-  decision is contradicted.
-- AC check commands: vitest project `unit` and playwright projects `chromium`, `firefox`
-  and `mobile` exist; every command runs.
-- Slicing plan re-derived on size and story priority, not on drift: the provisional
-  slice 2 (menu, speakers and meter, plus the `LobbyView` and `InCallView` snapshot
-  churn) exceeds the 800-line hard stop, and the P1 story (output selection) did not
-  lead. The pre-join surface moves to its own slice so the lobby snapshots change once.
-- Implementation base: `fkwp/feature/audio_quick_menu` = head + the repo agent contract
-  and the FEATURES_SPEC process, which are in review of their own. No source file differs
-  from head. The slices and this spec ride on one branch that opens a PR against it.
-
-### 2026-09-10 — owner decision: single PR
-- The five slices land as one PR with one commit per slice, at roughly 2000 changed lines.
-  Deviates from the 800-line hard stop in `FEATURES_SPEC/AGENTS.md` ("Turning a spec into
-  PRs", step 3); accepted by the owner for a feature of this size. Review is per commit.
-- The meter's capture cost stays unmeasured (see `## Measurements`): it needs a real-browser
-  CPU profile during a call, which the implementation environment cannot produce.
-
-### 2026-09-10 — implementation findings (head 029622f)
-- The level meter reads zero on Firefox in CI, and neither the test device nor the code is
-  the reason: Firefox's fake stream carries a 1 kHz tone at about a tenth of full scale,
-  and the same test drives the meter to 0.62 against Firefox off the runner, including
-  against the Docker image over plain HTTP that CI serves. The runner has no audio backend
-  for Firefox. AC26 is therefore skipped there, a deviation from its check.
-- Firefox starts an `AudioContext` suspended, which feeds the analyser silence until it
-  resumes of its own accord seconds later. The capture is now resumed on creation, so the
-  meter answers while the person is still speaking (D10).
-- AC27 is skipped on Firefox too, a deviation from its check, because headless Firefox
-  drives Tab unreliably, as `reconnect.spec.ts` records. AC25 skips Firefox, whose fake
-  stream enumerates no audio outputs and so has nothing to switch; its check names only
-  Chromium, so that is not a deviation.
-- Keyboard reach: the Radix menu swallows Tab and walks only its own items with the arrow
-  keys, so the meter and the slider were unreachable by keyboard alone. The audio menu
-  keeps Tab from the menu so the browser's focus order reaches them (AC20, AC27); the
-  exploration's keyboard test had only asserted that the controls exist.
-- Unit suite on the PR head: 99 files, 784 passing, 0 failing, 9 skipped (method:
-  `pnpm vitest run --project=unit`, 2026-09-10). The ≥ 771 / ≥ 98 floor holds.
-
-### 2026-09-10 — finding: menu taller than the viewport (AC22, D11)
-- With many devices the menu overflowed the viewport and carried the heading off the top:
-  its height bound applied to the content box, leaving the menu's own padding outside it.
-  Fixed by bounding the border box. AC22's check runs in jsdom, which lays nothing out, so
-  it passed throughout. The story `CallFooter › With Many Devices` now measures the layout
-  in a browser with the device count fixed; owner to decide whether AC22's check names it.
-  An e2e test cannot stand in for it, because how many devices overflow the menu depends on
-  how many a browser invents: the e2e test "audio menu stays inside a short window" asserts
-  only what holds at any device count.
-
-### 2026-09-10 — upstream PRs for the base of this branch
-- The repo agent contract and the FEATURES_SPEC process go to `main` on their own: #4256
-  (`fkwp/agents-md`) and #4255 (`fkwp/features-spec-process`). `fkwp/feature/audio_quick_menu`
-  carries both as if merged; rebasing it onto `main` after they land drops the duplicates.
-
-### 2026-09-10 — finding: chevron menus leave the root in the component build
-- Compound's `Menu` portals to `document.body`, and the component build rewrites every
-  selector to match only `[data-element-call-root]` or its descendants. A menu opened there
-  matches none of its own styles: no background, no border, no padding, and the audio menu's
-  height bound is inert, so nothing holds a long device list inside the window. Measured in
-  the component harness, which applies the same scoping the library build ships.
-- Not introduced by this feature. The camera chevron menu, untouched here, is equally
-  unstyled in that build, and no component test covers a menu, which is why it went unseen.
-- Out of scope for this spec: the fix is to give the portal the root element as its
-  container, which Compound does not expose today. Raised separately. The audio menu behaves
-  as specified standalone and as a widget, which is where its acceptance criteria are checked.
-
-### 2026-09-11 — review finding: a missing microphone read as a silent one (#4254)
-- The product spec's edge case for no microphone mapped to no FR and so to no acceptance
-  criterion, and the menu drew a level indicator at rest, which is what a working but
-  silent microphone draws. The owner chose a hint in the indicator's place, as FR-018
-  requires for a denied permission, over omitting the microphone group entirely. The level
-  state now tells a microphone that is absent from one that is silent.
-- Added as AC28 and the product spec's edge case reworded to match, both with the owner's
-  authorisation, since acceptance criteria and the product spec are human-owned.
-
-### 2026-09-11 — finding: `:focus-visible` cannot express D13 (#4254)
-- The menu moves focus onto whichever item the pointer is over, so the browser decides the
-  modality for a focus it did not see the user cause. Chromium calls every focus after any
-  key press keyboard-driven, so one Escape left the border following the mouse for the rest
-  of the session; Firefox never calls a programmatic focus keyboard-driven, so the border
-  never appeared there at all. Neither matches D13.
-- The menu now tracks which way each item was reached — a key press on the trigger or on an
-  item, against pointer movement over one — and the border follows that. Verified in both
-  browsers: the border appears only after a key press and leaves again on the next pointer
-  move. AC24's manual check could now name a unit test; owner's call.
-
-### 2026-09-11 — acceptance checks that could not fail (#4254)
-- Raised in review: AC22's check ran in jsdom, which lays nothing out, so it passed whatever
-  the layout did — the defect it exists for went unseen until a screenshot. Its check now
-  names the `CallFooter` "With Many Devices" story, which measures the geometry in a browser
-  with the device count fixed. The unit test and the short-window e2e stay as they are; the
-  criterion names the one that would fail.
-- AC24 was a manual check, and the border it describes turned out to be wrong in both
-  browsers for different reasons. Its check now names an e2e test that reads the painted
-  outline as the pointer and the keyboard take turns.
-- The same audit found AC15: its check asserted the attribute the stylesheet keys off, not
-  the greying, so losing the CSS rule would not have failed it. Re-anchored to the meter's
-  own story, which reads the applied opacity.
-- Every edit to `## Acceptance criteria` was made with the owner's authorisation. The
-  remaining manual checks are AC6, which needs Safari, and AC21, which needs a screen
-  reader.
-
-### 2026-09-11 — e2e tests must not assume how many devices a browser reports
-- Twice now a new e2e test has failed in CI for the same reason: how many devices a browser
-  invents differs between them and from a developer machine. Chromium reports several
-  microphones and outputs; Firefox in CI reports one microphone and no outputs, so the menu
-  holds a single selectable row. A test that hovered the second row timed out there.
-- Tests in `playwright/audio-menu.spec.ts` now assert only what holds at any device count.
-  Where a fixed device list is what makes the check meaningful, it belongs in a story.
-
-## PRs
-
-- #4254 — draft, one commit per slice — AC1–AC27 (AC6, AC21, AC24 manual by the reviewer;
-  AC26, AC27 on Chromium only)

FEATURES_SPEC/2026-09_Audio_Quick_Menu.notes.md

@@ -1,75 +0,0 @@
-# Audio quick menu — exploration notes
-
-Not load-bearing. Nothing here constrains the implementation; constraints live in the
-feature spec.
-
-## Findings from the spike
-
-- **The shared slider names itself after its tooltip.** `Slider` wraps its thumb in a
-  compound `Tooltip`, which sets `aria-labelledby` on the thumb and so overrides the
-  `label` prop's `aria-label`. A screen reader announced the volume control as "50%".
-  Worked around at the call site by putting the control's name into the tooltip text.
-  The same defect exists in Settings → Audio today and would be better fixed in
-  `Slider` itself.
-- **Arrow keys inside the menu.** The radix menu treats arrow keys as navigation
-  between items, so a slider placed inside it never receives them. The slider row stops
-  propagation for arrow/Home/End. Without this the slider is mouse-only, which would
-  have failed AC20 silently.
-- **jsdom gaps.** The radix slider needs `ResizeObserver` and the meter needs
-  `AudioContext`; neither exists in jsdom, so both are stubbed per test file rather
-  than globally.
-- **Snapshot churn.** `LobbyView` and `InCallView` snapshots changed because the mic
-  button is now wrapped in the chevron container in cases that previously rendered a
-  bare button. Reviewed before updating; the change is the intended one.
-
-## Findings from design review
-
-- **An invented design token fails silently.** The meter's bars were written with
-  `--cpd-radius-pill-effective`; the token is `--cpd-radius-pill-effect`. An unknown
-  custom property makes the whole `border-radius` declaration invalid, so the bars
-  rendered square with no error anywhere. Worth grepping for the token name before
-  using one.
-- **A sticky child paints over the menu's border.** `FloatingMenu` draws its border as
-  an `outline` inset by one border width rather than as a real border. A
-  `position: sticky` child is positioned, so it paints above that outline and its
-  opaque background covered the border at the left and right edges. Fixed with a
-  matching inline margin on the sticky row.
-- **The bar geometry has two coupled knobs.** The bars share the row, so their width
-  is whatever the gaps leave over: raising the gap thins them and raising the count
-  thins them too. Moving both at once cancels out, which cost two review rounds.
-  Across the inset row (~248px at the menu's 340px maximum):
-
-  | bars | gap | bar width | bar:gap |
-  | ---- | --- | --------- | ------- |
-  | 20   | 8px | 4.8px     | 0.60    |
-  | 18   | 8px | 6.2px     | 0.78    |
-  | 17   | 8px | 7.1px     | 0.88    |
-  | 16   | 8px | 8.0px     | 1.00    |
-
-  The design sits near 0.8, hence 18 bars at an 8px gap.
-
-- **The bars line up with the label column, not the menu edge.** A menu item keeps a
-  `4x` margin after its label plus a `2x` column reserved for the chevron, on top of
-  the menu's own `4x` padding, so the meter's inline-end inset is `2 * 4x + 2x`.
-
-## Still open with design
-
-- The mockup marks the active device with a radio circle; the menu marks it with a
-  device icon and a checkmark, which is the existing pattern shared with the camera
-  chevron. Changing it would either change the camera menu too or make the two
-  inconsistent. Left as-is pending design sign-off.
-
-## Not done
-
-- Storybook interaction tests were not run; that project drives a real browser.
-  `AudioLevelMeter.stories.tsx` covers the five meter states for visual review.
-- Sticky positioning, the focus border and the bar geometry are all unverified by
-  tests: jsdom has no layout. The tests assert the DOM structure that makes them
-  possible, and the rest was checked by eye in a browser.
-- No measurement of what the meter's second capture costs while a call is running.
-  This is the main thing left before sign-off, and it is the decision most likely to
-  be revisited: if the cost is material, D1 gets narrower.
-- `oxfmt` covers markdown, and `AGENTS.md`, `_TEMPLATE.product.md` and the product
-  spec do not match its style, so `pnpm format:check` fails on them. Left alone: the
-  product spec is not editable after `draft` and the other two are process documents.
-  Either format them in a separate commit or exclude the folder from `oxfmt`.

FEATURES_SPEC/2026-09_Audio_Quick_Menu.product.md

@@ -1,100 +0,0 @@
-# Feature Specification: Audio quick menu
-
-**Feature Branch**: `[not yet created]`
-**Created**: 2026-09-09
-**Feature Spec**: `2026-09_Audio_Quick_Menu.md`  <!-- status lives in the feature spec's frontmatter, not here -->
-**Owner**: fkwp
-**Source**: this file
-**Input**: User description: "The chevron next to the mic button only offers microphone selection ('Mic Source'). Extend it into a combined audio quick-menu that also lets the user pick the speaker/output. Microphone check: the live, input-level meter that visibly reacts to the user's voice — so they immediately see the mic is active. For now this is web/desktop only (mobile is another story). Stretch: validate if it's possible to also place the sound effects volume in that new chevron menu."
-
-## User Scenarios & Testing *(mandatory)*
-
-### User Story 1 - Choose where the call is heard, without leaving the call (Priority: P1)
-
-A participant realises the call is coming out of the laptop speakers instead of their headset. They open the chevron next to the microphone button, see a speaker section alongside the microphone section, pick their headset, and hear the difference immediately — the call view never goes away and the menu stays open so they can confirm the choice.
-
-**Why this priority**: This is the change that removes a full detour through the settings dialog during a live call, and it is the reason the menu is being reshaped at all. It is valuable on its own, with no dependency on the level meter or the volume slider.
-
-**Independent Test**: With two or more audio outputs attached, join a call, open the microphone chevron, and switch output. Audio follows the choice, and the same choice is visible in settings.
-
-**Acceptance Scenarios**:
-
-1. **Given** a participant in a call with two or more audio outputs available, **When** they open the microphone chevron, **Then** the menu shows a microphone section and a speaker section under one "Audio controls" heading, each marking the active device.
-2. **Given** the menu is open, **When** the participant selects a different speaker, **Then** call audio moves to that device, the row is marked active, and the menu stays open.
-3. **Given** the participant switched output from the menu, **When** they open settings, **Then** settings shows the same output as the active one.
-4. **Given** a browser that does not permit choosing an audio output, or a machine with exactly one output, **When** the participant opens the menu, **Then** the speaker section still shows which output is in use, presented as information rather than a choice.
-
----
-
-### User Story 2 - Confirm the microphone is picking me up (Priority: P2)
-
-Before speaking — or after being told "we can't hear you" — a participant opens the same menu and speaks. A level indicator next to the microphone section moves with their voice, so they can tell within a second whether the selected microphone is live, and can try another one in the same menu if it is not.
-
-**Why this priority**: It answers the single most common audio complaint, but the menu is useful without it, and it carries the largest open design and privacy questions.
-
-**Independent Test**: Open the menu, speak, and watch the indicator move; select a different microphone in the same menu and confirm the indicator follows it.
-
-**Acceptance Scenarios**:
-
-1. **Given** the menu is open and the participant is unmuted, **When** they speak, **Then** the indicator visibly rises and falls with their voice.
-2. **Given** the menu is open and the participant is muted, **When** they speak, **Then** the indicator still rises and falls, so they can verify the microphone before unmuting.
-3. **Given** the indicator is live, **When** the participant closes the menu, **Then** the indicator stops capturing from the microphone.
-4. **Given** the menu is open, **When** the participant selects a different microphone, **Then** the indicator follows the newly selected microphone and the menu stays open.
-5. **Given** the selected microphone produces no signal, **When** the participant speaks, **Then** the indicator rests in an idle state rather than showing an error.
-
----
-
-### User Story 3 - Adjust sound-effect volume without leaving the call (Priority: P3)
-
-Join and leave chimes and reaction sounds are too loud during a call. The participant opens the audio menu and moves a sound-effects slider until the next chime sits where they want it.
-
-**Why this priority**: A convenience placement of an existing setting. It is the smallest slice, it can be dropped without touching the other two, and the value it adds is discoverability rather than new capability.
-
-**Independent Test**: Move the slider in the menu, trigger a sound effect, and confirm both the audible change and that settings shows the new value.
-
-**Acceptance Scenarios**:
-
-1. **Given** the menu is open, **When** the participant moves the sound-effects slider, **Then** the next sound effect plays at the new level.
-2. **Given** the participant changed the level in the menu, **When** they open settings, **Then** the settings slider shows the same level, and changing it there is reflected back in the menu.
-
----
-
-### Edge Cases
-
-- The menu is opened while muted: the operating system's "microphone in use" indicator turns on even though the participant is muted. No disclosure in the menu is required — that indicator is expected to behave the same whether the participant is muted or not, and mute state and microphone sampling are independent of one another.
-- The active microphone or speaker is unplugged while the menu is open — the menu must settle on a device that exists rather than showing a stale selection.
-- No microphone is present at all: the menu says so where the level indicator would be. An indicator at rest is what a working but silent microphone shows, so the two must not look alike.
-- Microphone permission has not been granted yet — most likely when the menu is opened in the lobby before joining.
-- Another application or browser tab holds the microphone exclusively, so the level indicator receives no signal even though the device is fine. Rare on current operating systems, which share the microphone between applications; where it does happen, the indicator shows a greyed-out state.
-- Sound-effects volume is set to zero: effects are silent but the rest of the call audio is unaffected.
-
-## Requirements *(mandatory)*
-
-### Functional Requirements
-
-- **FR-001**: The audio quick menu MUST be opened from the chevron next to the microphone button and MUST present its controls under a single "Audio controls" heading.
-- **FR-002**: The menu MUST list the available microphones, mark the active one, and switch input immediately on selection while staying open.
-- **FR-003**: The menu MUST list the available audio outputs, mark the active one, and switch output immediately on selection while staying open.
-- **FR-004**: The microphone, speaker and sound-effects controls MUST be visually separated from one another within the menu.
-- **FR-005**: When the audio output cannot be changed — the browser does not permit choosing an output, or only one output exists — the menu MUST still show the active output as a non-selectable row.
-- **FR-006**: The output selected in the menu and the output selected in settings MUST be one and the same selection; a change in either MUST be reflected in the other.
-- **FR-007**: The menu MUST show a live indicator of the sound level at the selected microphone.
-- **FR-008**: The indicator MUST respond while the microphone is muted as well as while it is unmuted.
-- **FR-009**: The indicator MUST become live when the menu opens and MUST stop capturing from the microphone when the menu closes.
-- **FR-010**: Selecting a different microphone MUST re-point the indicator at that microphone without closing the menu.
-- **FR-011**: When the selected microphone produces no signal, the indicator MUST show an idle state rather than an error.
-- **FR-012**: Users MUST be able to change the sound-effects volume from the menu, taking effect from the next sound effect onward.
-- **FR-013**: Sound-effects volume MUST remain adjustable in settings, and both controls MUST read and write the same stored value.
-- **FR-014**: The menu MUST be available before joining and during a call on web and desktop, and before joining on every platform — the pre-join chevron already exists everywhere and MUST show the full menu.
-- **FR-015**: During a call on mobile, the microphone chevron MUST behave as it does today; the menu is not introduced there.
-- **FR-016**: Every control in the menu MUST be reachable and operable by keyboard alone.
-- **FR-017**: The level indicator MUST be focusable, and while it holds focus it MUST announce its current state to a screen reader.
-- **FR-018**: When microphone permission has been denied, the menu MUST show a hint saying so, in place of a silent idle indicator.
-
-## Success Criteria *(mandatory)*
-
-### Measurable Outcomes
-
-- **SC-001**: Changing the audio output never requires opening a dialog that covers the call: the other participants remain visible from the moment the participant reaches for the control until the new output is in use.
-- **SC-002**: With the menu open, speech produces visible movement in the level indicator while the person is still speaking. No millisecond target: perceived latency is explicitly not critical for this indicator.
-- **SC-003**: Every control in the menu, including the sound-effects slider, is reachable and operable with the keyboard alone, verified on the supported desktop browsers.

FEATURES_SPEC/AGENTS.md

@@ -1,415 +0,0 @@
-# FEATURE_SPEC — Agent Instructions
-
-This folder holds **feature specs distilled from experiments**. A spec is the durable
-artifact of an exploration; the exploration branch is not. Each spec must contain
-enough information for an agent to produce mergeable PRs against a *current* `main`
-without access to the original branch.
-
-## What this folder is not
-
-- Not a design-doc archive. Specs that are not intended to be implemented do not
-  belong here.
-- Not a place for narrative. Prose that does not constrain the implementation or its
-  verification should be cut.
-- Not a substitute for the PR description. The spec explains *why* and *what must be
-  true*; the PR explains *this diff*.
-
-## File naming
-
-`YYYY-MM_Snake_Case_Title.md` — e.g. `2026-09_Raise_Hand_Improvements.md`
-
-The filename is immutable once committed. Renames break links from PRs, issues and
-the drift log. If scope changes fundamentally, write a new spec and set
-`supersedes:` / `superseded_by:`.
-
-A sidecar `YYYY-MM_Snake_Case_Title.product.md` holds the product spec — user stories,
-functional requirements, success criteria. Copy `_TEMPLATE.product.md`. Product owns
-it; see "Brainstorming: the product spec".
-
-An optional sidecar `YYYY-MM_Snake_Case_Title.notes.md` holds lessons learned,
-narrative, dead-end logs and anything else that is worth keeping but does not
-constrain the implementation. Rules:
-
-- The sidecar is **never load-bearing**. Agents do not read it to derive
-  implementation, and nothing in it may contradict or extend the spec. If a note
-  constrains the work, it belongs in `## Decisions`, `## Rejected alternatives` or
-  `## Measurements` instead.
-- Agents may append to it (an observation from a drift check, a wrong turn during
-  implementation) and must never rewrite or delete existing content.
-- An agent that is `blocked` may read the sidecar to draft an open question, but
-  quotes what it found rather than acting on it.
-- No sidecar is required. An empty one is worse than none.
-
-## Style: facts only
-
-Applies to the spec file only. The product spec is prose by design and the notes
-sidecar is unconstrained. The spec is re-read on every regeneration, where prose costs context
-and dilutes the contract, so:
-
-- Bullets, not paragraphs. Declarative present tense. No motivation, no background,
-  no summary of what the code currently does beyond locating the change.
-- Name things instead of describing them — a path, a symbol, an event type, a command,
-  an event id. A reference is shorter and more precise than a sentence about it. Which
-  kind of reference is allowed depends on the section; see "Reference durability".
-- One line per decision plus at most one sentence of rationale. If the rationale needs
-  more, the extra goes in the sidecar.
-- No judgement adjectives (clean, elegant, proper, obviously) and no hedging (should
-  probably, might be nice). Either it is a constraint or it is not in the spec.
-- `## Problem` is at most five bullets.
-- Target under 200 lines for the whole spec; over 300 lines, split the feature or move
-  material to the sidecar.
-
-The test for any line: does it constrain the implementation, constrain its
-verification, or record a measured fact? If not, delete it or move it to the sidecar.
-
-## Reference durability
-
-The spec must stay implementable against a `main` nobody has seen yet, so which
-references are allowed depends on how fast they rot. Most to least durable:
-
-1. Protocol identifiers — `m.reaction`, `m.call.member`, `m.relates_to`, a reaction
-   key. MSC-bound; effectively permanent.
-2. Observable behaviour. Permanent.
-3. Concept names — membership, participation, session.
-4. Test names. Survive file moves and renames, because the test moves with the code.
-5. Exported symbols. Survive refactors sometimes.
-6. File paths. Rot fast.
-7. Line numbers. Never.
-
-Per section:
-
-- `## Problem`, `## Measurements`, `## Slicing plan`, `## Drift log` — any reference,
-  paths and internal symbols included. These describe the codebase **as of `base`**. A
-  reference going stale here is a finding for the drift check, not a defect, and
-  removing the concrete references would leave the drift check with nothing to verify.
-- `## Decisions`, `## Acceptance criteria` — levels 1 to 4 only. No file paths, no
-  internal symbols. This is the part that has to hold against a future `main`.
-- An acceptance criterion that is not user-observable is tagged `[internal]` and
-  anchored by **its test name**, not by the symbol under test. The test name moves with
-  a refactor; the symbol does not.
-
-`[internal]` ACs are legitimate and expected: an invariant that no current consumer can
-observe is exactly what protects the consumer that does not exist yet. Tagging them
-keeps visible which ACs defend a product requirement and which defend a code
-invariant.
-
-## Required frontmatter
-
-```yaml
----
-status: draft            # see state machine below
-blocked_from: null       # state to return to when leaving `blocked`
-title: Raise hand improvements
-owner: <human handle>    # a human, always
-signoff:                 # join condition for leaving exploration.signoff
-  eng: pending
-  design: pending
-  product: pending
-experiment_ref: <branch name or commit sha of the spike, if any>
-base: <sha of main the spec was validated against>
-repos: [matrix-js-sdk, element-call]    # in dependency order
-specs: [MSC4143]         # protocol documents touched, if any
-supersedes: []
-superseded_by: null
----
-```
-
-`base` is mandatory and is what makes drift detectable. `owner` is a human even when
-every section was drafted by an agent.
-
-## Brainstorming: the product spec
-
-The usual entry point is a human handing an agent a one-line feature idea. The output
-of that session is `<stem>.product.md`, not code and not a feature spec. Copy
-`_TEMPLATE.product.md` and fill it.
-
-Ownership: an agent may create and fill this file during `brainstorm`. From `draft`
-onwards **product owns it and agents do not edit it** — not to fix wording, not to
-resolve a marker, not to reconcile it with the code. Agents raise mismatches in the
-feature spec's `## Open questions`.
-
-If product's source of truth lives outside the repo (a tracker, a design doc), put its
-URL in the header `**Source**:` line and keep the requirement text and ids in the repo
-anyway. The ids are what the feature spec references; a link alone cannot be traced.
-
-Agent behaviour during the session:
-
-- **Ask, do not assume.** An unanswered question is recorded as
-  `[NEEDS CLARIFICATION: <the question>]`, inline where the answer would go. Filling a
-  gap with a plausible guess is the main failure mode of this state — the marker is a
-  deliverable, not a defect.
-- Ask in one round of at most five questions, ordered by how much the answer changes
-  the shape of the feature. Do not interview.
-- **No implementation in the product spec.** No file paths, symbols, libraries, event
-  types, API shapes or framework names. If a requirement cannot be stated without them,
-  it is not a product requirement.
-- Every user story must be independently deployable and demonstrable on its own. A
-  story that only makes sense once another story ships is not a story; merge it.
-- More than four priority levels means more than one feature. Split before `draft`.
-- Never invent an SC number. Ask for the target, or mark it
-  `[NEEDS CLARIFICATION]`.
-
-For protocol and infrastructure work, success criteria may be expressed as observable
-client behaviour or a wire-level invariant ("a client joining mid-session converges
-within one sync"), but still never as a code path or an internal API.
-
-`FR-###` and `SC-###` ids are immutable once assigned. Product may revise the document
-at any time, including after `in_production`, but a changed requirement gets a **new
-id** and the old one is marked superseded — never edited in place. Renumbering silently
-breaks every AC that references it, and there is no way to detect that afterwards.
-
-A new or changed FR after `implement` does not amend the current spec's scope. It is
-either a new feature spec or the next iteration; the mapping table simply shows an
-unmapped FR, which is the intended signal.
-
-## Traceability
-
-The product spec states intent; the feature spec states what must be true and how it is
-checked. They are kept in sync by ids, not by duplication.
-
-- Every `FR-###` maps to at least one acceptance criterion. Tag the AC with its
-  origin: `AC2 [FR-003] — <observable behaviour>`.
-- Every `SC-###` maps to an entry in `## Measurements` with a method. An SC with no
-  measurement blocks `exploration.signoff`.
-- Every user story maps to at least one slice. **Slice order follows story priority**
-  (P1 first) unless a technical dependency overrides it, and the override is recorded
-  in the slicing plan with its reason.
-- An AC with no `FR` origin is allowed and expected — implementation-level invariants
-  have no counterpart in the product spec. The converse is not: an unmapped FR is an
-  incomplete spec.
-- Agents do not resolve a mismatch between the two. The product spec wins on intent,
-  the feature spec wins on verification; a genuine contradiction is `blocked`.
-
-## Status state machine
-
-Transitions are explicit; an agent may perform only the ones marked (agent).
-
-```
-brainstorm ─► draft ─► exploration ─► implement ─► qa ─► in_production
-                           │              │        │
-                           └──────────────┴────────┴──► blocked ──► (blocked_from)
-                                                           │
-                                                           └──► abandoned
-```
-
-Exploration has sub-states, written dotted in `status`:
-
-```
-exploration.scoping ─► exploration.iterating ─► exploration.signoff
-        ▲                       │                      │
-        └───────────────────────┴──────────────────────┘
-```
-
-- `brainstorm` → `draft`: human. Requires `<stem>.product.md` to exist with at least one
-  P1 story carrying acceptance scenarios, every FR and SC id assigned, and every
-  remaining `[NEEDS CLARIFICATION]` copied into the feature spec's `## Open questions`.
-- `draft` → `exploration.scoping`: human. Requires `## Problem` and `## Out of scope`.
-  Scoping before the branch exists is what keeps exploration from becoming the
-  long-lived branch this folder replaces.
-- `exploration.scoping` → `.iterating`: human. `experiment_ref` must name the branch.
-- `.iterating` → `.signoff`: human. Requires `## Decisions`, `## Acceptance criteria`,
-  `## Rejected alternatives` and `## Measurements` to be complete, no
-  `[NEEDS CLARIFICATION]` left in the product spec, and full traceability (below).
-- `.signoff` → `implement`: **only when all three sign-offs in `signoff:` are `ok`.**
-  This is a join, not a sequence — a single reviewer cannot advance it. On entering
-  `implement`, the exploration branch stops being a base: it is reference material,
-  and implementation branches off current `main` (see "Turning a spec into PRs").
-- `.signoff` → `.iterating`: human, on any sign-off returning changes. Reset the
-  rejecting role to `pending`; leave the others as they are.
-- `implement` → `qa`: (agent) when every acceptance criterion is covered, as recorded
-  in `## PRs`, and the feature flag is enabled in the QA environment.
-- `qa` → `in_production`: human. The flag is on by default in production.
-- `qa` → `implement`: (agent) when a QA finding needs code. See "QA feedback".
-- any active state → `blocked`: (agent) when drift or an unresolved question prevents
-  progress. Requires a drift-log entry and `blocked_from: <state>`. Do not guess and
-  continue. Leaving `blocked` returns to `blocked_from`, never to a fixed state.
-- any state → `abandoned`: human only.
-
-`in_production` is terminal. A production regression does not reopen the spec: it
-either is an ordinary bug fix with no spec, or it is a new spec. The acceptance
-criteria remain as the regression contract (see "QA feedback").
-
-## QA feedback
-
-The point of the `qa` state is not to record that testing happened. It is to make the
-spec a better regeneration source than it was before implementation. So:
-
-- Every reproduced QA finding becomes **either** a new acceptance criterion **or** a
-  new entry in `## Rejected alternatives`. Never a prose note, never only a bug
-  tracker link.
-- (agent) may **append** ACs during `qa`, with provenance:
-  `AC7 [qa: <issue ref>] — <observable behaviour>` plus its check. Appending is
-  allowed; rewriting or reordering existing ACs is not.
-- A finding that invalidates a decision does not become an AC. It sets `blocked` — a
-  decision is human-owned in every state.
-- A finding that is out of scope goes to `## Out of scope` with its issue ref, so the
-  next regeneration does not treat it as a gap.
-
-This also applies after `in_production`: a production bug that reveals a missing AC is
-appended with `[prod: <ref>]` provenance without any state change.
-
-## Required sections
-
-Order matters — agents read top-down and the first three sections are the contract.
-
-1. **`## Problem`** — up to five bullets. What breaks today, for whom, observably,
-   with the file or symbol where it breaks.
-2. **`## Decisions`** — the choices the exploration settled, each with a one-line
-   rationale. **Human-owned. An agent must never add, remove or reword a decision.**
-   If a decision is missing, set `blocked` and ask.
-3. **`## Acceptance criteria`** — the load-bearing section. Each item must be
-   mechanically checkable and name its check:
-   - `AC1 [FR-002] — <observable behaviour>` / `check: yarn vitest run src/reactions/ReactionsReader.test.tsx -t "backfill"`
-   - `AC2 [FR-002] — <observable behaviour>` / `check: manual, <exact steps>`
-   - `AC3 [internal] — <invariant>` / `check: yarn vitest run <file> -t "<test name>"`
-   An acceptance criterion without a check is a wish; reject the spec (`blocked`).
-4. **`## Rejected alternatives`** — what the experiment tried and why it failed,
-   including measurements. This exists so regeneration does not re-walk dead ends. If
-   this section is empty for a spec with an `experiment_ref`, the spec is incomplete.
-5. **`## Measurements`** — numbers from the experiment with the method used to obtain
-   them (command, hardware, load profile). Numbers without a method are not usable as
-   regression baselines and must be marked `unverified`. A baseline states its direction: a
-   count that unrelated work grows — tests passing, test files — is a floor (`≥ n`); a
-   cost — latency, CPU, bundle size — is a ceiling (`≤ n`). An exact count is stale as
-   soon as `main` moves and is not a drift finding.
-6. **`## Out of scope`** — explicit non-goals, so agents stop expanding the diff.
-7. **`## Slicing plan`** — ordered, independently mergeable PRs (see below).
-8. **`## Drift log`** — append-only, agent-written.
-9. **`## PRs`** — append-only list of `#<n> — <state> — <ACs covered>`.
-
-Optional: `## Open questions` (blocks `exploration.signoff`), `## Migration / compat` (mandatory
-whenever wire format, event schema, or a published API changes).
-
-## Turning a spec into PRs
-
-Run these steps in order. Do not skip step 2.
-
-1. **Fetch and pin.** `git fetch origin` and record `origin/main`'s sha as `head`.
-   Never start from the exploration branch, and never rebase it — the branch is
-   reference material, not a base.
-2. **Drift check** against `base..head`:
-   - Do all files, symbols and modules named in the spec still exist?
-   - Have the invariants in `## Decisions` been contradicted by changes in main?
-   - Do the commands in `## Acceptance criteria` still run?
-   Write the result as a drift-log entry. On a contradicted decision: set `blocked`,
-   do not implement.
-3. **Re-derive the slicing plan** if drift changed it. Each slice must:
-   - build and pass CI on its own,
-   - be reviewable in one sitting (target < 400 changed lines, hard stop at 800 —
-     split further rather than exceeding it),
-   - map to at least one acceptance criterion, and
-   - land behind a flag or be inert if it is not the last slice of a user-visible
-     change.
-4. **Implement one slice at a time**, branch `spec/<spec-slug>/<n>-<short>` off the
-   pinned `head`. Tests for the slice's ACs go in the same PR as the code. A PR merges
-   only when every check of every AC it lists passes on that PR: automated checks in
-   CI, manual checks performed by a human reviewer with the result recorded in the PR
-   description. An AC is *covered* once such a PR has merged.
-5. **Open the PR** linking the spec path and listing the ACs it covers. Update
-   `## PRs` and `status`.
-6. **Do not touch merged or reviewed slices.** See the regeneration rule.
-
-## The regeneration rule
-
-Regeneration from spec is only allowed **before a human has reviewed the PR**.
-
-Once review has started, the PR is a shared artifact: rebase, fix forward, push
-incremental commits. Regenerating discards the reviewer's context and silently
-invalidates their approvals. If regeneration is unavoidable after review, close the
-old PR with an explanation and open a new one — never force-push a fresh generation
-over a reviewed branch.
-
-## Cross-repo and protocol work
-
-When `repos` has more than one entry, PRs are opened in `repos` order and each PR
-body states which upstream PR it depends on. Merging out of order is a spec
-violation, not an optimisation.
-
-When `specs` is non-empty:
-- the implementation PR references the section of the MSC it implements,
-- unmerged MSCs require the implementation to be feature-flagged and documented as
-  unstable (unstable prefixes, not stable identifiers), and
-- any deviation from the MSC text is recorded in `## Drift log`, not silently
-  resolved in favour of the code.
-
-## Drift-log format
-
-Append-only, newest last:
-
-```
-### 2026-09-14 — drift check (base 4f2a1c9 → head 9b17e02)
-- `ReactionsReader.getLastReactionEvent` now takes a `CallMembership` instead of an
-  event id → AC2 and AC3 check commands still valid, slice 3 needs rework
-- BLOCKING: decision D2 assumes a membership event change may keep a hand raised; main
-  now clears all reaction relations on membership replacement. Needs owner decision.
-```
-
-Drift entries are never rewritten or deleted, including entries that were later
-resolved. The log is the record of why the implementation diverged from the
-exploration.
-
-## Hard rules
-
-- Never fill a `[NEEDS CLARIFICATION]` marker with a guess, in any state.
-- Never put file paths, symbols or library names in the product spec.
-- Never reference a file path or an internal symbol in `## Decisions` or
-  `## Acceptance criteria`. Behaviour, protocol identifiers, concepts and test names
-  only.
-- Never edit `<stem>.product.md` after `draft`, and never renumber an FR or SC id.
-- Never add a line that does not constrain the implementation, constrain its
-  verification, or record a measured fact. It goes in the sidecar or nowhere.
-- Never modify `## Decisions`, `## Problem`, or `## Acceptance criteria`. These are
-  the human contract. Propose changes in `## Open questions` and set `blocked`.
-- Never invent measurements or acceptance checks. Absent is better than plausible.
-- Never widen scope past `## Out of scope`, even when the fix looks trivial.
-- Never open a PR while `status` is `draft`, any `exploration.*`, or `blocked`.
-- Never delete a spec file. Terminal states are `in_production` or `abandoned`.
-- If the spec and current `main` disagree about how the system works, **main wins as
-  description, the spec wins as intent** — record the difference and stop.
-
-## Spec template
-
-```markdown
----
-status: draft
-blocked_from: null
-title:
-owner:
-signoff:
-  eng: pending
-  design: pending
-  product: pending
-experiment_ref:
-base:
-repos: []
-specs: []
-supersedes: []
-superseded_by: null
----
-
-## Problem
-
-## Decisions
-- D1 — <decision> — <why>
-
-## Acceptance criteria
-- AC1 [FR-###] — <observable behaviour>
-  - check: <command or exact manual steps>
-- AC2 [internal] — <invariant>
-  - check: <command, anchored by test name>
-
-## Rejected alternatives
-- <approach> — <why it failed> — <evidence>
-
-## Measurements
-- <metric>: <value> (method: <command / setup>)
-
-## Out of scope
-
-## Slicing plan
-1. <slice> — covers AC1 — depends on: none
-
-## Drift log
-
-## PRs
-```

FEATURES_SPEC/_TEMPLATE.product.md

@@ -1,117 +0,0 @@
-# Feature Specification: [FEATURE NAME]
-
-**Feature Branch**: `[###-feature-name]`
-**Created**: [DATE]
-**Feature Spec**: `[YYYY-MM_Title.md]`  <!-- status lives in the feature spec's frontmatter, not here -->
-**Owner**: [product handle]
-**Source**: [URL of the tracker/doc this mirrors, or "this file"]
-**Input**: User description: "$ARGUMENTS"
-
-## User Scenarios & Testing *(mandatory)*
-
-<!--
-  IMPORTANT: User stories should be PRIORITIZED as user journeys ordered by importance.
-  Each user story/journey must be INDEPENDENTLY TESTABLE - meaning if you implement just ONE of them,
-  you should still have a viable MVP (Minimum Viable Product) that delivers value.
-
-  Assign priorities (P1, P2, P3, etc.) to each story, where P1 is the most critical.
-  Think of each story as a standalone slice of functionality that can be:
-  - Developed independently
-  - Tested independently
-  - Deployed independently
-  - Demonstrated to users independently
--->
-
-### User Story 1 - [Brief Title] (Priority: P1)
-
-[Describe this user journey in plain language]
-
-**Why this priority**: [Explain the value and why it has this priority level]
-
-**Independent Test**: [Describe how this can be tested independently - e.g., "Can be fully tested by [specific action] and delivers [specific value]"]
-
-**Acceptance Scenarios**:
-
-1. **Given** [initial state], **When** [action], **Then** [expected outcome]
-2. **Given** [initial state], **When** [action], **Then** [expected outcome]
-
----
-
-### User Story 2 - [Brief Title] (Priority: P2)
-
-[Describe this user journey in plain language]
-
-**Why this priority**: [Explain the value and why it has this priority level]
-
-**Independent Test**: [Describe how this can be tested independently]
-
-**Acceptance Scenarios**:
-
-1. **Given** [initial state], **When** [action], **Then** [expected outcome]
-
----
-
-### User Story 3 - [Brief Title] (Priority: P3)
-
-[Describe this user journey in plain language]
-
-**Why this priority**: [Explain the value and why it has this priority level]
-
-**Independent Test**: [Describe how this can be tested independently]
-
-**Acceptance Scenarios**:
-
-1. **Given** [initial state], **When** [action], **Then** [expected outcome]
-
----
-
-[Add more user stories as needed, each with an assigned priority]
-
-### Edge Cases
-
-<!--
-  ACTION REQUIRED: The content in this section represents placeholders.
-  Fill them out with the right edge cases.
--->
-
-- What happens when [boundary condition]?
-- How does system handle [error scenario]?
-
-## Requirements *(mandatory)*
-
-<!--
-  ACTION REQUIRED: The content in this section represents placeholders.
-  Fill them out with the right functional requirements.
--->
-
-### Functional Requirements
-
-- **FR-001**: System MUST [specific capability, e.g., "allow users to create accounts"]
-- **FR-002**: System MUST [specific capability, e.g., "validate email addresses"]
-- **FR-003**: Users MUST be able to [key interaction, e.g., "reset their password"]
-- **FR-004**: System MUST [data requirement, e.g., "persist user preferences"]
-- **FR-005**: System MUST [behavior, e.g., "log all security events"]
-
-*Example of marking unclear requirements:*
-
-- **FR-006**: System MUST authenticate users via [NEEDS CLARIFICATION: auth method not specified - email/password, SSO, OAuth?]
-- **FR-007**: System MUST retain user data for [NEEDS CLARIFICATION: retention period not specified]
-
-### Key Entities *(include if feature involves data)*
-
-- **[Entity 1]**: [What it represents, key attributes without implementation]
-- **[Entity 2]**: [What it represents, relationships to other entities]
-
-## Success Criteria *(mandatory)*
-
-<!--
-  ACTION REQUIRED: Define measurable success criteria.
-  These must be technology-agnostic and measurable.
--->
-
-### Measurable Outcomes
-
-- **SC-001**: [Measurable metric, e.g., "Users can complete account creation in under 2 minutes"]
-- **SC-002**: [Measurable metric, e.g., "System handles 1000 concurrent users without degradation"]
-- **SC-003**: [User satisfaction metric, e.g., "90% of users successfully complete primary task on first attempt"]
-- **SC-004**: [Business metric, e.g., "Reduce support tickets related to [X] by 50%"]

README.md

@@ -3,7 +3,6 @@
 [![Chat](https://img.shields.io/matrix/webrtc:matrix.org)](https://matrix.to/#/#webrtc:matrix.org)
 [![Localazy](https://img.shields.io/endpoint?url=https%3A%2F%2Fconnect.localazy.com%2Fstatus%2Felement-call%2Fdata%3Fcontent%3Dall%26title%3Dlocalazy%26logo%3Dtrue)](https://localazy.com/p/element-call)
 [![License](https://img.shields.io/github/license/element-hq/element-call)](LICENSE-AGPL-3.0)
-[![Codecov](https://img.shields.io/codecov/c/github/element-hq/element-call)](https://app.codecov.io/gh/element-hq/element-call)
 
 [🎬 Live Demo 🎬](https://call.element.io)
 
@@ -36,9 +35,8 @@ You can find the latest development version continuously deployed to
 ✅ **Decentralized & Federated** – No central authority; works across Matrix
 homeservers.  
 ✅ **End-to-End Encrypted** – Secure and private calls.  
-✅ **Standalone, Widget & Component Mode** – Use as an independent app, embed
-in Matrix clients as a widget, or (experimentally) mount it as a React component
-inside your own application.  
+✅ **Standalone & Widget Mode** – Use as an independent app or embed in Matrix
+clients.  
 ✅ **WebRTC-based** – No additional software required.  
 ✅ **Scalable with LiveKit** – Supports large meetings via SFU
 ([MSC4195: MatrixRTC using LiveKit backend](https://github.com/hughns/matrix-spec-proposals/blob/hughns/matrixrtc-livekit/proposals/4195-matrixrtc-livekit.md)).  
@@ -47,35 +45,28 @@ organize the flow of the meeting.
 ✅ **Emoji Reactions** – Users can react with emojis 👍️ 🎉 👏 🤘, adding
 engagement and interactivity to the conversation.
 
-## 🚀 Deployment & Packaging Options
+## 🚀 Deployment Options
 
-Element Call is developed using the
-[Matrix js-sdk](https://github.com/matrix-org/matrix-js-sdk) with Matroska mode.
-This allows the app to run either as a Standalone App directly connected to a
-homeserver with login interfaces or it can be used as a widget within a Matrix
-client.
+Element Call can be packaged in two ways:
 
-### 🖥️ Standalone Mode
+**Full Package** – Supports both **Standalone** and **Widget** mode. Hosted as
+a static web page and accessed via a URL when used as a widget.
 
-<p align="center">
-  <img src="./docs/element_call_standalone.drawio.png" alt="Element Call in Standalone Mode">
-</p>
+**Embedded Package** – 🚧 **Coming [Soon](https://github.com/element-hq/element-call/issues/2994):** Designed for **Widget mode** only. Bundled with a
+messenger app for seamless integration. This is the recommended method for
+embedding Element Call into a messenger app.
 
-In Standalone mode, Element Call operates as an independent, full-featured video
-conferencing web application, enabling users to join or host calls without
+### Standalone mode
+
+![Element Call in Standalone Mode](./docs/element_call_standalone.drawio.png)
+
+In Standalone mode Element Call operates as an independent, full-featured video
+conferencing web application, allowing users to join or host calls without
 requiring a separate Matrix client.
 
-### 📲 In-App Calling (Widget Mode in Messenger Apps)
+### Widget mode embedded in Messenger Apps
 
-When used as a widget 🧩, Element Call is solely responsible for the core calling
-functionality (MatrixRTC). Authentication, event handling, and room state
-updates (via the Client-Server API) are handled by the hosting client.
-Communication between Element Call and the client is managed through the widget
-API.
-
-<p align="center">
-  <img src="./docs/element_call_widget.drawio.png" alt="Element Call in Widget Mode">
-</p>
+![Element Call in Widget Mode](./docs/element_call_widget.drawio.png)
 
 Element Call can be embedded as a widget inside apps like
 [**Element Web**](https://github.com/element-hq/element-web) or **Element X
@@ -87,97 +78,58 @@ and voice calls within Matrix rooms.
 > [!IMPORTANT]
 > Embedded packaging is recommended for Element Call in widget mode!
 
-### 📦 Element Call Packaging
-
-Element Call offers two packaging options: one for standalone or widget
-deployment, and another for seamless widget-based integration into messenger
-apps. A third, experimental option builds it as a React component library for
-applications that want to render a call inside their own page rather than in an
-iframe. Below is an overview of each option.
-
-**Full Package** – Supports both **Standalone** and **Widget** mode. It is
-hosted as a static web page and can be accessed via a URL when used as a widget.
-
-<p align="center">
-  <img src="./docs/full_package.drawio.png" alt="Element Call Full Package">
-</p>
-
-**Embedded Package** – Designed specifically for **Widget mode** only. It is
-bundled with a messenger app for seamless integration and this is the
-recommended method for embedding Element Call.
-
-<p align="center">
-  <img src="./docs/embedded_package.drawio.png" alt="Element Call Embedded Package">
-</p>
-
-**Component Package (experimental)** – A library build of Element Call as a
-React component, consumed as a dependency by a host application that already
-has a Matrix client. See
-[Element Call as a component](#element-call-as-a-component-experimental) below.
-
-For more details on the packages, see the
-[Embedded vs. Standalone Guide](./docs/embedded_standalone.md).
-
 ## 🛠️ Self-Hosting
 
 For operating and deploying Element Call on your own server, refer to the
-[**Self-Hosting Guide**](./docs/self_hosting.md).
+[**Self-Hosting Guide**](./docs/self-hosting.md).
 
-## MatrixRTC Transports
+## 🧭 MatrixRTC Backend Discovery and Selection
 
-For proper operation of Element Call, each deployment needs to set up a
-MatrixRTC transport in the form of a LiveKit server as outlined in the
-[Self-Hosting Guide](./docs/self_hosting.md). A typical federated site
+For proper Element Call operation each site deployment needs a MatrixRTC backend
+setup as outlined in the [Self-Hosting](#self-hosting). A typical federated site
 deployment for three different sites A, B and C is depicted below.
 
-<p align="center">
-  <img src="./docs/Federated_Setup.drawio.png" alt="Element Call federated setup">
-</p>
+![Element Call federated setup](./docs/Federated_Setup.drawio.png)
 
-### Transport Discovery
+### Backend Discovery
 
-Element Call discovers the available MatrixRTC transports (as defined by
-[MSC4519](https://github.com/matrix-org/matrix-spec-proposals/pull/4519)) by
-hitting the `GET /_matrix/client/unstable/org.matrix.msc4143/rtc/transports`
-endpoint of the Client-Server API. An example response:
+MatrixRTC backend (according to
+[MSC4143](https://github.com/matrix-org/matrix-spec-proposals/pull/4143))
+is announced by the homeserver's `.well-known/matrix/client` file and discovered
+via the `org.matrix.msc4143.rtc_foci` key, e.g.:
 
 ```json
-{
-  "rtc_transports": [
+"org.matrix.msc4143.rtc_foci": [
     {
-      "type": "livekit",
-      "livekit_service_url": "https://matrix-rtc.example.com/livekit/jwt"
-    }
-  ]
-}
+        "type": "livekit",
+        "livekit_service_url": "https://someurl.com"
+    },
+]
 ```
 
 where the format for MatrixRTC using LiveKit backend is defined in
 [MSC4195](https://github.com/hughns/matrix-spec-proposals/blob/hughns/matrixrtc-livekit/proposals/4195-matrixrtc-livekit.md).
 In the example above Matrix clients do discover a focus of type `livekit` which
-points them to a [MatrixRTC Authorization Service](https://github.com/element-hq/lk-jwt-service)
-via `livekit_service_url`.
+points them to a Matrix LiveKit JWT Auth Service via `livekit_service_url`.
 
 ### Backend Selection
 
-- Each call participant proposes their discovered MatrixRTC transport from
+- Each call participant proposes their discovered MatrixRTC backend from
   `org.matrix.msc4143.rtc_foci` in their `org.matrix.msc3401.call.member` state event.
-- For the **LiveKit** MatrixRTC backend
+- For **LiveKit** MatrixRTC backend
   ([MSC4195](https://github.com/hughns/matrix-spec-proposals/blob/hughns/matrixrtc-livekit/proposals/4195-matrixrtc-livekit.md)),
-  the **first participant who joined the call** defines which backend will be used for this call via
-  the `foci_preferred` key in their `org.matrix.msc3401.call.member` state event.
-- During the actual call join flow, the **[MatrixRTC Authorization Service](https://github.com/element-hq/lk-jwt-service)**
-  provides the client with the **LiveKit SFU WebSocket URL** and an
-  **access JWT token** in order to exchange media via WebRTC.
+  the **first participant who joined the call** defines via the `foci_preferred`
+  key in their `org.matrix.msc3401.call.member` which actual MatrixRTC backend
+  will be used for this call.
+- During the actual call join flow, the **LiveKit JWT Auth Service** provides
+  the client with the **LiveKit SFU WebSocket URL** and an **access JWT token**
+  in order to exchange media via WebRTC.
 
 The example below illustrates how backend selection works across **Matrix
 federation**, using the setup from sites A, B, and C. It demonstrates backend
 selection for **Matrix rooms 123 and 456**, which include users from different
-homeservers.
-
-<p align="center">
-  <img src="./docs/SFU_selection.drawio.png" alt="Element Call SFU selection over Matrix federation">
-</p>
+homeservers.  
+![Element Call SFU selection over Matrix federation](./docs/SFU_selection.drawio.png)
 
 ## 🌍 Translation
 
@@ -188,13 +140,6 @@ discuss and coordinate translation efforts.
 
 ## 🛠️ Development
 
-### Dependencies
-
-- Node.js (e.g. via [nvm](https://github.com/nvm-sh/nvm))
-- [Corepack](https://github.com/nodejs/corepack) (not bundled with Node.js anymore starting from 25.0.0)
-- Docker client and runtime + Docker Compose (for the backend)
-  - On macOS you can install everything with `brew install colima docker docker-compose`
-
 ### Frontend
 
 To get started clone and set up this project:
@@ -202,8 +147,7 @@ To get started clone and set up this project:
 ```sh
 git clone https://github.com/element-hq/element-call.git
 cd element-call
-corepack enable
-pnpm install
+yarn
 ```
 
 To use it, create a local config by, e.g.,
@@ -211,178 +155,60 @@ To use it, create a local config by, e.g.,
 The `config.devenv.json` config should work with the backend development
 environment as outlined in the next section out of box.
 
+> [!NOTE]
+> Be aware, that this `config.devenv.json` is exposing a deprecated fallback
+> LiveKit config key. If the homeserver advertises SFU backend via
+> `.well-known/matrix/client` this has precedence.
+
 You're now ready to launch the development server:
 
 ```sh
-pnpm dev
+yarn dev
 ```
 
-See also:
-
-- [Developing with linked packages](./docs/linking.md)
-
-#### Element Call as a component (experimental)
-
-Element Call can also be embedded directly into another React application
-rather than being loaded in an iframe as a widget. `pnpm build:component`
-builds it as a library into `component/dist` (the bundle, its stylesheet and
-type declarations), and
-
-```sh
-pnpm dev:component
-```
-
-serves a harness on port 3001 that stands in for such an application: it signs
-in twice against the development backend and shows two calls side by side, in
-resizable boxes, with page furniture of its own around them. Use it to see how
-Element Call behaves when it does not own the page — the size it is given,
-whether it stays inside its container, and what it says to its host, which is
-logged along the bottom. The harness is served with the same development
-certificate as the app, so unless the development CA is trusted, the browser
-needs a certificate exception for `https://localhost:3001` as well (see the
-note under [Backend](#backend)). It reads the same `public/config.json` as
-`pnpm dev` if one exists, and runs with Element Call's defaults otherwise.
-
-The call lays itself out for the size of the element it is mounted in, not the
-window: a host that shrinks the container to a corner of its page gets the
-picture-in-picture layout, just as a host that shrank the whole iframe used to.
-The breakpoints in the stylesheets the component uses are
-`@container element-call` queries against its root element for the same reason;
-for the standalone app the root is the page, so they mean what the media queries
-they replaced did. (The standalone-only views, such as the home and login pages,
-still use plain media queries, since the component never shows them.)
-
-The component's stylesheet is confined to the element it is mounted in: the
-build rewrites every selector so that it matches only Element Call's root or
-what is inside it, with `html`, `body` and `:root` standing for that root (see
-`component/build/scopeStylesToRoot.ts`). A host's own page keeps its styles,
-and Element Call brings its own fonts and design tokens along.
-
-The component speaks every language the app does. English is bundled in; the
-other locales are split into chunks the host's bundler loads the first time
-they are needed. It starts in the browser's language, and follows the host's
-own language setting through the `language` prop (`supportedLanguages` lists
-the tags it accepts, and anything else falls back to its base language or to
-English). The `theme` prop works the same way and takes the same values as the
-widget's `theme` URL parameter: `light`, `dark`, `light-high-contrast` or
-`dark-high-contrast`. Both can change while a call is running without
-disturbing it.
-
-A host must call and await `initializeElementCall(config)` once before
-rendering the component: it loads the `Intl` polyfills, applies the
-deployment-wide `config.json`-style configuration and sets up translations.
-The component itself takes the host's `client` and the `roomId` to call in, an
-`intent` saying what the user asked for (which decides whether to show the
-lobby, ring, and so on), an optional `config` overriding what the intent
-implies, and an optional `hostBridge` through which Element Call tells the host
-that the user has joined or hung up, that it wants to stay on screen, and so
-on. The host makes its own requests (`join`, `hangUp`, `setDeviceMute`) through
-the handle exposed on `ref`. The full API is documented in the type declarations
-(`component/index.tsx` and `component/host.ts`).
-
-A few things differ from the widget on purpose: the component draws a solid
-background rather than a gradient unless told otherwise, never offers to edit
-the user's profile (the account is the host's), scopes its keyboard shortcuts to
-its own root element so that several instances can share a page, and only shows
-its own post-call and error screens when the host has not supplied a `close()`
-callback; with one, it asks the host to unmount it instead. The
-[global JS controls](./docs/controls.md) on `window` are unchanged and remain
-page-wide, so with several instances on one page they apply to all of them.
-
-The package is not published yet. A host installs it as a git dependency on the
-`component` directory of this repository,
-
-```json
-"@element-hq/element-call-component": "github:element-hq/element-call#main&path:/component"
-```
-
-whose `prepare` script runs the build on install. That build needs pnpm (via
-Corepack) on the host's machine, runs a full `pnpm install` of this repository
-and is memory-hungry, since it inherits the `--max-old-space-size` setting of
-the app build; the host's pnpm also has to allow it to run at all
-(`allowBuilds` in its `pnpm-workspace.yaml`). Note that `component/` is a pnpm
-project of its own for this reason, so pnpm commands run from inside that
-directory target it rather than the repository; run them from the repository
-root. The host imports the component from
-`@element-hq/element-call-component` and the stylesheet from
-`@element-hq/element-call-component/style.css`, and has to provide `react`,
-`react-dom`, `matrix-js-sdk` and `livekit-client` itself, since the bundle leaves
-them external.
-
 ### Backend
 
-A docker compose file `docker-compose-dev.yml` is provided to start the
-whole stack of components which is required for a local development environment
-including federation:
+A docker compose file `dev-backend-docker-compose.yml` is provided to start the
+whole stack of components which is required for a local development environment:
 
-- Minimum Synapse Setup (servernames: `synapse.m.localhost`, `synapse.othersite.m.localhost`)
-- MatrixRTC Authorization Service (Note: requires Federation API and hence a TLS reverse proxy)
-- Minimum LiveKit SFU setup using dev defaults for config
-- Minimum `localhost` Certificate Authority (CA) for Transport Layer Security (TLS)
-  - Hostnames: `m.localhost`, `*.m.localhost`, `*.othersite.m.localhost`
-  - Add [./backend/dev_tls_local-ca.crt](./backend/dev_tls_local-ca.crt) to your web browser's trusted
-    certificates
-- Minimum TLS reverse proxy for
-  - Synapse homeserver: `synapse.m.localhost` and `synapse.othersite.m.localhost`
-  - MatrixRTC backend: `matrix-rtc.m.localhost` and `matrix-rtc.othersite.m.localhost`
-  - Local Element Call development `call.m.localhost` via `pnpm dev --host `
-  - Element Web `app.m.localhost` and `app.othersite.m.localhost`
-  - Note certificates will expire on Thr, 20 September 2035 14:27:35 CEST
+- Minimum Synapse Setup (servername: `synapse.localhost`)
+- LiveKit JWT Service (Note requires Federation API and hence a TLS reverse proxy)
+- Minimum TLS reverse proxy (servername: `synapse.localhost`) Note certificates
+  are valid for at least 10 years from now
+- Minimum LiveKit SFU Setup using dev defaults for config
+- Redis db for completeness
 
 These use a test 'secret' published in this repository, so this must be used
 only for local development and **_never be exposed to the public Internet._**
 
-Make sure your Docker runtime is running (e.g. via `colima start`) and then start
-the backend components:
+Run backend components:
 
 ```sh
-pnpm backend
-# or for podman-compose:
-# podman-compose -f docker-compose-dev.yml up
-```
-
-> [!NOTE]
-> To ensure your local development frontend functions properly, you’ll need to
-> add certificate exceptions in your browser for `https://localhost:3000` and
-> `https://matrix-rtc.m.localhost/livekit/jwt/healthz`. This can be done either
-> by adding the minimum localhost CA
-> ([./backend/dev_tls_local-ca.crt](./backend/dev_tls_local-ca.crt)) to your web
-> browser's trusted certificates or by simply copying and pasting each URL into
-> your browser’s address bar and follow the prompts to add the exception.
-
-### Updating snapshots
-
-To update snapshots used in tests, use Vitest's `-u` flag, e.g.:
-
-```sh
-pnpm test DeveloperSettingsTab -u
+yarn backend
+# or  for podman-compose
+# podman-compose -f dev-backend-docker-compose.yml up
 ```
 
 ### Playwright tests
 
-Our Playwright tests run automatically as part of our CI along with our other
-tests, on every pull request.
+Our Playwright tests run automatically as part of our CI along with our other tests,
+on every pull request.
 
-You may need to follow instructions to set up your development environment for
-running Playwright by following
-<https://playwright.dev/docs/browsers#install-browsers> and
+You may need to follow instructions to set up your development environment for running
+Playwright by following <https://playwright.dev/docs/browsers#install-browsers> and
 <https://playwright.dev/docs/browsers#install-system-dependencies>.
 
-However the Playwright tests are run, an element-call instance must be running
-on https://localhost:3000 (this is configured in `playwright.config.ts`) - this
-is what will be tested. The tests under `playwright/component` instead drive
-the component harness (`pnpm dev:component`) on https://localhost:3001, which
-Playwright starts as a second web server; it is always a Vite dev server, even
-when the app itself is served from Docker with `USE_DOCKER`.
+However the Playwright tests are run, an element-call instance must be running on
+https://localhost:3000 (this is configured in `playwright.config.ts`) - this is what will
+be tested.
 
 The local backend environment should be running for the test to work:
-`pnpm backend`
+`yarn backend`
 
-There are a few different ways to run the tests yourself. The simplest is to
-run:
+There are a few different ways to run the tests yourself. The simplest is to run:
 
 ```shell
-pnpm run test:playwright
+yarn run test:playwright
 ```
 
 This will run the Playwright tests once, non-interactively.
@@ -390,7 +216,7 @@ This will run the Playwright tests once, non-interactively.
 There is a more user-friendly way to run the tests in interactive mode:
 
 ```shell
-pnpm run test:playwright:open
+yarn run test:playwright:open
 ```
 
 The easiest way to develop new test is to use the codegen feature of Playwright:
@@ -399,13 +225,13 @@ The easiest way to develop new test is to use the codegen feature of Playwright:
 npx playwright codegen
 ```
 
-This will record your action and write the test code for you. Use the tool bar
-to test visibility, text content and clicking.
+This will record your action and write the test code for you. Use the tool bar to test visibility, text content,
+clicking.
 
 ##### Investigate a failed test from the CI
 
-In the failed action page, click on the failed job, then scroll down to the
-`upload-artifact` step. You will find a link to download the zip report, as per:
+In the failed action page, click on the failed job, then scroll down to the `upload-artifact` step.
+You will find a link to download the zip report, as per:
 
 ```
 Artifact playwright-report has been successfully uploaded! Final size is 1360358 bytes. Artifact ID is 2746265841
@@ -418,9 +244,8 @@ Unzip the report then use this command to open the report in your browser:
 npx playwright show-report ~/Downloads/playwright-report/
 ```
 
-Under the failed test there is a small icon looking like "3 columns" (next to
-the test name file name), click on it to see the live screenshots/console
-output.
+Under the failed test there is a small icon looking like "3 columns" (next to test name file name),
+click on it to see the live screenshots/console output.
 
 ### Test Coverage
 
@@ -432,7 +257,7 @@ To add a new translation key you can do these steps:
 
 1. Add the new key entry to the code where the new key is used:
    `t("some_new_key")`
-1. Run `pnpm i18n` to extract the new key and update the translation files. This
+1. Run `yarn i18n` to extract the new key and update the translation files. This
    will add a skeleton entry to the `locales/en/app.json` file:
 
    ```jsonc
@@ -460,19 +285,9 @@ Usage and other technical details about the project can be found here:
 
 [**Docs**](./docs/README.md)
 
-## GitHub Labels
-
-GitHub labels in this repository are maintained in the [`labels.yml`](.github/labels.yml) file and
-automatically synced to GitHub using the [`sync-labels` workflow](.github/workflows/sync-labels.yml).
-We do this so that we can reuse the labels between repositories.
-
-> [!WARNING]
-> Do not manually edit labels in the GitHub UI. Any manual changes will be overridden by the
-> workflow on its next invocation.
-
 ## 📝 Copyright & License
 
-Copyright 2021-2026 New Vector Ltd
+Copyright 2021-2025 New Vector Ltd
 
 This software is dual-licensed by New Vector Ltd (Element). It can be used
 either:

WIDGET_TEST.md

@@ -1,28 +0,0 @@
-# Testing Element-Call in widget mode
-
-When running `pnpm backend` the latest element-web develop will be deployed and served on `http://localhost:8081`.
-In a development environment, you might prefer to just use the `element-web` repo directly, but this setup is useful for CI/CD testing.
-
-## Setup
-
-The element-web configuration is modified to:
-
-- Enable to use the local widget instance (`element_call.url` https://localhost:3000).
-- Enable the labs features (`feature_group_calls`, `feature_element_call_video_rooms`).
-
-The default configuration used by docker-compose is in `test-container/config.json`. There is a fixture for playwright
-that uses
-
-## Running the element-web instance
-
-It is part of the existing backend setup. To start the backend, run:
-
-```sh
-pnpm backend
-```
-
-Then open `http://localhost:8081` in your browser.
-
-## Basic fixture
-
-A base fixture is provided in `/playwright/fixtures/widget-user.ts` that will register two users that shares a room.

babel.config.cjs

@@ -0,0 +1,20 @@
+module.exports = {
+  presets: [
+    [
+      "@babel/preset-env",
+      {
+        targets: {
+          node: "current",
+        },
+      },
+    ],
+    [
+      "@babel/preset-react",
+      {
+        runtime: "automatic",
+      },
+    ],
+    "@babel/preset-typescript",
+  ],
+  plugins: ["babel-plugin-transform-vite-meta-env"],
+};

backend/dev_homeserver-othersite.yaml

@@ -1,75 +0,0 @@
-server_name: "synapse.othersite.m.localhost"
-public_baseurl: https://synapse.othersite.m.localhost/
-
-pid_file: /data/homeserver.pid
-
-listeners:
-  - port: 18008
-    tls: false
-    type: http
-    x_forwarded: true
-    resources:
-      - names: [client, federation, openid]
-        compress: false
-
-database:
-  name: sqlite3
-  args:
-    database: /data/homeserver.db
-
-media_store_path: /data/media_store
-signing_key_path: "/data/SERVERNAME.signing.key"
-
-# Due to custom TLS certificate with domains
-# - m.localhost, localhost
-# - *.m.localhost
-# - *.othersite.m.localhost
-# we disable certificate verification to allow for federation
-# WARNING: DO NOT USE IN PRODUCTION!!!
-federation_verify_certificates: false
-ip_range_blacklist: []
-trusted_key_servers:
-  - server_name: "synapse.m.localhost"
-    accept_keys_insecurely: true
-
-experimental_features:
-  # MSC3266: Room summary API. Used for knocking over federation
-  msc3266_enabled: true
-  # MSC4222 needed for syncv2 state_after. This allow clients to
-  # correctly track the state of the room.
-  msc4222_enabled: true
-  # sticky events for MatrixRTC user state
-  msc4354_enabled: true
-  # MatrixRTC
-  msc4143_enabled: true
-
-# The maximum allowed duration by which sent events can be delayed, as
-# per MSC4140. Must be a positive value if set.  Defaults to no
-# duration (null), which disallows sending delayed events.
-max_event_delay_duration: 24h
-
-# Required for Element Call in Single Page Mode due to on-the-fly user registration
-enable_registration: true
-enable_registration_without_verification: true
-
-# Shared secret for admin user registration via API (for testing only!)
-registration_shared_secret: "test_shared_secret_for_local_dev_only"
-
-report_stats: false
-
-# Ratelimiting settings for client actions (registration, login, messaging).
-#
-# Each ratelimiting configuration is made of two parameters:
-#   - per_second: number of requests a client can send per second.
-#   - burst_count: number of requests a client can send before being throttled.
-
-rc_message:
-  # This needs to match at least the heart-beat frequency plus a bit of headroom
-  # Currently the heart-beat is every 5 seconds which translates into a rate of 0.2s
-  per_second: 0.5
-  burst_count: 30
-
-matrix_rtc:
-  transports:
-    - type: livekit
-      livekit_service_url: https://matrix-rtc.othersite.m.localhost/livekit/jwt

backend/dev_homeserver.yaml

@@ -1,5 +1,5 @@
-server_name: "synapse.m.localhost"
-public_baseurl: https://synapse.m.localhost/
+server_name: "synapse.localhost"
+public_baseurl: http://synapse.localhost:8008/
 
 pid_file: /data/homeserver.pid
 
@@ -19,18 +19,8 @@ database:
 
 media_store_path: /data/media_store
 signing_key_path: "/data/SERVERNAME.signing.key"
-
-# Due to custom TLS certificate with domains
-# - m.localhost, localhost
-# - *.m.localhost
-# - *.othersite.m.localhost
-# we disable certificate verification to allow for federation.
-# WARNING: DO NOT USE IN PRODUCTION!!!
-federation_verify_certificates: false
-ip_range_blacklist: []
 trusted_key_servers:
-  - server_name: "synapse.othersite.m.localhost"
-    accept_keys_insecurely: true
+  - server_name: "matrix.org"
 
 experimental_features:
   # MSC3266: Room summary API. Used for knocking over federation
@@ -38,25 +28,12 @@ experimental_features:
   # MSC4222 needed for syncv2 state_after. This allow clients to
   # correctly track the state of the room.
   msc4222_enabled: true
-  # sticky events for MatrixRTC user state
-  msc4354_enabled: true
-  # MatrixRTC
-  msc4143_enabled: true
 
 # The maximum allowed duration by which sent events can be delayed, as
 # per MSC4140. Must be a positive value if set.  Defaults to no
 # duration (null), which disallows sending delayed events.
 max_event_delay_duration: 24h
 
-# Required for Element Call in Single Page Mode due to on-the-fly user registration
-enable_registration: true
-enable_registration_without_verification: true
-
-# Shared secret for admin user registration via API (for testing only!)
-registration_shared_secret: "test_shared_secret_for_local_dev_only"
-
-report_stats: false
-
 # Ratelimiting settings for client actions (registration, login, messaging).
 #
 # Each ratelimiting configuration is made of two parameters:
@@ -69,7 +46,9 @@ rc_message:
   per_second: 0.5
   burst_count: 30
 
-matrix_rtc:
-  transports:
-    - type: livekit
-      livekit_service_url: https://matrix-rtc.m.localhost/livekit/jwt
+# Required for Element Call in Single Page Mode due to on-the-fly user registration
+enable_registration: true
+enable_registration_without_verification: true
+
+report_stats: false
+serve_server_wellknown: true

backend/dev_livekit-othersite.yaml

@@ -1,24 +0,0 @@
-port: 17880
-bind_addresses:
-  - "0.0.0.0"
-rtc:
-  tcp_port: 17881
-  port_range_start: 50300
-  port_range_end: 50400
-  use_external_ip: false
-turn:
-  enabled: false
-  domain: localhost
-  cert_file: ""
-  key_file: ""
-  tls_port: 5349
-  udp_port: 443
-  external_tls: true
-keys:
-  devkey: secret
-room:
-  auto_create: false
-webhook:
-  api_key: devkey
-  urls:
-    - https://matrix-rtc.othersite.m.localhost/livekit/jwt/sfu_webhook

backend/dev_livekit.yaml

@@ -6,6 +6,11 @@ rtc:
   port_range_start: 50100
   port_range_end: 50200
   use_external_ip: false
+#redis:
+#    address: redis:6379
+#    username: ""
+#    password: ""
+#    db: 0
 turn:
   enabled: false
   domain: localhost
@@ -16,9 +21,3 @@ turn:
   external_tls: true
 keys:
   devkey: secret
-room:
-  auto_create: false
-webhook:
-  api_key: devkey
-  urls:
-    - https://matrix-rtc.m.localhost/livekit/jwt/sfu_webhook

backend/dev_nginx.conf

@@ -1,277 +0,0 @@
-# Synapse reverse proxy
-# domain synapse.m.localhost
-server {
-    listen                  80;
-    listen                  [::]:80;
-    listen                  443 ssl;
-    listen                  8448 ssl;
-    listen                  [::]:443 ssl;
-    listen                  [::]:8448 ssl;
-    server_name             synapse.m.localhost;
-    ssl_certificate         /root/ssl/cert.pem;
-    ssl_certificate_key     /root/ssl/key.pem;
-
-    # Reverse proxy for Matrix Synapse Homeserver
-    # This is also required for development environment.
-    # Reason: the lk-jwt-service uses the federation API for the openid token
-    #         verification, which requires TLS
-    location ~ ^(/_matrix|/_synapse/client)  {
-        proxy_pass "http://homeserver:8008";
-        proxy_http_version 1.1;
-        proxy_set_header X-Forwarded-For $remote_addr;
-        proxy_set_header X-Forwarded-Proto $scheme;
-        proxy_set_header Host $host;
-    }
-    location ~ ^(/_matrix|/_synapse/admin)  {
-        proxy_pass "http://homeserver:8008";
-        proxy_http_version 1.1;
-        proxy_set_header X-Forwarded-For $remote_addr;
-        proxy_set_header X-Forwarded-Proto $scheme;
-        proxy_set_header Host $host;
-    }
-
-}
-
-# Synapse reverse proxy
-# domain synapse.othersite.m.localhost
-server {
-    listen                  80;
-    listen                  [::]:80;
-    listen                  443 ssl;
-    listen                  8448 ssl;
-    listen                  [::]:443 ssl;
-    listen                  [::]:8448 ssl;
-    server_name             synapse.othersite.m.localhost;
-    ssl_certificate         /root/ssl/cert.pem;
-    ssl_certificate_key     /root/ssl/key.pem;
-
-    # Reverse proxy for Matrix Synapse Homeserver
-    # This is also required for development environment.
-    # Reason: the lk-jwt-service uses the federation API for the openid token
-    #         verification, which requires TLS
-    location ~ ^(/_matrix|/_synapse/client)  {
-        proxy_pass "http://homeserver-1:18008";
-        proxy_http_version 1.1;
-        proxy_set_header X-Forwarded-For $remote_addr;
-        proxy_set_header X-Forwarded-Proto $scheme;
-        proxy_set_header Host $host;
-    }
-
-    location ~ ^(/_matrix|/_synapse/admin)  {
-        proxy_pass "http://homeserver-1:18008";
-        proxy_http_version 1.1;
-        proxy_set_header X-Forwarded-For $remote_addr;
-        proxy_set_header X-Forwarded-Proto $scheme;
-        proxy_set_header Host $host;
-    }
-
-}
-
-# MatrixRTC reverse proxy
-# domain matrix-rtc.m.localhost
-# - MatrixRTC Authorization Service
-# - LiveKit SFU websocket signaling connection
-upstream jwt-auth-services {
-    server auth-server:6080;
-    server host.docker.internal:6080;
-}
-
-server {
-    listen                  443 ssl;
-    listen                  [::]:443 ssl;
-    server_name             matrix-rtc.m.localhost;
-    ssl_certificate         /root/ssl/cert.pem;
-    ssl_certificate_key     /root/ssl/key.pem;
-
-    http2 on;
-
-
-    location ^~ /livekit/jwt/ {
-
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      # JWT Service running at port 6080
-      proxy_pass http://jwt-auth-services/;
-
-    }
-
-    location ^~ /livekit/sfu/ {
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      proxy_send_timeout 120;
-      proxy_read_timeout 120;
-      proxy_buffering off;
-
-      proxy_set_header Accept-Encoding gzip;
-      proxy_set_header Upgrade $http_upgrade;
-      proxy_set_header Connection "upgrade";
-
-      # LiveKit SFU websocket connection running at port 7880
-      proxy_pass http://livekit-sfu:7880/;
-    }
-
-}
-
-# MatrixRTC reverse proxy
-# domain matrix-rtc.othersite.m.localhost
-# - MatrixRTC Authorization Service
-# - LiveKit SFU websocket signaling connection
-server {
-    listen                  443 ssl;
-    listen                  [::]:443 ssl;
-    server_name             matrix-rtc.othersite.m.localhost;
-    ssl_certificate         /root/ssl/cert.pem;
-    ssl_certificate_key     /root/ssl/key.pem;
-
-    http2 on;
-
-
-    location ^~ /livekit/jwt/ {
-
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      # JWT Service running at port 16080
-      proxy_pass http://auth-service-1:16080/;
-
-    }
-
-    location ^~ /livekit/sfu/ {
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      proxy_send_timeout 120;
-      proxy_read_timeout 120;
-      proxy_buffering off;
-
-      proxy_set_header Accept-Encoding gzip;
-      proxy_set_header Upgrade $http_upgrade;
-      proxy_set_header Connection "upgrade";
-
-      # LiveKit SFU websocket connection running at port 17880
-      proxy_pass http://livekit-sfu-1:17880/;
-    }
-
-}
-
-# Convenience reverse proxy for the call.m.localhost domain to element call
-# running on the host either via
-# - pnpm dev --host or
-# - falling back to http (the element call docker container)
-server {
-    listen                  80;
-    listen                  [::]:80;
-    server_name             call.m.localhost;
-
-    return 301 https://$host$request_uri;
-}
-
-server {
-    listen                  443 ssl;
-    listen                  [::]:443 ssl;
-    server_name             call.m.localhost;
-    ssl_certificate         /root/ssl/cert.pem;
-    ssl_certificate_key     /root/ssl/key.pem;
-
-    # 1. Attempt HTTPS first
-    location ^~ / {
-
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      proxy_pass https://host.docker.internal:3000;
-      proxy_ssl_verify              off;
-
-      # 2. Redirect specific errors (e.g., 502 Bad Gateway  or 504 Timeout)
-      # to the named fallback location
-      error_page 502 503 504 = @http_fallback;
-
-    }
-
-    # 3. Fallback location using HTTP
-    location @http_fallback {
-
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      proxy_pass http://host.docker.internal:8080;
-
-    }
-
-}
-
-# Convenience reverse proxy app.m.localhost for element web
-server {
-    listen                  80;
-    listen                  [::]:80;
-    server_name             app.m.localhost;
-
-    return 301 https://$host$request_uri;
-}
-
-server {
-    listen                  443 ssl;
-    listen                  [::]:443 ssl;
-    server_name             app.m.localhost;
-    ssl_certificate         /root/ssl/cert.pem;
-    ssl_certificate_key     /root/ssl/key.pem;
-
-
-    location ^~ / {
-
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      proxy_pass http://element-web:8081;
-      proxy_ssl_verify              off;
-
-    }
-
-}
-
-# Convenience reverse proxy app.othersite.m.localhost for element web
-server {
-    listen                  80;
-    listen                  [::]:80;
-    server_name             app.othersite.m.localhost;
-
-    return 301 https://$host$request_uri;
-}
-
-server {
-    listen                  443 ssl;
-    listen                  [::]:443 ssl;
-    server_name             app.othersite.m.localhost;
-    ssl_certificate         /root/ssl/cert.pem;
-    ssl_certificate_key     /root/ssl/key.pem;
-
-
-    location ^~ / {
-
-      proxy_set_header Host $host;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-
-      proxy_pass http://element-web-1:18081;
-      proxy_ssl_verify              off;
-
-    }
-
-}

backend/dev_tls_local-ca.crt

@@ -1,19 +0,0 @@
------BEGIN CERTIFICATE-----
-MIIDGjCCAgKgAwIBAgIUOlA2wgQUGZkKqNDvvifFWEsJfvYwDQYJKoZIhvcNAQEL
-BQAwHjEcMBoGA1UEAwwTRWxlbWVudCBDYWxsIERldiBDQTAeFw0yNjA1MTgwOTM0
-MzFaFw0yODA3MjYwOTM0MzFaMB4xHDAaBgNVBAMME0VsZW1lbnQgQ2FsbCBEZXYg
-Q0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCcImv3pStfIUo7PbOO
-XRVUXuDlApBOrg2dCnvZQ1Jfaf4MftGHj/pURkF4eoBuyH4k4+NLzWD0VcU1cM74
-RnxowJt4AceCGe5RK/rqal5fapXc2vYMM8P6xaQR86gkxohpufsLgTnSweh74yqN
-B5WHUnCX00/X0bh1ho2BMUvGM9+dI4MdgKdaQDgWK4zg9hwp2Z6Yq7SkJ/D8+sGW
-WGpn3osDakL8HTBqop+YVJgF40db50yFurfcfQ0gjVtT4JW8ejO9j8PS/S2oQ/s5
-mA1B470XhLtT5qTjGm2bp3WpYkTi5widps8PDzBp5eNr0HrvJqcw7BGpbvBlLa+3
-7dhLAgMBAAGjUDBOMB0GA1UdDgQWBBRDfyRM4yKUqW6vu/2KUSXGb8vswDAfBgNV
-HSMEGDAWgBRDfyRM4yKUqW6vu/2KUSXGb8vswDAMBgNVHRMEBTADAQH/MA0GCSqG
-SIb3DQEBCwUAA4IBAQBoAhD4W4Yi/VJ2pTKrzhstn1UF1rgQnRddnn97v5BaEV/X
-uuBXbSO+/ewjQUupRjePZFp9FFe9co1OiduKcDExlvPU1eIqkWAwDWjMDpI+Lw5q
-KI5yHzplmMrT/7jn9Tepl9atrIcfDeFkP1dGtdRPyU6ARJEEWJSKeH9ftmImAsbM
-ykXAqSyRl8+bPx1ISG4cNihOxFd38VPDHIW53umaRBgRcN4GcvloKBGrVtRFNM//
-H+md8HmNQMP+e7FamETxs28DxjsdpygxjiFNY/T2eD67dH50ZxC3qCxEG6TJsoAg
-TYJafnqEcGDfiWQyNZRBypuaRsRmmTR27hCPVgi8
------END CERTIFICATE-----

backend/dev_tls_local-ca.key

@@ -1,28 +0,0 @@
------BEGIN PRIVATE KEY-----
-MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQCcImv3pStfIUo7
-PbOOXRVUXuDlApBOrg2dCnvZQ1Jfaf4MftGHj/pURkF4eoBuyH4k4+NLzWD0VcU1
-cM74RnxowJt4AceCGe5RK/rqal5fapXc2vYMM8P6xaQR86gkxohpufsLgTnSweh7
-4yqNB5WHUnCX00/X0bh1ho2BMUvGM9+dI4MdgKdaQDgWK4zg9hwp2Z6Yq7SkJ/D8
-+sGWWGpn3osDakL8HTBqop+YVJgF40db50yFurfcfQ0gjVtT4JW8ejO9j8PS/S2o
-Q/s5mA1B470XhLtT5qTjGm2bp3WpYkTi5widps8PDzBp5eNr0HrvJqcw7BGpbvBl
-La+37dhLAgMBAAECggEAEsS4gc5jBk50I+bo3KYn2DqHgj/qpOqbTFNkS9uh3UJa
-fZoJCeiuyM6hNCBVq/uB3mFeg1Au5XAiAqiK2KFwdw8gIS7lkqgXU76brO4YZhPj
-6+aOSS03079KV7YYckNDRqJKoTlpgAI7Nhk6ljVhLiEk07tdD65wJACGpg8M8sg9
-dyAz+ANs9gs65iF5LYjH61O/AFlLqCRQh5/z0mjGX6G9uN27nxeUY4+n4QMAcd9D
-Gcygxjt+4nlQayNAlKMwVfps9bWNtI3Ye9knY4WGkrv5cJbW3bgjV6qrvQsbukbq
-xEYzcIlUiWGO9Tv7MN6rk5uQOyoKT/KUnfRmdVd3YQKBgQDMhWm6Q+WuI7Pyn57R
-tmY4rs+fSqTmv6xAOcozKJxffGaEwSUuNA15NvR/7iedcNqmH3XT9j90ZNVHe090
-ocm1HDUvzC9G5GRrdO6JTTksRaIMZEhosWxqH3DIuBJPLGbF/4obGE7//PJtmDEp
-QVL9Aa0WrcwAWhRzUdvCE+taMwKBgQDDbyZIvtlEr1w2V0bjXO536rRksBapc2ZJ
-XRKtrXivuVtiZYNDB0I7CCJ52cka61n3kyZz2mhQmLq4cAZXyKYWE2i643O+kc3S
-lpZEFSfDZ+3YlhxMxG9oEcgUSwVdbPlAhd/UR8V6n8o2Fm+gug9h6E2zY4fgHLJF
-8hOWoD4hiQKBgA7YXD1F8mT6eHRS+78zIyZYIf/o9iE9pm4fA7tE5lzT9ckLD/zT
-kGrM/2BN1BhMecJ3JCFXjXGQZB7FJ5ZKrA52VrH6ezAFIfjeyvWyYkUBZOrLWKoo
-vrrRP2mCWuneSjNzAf5HfGx+WsZztpXNBQ4SUhMEWHtqDnP0bCQhOAMbAoGAPfLv
-qcOFT3ZevoLv34ZHuQ9W20vOAyynUb4E+7SvOtSAmTIgZ5DXd6recs2MJ9JOlGG6
-oKKsyk9/cJNiD1V1AC5q1kLfH5tMKOK/AxnJnvFEvZDnq5Xg0pZAW95j9vdiEwfc
-qYeOm44nJPn7rHEOCzT93E1CdtHh2LYha2+kAjECgYEAh4qODleBi+2fnf2eq494
-/tAot3szu2+gjyCN00vGjtzoAuDKTYgo0cbU1ILk0Pgpp1NcIvdHz/wQnG9RLX7e
-Dfy1Q+UkyBK67SJUPvcYqBEaZ6ddyijJDunqh+U3nIBGP+IntKIKMIKiLF6wzTKz
-NRpK1HNmllp+O692ZtxoNDU=
------END PRIVATE KEY-----

backend/dev_tls_m.localhost.crt

@@ -1,21 +0,0 @@
------BEGIN CERTIFICATE-----
-MIIDijCCAnKgAwIBAgIUWkx2ad/F7QIj1JDaYfbLhiRV+EswDQYJKoZIhvcNAQEL
-BQAwHjEcMBoGA1UEAwwTRWxlbWVudCBDYWxsIERldiBDQTAeFw0yNjA1MTgwOTM0
-MzFaFw0yODA3MjYwOTM0MzFaMBgxFjAUBgNVBAMMDSoubS5sb2NhbGhvc3QwggEi
-MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC0hora/UCYMtrLJc6BOjonPUPi
-bYpbNiZYnvnqI4doKbV0LBT2TfokT7tpgdPCtHKV0RknsVSL8vhlXpkRqIiWPml8
-sZaa0+5NDGCQxexS2WVBlsoNCmAaqi/HNSFop6xaxGpQ3bu0iV3oIkUihveXAl6H
-C0VYyGifQ8D5onzepW2ayhemu47YRNSo8wETY5vIi0i/iajTTaw6JvwS+8Kv5/QV
-5prdvcFlG/oBs12p0+KoRyxskyzcdBdyIarvfY+9nDZwym5GfN32xO/iqtDuDQzw
-Q09h2OsfHJCw70IpHcgXLlEQF2DsFbmbVpWSU6HcMm6B7Yw1YeE64W4PRJp3AgMB
-AAGjgcUwgcIwHwYDVR0jBBgwFoAUQ38kTOMilKlur7v9ilElxm/L7MAwCQYDVR0T
-BAIwADALBgNVHQ8EBAMCBaAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwUwYDVR0RBEww
-SoIJbG9jYWxob3N0ggttLmxvY2FsaG9zdIINKi5tLmxvY2FsaG9zdIIXKi5vdGhl
-cnNpdGUubS5sb2NhbGhvc3SCCCoubmlwLmlvMB0GA1UdDgQWBBSd0sKIKmZzTnxT
-gNHHjsJNnFcYaTANBgkqhkiG9w0BAQsFAAOCAQEAeffRTrD9o9PVRIoul5r2chwP
-WF7JtvPdC5xWy9rlCfmIKRNzNRnpVw/mDF/jdhlWcENt3psN8Vb1NM3SECKve9KL
-8bDD2rJEoLBHIFQPS+XpEPqVGLHQcfBtGgs2XdILKvgXJyBHY/pgNZkQmXxYDVoc
-bH9PjJJ4V3t6+tiVWZ792739EU/pHaSz7tab+ycTiggs7mo18E5jpYILhWsDqIVs
-Kz3uczK2OR8537Ix64Z9kmKiklVAqE53odV7Qx2B+7DoOD/7KBN7SMy1KvR1ae6I
-p1ivtDKpBZWbb1ccFxp2cQ30qRHLJrt2YRwz268gx/A6rGXuW6UQPYf4ISNR4Q==
------END CERTIFICATE-----

backend/dev_tls_m.localhost.key

@@ -1,28 +0,0 @@
------BEGIN PRIVATE KEY-----
-MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQC0hora/UCYMtrL
-Jc6BOjonPUPibYpbNiZYnvnqI4doKbV0LBT2TfokT7tpgdPCtHKV0RknsVSL8vhl
-XpkRqIiWPml8sZaa0+5NDGCQxexS2WVBlsoNCmAaqi/HNSFop6xaxGpQ3bu0iV3o
-IkUihveXAl6HC0VYyGifQ8D5onzepW2ayhemu47YRNSo8wETY5vIi0i/iajTTaw6
-JvwS+8Kv5/QV5prdvcFlG/oBs12p0+KoRyxskyzcdBdyIarvfY+9nDZwym5GfN32
-xO/iqtDuDQzwQ09h2OsfHJCw70IpHcgXLlEQF2DsFbmbVpWSU6HcMm6B7Yw1YeE6
-4W4PRJp3AgMBAAECggEAIgdIbk4VmnrfjjKCsg5JPvNH9AsE7PuQj9zrq+xljkdq
-aksS6ni5YZXb9F/iDE4aWU4waTB+iODUXLtPrCnyESwTk0sgYe/39/MQ0slUKivL
-b+keDgY6JlyVI/5KXWFZ1kQ27CZXxwiruGGZWZBKZF8wdVE1Ea65Neg+HHA6DHee
-Jck002gtgO/J1MMbB1MzdtGcsejYLrA+mO6YddQhA65xdQMljTEfyUwgTVv0pWde
-biyKegGK77vlsOyoCkMpVYORG5NMV1Kxs+htA79yuIW71tWHqVbcRMyoM+BaHzPh
-7uprs+8vYDFrO39LseczA8gURWwUsCgQ0yQ6Ix5W7QKBgQDnSK4AzjPpDEArdHuV
-VGKyzrfPtzH0VV/yTH9hvByNG6i/x8sE/r2KPi5nRMi4PAjjqmxyO1G5qwDOfzvK
-sBvwFrTRpmbnqGITVKPPivdoI9+RveN+FxhOXVA8NylAOv/dtSoakYwg3e507UsC
-RuFW3Re0Oc+0XFq4C8rQyLkIOwKBgQDH0T9gww+XbwIGCtiNpnEziU9FXBKSVwXf
-dCxYcTLPATq3BqHmP4OUA0v+sa3wPcnBkXF7q6eoB9+S6ZYQA/b2BXGU5/j9xYd4
-29cF4DlPkhTwF9S8b+h1zhlGIn96Lw/vZuj7Bc3wuwxvB17d8dpyo8bZynIe7BvF
-KSPJz+2O9QKBgFFyd8xS0VcFeGeVKpwozmUXhQWCBvZ7RkGGjOk3HHrYvbFjw2vr
-5YWUZjT5tRGkGqFJ98y2dQ5EWRFfHwg+wmfnJyAZUG3OD1OtX86Lqpqi321siHtz
-2JxoIgRCjKVQ4aAK11vp24YLgZjto5eWrG4xh9Jw9WMXjt73UCH8PaTXAoGBAIff
-TY1qlmuO3H1nWqHXkBpPQEwVs7s22ZN817q8HqSMXXSfWe/LOJmpND/YakJ2gX7S
-e6xwqOylje3EUHpLd98LDJUIuFM3wkr4klo4gkANQZeRXONV5WhV4PHD+5MF9XwB
-KmOnKsaLKoVFKckZ8EUMAOePtdI5ExkaRG+yqAMRAoGAJyUFK+V9ST1N/6wYgqor
-vywMSRE2cF2WvVIxdMvWffmpoj40bG6lAlaSWm29E2T8SVvAKsRid0wDgCQ4QTEn
-ft7yUDjqVALCJVCrOFHDY0BPStkm6njMWagr/0lGr9zUWqbBOKJhNfDJlykv8gaF
-8kWTgabrMCKmpTi7fBWbzZA=
------END PRIVATE KEY-----

backend/dev_tls_setup

@@ -1,40 +0,0 @@
-#!/bin/bash
-
-# Step 1: Create a Root CA key and cert
-openssl genrsa -out dev_tls_local-ca.key 2048
-openssl req -x509 -new -nodes \
-  -days 800 \
-  -subj "/CN=Element Call Dev CA" \
-  -key dev_tls_local-ca.key \
-  -out dev_tls_local-ca.crt \
-  -sha256 -addext "basicConstraints=CA:TRUE"
-
-# Step 2: Create a private key and CSR for *.m.localhost
-openssl req -new -nodes -newkey rsa:2048 \
-  -keyout dev_tls_m.localhost.key \
-  -out dev_tls_m.localhost.csr \
-  -subj "/CN=*.m.localhost"
-
-# Step 3: Sign the CSR with your CA
-openssl x509 \
-  -req -in dev_tls_m.localhost.csr \
-  -CA dev_tls_local-ca.crt -CAkey dev_tls_local-ca.key \
-  -CAcreateserial \
-  -out dev_tls_m.localhost.crt \
-  -days 800 \
-  -sha256 \
-  -extfile <( cat <<EOF
-authorityKeyIdentifier=keyid,issuer
-basicConstraints=CA:FALSE
-keyUsage = digitalSignature, keyEncipherment
-extendedKeyUsage = serverAuth
-subjectAltName = @alt_names
-
-[alt_names]
-DNS.1 = localhost
-DNS.2 = m.localhost
-DNS.3 = *.m.localhost
-DNS.4 = *.othersite.m.localhost
-DNS.5 = *.nip.io
-EOF
-)

backend/ew.test.config.json

@@ -1,53 +0,0 @@
-{
-  "default_server_config": {
-    "m.homeserver": {
-      "base_url": "https://synapse.m.localhost",
-      "server_name": "synapse.m.localhost"
-    }
-  },
-  "disable_custom_urls": false,
-  "disable_guests": false,
-  "disable_login_language_selector": false,
-  "disable_3pid_login": false,
-  "force_verification": false,
-  "brand": "Element",
-  "integrations_ui_url": "https://scalar.vector.im/",
-  "integrations_rest_url": "https://scalar.vector.im/api",
-  "integrations_widgets_urls": [
-    "https://scalar.vector.im/_matrix/integrations/v1",
-    "https://scalar.vector.im/api",
-    "https://scalar-staging.vector.im/_matrix/integrations/v1",
-    "https://scalar-staging.vector.im/api",
-    "https://scalar-staging.riot.im/scalar/api"
-  ],
-  "default_widget_container_height": 280,
-  "default_country_code": "GB",
-  "show_labs_settings": false,
-  "features": {
-    "feature_element_call_video_rooms": true,
-    "feature_video_rooms": true,
-    "feature_group_calls": true,
-    "feature_release_announcement": false
-  },
-  "default_federate": true,
-  "default_theme": "light",
-  "room_directory": {
-    "servers": ["matrix.org"]
-  },
-  "enable_presence_by_hs_url": {
-    "https://matrix.org": false,
-    "https://matrix-client.matrix.org": false
-  },
-  "setting_defaults": {
-    "breadcrumbs": true,
-    "feature_group_calls": true
-  },
-  "jitsi": {
-    "preferred_domain": "meet.element.io"
-  },
-  "element_call": {
-    "participant_limit": 8,
-    "brand": "Element Call"
-  },
-  "map_style_url": "https://api.maptiler.com/maps/streets/style.json?key=fU3vlMsMn4Jb6dnEIFsx"
-}

backend/ew.test.othersite.config.json

@@ -1,53 +0,0 @@
-{
-  "default_server_config": {
-    "m.homeserver": {
-      "base_url": "https://synapse.othersite.m.localhost",
-      "server_name": "synapse.othersite.m.localhost"
-    }
-  },
-  "disable_custom_urls": false,
-  "disable_guests": false,
-  "disable_login_language_selector": false,
-  "disable_3pid_login": false,
-  "force_verification": false,
-  "brand": "Element",
-  "integrations_ui_url": "https://scalar.vector.im/",
-  "integrations_rest_url": "https://scalar.vector.im/api",
-  "integrations_widgets_urls": [
-    "https://scalar.vector.im/_matrix/integrations/v1",
-    "https://scalar.vector.im/api",
-    "https://scalar-staging.vector.im/_matrix/integrations/v1",
-    "https://scalar-staging.vector.im/api",
-    "https://scalar-staging.riot.im/scalar/api"
-  ],
-  "default_widget_container_height": 280,
-  "default_country_code": "GB",
-  "show_labs_settings": false,
-  "features": {
-    "feature_element_call_video_rooms": true,
-    "feature_video_rooms": true,
-    "feature_group_calls": true,
-    "feature_release_announcement": false
-  },
-  "default_federate": true,
-  "default_theme": "light",
-  "room_directory": {
-    "servers": ["matrix.org"]
-  },
-  "enable_presence_by_hs_url": {
-    "https://matrix.org": false,
-    "https://matrix-client.matrix.org": false
-  },
-  "setting_defaults": {
-    "breadcrumbs": true,
-    "feature_group_calls": true
-  },
-  "jitsi": {
-    "preferred_domain": "meet.element.io"
-  },
-  "element_call": {
-    "participant_limit": 8,
-    "brand": "Element Call"
-  },
-  "map_style_url": "https://api.maptiler.com/maps/streets/style.json?key=fU3vlMsMn4Jb6dnEIFsx"
-}

backend/playwright_homeserver-othersite.yaml

@@ -1,92 +0,0 @@
-server_name: "synapse.othersite.m.localhost"
-public_baseurl: https://synapse.othersite.m.localhost/
-
-pid_file: /data/homeserver.pid
-
-listeners:
-  - port: 18008
-    tls: false
-    type: http
-    x_forwarded: true
-    resources:
-      - names: [client, federation, openid]
-        compress: false
-
-database:
-  name: sqlite3
-  args:
-    database: /data/homeserver.db
-
-media_store_path: /data/media_store
-signing_key_path: "/data/SERVERNAME.signing.key"
-
-# Due to custom TLS certificate with domains
-# - m.localhost, localhost
-# - *.m.localhost
-# - *.othersite.m.localhost
-# we disable certificate verification to allow for federation.
-# WARNING: DO NOT USE IN PRODUCTION!!!
-federation_verify_certificates: false
-ip_range_blacklist: []
-trusted_key_servers:
-  - server_name: "synapse.m.localhost"
-    accept_keys_insecurely: true
-
-experimental_features:
-  # MSC3266: Room summary API. Used for knocking over federation
-  msc3266_enabled: true
-  # MSC4222 needed for syncv2 state_after. This allow clients to
-  # correctly track the state of the room.
-  msc4222_enabled: true
-  # sticky events for MatrixRTC user state
-  msc4354_enabled: true
-  # MatrixRTC
-  msc4143_enabled: true
-
-# The maximum allowed duration by which sent events can be delayed, as
-# per MSC4140. Must be a positive value if set.  Defaults to no
-# duration (null), which disallows sending delayed events.
-max_event_delay_duration: 24h
-
-# Required for Element Call in Single Page Mode due to on-the-fly user registration
-enable_registration: true
-enable_registration_without_verification: true
-
-# Shared secret for admin user registration via API (for testing only!)
-registration_shared_secret: "test_shared_secret_for_local_dev_only"
-
-report_stats: false
-
-# Ratelimiting settings for client actions (registration, login, messaging).
-#
-# Each ratelimiting configuration is made of two parameters:
-#   - per_second: number of requests a client can send per second.
-#   - burst_count: number of requests a client can send before being throttled.
-
-rc_message:
-  per_second: 10000
-  burst_count: 10000
-
-rc_delayed_event_mgmt:
-  per_second: 10000
-  burst_count: 10000
-
-rc_login:
-  address:
-    per_second: 10000
-    burst_count: 10000
-  account:
-    per_second: 10000
-    burst_count: 10000
-  failed_attempts:
-    per_second: 10000
-    burst_count: 10000
-
-rc_registration:
-  per_second: 10000
-  burst_count: 10000
-
-matrix_rtc:
-  transports:
-    - type: livekit
-      livekit_service_url: https://matrix-rtc.othersite.m.localhost/livekit/jwt

backend/playwright_homeserver.yaml

@@ -1,5 +1,5 @@
-server_name: "synapse.m.localhost"
-public_baseurl: https://synapse.m.localhost/
+server_name: "synapse.localhost"
+public_baseurl: http://synapse.localhost:8008/
 
 pid_file: /data/homeserver.pid
 
@@ -19,18 +19,8 @@ database:
 
 media_store_path: /data/media_store
 signing_key_path: "/data/SERVERNAME.signing.key"
-
-# Due to custom TLS certificate with domains
-# - m.localhost, localhost
-# - *.m.localhost
-# - *.othersite.m.localhost
-# we disable certificate verification to allow for federation.
-# WARNING: DO NOT USE IN PRODUCTION!!!
-federation_verify_certificates: false
-ip_range_blacklist: []
 trusted_key_servers:
-  - server_name: "synapse.othersite.m.localhost"
-    accept_keys_insecurely: true
+  - server_name: "matrix.org"
 
 experimental_features:
   # MSC3266: Room summary API. Used for knocking over federation
@@ -38,25 +28,12 @@ experimental_features:
   # MSC4222 needed for syncv2 state_after. This allow clients to
   # correctly track the state of the room.
   msc4222_enabled: true
-  # sticky events for MatrixRTC user state
-  msc4354_enabled: true
-  # MatrixRTC
-  msc4143_enabled: true
 
 # The maximum allowed duration by which sent events can be delayed, as
 # per MSC4140. Must be a positive value if set.  Defaults to no
 # duration (null), which disallows sending delayed events.
 max_event_delay_duration: 24h
 
-# Required for Element Call in Single Page Mode due to on-the-fly user registration
-enable_registration: true
-enable_registration_without_verification: true
-
-# Shared secret for admin user registration via API (for testing only!)
-registration_shared_secret: "test_shared_secret_for_local_dev_only"
-
-report_stats: false
-
 # Ratelimiting settings for client actions (registration, login, messaging).
 #
 # Each ratelimiting configuration is made of two parameters:
@@ -67,10 +44,6 @@ rc_message:
   per_second: 10000
   burst_count: 10000
 
-rc_delayed_event_mgmt:
-  per_second: 10000
-  burst_count: 10000
-
 rc_login:
   address:
     per_second: 10000
@@ -86,7 +59,9 @@ rc_registration:
   per_second: 10000
   burst_count: 10000
 
-matrix_rtc:
-  transports:
-    - type: livekit
-      livekit_service_url: https://matrix-rtc.m.localhost/livekit/jwt
+# Required for Element Call in Single Page Mode due to on-the-fly user registration
+enable_registration: true
+enable_registration_without_verification: true
+
+report_stats: false
+serve_server_wellknown: true

backend/redis.conf

@@ -0,0 +1,5 @@
+bind 0.0.0.0
+protected-mode yes
+port 6379
+timeout 0
+tcp-keepalive 300

backend/tls_localhost_cert.pem

@@ -0,0 +1,22 @@
+-----BEGIN CERTIFICATE-----
+MIIDtzCCAp+gAwIBAgIUCmJjl3HAeLmrPwRg+/OzikW6peQwDQYJKoZIhvcNAQEL
+BQAwazELMAkGA1UEBhMCR0IxDzANBgNVBAgMBkxvbmRvbjEPMA0GA1UEBwwGTG9u
+ZG9uMQ4wDAYDVQQKDAVBbHJvczEWMBQGA1UECwwNSVQgRGVwYXJ0bWVudDESMBAG
+A1UEAwwJbG9jYWxob3N0MB4XDTI0MTEwNDIxNDcwMFoXDTM0MTEwMjIxNDcwMFow
+azELMAkGA1UEBhMCR0IxDzANBgNVBAgMBkxvbmRvbjEPMA0GA1UEBwwGTG9uZG9u
+MQ4wDAYDVQQKDAVBbHJvczEWMBQGA1UECwwNSVQgRGVwYXJ0bWVudDESMBAGA1UE
+AwwJbG9jYWxob3N0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs368
+ExLSudP8luNoY5UfaPqBSVJUPYBi+JGyd36tyN75p5OI7xSfHTttQxuD4KrExBFP
+C8mAhE1eoZPBVBOZJ4FYWBJfMaQnCjeqU+laP36td65kSJYbUYlKYH1WpxEpCdgx
+wWOKkP/kPX5YXbYqODx9aBJXgoT3yAJW7AniIoL+eLFnS9Xo86TPqCDBTJU9ocwK
+gPIDLhDv60724rhZT1kbGp7ECqRovndoDTQjuws2D3yNMfQ+4rrQGPXHGmP5PcaR
+0R7uueB+6APyC7MJbuhbxxg/+DFHrRi3lJsgwxuh2hi/+vWw8zgKlgYIwHFA9X0l
+cX0UlQdENMH3bgcGIwIDAQABo1MwUTAdBgNVHQ4EFgQUUFGxw7zoiHXGwRqtagjZ
+RPYc85cwHwYDVR0jBBgwFoAUUFGxw7zoiHXGwRqtagjZRPYc85cwDwYDVR0TAQH/
+BAUwAwEB/zANBgkqhkiG9w0BAQsFAAOCAQEALokb1z2lu3qW141b2wm14ilZQKCZ
+reNNuUR95Uom96FXPH4QVEH+mYTXXJ5UrfNhQYKQFpdE+5S4HL/UqEOxtWvbAHpK
+nsLQ62J8m+0+uwiJGqeQpWr03KJgXDAVE9X3XwMlp/+buxSLhc+GIHWuXW56itV2
+jiZJYjhO5SnhhgTWNoVZk93qXuuWEN0yacw7c3Fr1IvFYYYWufbXTk70dbZihPDK
+VD141o8tpp6FerSKHNYDqkVFDyTz3DVOhQQJ59zfMre7bFr+PpTTl4vIuGzXEY+E
+HPjUSlOzwkCoh5fu7Fs3qG55rJt8akhTEoKpiBTaLucgAjVWNHeci1+Yxg==
+-----END CERTIFICATE-----

backend/tls_localhost_key.pem

@@ -0,0 +1,28 @@
+-----BEGIN PRIVATE KEY-----
+MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQCzfrwTEtK50/yW
+42hjlR9o+oFJUlQ9gGL4kbJ3fq3I3vmnk4jvFJ8dO21DG4PgqsTEEU8LyYCETV6h
+k8FUE5kngVhYEl8xpCcKN6pT6Vo/fq13rmRIlhtRiUpgfVanESkJ2DHBY4qQ/+Q9
+flhdtio4PH1oEleChPfIAlbsCeIigv54sWdL1ejzpM+oIMFMlT2hzAqA8gMuEO/r
+TvbiuFlPWRsansQKpGi+d2gNNCO7CzYPfI0x9D7iutAY9ccaY/k9xpHRHu654H7o
+A/ILswlu6FvHGD/4MUetGLeUmyDDG6HaGL/69bDzOAqWBgjAcUD1fSVxfRSVB0Q0
+wfduBwYjAgMBAAECggEACTqdSExxzJ+LX5ARFaWyOBSWly2GKqSyR14+aInOklhx
+9QgkmfOxJrCf3TvJ8RWhXloW0Aqr8qGDxG0Ixgjn7rG7gskXCey1xn8MNppLS0kj
+ztaG+NB3AR89ABm8XdoHsSY45geh3/Ni9I0i1VardGQafUJhgNLTZqjwIodzkBtJ
+S/bi4uFk1lGNfuvWQvWqzGXUvd1l1YupV6iA4GfhXlUvrSBZwftLBD6xEvQaSqsA
+pHvBxTfMXG4RMAkNPDIElkuQ8++CGi1gIRkJfmrv4OgbbitteMnxqqqGYV0zSNCg
+R/5FG6umIV7lDLBHZCSCk7wmfmq2UUvzhHThHy4yMQKBgQDu4TwFJCIcVIj7Wj4r
+DUBFvz6Lgbltqb+YAMUBtpiDcAQxDJWmedh6dK04ts5CFAFRlRjjuz2uFn7qlVBm
+uye9R7tL+tOv5viqDXU78a4snFywoXub6yzpbxrW8B4W1pdIUvQmhwCcDwvO1V24
+7Vj2vxcM5I9dsk1aCQSi3VY5yQKBgQDAW/VoTRwhU6OUc6sji5Z5dnkMjkP6NZK9
+CSrTWLAMGaLPY+g6fFS7JMNSvfWm/okypD6rcN7p0cxMK3mfFKmMiyPRde0wdrci
+sGFjGxM/2d2D7KTMC9iMYwA0K17UIna+UiYPfhR/muIg/dCyjlkKDFs9Z4jk//r1
+91bmznt2iwKBgFdiYXhn/Wprqih4nKFXGZnqGdEixVhObl4GegrkZuo+AeqHdf8O
+N5ikMfG7PbyCYPEdH5u/FRMn+4mI0X6jHChroyJqQSHp1jEu9yHUiSicknOyvusM
+nsNN932FHRyxp2m3nsSxQhHUlzc0ajKJ8K9iu+XlfmSCIzW6cs25Nh+xAoGBAJro
+M0wIdPPdsCj3sUVRvx8XqknTM6kGhaIYBNXoYPWNm5BaC4U15OJEq8sxUOdnqcMP
+g6x6m/k+S8C3bh0O/a9Bydl/l0BlCfw0gGjYP/s2ju4Tn272xy/e9iYNGzPIgUmp
+TB9D0GwmpZ4d6HgyrD+sTbm4bATGpCp6QhBjDggbAoGBAJVMMtZ4pF8D6mLMRZGR
+pQjNPy+MH13XYmDRc/BSF8KJ4yKk3tohr9LSXzxR0SEB43NoL1bHkucZrNjGyL8x
+jktnwkoIs96kO2mPrl1TqWkXs5RjGkkSTbAJovIcvkRU31SWap/WzN2kHpmRVcQc
+KEFKXT5fUYZCLLWxhgZFlGPp
+-----END PRIVATE KEY-----

backend/tls_localhost_nginx.conf

@@ -0,0 +1,40 @@
+server {
+    listen                  80;
+    listen                  [::]:80;
+    listen                  443 ssl;
+    listen                  8448 ssl;
+    listen                  [::]:443 ssl;
+    listen                  [::]:8448 ssl;
+    server_name             synapse.localhost;
+    ssl_certificate         /root/ssl/cert.pem;
+    ssl_certificate_key     /root/ssl/key.pem;
+
+    # well-known config adding rtc_foci backend
+    # Note well-known is currently not effective due to:
+    # https://spec.matrix.org/v1.12/client-server-api/#well-known-uri the spec
+    # says it must be at https://$server_name/... (implied port 443) Hence, we
+    # currently rely for local development environment on deprecated config.json
+    # setting for livekit_service_url
+    location /.well-known/matrix/client {
+        return 200 '{"m.homeserver": {"base_url": "http://synapse.localhost:8008"}, "org.matrix.msc4143.rtc_foci": [{"type": "livekit", "livekit_service_url": "http://localhost:8080"}]}';
+        default_type application/json;
+        add_header Access-Control-Allow-Origin *;
+    }
+
+    # Reverse proxy for Matrix Synapse Homeserver
+    # This is also required for development environment.
+    # Reason: the lk-jwt-service uses the federation API for the openid token
+    #         verification, which requires TLS
+    location / {
+        proxy_pass "http://homeserver:8008";
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+        proxy_set_header Host $host;
+        proxy_set_header X-Forwarded-For $remote_addr;
+        proxy_set_header X-Forwarded-Proto $scheme;
+    }
+
+    error_page   500 502 503 504  /50x.html;
+
+}

codecov.yaml

@@ -13,6 +13,7 @@ coverage:
         informational: true
     patch:
       default:
-        # Enforce 80% coverage on all lines that a PR
+        # Encourage (but don't enforce) 80% coverage on all lines that a PR
         # touches
         target: 80%
+        informational: true

component/ElementCall.module.css

@@ -1,43 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-/* The container a host mounts us into. It fills whatever space the host gives
-it, and nothing we draw may leave it.
-
-That takes two separate things, which are easy to mistake for one. `isolation`
-gives us a stacking context, so nothing inside can be layered above the host's
-own interface. Containment makes us the containing block for `position: fixed`
-descendants, and clips what we paint to our own box: without it, the modal
-scrim and dialog — which are positioned `fixed` and centred, since in the app
-they are meant to cover the page — resolve against the viewport and appear in
-the middle of the host's window rather than in the middle of the call.
-
-The clipping cuts both ways: a menu near the edge of a small container is
-trimmed rather than overflowing into the host. That is the trade being a
-component rather than a page makes. */
-.root {
-  display: flex;
-  flex-direction: column;
-  inline-size: 100%;
-  block-size: 100%;
-  isolation: isolate;
-  contain: layout paint;
-  position: relative;
-  background-color: var(--cpd-color-bg-canvas-default);
-  color: var(--cpd-color-text-primary);
-  -webkit-font-smoothing: antialiased;
-  -moz-osx-font-smoothing: grayscale;
-  -webkit-tap-highlight-color: transparent;
-}
-
-/* Compound's overlay container, which holds tooltips and popovers, has to fill
-the container for the elements inside it to be positioned against it. The
-standalone page does the same for the container under `#root`. */
-.root > [data-overlay-container] {
-  position: relative;
-  block-size: 100%;
-}

component/build/scopeStylesToRoot.test.ts

@@ -1,112 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import { describe, expect, it } from "vitest";
-import postcss from "postcss";
-
-import { ROOT_SELECTOR, scopeStylesToRoot } from "./scopeStylesToRoot";
-
-const inRoot = `:where(${ROOT_SELECTOR}, ${ROOT_SELECTOR} *)`;
-const isRoot = `:where(${ROOT_SELECTOR})`;
-
-async function scope(css: string, file = "base.css"): Promise<string> {
-  const result = await postcss([scopeStylesToRoot()]).process(css, {
-    from: file,
-  });
-  return result.css;
-}
-
-describe("scopeStylesToRoot", () => {
-  it("makes the root stand in for the document", async () => {
-    expect(await scope("html { line-height: 1.15 }")).toBe(
-      `${isRoot} { line-height: 1.15 }`,
-    );
-    expect(await scope("body { margin: 0 }")).toBe(`${isRoot} { margin: 0 }`);
-    expect(await scope(":root { --a: 1 }")).toBe(`${isRoot} { --a: 1 }`);
-    expect(await scope("body.no-scroll-body { position: fixed }")).toBe(
-      `${isRoot}.no-scroll-body { position: fixed }`,
-    );
-    expect(await scope("body .x { color: red }")).toBe(
-      `${isRoot} .x { color: red }`,
-    );
-  });
-
-  it("collapses selectors that all became the root", async () => {
-    expect(await scope("html, body, input { font: inherit }")).toBe(
-      `${isRoot},input${inRoot} { font: inherit }`,
-    );
-  });
-
-  it("confines everything else to the root and what is inside it", async () => {
-    expect(await scope("h1 { margin: 0 }")).toBe(`h1${inRoot} { margin: 0 }`);
-    expect(await scope(".cpd-theme-dark { --a: 1 }")).toBe(
-      `.cpd-theme-dark${inRoot} { --a: 1 }`,
-    );
-    expect(await scope("* { box-sizing: border-box }")).toBe(
-      `*${inRoot} { box-sizing: border-box }`,
-    );
-    expect(await scope(".a > .b + .c { color: red }")).toBe(
-      `.a>.b+.c${inRoot} { color: red }`,
-    );
-  });
-
-  it("keeps pseudo-elements last", async () => {
-    expect(await scope("button::-moz-focus-inner { border: 0 }")).toBe(
-      `button${inRoot}::-moz-focus-inner { border: 0 }`,
-    );
-    expect(await scope(".a .b:hover::after { content: '' }")).toBe(
-      `.a .b:hover${inRoot}::after { content: '' }`,
-    );
-    expect(await scope("p:first-letter { color: red }")).toBe(
-      `p${inRoot}:first-letter { color: red }`,
-    );
-  });
-
-  it("leaves alone what already names the root", async () => {
-    const css = `${ROOT_SELECTOR}[data-platform="ios"] { --a: 1 }`;
-    expect(await scope(css)).toBe(css);
-  });
-
-  it("reaches into layers and media queries", async () => {
-    expect(
-      await scope(
-        "@layer normalize { h1 { margin: 0 } } @media (min-width: 1px) { p { margin: 0 } }",
-      ),
-    ).toBe(
-      `@layer normalize { h1${inRoot} { margin: 0 } } @media (min-width: 1px) { p${inRoot} { margin: 0 } }`,
-    );
-  });
-
-  it("does not touch keyframes or nested rules", async () => {
-    expect(
-      await scope("@keyframes spin { from { opacity: 0 } to { opacity: 1 } }"),
-    ).toBe("@keyframes spin { from { opacity: 0 } to { opacity: 1 } }");
-    expect(
-      await scope(
-        ".a { color: red; &:hover { color: blue } .b { color: green } }",
-      ),
-    ).toBe(
-      `.a${inRoot} { color: red; &:hover { color: blue } .b { color: green } }`,
-    );
-  });
-
-  it("only touches the bare selectors of a CSS module", async () => {
-    const file = "Settings.module.css";
-    expect(await scope("pre { font-size: 1px }", file)).toBe(
-      `pre${inRoot} { font-size: 1px }`,
-    );
-    expect(await scope(".modal pre { font-size: 1px }", file)).toBe(
-      `.modal pre${inRoot} { font-size: 1px }`,
-    );
-    expect(await scope(".box_abc12 { border: 0 }", file)).toBe(
-      ".box_abc12 { border: 0 }",
-    );
-    expect(await scope(".a .b_abc12:hover { border: 0 }", file)).toBe(
-      ".a .b_abc12:hover { border: 0 }",
-    );
-  });
-});

component/build/scopeStylesToRoot.ts

@@ -1,161 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import {
-  type AtRule,
-  type Container,
-  type Document,
-  type Plugin,
-  type Rule,
-} from "postcss";
-import selectorParser, {
-  type Node,
-  type Pseudo,
-  type Selector,
-} from "postcss-selector-parser";
-
-/**
- * How the stylesheets find Element Call's root element. The attribute is put
- * there by `useTheme`, on the container the host gives the component.
- */
-export const ROOT_SELECTOR = "[data-element-call-root]";
-
-// Both are `:where()`, which has no specificity of its own, so the rules keep
-// exactly the weight they had before being scoped and nothing in Element Call's
-// cascade changes — only where it applies.
-//
-// The root, or anything inside it. Appended to the element a rule is about,
-// rather than prepended to the whole selector, so that a rule about the root
-// itself (its theme class, say) still matches.
-const IN_ROOT = `:where(${ROOT_SELECTOR}, ${ROOT_SELECTOR} *)`;
-// The root itself, standing in for the document.
-const IS_ROOT = `:where(${ROOT_SELECTOR})`;
-
-/**
- * Confines a stylesheet to Element Call's root element, for the build of
- * Element Call as a component.
- *
- * As a page of its own, Element Call can style the document: normalize.css and
- * Compound speak of `html`, `body` and bare elements, and the design tokens are
- * declared on `:root`. As a component, all of that would land on the host's
- * document too. This rewrites every selector so that it matches only the root
- * or its descendants:
- *
- * - `html`, `body` and `:root` become the root element, which is what stands in
- *   for the document inside a host.
- * - Everything else keeps its selector and gains `:where([data-element-call-root],
- *   [data-element-call-root] *)` on the element it styles.
- * - Selectors that already name the root are left alone, as are keyframe
- *   selectors and rules nested inside another rule, which are relative to it.
- *
- * CSS modules are scoped by their class names already, so only their selectors
- * that would match by element alone — `pre` rather than `.pre` — are touched.
- *
- * The root's fonts and design tokens are still inherited by everything inside
- * it, the way they were from `body` and `:root`, and `@font-face` declarations
- * stay global, which they are by nature.
- */
-export function scopeStylesToRoot(): Plugin {
-  return {
-    postcssPlugin: "element-call-scope-styles-to-root",
-    Once(root) {
-      const isModule =
-        root.source?.input.file?.endsWith(".module.css") ?? false;
-      root.walkRules((rule) => {
-        if (isRelative(rule)) return;
-        rule.selector = (isModule ? scopeBare : scopeAll).processSync(
-          rule.selector,
-          { lossless: false },
-        );
-      });
-    },
-  };
-}
-
-/** Whether a rule's selectors are relative to something other than the document. */
-function isRelative(rule: Rule): boolean {
-  let parent: Container | Document | undefined = rule.parent;
-  while (parent !== undefined) {
-    if (parent.type === "rule") return true;
-    if (parent.type === "atrule") {
-      const { name } = parent as AtRule;
-      if (name.endsWith("keyframes") || name === "page") return true;
-    }
-    parent = parent.parent;
-  }
-  return false;
-}
-
-const processor = (isModule: boolean): ReturnType<typeof selectorParser> =>
-  selectorParser((selectors) => {
-    selectors.each((selector) => {
-      scopeSelector(selector, isModule);
-    });
-    // Mapping `html, body` onto the root leaves the same selector twice
-    const seen = new Set<string>();
-    selectors.each((selector) => {
-      const text = String(selector).trim();
-      if (seen.has(text)) selector.remove();
-      else seen.add(text);
-    });
-  });
-
-// Everything, for stylesheets that speak of the document; only what a class
-// does not already confine, for CSS modules
-const scopeAll = processor(false);
-const scopeBare = processor(true);
-
-function scopeSelector(selector: Selector, isModule: boolean): void {
-  if (String(selector).includes(ROOT_SELECTOR)) return;
-
-  const compounds = splitCompounds(selector);
-  if (compounds.length === 0) return;
-
-  // Something said of the document is said of the root instead
-  const document = compounds[0].find(isDocumentSelector);
-  if (document !== undefined) {
-    document.replaceWith(pseudo(IS_ROOT));
-    return;
-  }
-
-  const subject = compounds.at(-1)!;
-  if (isModule && subject.some((node) => node.type === "class")) return;
-
-  // Pseudo-elements have to come last in a compound selector
-  const pseudoElement = subject.find(isPseudoElement);
-  if (pseudoElement === undefined) selector.append(pseudo(IN_ROOT));
-  else selector.insertBefore(pseudoElement, pseudo(IN_ROOT));
-}
-
-/** The compound selectors making up a complex selector, in order. */
-function splitCompounds(selector: Selector): Node[][] {
-  const compounds: Node[][] = [[]];
-  for (const node of selector.nodes) {
-    if (node.type === "combinator") compounds.push([]);
-    else if (node.type !== "comment") compounds.at(-1)!.push(node);
-  }
-  return compounds.filter((compound) => compound.length > 0);
-}
-
-function isDocumentSelector(node: Node): boolean {
-  return (
-    (node.type === "tag" && (node.value === "html" || node.value === "body")) ||
-    (node.type === "pseudo" && node.value === ":root")
-  );
-}
-
-function isPseudoElement(node: Node): node is Pseudo {
-  if (node.type !== "pseudo") return false;
-  return (
-    node.value.startsWith("::") ||
-    [":before", ":after", ":first-line", ":first-letter"].includes(node.value)
-  );
-}
-
-function pseudo(text: string): Pseudo {
-  return selectorParser().astSync(text).nodes[0].nodes[0].clone() as Pseudo;
-}

component/dev/DevHostBridge.ts

@@ -1,46 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import { type ElementCallHostBridge } from "../index";
-
-/**
- * A host bridge that reports everything it is told, so that the harness can
- * watch what Element Call says to its host. (What the host says to Element
- * Call goes through the component's handle, and is logged by the pane.)
- */
-export function createDevHostBridge(
-  log: (message: string) => void,
-  /** What the host does when Element Call asks to be closed. */
-  onClose: () => void,
-): ElementCallHostBridge {
-  /**
-   * Records something Element Call told the host. Nothing is sent anywhere, so
-   * this is only asynchronous because a real host's answer would have to be.
-   */
-  const told = async (message: string): Promise<void> => {
-    log(`→ ${message}`);
-    await Promise.resolve();
-  };
-
-  return {
-    setAlwaysOnScreen: async (alwaysOnScreen): Promise<void> =>
-      await told(`setAlwaysOnScreen(${alwaysOnScreen})`),
-    contentLoaded: async (): Promise<void> => await told("contentLoaded"),
-    notifyJoined: async (): Promise<void> => await told("notifyJoined"),
-    notifyHungUp: async (): Promise<void> => await told("notifyHungUp"),
-    notifyDeviceMute: async (state): Promise<void> =>
-      await told(
-        `notifyDeviceMute(audio: ${state.audio_enabled}, video: ${state.video_enabled})`,
-      ),
-    // Present because this host really can dismiss Element Call, which is what
-    // makes it offer a close affordance at all
-    close: async (): Promise<void> => {
-      await told("close");
-      onClose();
-    },
-  };
-}

component/dev/Harness.module.css

@@ -1,140 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-.credentials {
-  display: flex;
-  flex-direction: column;
-  gap: 8px;
-  max-inline-size: 420px;
-  margin: 48px auto;
-  padding: 24px;
-  background-color: #ffffff;
-  border: 1px solid #d4d4d8;
-  border-radius: 8px;
-}
-
-.field {
-  display: flex;
-  flex-direction: column;
-  gap: 4px;
-}
-
-.error {
-  color: #b91c1c;
-}
-
-.harness {
-  display: grid;
-  grid-template-rows: auto 1fr auto;
-  block-size: 100%;
-}
-
-.header,
-.paneBar {
-  display: flex;
-  align-items: center;
-  gap: 12px;
-  padding: 8px 12px;
-  border-block-end: 1px solid #d4d4d8;
-  background-color: #ffffff;
-}
-
-.header h1 {
-  font-size: 16px;
-  margin: 0;
-}
-
-.middle {
-  display: flex;
-  min-block-size: 0;
-}
-
-.sidebar {
-  flex: 0 0 220px;
-  padding: 12px;
-  border-inline-end: 1px solid #d4d4d8;
-  background-color: #ffffff;
-  overflow-y: auto;
-}
-
-.panes {
-  display: flex;
-  flex-wrap: wrap;
-  /* So that a pane is the size it was dragged to, rather than being stretched
-  to fill the row */
-  align-items: flex-start;
-  align-content: flex-start;
-  gap: 16px;
-  padding: 16px;
-  flex: 1;
-  min-inline-size: 0;
-  overflow: auto;
-}
-
-.pane {
-  display: flex;
-  flex-direction: column;
-  border: 1px solid #d4d4d8;
-  border-radius: 8px;
-  overflow: hidden;
-  background-color: #ffffff;
-}
-
-.paneBar {
-  flex-wrap: wrap;
-  gap: 6px;
-  border-block-end: none;
-}
-
-/* The space the host gives Element Call. Resizable so that the sizes it has to
-cope with can be found by dragging rather than by rebuilding, and `overflow:
-hidden` both to enable the resize handle and to show up anything inside Element
-Call that does not fit the box it was given. */
-.paneCall {
-  inline-size: 560px;
-  block-size: 420px;
-  min-inline-size: 180px;
-  min-block-size: 180px;
-  resize: both;
-  overflow: hidden;
-}
-
-.log {
-  max-block-size: 180px;
-  overflow-y: auto;
-  padding: 8px 12px;
-  border-block-start: 1px solid #d4d4d8;
-  background-color: #ffffff;
-  font-size: 12px;
-}
-
-.log h2 {
-  font-size: 13px;
-  margin: 0 0 4px;
-}
-
-.log ol {
-  margin: 0;
-  padding: 0;
-  list-style: none;
-}
-
-/* A host overlay, which Element Call must not be able to draw over */
-.dialogScrim {
-  position: fixed;
-  inset: 0;
-  display: grid;
-  place-items: center;
-  background-color: rgb(0 0 0 / 50%);
-  z-index: 10;
-}
-
-.dialog {
-  padding: 24px;
-  border-radius: 8px;
-  background-color: #ffffff;
-}

component/dev/Harness.tsx

@@ -1,380 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import {
-  type FC,
-  type FormEvent,
-  type ReactNode,
-  useCallback,
-  useMemo,
-  useRef,
-  useState,
-} from "react";
-import { type MatrixClient } from "matrix-js-sdk";
-import { logger } from "matrix-js-sdk/lib/logger";
-
-import {
-  ElementCall,
-  type ElementCallHandle,
-  supportedLanguages,
-} from "../index";
-import { createDevHostBridge } from "./DevHostBridge";
-import { createSession, joinRoom } from "./session";
-import styles from "./Harness.module.css";
-
-interface Credentials {
-  homeserver: string;
-  username: string;
-  password: string;
-  room: string;
-}
-
-const CREDENTIALS_KEY = "element-call-component-harness";
-
-const DEFAULT_CREDENTIALS: Credentials = {
-  homeserver: "https://synapse.m.localhost",
-  username: "",
-  password: "",
-  room: "",
-};
-
-/**
- * The credentials to start with: the last ones used, so that a reload does not
- * mean typing them again, overridden by anything in the query string.
- *
- * A host reading its own URL is entirely proper — it was Element Call doing so
- * that was the mistake. It lets the end-to-end tests, or a shared link, say
- * which account and room to use.
- */
-function loadCredentials(): Credentials {
-  let stored: Partial<Credentials> = {};
-  try {
-    const json = localStorage.getItem(CREDENTIALS_KEY);
-    if (json !== null) stored = JSON.parse(json) as Credentials;
-  } catch (e) {
-    logger.warn("Could not read the stored harness credentials", e);
-  }
-
-  const query = new URLSearchParams(location.search);
-  const fromUrl = Object.fromEntries(
-    (["homeserver", "username", "password", "room"] as const)
-      .map((name) => [name, query.get(name)])
-      .filter(([, value]) => value !== null),
-  ) as Partial<Credentials>;
-
-  return { ...DEFAULT_CREDENTIALS, ...stored, ...fromUrl };
-}
-
-interface Session {
-  label: string;
-  client: MatrixClient;
-}
-
-type State =
-  | { phase: "credentials" }
-  | { phase: "starting"; progress: string }
-  | { phase: "started"; roomId: string; sessions: Session[] }
-  | { phase: "failed"; error: string };
-
-interface LogEntry {
-  pane: string;
-  message: string;
-  at: string;
-}
-
-/**
- * One Element Call component, with the controls a host would have over it: the
- * requests it can make of Element Call, and the ability to take it off screen
- * altogether.
- */
-const Pane: FC<{
-  session: Session;
-  roomId: string;
-  theme: string | undefined;
-  language: string | undefined;
-  log: (pane: string, message: string) => void;
-}> = ({ session, roomId, theme, language, log }): ReactNode => {
-  const [mounted, setMounted] = useState(true);
-
-  const bridge = useMemo(
-    () =>
-      createDevHostBridge(
-        (message) => log(session.label, message),
-        () => setMounted(false),
-      ),
-    [log, session.label],
-  );
-
-  // What the host asks of Element Call goes through the component's handle.
-  // Worth saying out loud when a request is refused — asking to hang up when
-  // there is no call, say — since that is the sort of thing the harness is for.
-  const handle = useRef<ElementCallHandle>(null);
-  const ask = (
-    name: string,
-    make: (handle: ElementCallHandle) => Promise<unknown>,
-  ): void => {
-    if (handle.current === null) {
-      log(session.label, `← ${name}: not mounted`);
-      return;
-    }
-    log(session.label, `← ${name}`);
-    make(handle.current).then(
-      (reply) =>
-        log(
-          session.label,
-          `→ ${name} acknowledged${reply === undefined ? "" : `: ${JSON.stringify(reply)}`}`,
-        ),
-      (e: unknown) => log(session.label, `→ ${name} refused: ${e}`),
-    );
-  };
-
-  return (
-    <section className={styles.pane} data-testid="call-pane">
-      <div className={styles.paneBar}>
-        <strong>{session.label}</strong>
-        <code>{session.client.getDeviceId()}</code>
-        <button onClick={(): void => setMounted((m) => !m)}>
-          {mounted ? "Unmount" : "Mount"}
-        </button>
-        <button
-          onClick={(): void =>
-            ask(
-              "setDeviceMute(audio: false)",
-              async (h) => await h.setDeviceMute({ audio_enabled: false }),
-            )
-          }
-        >
-          Mute
-        </button>
-        <button
-          onClick={(): void => ask("hangUp", async (h) => await h.hangUp())}
-        >
-          Hang up
-        </button>
-      </div>
-      {/* Resizable, because how Element Call copes with the size it is given is
-      one of the things we cannot find out from the standalone app */}
-      <div className={styles.paneCall} data-testid="call-container">
-        {mounted && (
-          <ElementCall
-            ref={handle}
-            client={session.client}
-            roomId={roomId}
-            hostBridge={bridge}
-            theme={theme}
-            language={language}
-          />
-        )}
-      </div>
-    </section>
-  );
-};
-
-/** Host furniture, to make it visible if Element Call styles anything but itself. */
-const HostChrome: FC = (): ReactNode => (
-  <nav className={styles.sidebar}>
-    <h2>Host chrome</h2>
-    <p>
-      This column belongs to the host. If Element Call&apos;s stylesheet reaches
-      outside its own container, it shows up here.
-    </p>
-    <hr />
-    <ul>
-      <li>Some room</li>
-      <li>Another room</li>
-    </ul>
-    <button>A host button</button>
-  </nav>
-);
-
-/**
- * A dialog of the host's own, over the top of the calls. Element Call as a
- * component has to sit underneath this — being unable to is one of the reasons
- * for a component rather than an iframe.
- */
-const HostDialog: FC<{ onClose: () => void }> = ({ onClose }): ReactNode => (
-  <div className={styles.dialogScrim}>
-    <div className={styles.dialog}>
-      <h2>A dialog belonging to the host</h2>
-      <p>This should cover the calls completely.</p>
-      <button onClick={onClose}>Close</button>
-    </div>
-  </div>
-);
-
-/**
- * Stands in for a host application using the Element Call component: it owns the Matrix
- * clients, the page and the space each call is given, and reaches Element Call
- * only through the component's public interface.
- *
- * Two calls at once, from two devices of the same account, so that a real call
- * happens between them and anything Element Call keeps once per process rather
- * than once per call shows itself.
- */
-export const Harness: FC = (): ReactNode => {
-  const [credentials, setCredentials] = useState(loadCredentials);
-  const [state, setState] = useState<State>({ phase: "credentials" });
-  const [entries, setEntries] = useState<LogEntry[]>([]);
-  const [dialogOpen, setDialogOpen] = useState(false);
-  // The host's language setting, which Element Call follows. Undefined means
-  // the host has none and Element Call uses the browser's.
-  const [language, setLanguage] = useState<string | undefined>(undefined);
-  const [theme, setTheme] = useState<string | undefined>(undefined);
-
-  const log = useCallback((pane: string, message: string): void => {
-    setEntries((entries) =>
-      [
-        ...entries,
-        { pane, message, at: new Date().toLocaleTimeString() },
-      ].slice(-100),
-    );
-  }, []);
-
-  const start = useCallback(
-    (event: FormEvent): void => {
-      event.preventDefault();
-      localStorage.setItem(CREDENTIALS_KEY, JSON.stringify(credentials));
-      const { homeserver, username, password, room } = credentials;
-
-      const progress = (message: string): void =>
-        setState({ phase: "starting", progress: message });
-      progress("Starting");
-
-      void (async (): Promise<void> => {
-        try {
-          // One at a time: two logins at once from the same account is the
-          // shape of request homeservers rate limit
-          const sessions: Session[] = [];
-          for (const label of ["Call A", "Call B"])
-            sessions.push({
-              label,
-              client: await createSession(
-                homeserver,
-                username,
-                password,
-                (message) => progress(`${label}: ${message}`),
-              ),
-            });
-
-          progress("Joining the room");
-          let roomId = room;
-          for (const { client } of sessions)
-            roomId = await joinRoom(client, roomId);
-
-          setState({ phase: "started", roomId, sessions });
-        } catch (e) {
-          logger.error("The harness could not start", e);
-          setState({ phase: "failed", error: `${e}` });
-        }
-      })();
-    },
-    [credentials],
-  );
-
-  const field = (
-    name: keyof Credentials,
-    label: string,
-    type = "text",
-  ): ReactNode => (
-    <label className={styles.field}>
-      {label}
-      <input
-        type={type}
-        value={credentials[name]}
-        onChange={(e): void =>
-          setCredentials((c) => ({ ...c, [name]: e.target.value }))
-        }
-      />
-    </label>
-  );
-
-  if (state.phase !== "started")
-    return (
-      <form className={styles.credentials} onSubmit={start}>
-        <h1>Element Call component harness</h1>
-        <p>
-          Signs in twice and shows the Element Call component twice, in a page
-          that is not Element Call&apos;s own.
-        </p>
-        {field("homeserver", "Homeserver")}
-        {field("username", "Username")}
-        {field("password", "Password", "password")}
-        {field("room", "Room ID or alias")}
-        <button type="submit" disabled={state.phase === "starting"}>
-          Start
-        </button>
-        {state.phase === "starting" && <p>{state.progress}</p>}
-        {state.phase === "failed" && (
-          <p className={styles.error}>{state.error}</p>
-        )}
-      </form>
-    );
-
-  return (
-    <div className={styles.harness}>
-      <header className={styles.header}>
-        <h1>Element Call component harness</h1>
-        <code>{state.roomId}</code>
-        <button onClick={(): void => setDialogOpen(true)}>
-          Open a host dialog
-        </button>
-        <label>
-          Theme{" "}
-          <select
-            value={theme ?? ""}
-            onChange={(e): void => setTheme(e.target.value || undefined)}
-          >
-            <option value="">Element Call&apos;s choice</option>
-            <option value="light">light</option>
-            <option value="dark">dark</option>
-          </select>
-        </label>
-        <label>
-          Language{" "}
-          <select
-            value={language ?? ""}
-            onChange={(e): void => setLanguage(e.target.value || undefined)}
-          >
-            <option value="">Browser default</option>
-            {supportedLanguages.map((tag) => (
-              <option key={tag} value={tag}>
-                {tag}
-              </option>
-            ))}
-          </select>
-        </label>
-      </header>
-      <div className={styles.middle}>
-        <HostChrome />
-        <main className={styles.panes}>
-          {state.sessions.map((session) => (
-            <Pane
-              key={session.label}
-              session={session}
-              roomId={state.roomId}
-              theme={theme}
-              language={language}
-              log={log}
-            />
-          ))}
-        </main>
-      </div>
-      <section className={styles.log} data-testid="bridge-log">
-        <h2>Host bridge</h2>
-        <ol>
-          {entries.map((entry, i) => (
-            <li key={i}>
-              <code>{entry.at}</code> <strong>{entry.pane}</strong>{" "}
-              {entry.message}
-            </li>
-          ))}
-        </ol>
-      </section>
-      {dialogOpen && <HostDialog onClose={(): void => setDialogOpen(false)} />}
-    </div>
-  );
-};

component/dev/host.css

@@ -1,23 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-/* The host page's own styles. Deliberately plain, and deliberately not using
-Element Call's design tokens: the harness should look like it does because of
-this file, not because Element Call styled it. */
-
-html,
-body,
-#root {
-  height: 100%;
-}
-
-body {
-  margin: 0;
-  font-family: system-ui, sans-serif;
-  background-color: #f4f4f5;
-  color: #18181b;
-}

component/dev/index.html

@@ -1,21 +0,0 @@
-<!doctype html>
-<!--
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
--->
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Element Call component harness</title>
-  </head>
-  <body>
-    <!-- Deliberately plain: this page stands in for a host application, so
-    anything it looks like must have come from the host's own styles or from
-    Element Call reaching outside its container. -->
-    <div id="root"></div>
-    <script type="module" src="./main.tsx"></script>
-  </body>
-</html>

component/dev/main.tsx

@@ -1,42 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import { StrictMode } from "react";
-import { createRoot } from "react-dom/client";
-import { logger } from "matrix-js-sdk/lib/logger";
-
-import { type ConfigOptions, initializeElementCall } from "../index";
-import { Harness } from "./Harness";
-// After Element Call's, so that the host has the last word on its own page
-import "./host.css";
-
-/**
- * The development app's own `config.json`, so that the harness runs Element
- * Call the way `pnpm dev` does. It is not in the repository — developers copy
- * it from `config/config.devenv.json` — so its absence is expected rather than
- * an error.
- */
-async function loadConfig(): Promise<ConfigOptions> {
-  try {
-    const response = await fetch("/config.json");
-    if (response.ok) return (await response.json()) as ConfigOptions;
-    logger.warn(
-      `No config.json (${response.status}); running with Element Call's defaults`,
-    );
-  } catch (e) {
-    logger.warn("Could not read config.json", e);
-  }
-  return {};
-}
-
-await initializeElementCall(await loadConfig());
-
-createRoot(document.getElementById("root")!).render(
-  <StrictMode>
-    <Harness />
-  </StrictMode>,
-);

component/dev/session.ts

@@ -1,79 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import {
-  ClientEvent,
-  createClient,
-  type MatrixClient,
-  MemoryStore,
-  SyncState,
-} from "matrix-js-sdk";
-
-/**
- * Logs in and brings up a client the way a host application would, so that the
- * component is handed a real one rather than something Element Call built for
- * itself.
- *
- * Everything is kept in memory and a fresh login happens on every reload. That
- * costs a device on the development homeserver each time, which is harmless,
- * and buys the harness two clients that cannot tread on each other's storage.
- * Persisting the login to make reloads quicker would mean persisting the
- * crypto store too: reusing a device ID with a fresh crypto store generates new
- * device keys, and uploading them conflicts with the ones the server already
- * holds.
- */
-export async function createSession(
-  homeserver: string,
-  username: string,
-  password: string,
-  onProgress: (message: string) => void,
-): Promise<MatrixClient> {
-  onProgress("Logging in");
-  const login = await createClient({ baseUrl: homeserver }).login(
-    "m.login.password",
-    { identifier: { type: "m.id.user", user: username }, password },
-  );
-
-  const client = createClient({
-    baseUrl: homeserver,
-    accessToken: login.access_token,
-    userId: login.user_id,
-    deviceId: login.device_id,
-    store: new MemoryStore(),
-    useAuthorizationHeader: true,
-    fallbackICEServerAllowed: true,
-  });
-
-  onProgress(`Setting up crypto for ${login.device_id}`);
-  await client.initRustCrypto({ useIndexedDB: false });
-
-  onProgress(`Syncing ${login.device_id}`);
-  await client.startClient();
-  await new Promise<void>((resolve) => {
-    const onSync = (state: SyncState): void => {
-      if (state !== SyncState.Prepared && state !== SyncState.Syncing) return;
-      client.off(ClientEvent.Sync, onSync);
-      resolve();
-    };
-    client.on(ClientEvent.Sync, onSync);
-  });
-
-  return client;
-}
-
-/**
- * The room to call in, joining it if this session is not in it yet — a host
- * hands Element Call a room it already knows about, so the harness has to get
- * itself into that position first.
- */
-export async function joinRoom(
-  client: MatrixClient,
-  roomIdOrAlias: string,
-): Promise<string> {
-  const room = await client.joinRoom(roomIdOrAlias);
-  return room.roomId;
-}

component/host.test.ts

@@ -1,161 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import { renderHook } from "@testing-library/react";
-import { createRef } from "react";
-import { describe, expect, test, vi } from "vitest";
-
-import {
-  type ElementCallHandle,
-  type ElementCallHostBridge,
-  useComponentHostBridge,
-} from "./host";
-
-describe("useComponentHostBridge", () => {
-  test("keeps one identity while the host supplies new objects", () => {
-    const { result, rerender } = renderHook(
-      ({ supplied }: { supplied: ElementCallHostBridge }) =>
-        useComponentHostBridge(supplied, undefined, undefined),
-      { initialProps: { supplied: {} } },
-    );
-    const first = result.current;
-    rerender({ supplied: { notifyJoined: async () => {} } });
-    expect(result.current).toBe(first);
-  });
-
-  test("forwards to whatever the host most recently supplied", async () => {
-    const before = vi.fn().mockResolvedValue(undefined);
-    const after = vi.fn().mockResolvedValue(undefined);
-    const { result, rerender } = renderHook(
-      ({ supplied }: { supplied: ElementCallHostBridge }) =>
-        useComponentHostBridge(supplied, undefined, undefined),
-      { initialProps: { supplied: { notifyJoined: before } } },
-    );
-    rerender({ supplied: { notifyJoined: after } });
-
-    await result.current.notifyJoined();
-    expect(before).not.toHaveBeenCalled();
-    expect(after).toHaveBeenCalledOnce();
-  });
-
-  test("is quiet about what the host did not implement", async () => {
-    const { result } = renderHook(() =>
-      useComponentHostBridge(undefined, undefined, undefined),
-    );
-    await expect(result.current.contentLoaded()).resolves.toBeUndefined();
-    await expect(
-      result.current.notifyDeviceMute({
-        audio_enabled: true,
-        video_enabled: false,
-      }),
-    ).resolves.toBeUndefined();
-    expect(result.current.supportsReactions).toBe(true);
-    // Starting the user unmuted unasked is something a host has to opt into
-    expect(result.current.allowJoinUnmutedViaIntent).toBe(false);
-  });
-
-  test("lets the host allow joining unmuted on the intent", () => {
-    const { result, rerender } = renderHook(
-      ({ supplied }: { supplied: ElementCallHostBridge }) =>
-        useComponentHostBridge(supplied, undefined, undefined),
-      { initialProps: { supplied: {} } },
-    );
-    expect(result.current.allowJoinUnmutedViaIntent).toBe(false);
-
-    // Read through to whatever the host most recently said
-    rerender({ supplied: { allowJoinUnmutedViaIntent: true } });
-    expect(result.current.allowJoinUnmutedViaIntent).toBe(true);
-  });
-
-  test("only has a close when the host has one, since that is a signal", () => {
-    const { result, rerender } = renderHook(
-      ({ supplied }: { supplied: ElementCallHostBridge }) =>
-        useComponentHostBridge(supplied, undefined, undefined),
-      { initialProps: { supplied: {} } },
-    );
-    expect(result.current.close).toBeUndefined();
-
-    const close = vi.fn().mockResolvedValue(undefined);
-    rerender({ supplied: { close } });
-    expect(result.current.close).toBeDefined();
-  });
-
-  test("never offers profile changes, since the account is the host's", () => {
-    const { result } = renderHook(() =>
-      useComponentHostBridge(undefined, undefined, undefined),
-    );
-    expect(result.current.supportsProfileChanges).toBe(false);
-  });
-
-  describe("the handle", () => {
-    test("delivers a request to what is listening and resolves on its reply", async () => {
-      const ref = createRef<ElementCallHandle>();
-      const { result } = renderHook(() =>
-        useComponentHostBridge(undefined, ref, undefined),
-      );
-
-      const received = vi.fn();
-      result.current.deviceMute$.subscribe(({ data, reply }) => {
-        received(data);
-        reply({ audio_enabled: data.audio_enabled!, video_enabled: true });
-      });
-
-      await expect(
-        ref.current!.setDeviceMute({ audio_enabled: false }),
-      ).resolves.toEqual({ audio_enabled: false, video_enabled: true });
-      expect(received).toHaveBeenCalledWith({ audio_enabled: false });
-    });
-
-    test("refuses a request nothing in Element Call is listening for", async () => {
-      const ref = createRef<ElementCallHandle>();
-      renderHook(() => useComponentHostBridge(undefined, ref, undefined));
-
-      await expect(ref.current!.hangUp()).rejects.toThrow(
-        "Nothing in Element Call can hang up right now",
-      );
-    });
-  });
-
-  describe("the theme", () => {
-    test("reaches a subscriber that arrives after it was set", () => {
-      const { result } = renderHook(() =>
-        useComponentHostBridge(undefined, undefined, "light"),
-      );
-      const names: (string | undefined)[] = [];
-      result.current.themeChange$.subscribe(({ data }) =>
-        names.push(data.name),
-      );
-      expect(names).toEqual(["light"]);
-    });
-
-    test("follows the prop", () => {
-      const { result, rerender } = renderHook(
-        ({ theme }: { theme: string | undefined }) =>
-          useComponentHostBridge(undefined, undefined, theme),
-        { initialProps: { theme: "light" } },
-      );
-      const names: (string | undefined)[] = [];
-      result.current.themeChange$.subscribe(({ data }) =>
-        names.push(data.name),
-      );
-
-      rerender({ theme: "dark" });
-      expect(names).toEqual(["light", "dark"]);
-    });
-
-    test("says nothing when the host leaves the theme to Element Call", () => {
-      const { result } = renderHook(() =>
-        useComponentHostBridge(undefined, undefined, undefined),
-      );
-      const names: (string | undefined)[] = [];
-      result.current.themeChange$.subscribe(({ data }) =>
-        names.push(data.name),
-      );
-      expect(names).toEqual([]);
-    });
-  });
-});

component/host.ts

@@ -1,201 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-/**
- * How a host application and the Element Call component talk to each other.
- *
- * Inside Element Call the host is a {@link HostBridge}, which carries the
- * host's requests as rxjs observables because that is what the widget API and
- * the view models work in. A host should not have to know about rxjs, or agree
- * with us on a version of it, so a component host sees neither: it implements
- * plain async callbacks for what Element Call tells it, and makes its own
- * requests through an imperative handle on the component, the way it would
- * call `play()` on a video element. This module adapts the one to the other.
- */
-
-import { type Ref, useEffect, useImperativeHandle } from "react";
-import { ReplaySubject, Subject } from "rxjs";
-
-import {
-  type DeviceMuteRequest,
-  type DeviceMuteState,
-  type HostBridge,
-  type HostRequest,
-} from "../src/HostBridge";
-import { type JoinCallData } from "../src/widget";
-import { useInitial } from "../src/useInitial";
-import { useLatest } from "../src/useLatest";
-
-/**
- * What Element Call tells the application hosting it as a component.
- * Everything is optional: a host implements what it wants to hear about.
- *
- * Compared by nothing — Element Call always calls whichever one it was most
- * recently given, so this may be written inline.
- */
-export interface ElementCallHostBridge {
-  /**
-   * Asks the host to keep Element Call on screen (or stop doing so), so that a
-   * call in progress is not torn down when the user navigates elsewhere.
-   */
-  setAlwaysOnScreen?(alwaysOnScreen: boolean): Promise<void>;
-  /** Tells the host that Element Call has finished loading. */
-  contentLoaded?(): Promise<void>;
-  /** Tells the host that the user has joined the call. */
-  notifyJoined?(): Promise<void>;
-  /** Tells the host that the user has hung up. */
-  notifyHungUp?(): Promise<void>;
-  /** Tells the host the user's current audio and video mute state. */
-  notifyDeviceMute?(state: DeviceMuteState): Promise<void>;
-  /**
-   * Asks the host to close Element Call: to unmount the component. Its
-   * presence is what makes Element Call offer a close button on its error
-   * screens, and leave the host to decide what is shown once a call has ended.
-   * Without it, Element Call shows its own post-call screen, if it has one for
-   * the situation, or nothing.
-   */
-  close?(): Promise<void>;
-  /**
-   * Whether Element Call may send and receive reactions in this room.
-   * Defaults to true.
-   */
-  readonly supportsReactions?: boolean;
-  /**
-   * Whether the user may start unmuted when the intent skips the lobby, so
-   * that they never see their devices before joining. Defaults to false: the
-   * user starts muted and unmutes themselves. A host that chose the intent on
-   * the user's behalf, and is sure they expect to be heard and seen at once,
-   * says so here — as a Matrix client hosting Element Call as a widget does.
-   */
-  readonly allowJoinUnmutedViaIntent?: boolean;
-}
-
-/**
- * What a host can ask of a mounted Element Call, reached through the
- * component's `ref`. Each request resolves once Element Call has acted on it,
- * and rejects if nothing in Element Call is in a position to act: hanging up
- * when there is no call, say.
- */
-export interface ElementCallHandle {
-  /**
-   * Joins the call, when Element Call was configured to `preload` and is
-   * waiting to be told to. Says which devices to join with.
-   */
-  join(devices: JoinCallData): Promise<void>;
-  /** Leaves the call. */
-  hangUp(): Promise<void>;
-  /**
-   * Changes the mute state, for whichever of audio and video is given, and
-   * reports the state that results.
-   */
-  setDeviceMute(request: DeviceMuteRequest): Promise<DeviceMuteState>;
-}
-
-/** Hands a request to Element Call and waits for it to be acknowledged. */
-async function request<Data, Reply>(
-  listeners: Subject<HostRequest<Data, Reply>>,
-  what: string,
-  data: Data,
-): Promise<Reply> {
-  if (!listeners.observed)
-    throw new Error(`Nothing in Element Call can ${what} right now`);
-  return await new Promise((resolve) =>
-    listeners.next({ data, reply: resolve }),
-  );
-}
-
-/**
- * The {@link HostBridge} the rest of Element Call sees, built from what a
- * component host supplies and wired to the handle it is given.
- *
- * The bridge is created once and never changes identity — everything that
- * depends on it would otherwise restart when the host re-rendered with a new
- * object — and forwards each call to whatever the host most recently passed.
- */
-export function useComponentHostBridge(
-  supplied: ElementCallHostBridge | undefined,
-  ref: Ref<ElementCallHandle> | undefined,
-  /** The theme the host wants, or undefined to leave it to Element Call. */
-  theme: string | undefined,
-): HostBridge {
-  const latest = useLatest(supplied ?? {});
-
-  const requests = useInitial(() => ({
-    // The theme is state, not an event: a `theme` prop rather than a request
-    // on the handle. It travels this channel because that is how the rest of
-    // Element Call hears about a host's theme, and replays so that whatever
-    // subscribes after the host has set it — everything, on first render —
-    // still hears the current one.
-    themeChange$: new ReplaySubject<HostRequest<{ name?: string }>>(1),
-    join$: new Subject<HostRequest<JoinCallData>>(),
-    hangUp$: new Subject<HostRequest<Record<string, never>>>(),
-    deviceMute$: new Subject<HostRequest<DeviceMuteRequest, DeviceMuteState>>(),
-  }));
-
-  useEffect(() => {
-    if (theme !== undefined)
-      requests.themeChange$.next({ data: { name: theme }, reply: () => {} });
-  }, [requests, theme]);
-
-  const bridge = useInitial((): HostBridge => ({
-    setAlwaysOnScreen: async (alwaysOnScreen) => {
-      await latest.current.setAlwaysOnScreen?.(alwaysOnScreen);
-    },
-    contentLoaded: async () => {
-      await latest.current.contentLoaded?.();
-    },
-    notifyJoined: async () => {
-      await latest.current.notifyJoined?.();
-    },
-    notifyHungUp: async () => {
-      await latest.current.notifyHungUp?.();
-    },
-    notifyDeviceMute: async (state) => {
-      await latest.current.notifyDeviceMute?.(state);
-    },
-    // Whether these exist is itself information, so they are read through
-    // rather than wrapped unconditionally
-    get close() {
-      const close = latest.current.close;
-      return close === undefined
-        ? undefined
-        : async (): Promise<void> => await close();
-    },
-    // Not offered to a component host: the client it hands over holds the
-    // credentials to fetch media itself. A widget's client does not, which
-    // is what the internal bridge's `downloadMedia` is for.
-    get supportsReactions(): boolean {
-      return latest.current.supportsReactions ?? true;
-    },
-    get allowJoinUnmutedViaIntent(): boolean {
-      return latest.current.allowJoinUnmutedViaIntent ?? false;
-    },
-    // Whatever the host says or does not say, the account is its own: it
-    // signed the user in and handed us the client. So Element Call never
-    // offers to edit the profile from inside a component.
-    supportsProfileChanges: false,
-    ...requests,
-  }));
-
-  useImperativeHandle(
-    ref,
-    (): ElementCallHandle => ({
-      join: async (devices) =>
-        await request(requests.join$, "join a call", devices),
-      hangUp: async () => await request(requests.hangUp$, "hang up", {}),
-      setDeviceMute: async (muteRequest) =>
-        await request(
-          requests.deviceMute$,
-          "change the mute state",
-          muteRequest,
-        ),
-    }),
-    [requests],
-  );
-
-  return bridge;
-}

component/index.tsx

@@ -1,358 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-/**
- * EXPERIMENTAL
- *
- * Element Call as a React component, for an application that wants to show a
- * call inside itself rather than in an iframe.
- *
- * The host supplies the client and says which room to call in; Element Call
- * supplies the call. Everything it would otherwise take from the page it is on
- * — the URL, the document body, a Matrix session of its own — comes from the
- * host instead, or is confined to the container it is mounted in.
- */
-
-// The design tokens, fonts and element defaults every Element Call stylesheet
-// builds on. Written for a page, they speak of `html`, `body` and bare
-// elements; the component build confines them, and every other stylesheet in
-// this bundle, to the root element below (see build/scopeStylesToRoot.ts), so
-// that the host's document is left as it was.
-//
-// Where these land relative to the component stylesheets is the bundler's
-// choice — the standalone app puts them first, this build puts them in the
-// middle — so nothing in base.css may depend on winning or losing against a
-// component's own rules at equal specificity. It currently does not: what it
-// declares unlayered is custom properties on Element Call's root, which
-// components inherit rather than compete with, and everything from Compound
-// sits in a `@layer`, which loses to unlayered rules either way.
-import "../src/base.css";
-
-import {
-  type FC,
-  type JSX,
-  type ReactNode,
-  type Ref,
-  useEffect,
-  useLayoutEffect,
-  useMemo,
-  useRef,
-  useState,
-} from "react";
-import { type MatrixClient } from "matrix-js-sdk";
-import { logger } from "matrix-js-sdk/lib/logger";
-import { I18nextProvider } from "react-i18next";
-import { TooltipProvider } from "@vector-im/compound-web";
-import { ErrorBoundary } from "@sentry/react";
-import { shouldPolyfill as shouldPolyfillSegmenter } from "@formatjs/intl-segmenter/should-polyfill";
-import { shouldPolyfill as shouldPolyfillDurationFormat } from "@formatjs/intl-durationformat/should-polyfill.js";
-
-import LanguageDetector from "i18next-browser-languagedetector";
-
-import EN from "../locales/en/app.json";
-import { CallView } from "../src/room/CallView";
-import { ErrorPage } from "../src/FullScreenView";
-import { ClientProvider } from "../src/ClientContext";
-import { HostBridgeProvider } from "../src/HostBridge";
-import { RootElementProvider, useRootElement } from "../src/RootElementContext";
-import {
-  configurationForIntent,
-  componentProperties,
-  type UrlConfiguration,
-  type UrlParams,
-  UrlParamsProvider,
-  type UrlProperties,
-  UserIntent,
-  useUrlParams,
-} from "../src/UrlParams";
-import { MediaDevicesContext } from "../src/MediaDevicesContext";
-import { MediaDevices } from "../src/state/MediaDevices";
-import { ObservableScope } from "../src/state/ObservableScope";
-import { ProcessorProvider } from "../src/livekit/TrackProcessorContext";
-import { Config } from "../src/config/Config";
-import { type ConfigOptions } from "../src/config/ConfigOptions";
-import { i18n } from "../src/utils/i18n";
-import { useTheme } from "../src/useTheme";
-import { useStableValue } from "../src/useStableValue";
-import styles from "./ElementCall.module.css";
-import {
-  type ElementCallHandle,
-  type ElementCallHostBridge,
-  useComponentHostBridge,
-} from "./host";
-import { supportedLanguages, translationsBackend } from "./localization";
-
-// The languages Element Call can be shown in
-export { supportedLanguages } from "./localization";
-
-// How the host and Element Call talk to each other, and what they say
-export { type ElementCallHandle, type ElementCallHostBridge } from "./host";
-export {
-  type DeviceMuteRequest,
-  type DeviceMuteState,
-} from "../src/HostBridge";
-export { type JoinCallData } from "../src/widget";
-// The deployment-wide configuration, as distinct from ElementCallConfiguration
-// above, which is per call
-export { type ConfigOptions } from "../src/config/ConfigOptions";
-// The values that appear in ElementCallConfiguration and in the intent
-export {
-  BackgroundStyle,
-  HeaderStyle,
-  UserIntent,
-  type UrlConfiguration,
-} from "../src/UrlParams";
-
-/**
- * How Element Call should behave. Everything is optional; anything left out
- * takes the default that {@link ElementCallProps.intent} implies.
- *
- * This is the behaviour a widget can be configured with through its URL, plus
- * the one fact about the call a host has a say in here, the background. The
- * rest of what a widget's URL carries — who the user is, how to reach the
- * homeserver, where to report analytics, the shared secret of a room that is
- * encrypted with one — a component host supplies by other routes, or not at
- * all; and what can change while the call is running, the theme and the
- * language, is a prop of its own.
- */
-export type ElementCallConfiguration = Partial<UrlConfiguration> &
-  Partial<Pick<UrlProperties, "background">>;
-
-export interface ElementCallProps {
-  /**
-   * The client to place the call with. Element Call does not authenticate
-   * anyone or manage a session of its own; this one is the host's.
-   */
-  client: MatrixClient;
-  /** The room to call in. The host's client must already know about it. */
-  roomId: string;
-  /**
-   * What the user asked for — whether they started the call or joined one that
-   * was already running, and whether it is a call in a group or a DM. Element
-   * Call decides what each of those means: whether to show the lobby first,
-   * whether to ring, and so on.
-   *
-   * Defaults to joining an existing group call, which is the most conservative
-   * reading, but a host that knows which button the user pressed should say so.
-   */
-  intent?: UserIntent;
-  /**
-   * How Element Call should behave, overriding whatever {@link intent} implies.
-   * A host that finds itself setting a lot of these probably wants a different
-   * intent instead.
-   *
-   * Compared by value, so it is fine to write this inline; only a change to
-   * what it says restarts anything.
-   */
-  config?: ElementCallConfiguration;
-  /**
-   * What Element Call tells the host while the call is running: that the user
-   * has joined or hung up, that it would like to be kept on screen, and so on.
-   * Without one, Element Call assumes nobody is listening.
-   */
-  hostBridge?: ElementCallHostBridge;
-  /**
-   * What the host tells Element Call: to hang up, to mute, to join. Available
-   * once the component has rendered.
-   */
-  ref?: Ref<ElementCallHandle>;
-  /**
-   * The theme to show Element Call in, `light` or `dark`. Left out, Element
-   * Call picks. Changes take effect at once, and cost nothing else.
-   */
-  theme?: string;
-  /**
-   * The language to show Element Call in, as a BCP 47 tag: one of
-   * {@link supportedLanguages}, or something that falls back to one (`de-AT`
-   * to `de`). Left out, the browser's language is used.
-   *
-   * Translations are one thing shared by every Element Call on the page, so
-   * the most recently set language wins for all of them.
-   */
-  language?: string;
-}
-
-/**
- * Prepares the things Element Call needs before it can be shown: translations,
- * `Intl` polyfills for older browsers, and its configuration.
- *
- * Await this once, before rendering {@link ElementCall}.
- */
-export async function initializeElementCall(
-  config: ConfigOptions = {},
-): Promise<void> {
-  const polyfills: Promise<unknown>[] = [];
-  if (shouldPolyfillSegmenter())
-    polyfills.push(import("@formatjs/intl-segmenter/polyfill-force"));
-  if (shouldPolyfillDurationFormat())
-    polyfills.push(import("@formatjs/intl-durationformat/polyfill-force.js"));
-  await Promise.all(polyfills);
-
-  Config.initWith(config);
-  await i18n
-    .use(translationsBackend)
-    .use(new LanguageDetector())
-    .init({
-      fallbackLng: "en",
-      defaultNS: "app",
-      keySeparator: ".",
-      nsSeparator: false,
-      pluralSeparator: "_",
-      contextSeparator: "|",
-      supportedLngs: [...supportedLanguages],
-      interpolation: { escapeValue: false },
-      // English is bundled in, so the fallback never has to be loaded; every
-      // other language arrives from the backend when first asked for.
-      partialBundledLanguages: true,
-      resources: { en: { app: EN } },
-      detection: {
-        // The browser's language, until the host says otherwise through the
-        // `language` prop. Nothing is remembered: the choice is the host's.
-        order: ["navigator"],
-        caches: [],
-      },
-    });
-}
-
-/** Applies the theme and background to the container, before it is painted. */
-const Decoration: FC<{ children: JSX.Element }> = ({ children }) => {
-  useTheme();
-  const { background } = useUrlParams();
-  const rootElement = useRootElement();
-  useLayoutEffect(() => {
-    rootElement.setAttribute("data-background", background);
-  }, [rootElement, background]);
-  return children;
-};
-
-export const ElementCall: FC<ElementCallProps> = ({
-  client,
-  roomId,
-  intent = UserIntent.JoinExistingCall,
-  config,
-  hostBridge: suppliedHostBridge,
-  ref,
-  theme,
-  language,
-}): ReactNode => {
-  const hostBridge = useComponentHostBridge(suppliedHostBridge, ref, theme);
-
-  useEffect(() => {
-    if (language !== undefined)
-      i18n
-        .changeLanguage(language)
-        .catch((e) => logger.error(`Could not switch to ${language}`, e));
-  }, [language]);
-
-  // The container is what Element Call decorates and portals into, so nothing
-  // inside can render until we have it.
-  const [container, setContainer] = useState<HTMLDivElement | null>(null);
-
-  // Element Call has no URL of its own to read any of this from, and the
-  // host's URL is not Element Call's business, so the defaults come from the
-  // intent with the host's wishes over the top.
-  //
-  // Everything downstream — the mute state, the call view model and with it
-  // the media connection — is keyed on the identity of this object, so it has
-  // to be stable for as long as its contents are. A host writing `config`
-  // inline would otherwise tear the call down on every render.
-  const stableConfig = useStableValue(config);
-  const params = useMemo(
-    (): UrlParams => ({
-      ...componentProperties,
-      roomId,
-      ...configurationForIntent(intent),
-      ...stableConfig,
-    }),
-    [roomId, intent, stableConfig],
-  );
-
-  // Created in an effect so that the scope it lives in ends when the component
-  // is unmounted (or these options change), rather than keeping its device
-  // observers running for the rest of the page's life. Null until then, which
-  // is one render.
-  const { controlledAudioDevices, callIntent } = params;
-  const [mediaDevices, setMediaDevices] = useState<MediaDevices | null>(null);
-  useEffect(() => {
-    const scope = new ObservableScope();
-    setMediaDevices(
-      new MediaDevices(scope, { controlledAudioDevices, callIntent }),
-    );
-    return (): void => {
-      setMediaDevices(null);
-      scope.end();
-    };
-  }, [controlledAudioDevices, callIntent]);
-
-  const room = client.getRoom(roomId);
-  const rtcSession = useMemo(
-    () => (room === null ? null : client.matrixRTC.getRoomSession(room)),
-    [client, room],
-  );
-
-  if (rtcSession === null)
-    logger.error(
-      `Element Call was asked to call in ${roomId}, which its host's client does not know about`,
-    );
-
-  // Everything the call needs is in hand once these exist, and the first
-  // render with them is where the call itself appears: the moment the host
-  // is told that Element Call has loaded, as the widget tells its client once
-  // its own initialisation is over. Once per mount, however often the pieces
-  // are later swapped out.
-  const ready =
-    container !== null && rtcSession !== null && mediaDevices !== null;
-  const announcedLoaded = useRef(false);
-  useEffect(() => {
-    if (!ready || announcedLoaded.current) return;
-    announcedLoaded.current = true;
-    hostBridge
-      .contentLoaded()
-      .catch((e) => logger.error("Could not tell the host we had loaded", e));
-  }, [ready, hostBridge]);
-
-  return (
-    <I18nextProvider i18n={i18n}>
-      <HostBridgeProvider value={hostBridge}>
-        <UrlParamsProvider value={params}>
-          <div ref={setContainer} className={styles.root}>
-            {ready && (
-              <RootElementProvider value={container}>
-                {/* Whatever goes wrong in here is shown in here. Left to
-                  propagate, an error would unmount the host's own tree. */}
-                <ErrorBoundary
-                  fallback={(error) => <ErrorPage error={error} />}
-                  // A broken call should not hold the host on screen
-                  onError={() => void hostBridge.setAlwaysOnScreen(false)}
-                >
-                  <Decoration>
-                    <TooltipProvider>
-                      <ClientProvider client={client}>
-                        <MediaDevicesContext value={mediaDevices}>
-                          <ProcessorProvider>
-                            <CallView
-                              client={client}
-                              rtcSession={rtcSession}
-                              isPasswordlessUser={false}
-                              confineToRoom={params.confineToRoom}
-                              preload={params.preload}
-                              skipLobby={params.skipLobby}
-                            />
-                          </ProcessorProvider>
-                        </MediaDevicesContext>
-                      </ClientProvider>
-                    </TooltipProvider>
-                  </Decoration>
-                </ErrorBoundary>
-              </RootElementProvider>
-            )}
-          </div>
-        </UrlParamsProvider>
-      </HostBridgeProvider>
-    </I18nextProvider>
-  );
-};

component/localization.test.ts

@@ -1,46 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-import { describe, expect, test } from "vitest";
-
-import { supportedLanguages, translationsBackend } from "./localization";
-
-const read = async (
-  language: string,
-  namespace = "app",
-): Promise<Record<string, unknown>> =>
-  await new Promise((resolve, reject) =>
-    translationsBackend.read(language, namespace, (error, data) => {
-      if (error) reject(error);
-      else resolve(data as Record<string, unknown>);
-    }),
-  );
-
-describe("component translations", () => {
-  test("offer every language in locales/, tagged as its directory is", () => {
-    expect(supportedLanguages).toContain("en");
-    expect(supportedLanguages).toContain("de");
-    expect(supportedLanguages).toContain("zh-Hans");
-    expect(new Set(supportedLanguages).size).toBe(supportedLanguages.length);
-  });
-
-  test("load a language's translations on demand", async () => {
-    const de = await read("de");
-    expect(de).toHaveProperty("action");
-    expect(de).not.toEqual(await read("en"));
-  });
-
-  test("refuse a language there are no translations for", async () => {
-    await expect(read("xx")).rejects.toThrow("No app translations for xx");
-  });
-
-  test("refuse a namespace there are no translations for", async () => {
-    await expect(read("en", "other")).rejects.toThrow(
-      "No other translations for en",
-    );
-  });
-});

component/localization.ts

@@ -1,55 +0,0 @@
-/*
-Copyright 2026 Element Creations Ltd.
-
-SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
-Please see LICENSE in the repository root for full details.
-*/
-
-/**
- * Translations for Element Call as a component.
- *
- * The standalone app fetches its locale files at runtime from URLs its own
- * build emits, which a host serving the library from somewhere else could not
- * resolve. The component instead has the bundler split every locale into a
- * chunk of its own, loaded the first time its language is asked for; English,
- * the fallback, is bundled in so that the first paint never waits for it.
- */
-
-import { type BackendModule, type ResourceKey } from "i18next";
-
-import { languageOfLocalePath } from "../src/utils/i18n";
-
-/** Every locale, as a lazily imported module. */
-const translations = import.meta.glob<{ default: ResourceKey }>(
-  "../locales/*/app.json",
-);
-
-/**
- * The languages Element Call can be shown in, as BCP 47 tags — `en`, `de`,
- * `zh-Hans` and so on. A language that is not one of these falls back to its
- * base language where there is one (`de-AT` to `de`), and to English otherwise.
- */
-export const supportedLanguages: readonly string[] = [
-  ...new Set(Object.keys(translations).map(languageOfLocalePath)),
-];
-
-/** Loads translations on demand. */
-export const translationsBackend: BackendModule = {
-  type: "backend",
-  init(): void {},
-  read(language: string, namespace: string, callback): void {
-    const load = translations[`../locales/${language}/${namespace}.json`];
-    if (load === undefined) {
-      callback(new Error(`No ${namespace} translations for ${language}`), null);
-      return;
-    }
-    load().then(
-      (module) => callback(null, module.default),
-      (error: unknown) =>
-        callback(
-          error instanceof Error ? error : new Error(String(error)),
-          null,
-        ),
-    );
-  },
-};

component/package.json

@@ -1,42 +0,0 @@
-{
-  "name": "@element-hq/element-call-component",
-  "version": "0.0.0",
-  "description": "Element Call as a React component. Consumed straight from the repository as a git dependency (github:element-hq/element-call#<ref>&path:/component): the host's package manager runs `prepare`, which builds `dist/`.",
-  "license": "SEE LICENSE IN ../README.md",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/element-hq/element-call",
-    "directory": "component"
-  },
-  "type": "module",
-  "devEngines": {
-    "packageManager": {
-      "name": "pnpm"
-    }
-  },
-  "files": [
-    "dist"
-  ],
-  "main": "./dist/element-call.js",
-  "module": "./dist/element-call.js",
-  "types": "./dist/types/component/index.d.ts",
-  "exports": {
-    ".": {
-      "types": "./dist/types/component/index.d.ts",
-      "default": "./dist/element-call.js"
-    },
-    "./style.css": "./dist/element-call.css"
-  },
-  "sideEffects": [
-    "*.css"
-  ],
-  "scripts": {
-    "prepare": "cd .. && pnpm install --frozen-lockfile && pnpm build:component"
-  },
-  "peerDependencies": {
-    "livekit-client": "^2.18.1",
-    "matrix-js-sdk": "*",
-    "react": "^19",
-    "react-dom": "^19"
-  }
-}

component/pnpm-lock.yaml

@@ -1,9 +0,0 @@
-lockfileVersion: '9.0'
-
-settings:
-  autoInstallPeers: false
-  excludeLinksFromLockfile: false
-
-importers:
-
-  .: {}

component/pnpm-workspace.yaml

@@ -1,14 +0,0 @@
-# Makes `component/` a pnpm project of its own rather than a directory inside
-# the repository's workspace. That matters when a host installs the component
-# straight from this repository (`github:element-hq/element-call#…&path:/component`):
-# pnpm prepares such a dependency by running `pnpm install` in this directory,
-# and only a project root gets its `prepare` script (see package.json) run, which
-# is what builds `dist/`. Inside the repository's own workspace the install
-# would silently target the repository instead and build nothing.
-#
-# Consequence for development: pnpm commands run from within this directory see
-# this project, not the repository; run them from the repository root.
-
-# Nothing to install here: the peers in package.json are the host's, and the
-# build runs against the repository's own node_modules (see `prepare`).
-autoInstallPeers: false

component/tsconfig.build.json

@@ -1,20 +0,0 @@
-{
-  // Declaration output for the component package (`pnpm build:component:types`).
-  // The root tsconfig only type-checks; this one emits `.d.ts` files, and nothing
-  // else, for everything the component's entry point reaches. The layout under
-  // `dist/types` mirrors the repository (`component/index.d.ts`, `src/…`), which
-  // is what `package.json` points its `types` at.
-  "extends": "../tsconfig.json",
-  "compilerOptions": {
-    "noEmit": false,
-    "emitDeclarationOnly": true,
-    "declaration": true,
-    "declarationMap": false,
-    "rootDir": "..",
-    "outDir": "./dist/types"
-  },
-  // The entry point, plus the ambient declarations (CSS modules, `?react` SVGs,
-  // `import.meta.env`, …) that the sources it reaches rely on.
-  "include": ["./index.tsx", "../src/@types/*.d.ts"],
-  "exclude": []
-}

config/config.devenv.json

@@ -1,14 +1,15 @@
 {
   "default_server_config": {
     "m.homeserver": {
-      "base_url": "https://synapse.m.localhost",
-      "server_name": "synapse.m.localhost"
+      "base_url": "http://synapse.localhost:8008",
+      "server_name": "synapse.localhost"
     }
   },
-  "ssla": "https://static.element.io/legal/element-software-and-services-license-agreement-uk-1.pdf",
-  "matrix_rtc_session": {
-    "wait_for_key_rotation_ms": 3000,
-    "membership_event_expiry_ms": 180000000,
-    "network_error_retry_ms": 100
-  }
+  "livekit": {
+    "livekit_service_url": "http://localhost:8009"
+  },
+  "features": {
+    "feature_use_device_session_member_events": true
+  },
+  "eula": "https://static.element.io/legal/online-EULA.pdf"
 }

config/config.sample.json

@@ -8,11 +8,8 @@
   "livekit": {
     "livekit_service_url": "https://livekit-jwt.mydomain.com"
   },
-  "ssla": "https://static.element.io/legal/element-software-and-services-license-agreement-uk-1.pdf",
-  "matrix_rtc_mode": "compatibility",
-  "matrix_rtc_session": {
-    "wait_for_key_rotation_ms": 3000,
-    "membership_event_expiry_ms": 180000000,
-    "network_error_retry_ms": 100
-  }
+  "features": {
+    "feature_use_device_session_member_events": true
+  },
+  "eula": "https://static.element.io/legal/online-EULA.pdf"
 }

config/config_netlify_preview.json

@@ -5,18 +5,18 @@
       "server_name": "call-unstable.ems.host"
     }
   },
-  "ssla": "https://static.element.io/legal/element-software-and-services-license-agreement-uk-1.pdf",
-  "matrix_rtc_session": {
-    "wait_for_key_rotation_ms": 3000,
-    "membership_event_expiry_ms": 180000000,
-    "network_error_retry_ms": 100
+  "livekit": {
+    "livekit_service_url": "https://livekit-jwt.call.element.dev"
+  },
+  "features": {
+    "feature_use_device_session_member_events": true
   },
   "posthog": {
     "api_key": "phc_rXGHx9vDmyEvyRxPziYtdVIv0ahEv8A9uLWFcCi1WcU",
     "api_host": "https://posthog-element-call.element.io"
   },
   "rageshake": {
-    "submit_url": "https://rageshakes.element.io/api/submit"
+    "submit_url": "https://element.io/bugreports/submit"
   },
   "sentry": {
     "environment": "netlify-pr-preview",

config/config_netlify_preview_sdk.json

@@ -1,14 +0,0 @@
-{
-  "default_server_config": {
-    "m.homeserver": {
-      "base_url": "https://call-unstable.ems.host",
-      "server_name": "call-unstable.ems.host"
-    }
-  },
-  "ssla": "https://static.element.io/legal/element-software-and-services-license-agreement-uk-1.pdf",
-  "matrix_rtc_session": {
-    "wait_for_key_rotation_ms": 3000,
-    "membership_event_expiry_ms": 180000000,
-    "network_error_retry_ms": 100
-  }
-}

config/otel_dev/README.md

@@ -1,12 +1,5 @@
 # OpenTelemetry Collector for development
 
-## Edit:
-
-Open telemetry has been removed in: https://github.com/element-hq/element-call/pull/3586
-Check this PR to get back the implementation or to use it as reference to add it back.
-
----
-
 This directory contains a docker compose file that starts a jaeger all-in-one instance
 with an in-memory database, along with a standalone OpenTelemetry collector that forwards
 traces into the jaeger. Jaeger has a built-in OpenTelemetry collector, but it can't be

dev-backend-docker-compose.yml

@@ -0,0 +1,86 @@
+networks:
+  ecbackend:
+
+services:
+  auth-service:
+    image: ghcr.io/element-hq/lk-jwt-service:latest-ci
+    hostname: auth-server
+    environment:
+      - LK_JWT_PORT=8080
+      - LIVEKIT_URL=ws://localhost:7880
+      - LIVEKIT_KEY=devkey
+      - LIVEKIT_SECRET=secret
+      # If the configured homeserver runs on localhost, it'll probably be using
+      # a self-signed certificate
+      - LIVEKIT_INSECURE_SKIP_VERIFY_TLS=YES_I_KNOW_WHAT_I_AM_DOING
+    deploy:
+      restart_policy:
+        condition: on-failure
+    ports:
+      # HOST_PORT:CONTAINER_PORT
+      - 8009:8080
+    networks:
+      - ecbackend
+
+  livekit:
+    image: livekit/livekit-server:latest
+    command: --dev --config /etc/livekit.yaml
+    restart: unless-stopped
+    # The SFU seems to work far more reliably when we let it share the host
+    # network rather than opening specific ports (but why?? we're not missing
+    # any…)
+    ports:
+      # HOST_PORT:CONTAINER_PORT
+      - 7880:7880/tcp
+      - 7881:7881/tcp
+      - 7882:7882/tcp
+      - 50100-50200:50100-50200/udp
+    volumes:
+      - ./backend/dev_livekit.yaml:/etc/livekit.yaml:Z
+    networks:
+      - ecbackend
+
+  redis:
+    image: redis:6-alpine
+    command: redis-server /etc/redis.conf
+    ports:
+      # HOST_PORT:CONTAINER_PORT
+      - 6379:6379
+    volumes:
+      - ./backend/redis.conf:/etc/redis.conf:Z
+    networks:
+      - ecbackend
+
+  synapse:
+    hostname: homeserver
+    image: docker.io/matrixdotorg/synapse:latest
+    environment:
+      - SYNAPSE_CONFIG_PATH=/data/cfg/homeserver.yaml
+      # Needed for rootless podman-compose such that the uid/gid mapping does
+      # fit local user uid. If the container runs as root (uid 0) it is fine as
+      # it actually maps to your non-root user on the host (e.g. 1000).
+      # Otherwise uid mapping will not match your non-root user.
+      - UID=0
+      - GID=0
+    volumes:
+      - ./backend/synapse_tmp:/data:Z
+      - ./backend/dev_homeserver.yaml:/data/cfg/homeserver.yaml:Z
+    networks:
+      - ecbackend
+
+  nginx:
+    #  openssl req -x509 -nodes -days 3650 -newkey rsa:2048 -keyout tls_localhost_key.pem -out tls_localhost_cert.pem -subj "/C=GB/ST=London/L=London/O=Alros/OU=IT Department/CN=localhost"
+    hostname: synapse.localhost
+    image: nginx:latest
+    volumes:
+      - ./backend/tls_localhost_nginx.conf:/etc/nginx/conf.d/default.conf:Z
+      - ./backend/tls_localhost_key.pem:/root/ssl/key.pem:Z
+      - ./backend/tls_localhost_cert.pem:/root/ssl/cert.pem:Z
+    ports:
+      # HOST_PORT:CONTAINER_PORT
+      - "8008:80"
+      - "4443:443"
+    depends_on:
+      - synapse
+    networks:
+      - ecbackend

docker-compose-dev.yml

@@ -1,183 +0,0 @@
-networks:
-  ecbackend:
-
-services:
-  auth-service:
-    image: ghcr.io/element-hq/lk-jwt-service:0.4.4
-    pull_policy: always
-    hostname: auth-server
-    environment:
-      - LIVEKIT_JWT_PORT=6080
-      - LIVEKIT_URL=wss://matrix-rtc.m.localhost/livekit/sfu
-      - LIVEKIT_KEY=devkey
-      - LIVEKIT_SECRET=secret
-      # If the configured homeserver runs on localhost, it'll probably be using
-      # a self-signed certificate
-      - LIVEKIT_INSECURE_SKIP_VERIFY_TLS=YES_I_KNOW_WHAT_I_AM_DOING
-      - LIVEKIT_FULL_ACCESS_HOMESERVERS=*
-    deploy:
-      restart_policy:
-        condition: on-failure
-    ports:
-      # HOST_PORT:CONTAINER_PORT
-      - 6080:6080
-    networks:
-      - ecbackend
-
-  auth-service-1:
-    image: ghcr.io/element-hq/lk-jwt-service:0.4.4
-    pull_policy: always
-    hostname: auth-server-1
-    environment:
-      - LIVEKIT_JWT_PORT=16080
-      - LIVEKIT_URL=wss://matrix-rtc.othersite.m.localhost/livekit/sfu
-      - LIVEKIT_KEY=devkey
-      - LIVEKIT_SECRET=secret
-      # If the configured homeserver runs on localhost, it'll probably be using
-      # a self-signed certificate
-      - LIVEKIT_INSECURE_SKIP_VERIFY_TLS=YES_I_KNOW_WHAT_I_AM_DOING
-      - LIVEKIT_FULL_ACCESS_HOMESERVERS=*
-    deploy:
-      restart_policy:
-        condition: on-failure
-    ports:
-      # HOST_PORT:CONTAINER_PORT
-      - 16080:16080
-    networks:
-      - ecbackend
-
-  livekit:
-    image: livekit/livekit-server:v1.13.4
-    pull_policy: always
-    hostname: livekit-sfu
-    command: --dev --config /etc/livekit.yaml
-    restart: unless-stopped
-    # The SFU seems to work far more reliably when we let it share the host
-    # network rather than opening specific ports (but why?? we're not missing
-    # any…)
-    ports:
-      # HOST_PORT:CONTAINER_PORT
-      - 7880:7880/tcp
-      - 7881:7881/tcp
-      - 7882:7882/tcp
-      - 50100-50200:50100-50200/udp
-    volumes:
-      - ./backend/dev_tls_m.localhost.crt:/local_cert.pem:Z
-      - ./backend/dev_livekit.yaml:/etc/livekit.yaml:Z
-    environment:
-      - SSL_CERT_FILE=/local_cert.pem
-    networks:
-      - ecbackend
-
-  livekit-1:
-    image: livekit/livekit-server:v1.13.4
-    pull_policy: always
-    hostname: livekit-sfu-1
-    command: --dev --config /etc/livekit.yaml
-    restart: unless-stopped
-    # The SFU seems to work far more reliably when we let it share the host
-    # network rather than opening specific ports (but why?? we're not missing
-    # any…)
-    ports:
-      # HOST_PORT:CONTAINER_PORT
-      - 17880:17880/tcp
-      - 17881:17881/tcp
-      - 17882:17882/tcp
-      - 50300-50400:50300-50400/udp
-    volumes:
-      - ./backend/dev_tls_m.localhost.crt:/local_cert.pem:Z
-      - ./backend/dev_livekit-othersite.yaml:/etc/livekit.yaml:Z
-    environment:
-      - SSL_CERT_FILE=/local_cert.pem
-    networks:
-      - ecbackend
-
-  synapse:
-    hostname: homeserver
-    image: ghcr.io/element-hq/synapse:latest
-    pull_policy: always
-    environment:
-      - SYNAPSE_CONFIG_PATH=/data/cfg/homeserver.yaml
-      # Needed for rootless podman-compose such that the uid/gid mapping does
-      # fit local user uid. If the container runs as root (uid 0) it is fine as
-      # it actually maps to your non-root user on the host (e.g. 1000).
-      # Otherwise uid mapping will not match your non-root user.
-      - UID=0
-      - GID=0
-    volumes:
-      - ./backend/synapse_tmp:/data:Z
-      - ./backend/dev_homeserver.yaml:/data/cfg/homeserver.yaml:Z
-    networks:
-      - ecbackend
-
-  synapse-1:
-    hostname: homeserver-1
-    image: ghcr.io/element-hq/synapse:latest
-    pull_policy: always
-    environment:
-      - SYNAPSE_CONFIG_PATH=/data/cfg/homeserver.yaml
-      # Needed for rootless podman-compose such that the uid/gid mapping does
-      # fit local user uid. If the container runs as root (uid 0) it is fine as
-      # it actually maps to your non-root user on the host (e.g. 1000).
-      # Otherwise uid mapping will not match your non-root user.
-      - UID=0
-      - GID=0
-    volumes:
-      - ./backend/synapse_tmp_othersite:/data:Z
-      - ./backend/dev_homeserver-othersite.yaml:/data/cfg/homeserver.yaml:Z
-    networks:
-      - ecbackend
-
-  element-web:
-    image: ghcr.io/element-hq/element-web:develop
-    pull_policy: always
-    volumes:
-      - ./backend/ew.test.config.json:/app/config.json:Z
-    environment:
-      ELEMENT_WEB_PORT: 8081
-    ports:
-      - "8081:8081"
-    networks:
-      - ecbackend
-
-  element-web-1:
-    image: ghcr.io/element-hq/element-web:develop
-    pull_policy: always
-    volumes:
-      - ./backend/ew.test.othersite.config.json:/app/config.json:Z
-    environment:
-      ELEMENT_WEB_PORT: 18081
-    ports:
-      # HOST_PORT:CONTAINER_PORT
-      - "18081:18081"
-    networks:
-      - ecbackend
-
-  nginx:
-    #  see backend/dev_tls_setup for how to generate the tls certs
-    hostname: synapse.m.localhost
-    image: nginx:latest@sha256:4ae259ae64fbedb67918c07d167fdcb0e05855a1615480ca445bea485e7d65ff
-    pull_policy: always
-    volumes:
-      - ./backend/dev_nginx.conf:/etc/nginx/conf.d/default.conf:Z
-      - ./backend/dev_tls_m.localhost.key:/root/ssl/key.pem:Z
-      - ./backend/dev_tls_m.localhost.crt:/root/ssl/cert.pem:Z
-    ports:
-      # HOST_PORT:CONTAINER_PORT
-      - "443:443"
-      - "8008:80"
-      - "4443:443"
-      - "8448:8448"
-    extra_hosts:
-      - "host.docker.internal:host-gateway"
-      - "auth-server:127.0.0.1"
-      - "auth-server-1:127.0.0.1"
-    depends_on:
-      - synapse
-    networks:
-      ecbackend:
-        aliases:
-          - synapse.m.localhost
-          - synapse.othersite.m.localhost
-          - matrix-rtc.m.localhost
-          - matrix-rtc.othersite.m.localhost

docker-compose-playwright.yml

@@ -1,19 +0,0 @@
-# This file contains overrides to docker-compose-dev.yml and should
-# only be used in combination with that file.
-services:
-  synapse:
-    # Pin to a SHA so that upstream cannot break our tests. Renovate handles regular updates.
-    image: ghcr.io/element-hq/synapse:latest@sha256:da325af40104051923899e5f5a2f1d537e6e3ccf2f0f38285689ae9bbfdb190a
-    volumes:
-      - ./backend/playwright_homeserver.yaml:/data/cfg/homeserver.yaml:Z
-  synapse-1:
-    # Pin to a SHA so that upstream cannot break our tests. Renovate handles regular updates.
-    image: ghcr.io/element-hq/synapse:latest@sha256:da325af40104051923899e5f5a2f1d537e6e3ccf2f0f38285689ae9bbfdb190a
-    volumes:
-      - ./backend/playwright_homeserver-othersite.yaml:/data/cfg/homeserver.yaml:Z
-  element-web:
-    # Pin to a SHA so that upstream cannot break our tests. Renovate handles regular updates.
-    image: ghcr.io/element-hq/element-web:develop@sha256:6ed62b2963ae098a1f79521eb516834dcf29452168e281cc359d9cfb4380adf6
-  element-web-1:
-    # Pin to a SHA so that upstream cannot break our tests. Renovate handles regular updates.
-    image: ghcr.io/element-hq/element-web:develop@sha256:6ed62b2963ae098a1f79521eb516834dcf29452168e281cc359d9cfb4380adf6

docs/README.md

@@ -1,20 +1,8 @@
 ## Element Call Docs
 
-This folder contains documentation for setup, usage, and development of Element Call.
+This folder contains documentation for Element Call setup and usage.
 
-- [Embedded vs standalone mode](./embedded_standalone.md)
-- [Element Call as a React component (experimental)](../README.md#element-call-as-a-component-experimental)
-- [Url format and parameters](./url_params.md)
+- [Embedded vs standalone mode](./embedded-standalone.md)
+- [Url format and parameters](./url-params.md)
 - [Global JS controls](./controls.md)
-- [MatrixRTC modes](./matrix_rtc_modes.md)
-- [Self-Hosting](./self_hosting.md)
-- [Developing with linked packages](./linking.md)
-
-### Writing code for Element Call (agent-readable conventions)
-
-Entry point: [AGENTS.md](../AGENTS.md).
-
-- [Agent workflow](./agents/workflow.md)
-- [Architecture](./agents/architecture.md)
-- [Code style](./agents/code-style.md)
-- [Testing](./agents/testing.md)
+- [Self-Hosting](./self-hosting.md)

docs/_developer.md

@@ -1,112 +0,0 @@
-# Developer help
-
-## Testing on Mobile Devices
-
-When developing Element Call locally, you may want to test on physical mobile devices (iOS/Android)
-on the same WiFi network.
-
-**Known Limitations:** For now this setup allows to use your local EC server but not yet the SFUs and Synapses.
-
-### Prerequisites
-
-1. **Start the dev server**
-
-   ```bash
-   pnpm dev
-   ```
-
-Check the output for the `➜  Network` (this will contain the local IP address of your laptop)
-
-```
-  ➜  Local:   https://m.localhost:3000/                                                                                                                                                                 12:06:48
-  ➜  Local:   https://vite.m.localhost:3000/                                                                                                                                                            12:06:48
-  ➜  Local:   https://vite.othersite.m.localhost:3000/                                                                                                                                                  12:06:48
-  ➜  Local:   https://vite.nip.io:3000/                                                                                                                                                                 12:06:48
-  ➜  Network: https://192.168.0.122:3000/
-```
-
-2. **Transfer the CA certificate to your phone**
-
-   The file is located at `backend/dev_tls_local-ca.crt`. Transfer it via:
-   - Matrix room
-   - AirDrop for iphone
-
-### IOS Setup
-
-**Install the certificate profile on iPhone**
-
-- Open the `dev_tls_local-ca.crt` file on your iPhone
-- You'll see "Profile Downloaded"
-- Go to **Settings → General → VPN & Device Management** (or **Settings → General → Profiles**)
-- Tap the "Element Call Dev CA" profile
-- Tap **Install** and enter your passcode
-- Confirm by tapping **Install** again
-
-**Enable full trust (Critical!)**
-
-- Go to **Settings → General → About → Certificate Trust Settings**
-- Under "Enable Full Trust for Root Certificates"
-- Toggle **ON** for "Element Call Dev CA"
-- Confirm the security warning
-
-**Access Element Call**
-
-Find your laptop's IP address (e.g., `192.168.0.122`) and use one of these URLs in Safari to validate:
-
-```
-https://192-168-0-122.nip.io:3000/
-```
-
-**For Element X iOS Developer Tools**
-
-In Element X's developer settings, set the Element Call URL to the nip.io url (replace . with - in the IP address):
-
-```
-https://192-168-0-122.nip.io:3000/room
-```
-
-### Android Setup
-
-**Transfer the CA certificate to your Android device**
-
-The file is located at `backend/dev_tls_local-ca.crt`.
-
-**Install the certificate**
-
-This might vary by Android version and manufacturer, but generally:
-
-- Open **Settings** search for "CA Certificate"/"Certificate"
-- Tap **Install a certificate** or **Install from storage**
-- Select **CA certificate**
-- Confirm the security warning
-- Navigate to and select the `dev_tls_local-ca.crt` file
-- Give it a name like "Element Call Dev CA"
-
-**Access Element Call**
-
-Find your laptop's IP address (e.g., `192.168.0.122`) and use one of these URLs in Chrome to validate:
-
-```
-https://192-168-0-122.nip.io:3000/
-```
-
-**For Element X Android Developer Tools**
-
-In Element X's developer settings, set the Element Call URL to the nip.io url (replace . with - in the IP address):
-
-```
-https://192-168-0-122.nip.io:3000/room
-```
-
-### Why nip.io?
-
-[nip.io](https://nip.io) is a free wildcard DNS service that automatically resolves domain names containing IP addresses. For example, `192-168-0-122.nip.io` automatically resolves to `192.168.0.122`. This means:
-
-- No need to regenerate certificates when your laptop's IP changes
-- Works from any device without DNS configuration
-- iOS/Android treat it as a proper domain name, not an IP address
-- One-time certificate setup works for all future IP addresses
-
-> [!IMPORTANT]
-> Make sure your network router doesn't enforce DNS rebinding protection (which will
-> break nip.io). If it does, try allow-listing nip.io in your router's administration interface.

docs/agents/architecture.md

@@ -1,79 +0,0 @@
-# Architecture
-
-## Logic lives in view models; components render
-
-- Call logic lives in `src/state/`. A component that derives call state is
-  misplaced logic.
-- Composing behaviors: a factory taking `(scope, ...deps$)`, returning named
-  behaviors plus callbacks. Copy `src/state/LayoutSwitchViewModel.ts`. Prefer this
-  for anything new.
-- Owning a resource: a class taking the scope in its constructor — `MediaDevices`,
-  `MuteStates`, `TileStore`, `Publisher`, `Connection`. Both styles are current;
-  don't convert one to the other in passing.
-- `foo$` is an observable. `Behavior<T>`, an observable with a current value, is
-  the default for anything a view reads.
-
-## The view model / view contract
-
-- Components take `vm: ViewModel<Snapshot>` and read state through `useBehavior`.
-  See `CallFooter`, `InCallView`, `LobbyView`, `SettingsModal`.
-- A snapshot is `Actions & State`; every field becomes a `foo$` behavior, and none
-  is optional.
-- An unavailable action is `undefined`, not a separate `canDoThing` flag — the
-  presence of the callback drives the rendering.
-- Subscribe in an effect only to drive a side effect off an event stream, as
-  `ReactionAudioRenderer` does; never to read state a behavior already holds.
-
-## Scopes own lifetimes
-
-- `ObservableScope` bounds every subscription a view model creates.
-- Reference only the scope defined in the same function; one captured from an
-  enclosing scope outlives its owner, and `no-observablescope-leak` rejects it.
-
-## Nothing reads the page
-
-Element Call can be mounted several times inside a host's React tree, so it owns
-neither window, URL, document nor router. Each seam defaults to the old standalone
-and widget behaviour.
-
-| Never                                         | Use                                                           |
-| --------------------------------------------- | ------------------------------------------------------------- |
-| the `widget` global                           | `useHostBridge()` — `src/HostBridge.ts`                       |
-| `getUrlParams()`, `window.location`           | `useUrlParams()`                                              |
-| `useNavigate("/")`, `<Link to="/">`           | `useLeaveToHome()`, `LeaveToHomeLink`                         |
-| `document.body`                               | `useRootElement()`                                            |
-| `window.innerWidth/Height`, `useMediaQuery`   | `useRootSizeMatches()` in views, `windowSize$` in view models |
-| global `i18next`                              | the instance in `src/utils/i18n.ts`                           |
-| config or analytics reading their environment | `Config.initWith()`, `PosthogAnalytics.configure()`           |
-
-- View models take values as options, never `getUrlParams()`
-  (`callViewModelOptionsFromParams`, `CallViewModelOptions.hostBridge`).
-- The host bridge is the only channel to the host: `createWidgetHostBridge(widget)`,
-  `nullHostBridge` standalone, `useComponentHostBridge`. State a capability
-  (`supportsReactions`, `supportsProfileChanges`); never infer it from being a
-  widget.
-- Shortcuts and portals attach to the root element, so two instances don't fight.
-- Known debt, not precedent: `Grid` measures `window.innerHeight`; `ErrorView`'s
-  reload and `getAbsoluteRoomUrl` use `window.location`; recaptcha appends to
-  `document.body` on the standalone login path.
-
-## Context differences are options, not checks
-
-- Named options with per-intent defaults (`configurationForIntent`), never a
-  runtime check for who is hosting.
-- `controlledAudioDevices`, not the platform, is what makes `MediaDevices` pick
-  `AndroidControlledAudioOutput` / `IOSControlledAudioOutput` over the web
-  `AudioOutput`. Intent presets set it on non-desktop; standalone leaves it off.
-- URL params are a published contract: change one, update `docs/url_params.md`.
-
-## Build targets
-
-Code that builds in only one is a bug.
-
-- `build:full` — standalone app, also widget mode.
-- `build:embedded` — `@element-hq/element-call-embedded`.
-- `build:sdk` — SDK library, entry `sdk/main.ts`.
-- `build:component` — `@element-hq/element-call-component`, sources in `component/`
-  (its own pnpm project; run pnpm from the repo root). Host API is in the README;
-  `pnpm lint:externals` rejects an import of a `react` / `react-dom` /
-  `matrix-js-sdk` / `livekit-client` subpath the externals list omits.

docs/agents/code-style.md

@@ -1,74 +0,0 @@
-# Code style
-
-_Clean Code_ (Robert C. Martin): small functions, intention-revealing names, low
-noise.
-
-## Reuse before you build
-
-Look before you write, in this order:
-
-1. **Compound Web** — `@vector-im/compound-web` for buttons, tooltips, alerts,
-   dialogs, menus, form controls, avatars; icons in
-   `@vector-im/compound-design-tokens/assets/web/icons`.
-2. **This repo** — `src/button/`, `src/components/`, `src/input/`, `src/form/`,
-   `src/tabs/`, and `Modal`, `Avatar`, `Toast`, `Slider`, `ErrorView`,
-   `FullScreenView` at the root of `src/`.
-3. **The nearest existing feature** — grep for the same shape first. A hook is
-   often what you want to extract, not a component.
-
-If nothing fits, name the new shared component in the PR body and say what you
-rejected and why — never add one silently. Extend or parameterise before forking,
-and extract shared logic into a hook both callers use before copying it; if you
-copy, the PR says so.
-
-## Ordering
-
-- **Newspaper order.** Headline first, detail down. A file opens with what it
-  exists to provide.
-- **Stepdown rule.** Caller above callee. A helper used by one function sits
-  beneath it, which needs a `function` declaration, not a `const` arrow. Existing
-  arrow components above their callers are not a pattern to extend — nor to churn.
-- **Suites.** Test cases first, helpers below. Older suites invert this; follow the
-  rule in new ones, don't reorder old ones.
-- **Names.** What a thing means, not what it is made of: `naturalLayout$`, not
-  `computedLayout$`. Comments explain why, never what.
-
-## TypeScript, React and RxJS idiom win on a clash
-
-- Hooks stay unconditional at the top of a component.
-- `useCallback` / `useMemo` dependency arrays sometimes force inlining.
-- An RxJS pipeline stays one expression. Name the behavior, not each operator.
-- A long factory is fine when it reads as a list of named behaviors.
-  `CallViewModel.ts` is long because the domain is.
-- Marble test tables are dense on purpose.
-
-## Enforced by lint
-
-- Copyright header on every file: `Copyright <current year> Element Creations Ltd.`
-  plus the AGPL / commercial SPDX line.
-- `logger` from `matrix-js-sdk/lib/logger`, never `console`, and no top-level
-  `logger.getChild()`. The `console` ban is only enforced under `src/*/**`.
-- No floating or misused promises; async functions typed `Promise<T>`.
-- Inline type imports (`import { type Foo }`), so matrix-js-sdk stays lazily
-  loadable.
-- Deep-import `matrix-js-sdk/lib/<module>` as the codebase does. Banned is the bare
-  `matrix-js-sdk/lib`, `lib/index` and anything under `src/`.
-
-## CSS
-
-- Compound components and `--cpd-*` tokens in CSS modules. A hardcoded colour or px
-  spacing is a design question, not a licence to inline a hex.
-- Size against the root, not the window: `@container element-call (…)` and
-  `cqw` / `cqh`, never `@media (width)` or `vw` / `vh`. Media queries stay correct
-  only in standalone-only views — home, login.
-- Style `[data-element-call-root]`, never `body` or `:root`; the component build
-  makes those stand for the root (`component/build/scopeStylesToRoot.ts`).
-
-## Strings and a11y
-
-- Strings through `t()`: add the key, run `pnpm i18n`, fill `locales/en/app.json`.
-  Other locales come from Localazy; never hand-edit them.
-- `t` from `useTranslation()`, or `src/utils/i18n.ts` outside React. Never the
-  `i18next` global — several instances share a page.
-- Accessible names on controls, `aria-pressed` on toggles, keyboard reachability.
-  `jsx-a11y` rules are errors; `vitest-axe` is available.

docs/agents/testing.md

@@ -1,51 +0,0 @@
-# Testing
-
-Three layers; a user-facing feature needs all three. Unit proves the logic,
-Storybook proves the rendering, e2e proves the feature. Codecov gates 80% on the
-lines a PR touches.
-
-## Unit
-
-- View model tests use `withTestScheduler` + `testScope()` from `src/utils/test.ts`
-  and read as ASCII timelines. Copy `LayoutSwitchViewModel.test.ts`.
-- Component tests use Testing Library, queried by role and accessible name.
-- Reuse the factories in `src/utils/test.ts` — `mockRemoteParticipant`,
-  `mockMatrixRoom`, `mockLivekitRoom`, `MockRTCSession`. Hand-rolled mocks drift.
-- Snapshots live in `__snapshots__/`; update with `pnpm test <Name> -u`.
-- `component/**/*.test.ts` runs in the same jsdom project as `src`.
-
-## Storybook
-
-A deliverable, not documentation: `pnpm test:storybook` runs every story as a real
-browser test in the same CI job as the unit suite. **A UI change without a story is
-incomplete.** Only three stories exist so far, so copy `CallFooter.stories.tsx`.
-
-- Drive the component from a snapshot via `useStaticViewModel`, never internals.
-- One named story per state that matters — loading, error, empty, denied, mobile.
-- Assert in a `play` function with `userEvent` / `expect` from `storybook/test`.
-- Mobile is `globals: { viewport: { value: "mobile2" } }`, not a second component.
-- Expose interesting props through `argTypes`.
-
-`.storybook/preview.tsx` supplies `TooltipProvider`, `src/index.css` and English
-translations. The browser is Playwright's, so a fresh clone needs
-`pnpm playwright install` once.
-
-## End-to-end
-
-- `playwright/*.spec.ts` — standalone, on Chromium and Firefox.
-- `playwright/widget/` — widget mode, where cross-context bugs surface.
-- `playwright/component/` — the component in a host page, via the harness on port
-  3001 that Playwright starts as a second web server. Catches container-relative
-  layout, styles escaping the root, two instances on a page, host-bridge reports.
-- `playwright/mobile/` — Pixel 7, `mobile` project only.
-
-Test what a user observes: the peer sees the change, it survives a reconnect, it is
-right after a reload. Reuse `playwright/spa-helpers.ts`,
-`playwright/widget/test-helpers.ts`, `playwright/fixtures/`.
-
-```sh
-pnpm test                   # unit + storybook
-pnpm backend                # Synapse + LiveKit, required for e2e
-pnpm test:playwright        # or :open
-pnpm dev:component          # component harness, port 3001
-```

docs/agents/workflow.md

@@ -1,48 +0,0 @@
-# Agent workflow
-
-## Scratch files live in `agent-workspace/`
-
-Git-ignored. One kebab-case subfolder per task, matching the branch topic:
-`agent-workspace/<slug>/`.
-
-| File                        | Purpose                                                                          |
-| --------------------------- | -------------------------------------------------------------------------------- |
-| `plan.md`                   | The concrete approach — files, symbols, edit order — once direction is confirmed |
-| `commit-msg.txt`            | `git commit -F agent-workspace/<slug>/commit-msg.txt`                            |
-| `pr-body.md`                | `gh pr create --body-file agent-workspace/<slug>/pr-body.md`                     |
-| `implementation-summary.md` | What was built, decisions, trade-offs                                            |
-| `NN-prompt.md`              | Raw prompt text, numbered, when worth keeping                                    |
-
-- Nothing here is durable. The folder is ignored, so anything worth keeping is
-  promoted into the PR body, a doc, or a feature spec before the task ends.
-- Never write scratch files to the repo root. Stray `load_test_summary.md` and
-  `config.json_` files are what this folder prevents.
-- Start `pr-body.md` from `.github/PULL_REQUEST_TEMPLATE.md` and fill every
-  section.
-- Commit subjects are plain imperative English. No conventional-commits prefixes.
-- A `plan.md` and a feature spec sit at different altitudes; neither replaces the
-  other. A spec in `FEATURES_SPEC/` is durable and deliberately abstract —
-  behaviour, decisions, acceptance criteria — so the feature can be rebuilt against
-  a `main` nobody has seen yet. A plan is one slice of it landing on today's
-  `main`: the paths, symbols and edit order the spec's decisions and criteria must
-  not name. `FEATURES_SPEC/AGENTS.md` wins wherever the two genuinely overlap.
-
-## Hand off before the quality pass
-
-- Implement the change, run the narrowest check that rules out an obviously broken
-  handoff, then stop and ask whether the direction is right.
-- Full `pnpm lint`, the whole suite, coverage and benchmarks come after the
-  direction is confirmed.
-- Wider refactors, extra tests and documentation polish are follow-up work, not
-  part of the first handoff.
-- If a check is needed before feedback, keep it to the touched code and say why.
-
-## Commit and PR readiness
-
-- Commit once the user confirms direction, or asks for one. Not before.
-- Before committing, every gate in [AGENTS.md](../../AGENTS.md#gates) is green and
-  the change is covered at the layers [testing.md](./testing.md) asks for. Read the
-  diff against [code-style.md](./code-style.md).
-- Re-run the whole checklist after any fix. Commit only on green.
-- Once a human has started reviewing, fix forward — never force-push a
-  regeneration over a review in progress.

docs/controls.md

@@ -1,34 +1,7 @@
 # Global JS controls
 
-A few aspects of Element Call's interface can be controlled through a global API on the `window`.
-
-## Picture-in-picture
+A few aspects of Element Call's interface can be controlled through a global API on the `window`:
 
 - `controls.canEnterPip(): boolean` Determines whether it's possible to enter picture-in-picture mode.
 - `controls.enablePip(): void` Puts the call interface into picture-in-picture mode. Throws if not in a call.
 - `controls.disablePip(): void` Takes the call interface out of picture-in-picture mode, restoring it to its natural display mode. Throws if not in a call.
-- `controls.onPipMediaOrientationUpdate: ((orientation: "landscape"|"portrait") => void) | undefined` Callback called whenever the PiP media orientation changes.
-  The client should track this value to already initiate the pip in the right orientation.
-  It should update the orientation of the current Pip window when called.
-
-## Audio devices
-
-On mobile platforms (iOS, Android), web views do not reliably support selecting audio output devices such as the main speaker, earpiece, or headset. To address this limitation, the following functions allow the hosting application (e.g., Element Web, Element X) to manage audio devices via exposed JavaScript interfaces. These functions must be enabled using the URL parameter `controlledAudioDevices` to take effect.
-
-- `controls.setAvailableAudioDevices(devices: { id: string, name: string, forEarpiece?: boolean, isEarpiece?: boolean isSpeaker?: boolean, isExternalHeadset?: boolean }[]): void` Sets the list of available audio outputs. `forEarpiece` is used on iOS only.
-  It flags the device that should be used if the user selects earpiece mode. This should be the main stereo loudspeaker of the device.
-- `controls.onAudioDeviceSelect: ((id: string) => void) | undefined` Callback called whenever the user or application selects a new audio output.
-- `controls.setAudioDevice(id: string): void` Sets the selected audio device in Element Call's menu. This should be used if the OS decides to automatically switch to Bluetooth, for example.
-- `controls.setAudioEnabled(enabled: boolean)` Enables/disables all audio output from the application. Output is enabled by default.
-- `controls.onAudioPlaybackStarted: ((id: string) => void) | undefined`: This will be called the first time we start
-  playing audio in the webview. It can be helpful to do device setup on the native app when the webviews audio is ready.
-  In particular android is using it to setup the output channel so that the call volume can
-  be controlled by the hardware volume rocker.
-
-## Element Call button delegation
-
-Callbacks for buttons in EC that are handled by the native application
-
-- `showNativeAudioDevicePicker: (() => void) | undefined`. Callback called whenever the user presses the output button in the settings menu.
-  This button is only shown on iOS. (`/iPad|iPhone|iPod|Mac/.test(navigator.userAgent)`)
-- `onBackButtonPressed: (() => void) | undefined`. Callback when the webview detects a tab on the header's back button.