chore: publish

- appium@3.6.0
 - @appium/base-driver@10.7.2
 - @appium/base-plugin@3.3.3
 - @appium/docutils@2.5.2
 - @appium/driver-test-support@2.0.1
 - @appium/eslint-config-appium-ts@3.2.4
 - @appium/execute-driver-plugin@6.0.7
 - @appium/fake-driver@6.2.2
 - @appium/fake-plugin@4.3.3
 - @appium/images-plugin@4.2.8
 - @appium/logger@2.0.10
 - @appium/opencv@4.1.7
 - @appium/oxc-config@1.1.0
 - @appium/plugin-test-support@2.0.1
 - @appium/relaxed-caps-plugin@2.2.5
 - @appium/schema@1.3.0
 - @appium/semantic-release-config@1.1.0
 - @appium/storage-plugin@1.1.8
 - @appium/strongbox@1.1.3
 - @appium/support@7.2.6
 - @appium/tsconfig@1.2.0
 - @appium/types@1.6.0
 - @appium/universal-xml-plugin@2.1.7

.claude/CLAUDE.md

@@ -0,0 +1,10 @@
+<!-- CODEGRAPH_START -->
+## CodeGraph
+
+In repositories indexed by CodeGraph (a `.codegraph/` directory exists at the repo root), reach for it BEFORE grep/find or reading files when you need to understand or locate code:
+
+- **MCP tool** (when available): `codegraph_explore` answers most code questions in one call — the relevant symbols' verbatim source plus the call paths between them, including dynamic-dispatch hops grep can't follow. Name a file or symbol in the query to read its current line-numbered source. If it's listed but deferred, load it by name via tool search.
+- **Shell** (always works): `codegraph explore "<symbol names or question>"` prints the same output.
+
+If there is no `.codegraph/` directory, skip CodeGraph entirely — indexing is the user's decision.
+<!-- CODEGRAPH_END -->

.claude/settings.json

@@ -0,0 +1,17 @@
+{
+  "permissions": {
+    "allow": ["mcp__codegraph__*"]
+  },
+  "hooks": {
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "codegraph prompt-hook"
+          }
+        ]
+      }
+    ]
+  }
+}

.codegraph/.gitignore

@@ -0,0 +1,5 @@
+# CodeGraph data files — local to each machine, not for committing.
+# Ignore everything in .codegraph/ except this file itself, so transient
+# files (the database, daemon.pid, sockets, logs) never show up in git.
+*
+!.gitignore

.cursor/mcp.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "codegraph": {
+      "type": "stdio",
+      "command": "codegraph",
+      "args": ["serve", "--mcp", "--path", "."]
+    }
+  }
+}

.editorconfig

@@ -8,6 +8,7 @@ end_of_line = lf
 charset = utf-8
 trim_trailing_whitespace = true
 insert_final_newline = true
+max_line_length = 120
 
 [*.md]
 trim_trailing_whitespace = false

.fossa.yml

@@ -29,8 +29,6 @@ targets:
       path: ./packages/fake-driver
     - type: npm
       path: ./packages/support
-    - type: npm
-      path: ./packages/test-support
     - type: npm
       path: ./packages/types
     - type: npm

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -3,7 +3,6 @@ description: Create a new bug report.
 title: '🐞 bug: <title>'
 labels: [Bug, Needs Triage]
 body:
-
   - type: markdown
     attributes:
       value: ':stop_sign: _Make sure you are reporting an issue. For general questions, please use [http://discuss.appium.io](http://discuss.appium.io)._'
@@ -13,9 +12,9 @@ body:
       label: Is there an existing issue for this?
       description: 'Please [search :mag: the issues](https://github.com/appium/appium/issues) to check if this bug has already been reported.'
       options:
-      - label: I have searched the existing issues
-        required: true
-  
+        - label: I have searched the existing issues
+          required: true
+
   - type: input
     attributes:
       label: Appium Version
@@ -49,7 +48,7 @@ body:
       description: |
         You can retrieve the latest server/driver/plugin version number by running `npm info <package-name> version`. If you are not up to date, please try to reproduce your issue after updating all affected components.
       options:
-      - label: I confirm the issue is still reproducible with the latest component versions
+        - label: I confirm the issue is still reproducible with the latest component versions
 
   - type: textarea
     attributes:
@@ -82,10 +81,10 @@ body:
 
         :warning: _Remember to redact or remove any sensitive information!_
       value: |
-          - Debug details (`appium --show-debug-info`):
-          - Last component version(s) which did _not_ exhibit the problem:
-          - Platform and version of device under test:
-          - Real device or emulator/simulator:
+        - Debug details (`appium --show-debug-info`):
+        - Last component version(s) which did _not_ exhibit the problem:
+        - Platform and version of device under test:
+        - Real device or emulator/simulator:
 
   - type: textarea
     attributes:

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: true
 contact_links:
-  - name: ❓ Question 
+  - name: ❓ Question
     url: https://discuss.appium.io/
     about: Please use the Appium forum for any questions.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,9 +1,8 @@
 name: 💡 Feature Request
 description: Suggest an idea for this project.
-title: "💡 feat: <title>"
+title: '💡 feat: <title>'
 labels: [Enhancement]
 body:
-
   - type: textarea
     attributes:
       label: Is your feature request related to a problem?

.github/actions/setup-build/action.yml

@@ -20,12 +20,12 @@ runs:
   using: composite
   steps:
     - name: Use Node.js ${{ inputs.node-version }}
-      uses: actions/setup-node@v6
+      uses: actions/setup-node@v7.0.0
       with:
         node-version: ${{ inputs.node-version }}
         cache: npm
     - name: SocketDev Security Check
-      uses: SocketDev/action@v1
+      uses: SocketDev/action@v1.3.2
       with:
         mode: firewall-free
     - name: Install dependencies

.github/copilot-instructions.md

@@ -0,0 +1,9 @@
+# Copilot Instructions
+
+## Code Review
+
+When reviewing JavaScript or TypeScript changes, check new uses of Node.js built-in APIs against the supported Node.js versions declared in package.json#engines.node. The current supported range is ^20.19.0 || ^22.12.0 || >=24.0.0.
+
+For each new Node.js built-in API or option, verify that it exists and is stable across all supported Node.js versions. If any supported version lacks the API, only supports it experimentally, or has different behavior, leave a review comment and suggest using the existing dependency, adding a fallback, avoiding the API, or raising the engine requirement.
+
+Example: util.styleText exists in Node.js 20.12+, but only became stable in Node.js 22.13.0 and 23.5.0. Because this repository supports Node.js 20.19.0 and 22.12.0, replacing a color library with util.styleText should be flagged unless the project explicitly accepts relying on a non-stable API for those supported versions.

.github/labeler.yml

@@ -73,6 +73,11 @@ labels:
     matcher:
       files: ['packages/eslint-config-appium-ts/**']
 
+  - label: '@appium/oxc-config'
+    sync: true
+    matcher:
+      files: ['packages/oxc-config/**']
+
   - label: '@appium/execute-driver-plugin'
     sync: true
     matcher:
@@ -118,6 +123,11 @@ labels:
     matcher:
       files: ['packages/schema/**']
 
+  - label: '@appium/semantic-release-config'
+    sync: true
+    matcher:
+      files: ['packages/semantic-release-config/**']
+
   - label: '@appium/support'
     sync: true
     matcher:
@@ -128,11 +138,6 @@ labels:
     matcher:
       files: ['packages/strongbox/**']
 
-  - label: '@appium/test-support'
-    sync: true
-    matcher:
-      files: ['packages/test-support/**']
-
   - label: '@appium/tsconfig'
     sync: true
     matcher:

.github/workflows/auto-labeler.yml

@@ -13,4 +13,4 @@ jobs:
     name: Auto-Label PRs
     runs-on: ubuntu-latest
     steps:
-      - uses: fuxingloh/multi-labeler@v4
+      - uses: fuxingloh/multi-labeler@v5.0.0

.github/workflows/build.yml

@@ -6,7 +6,7 @@ on:
     # this list of paths could potentially impact the build
     paths:
       - '**/tsconfig*.json'
-      - 'packages/base-driver/static/**/*'
+      - 'packages/base-driver/test-fixtures/**/*'
       - 'packages/*/test/**'
       - 'packages/*/bin'
       - 'packages/**/*.ts'
@@ -15,10 +15,9 @@ on:
       - 'package*.json'
       - 'lerna.json'
       - '.npmrc'
-      - '.mocharc.js'
       - '.github/workflows/build.yml' # this file
-      - '.eslintrc'
-      - '.eslintignore'
+      - 'oxlint.config.mjs'
+      - 'oxfmt.config.mjs'
       - '!**/sample-code/**'
       - '!packages/*/docs/**'
   pull_request:
@@ -26,7 +25,7 @@ on:
       - master
     paths:
       - '**/tsconfig*.json'
-      - 'packages/base-driver/static/**/*'
+      - 'packages/base-driver/test-fixtures/**/*'
       - 'packages/*/test/**'
       - 'packages/*/bin'
       - 'packages/**/*.ts'
@@ -35,10 +34,9 @@ on:
       - 'package*.json'
       - 'lerna.json'
       - '.npmrc'
-      - '.mocharc.js'
       - '.github/workflows/build.yml' # this file
-      - '.eslintrc'
-      - '.eslintignore'
+      - 'oxlint.config.mjs'
+      - 'oxfmt.config.mjs'
       - '!**/sample-code/**'
       - '!packages/*/docs/**'
 
@@ -61,7 +59,7 @@ jobs:
     outputs:
       packages: ${{ steps.discover-packages.outputs.packages }}
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Discover packages with e2e tests
         id: discover-packages
         run: |
@@ -103,14 +101,14 @@ jobs:
 
   test-smoke:
     needs:
-    - prepare_matrix
+      - prepare_matrix
     name: Smoke Tests
     strategy:
       matrix:
         node-version: ${{ fromJSON(needs.prepare_matrix.outputs.versions) }}
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Setup, install and build
         uses: ./.github/actions/setup-build
         with:
@@ -122,14 +120,14 @@ jobs:
 
   test-unit:
     needs:
-    - prepare_matrix
+      - prepare_matrix
     name: Unit Tests
     strategy:
       matrix:
         node-version: ${{ fromJSON(needs.prepare_matrix.outputs.versions) }}
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Setup, install and build
         uses: ./.github/actions/setup-build
         with:
@@ -141,14 +139,14 @@ jobs:
 
   test-types:
     needs:
-    - prepare_matrix
+      - prepare_matrix
     name: Type Tests
     strategy:
       matrix:
         node-version: ${{ fromJSON(needs.prepare_matrix.outputs.versions) }}
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Setup, install and build
         uses: ./.github/actions/setup-build
         with:
@@ -160,8 +158,8 @@ jobs:
 
   test-e2e:
     needs:
-    - prepare_matrix
-    - prepare_e2e_packages
+      - prepare_matrix
+      - prepare_e2e_packages
     name: E2E Tests - ${{ matrix.package_dir }} (Node ${{ matrix.node-version }})
     if: ${{ github.event_name == 'pull_request' }}
     strategy:
@@ -171,7 +169,7 @@ jobs:
         package_dir: ${{ fromJSON(needs.prepare_e2e_packages.outputs.packages) }}
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Setup, install and build
         uses: ./.github/actions/setup-build
         with:
@@ -188,12 +186,14 @@ jobs:
     name: Lint
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Setup and install (no build)
         uses: ./.github/actions/setup-build
         with:
           node-version: lts/*
           install-command: npm ci
           run-build: 'false'
-      - name: ESLint
+      - name: Lint
         run: npm run lint:ci
+      - name: Format check
+        run: npm run format:check

.github/workflows/clean-cache.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out code
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7.0.1
 
       - name: Cleanup
         run: |

.github/workflows/crowdin-stats.yml

@@ -21,9 +21,9 @@ jobs:
             project_name: appium-inspector
 
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Use Node.js LTS
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7.0.0
         with:
           node-version: lts/*
           cache: 'npm'
@@ -36,7 +36,7 @@ jobs:
           CROWDIN_PROJECT_ID: ${{ vars[matrix.project_id_var] }}
           CROWDIN_TOKEN: ${{ secrets.CROWDIN_DOCS_TOKEN }}
       - name: Post to Slack for ${{ matrix.project_name }}
-        uses: slackapi/slack-github-action@v2.1.1
+        uses: slackapi/slack-github-action@v4.0.0
         with:
           errors: true
           webhook: ${{ secrets.SLACK_WEBHOOK_URL }}

.github/workflows/crowdin-sync-docs-translations.yml

@@ -12,11 +12,11 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
         with:
           persist-credentials: false
       - name: Use Node.js LTS
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7.0.0
         with:
           node-version: lts/*
           cache: 'npm'
@@ -29,7 +29,7 @@ jobs:
           CROWDIN_PROJECT_ID: ${{ vars.CROWDIN_DOCS_PROJECT_ID }}
           CROWDIN_TOKEN: ${{ secrets.CROWDIN_DOCS_TOKEN }}
       - name: Create Pull Request
-        uses: peter-evans/create-pull-request@v7.0.9
+        uses: peter-evans/create-pull-request@v8.1.1
         with:
           token: ${{ github.token }}
           commit-message: 'docs(appium): Update documentation translations'

.github/workflows/crowdin-update-docs-resources.yml

@@ -15,9 +15,9 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Use Node.js LTS
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7.0.0
         with:
           node-version: lts/*
           cache: 'npm'

.github/workflows/deploy.yml

@@ -14,13 +14,13 @@ jobs:
     outputs:
       versions: ${{ steps.generate-matrix.outputs.lts }}
     steps:
-    - name: Select all current LTS versions of Node.js
-      id: generate-matrix
-      uses: msimerson/node-lts-versions@v1
+      - name: Select all current LTS versions of Node.js
+        id: generate-matrix
+        uses: msimerson/node-lts-versions@v2.0.2
 
   check:
     needs:
-    - prepare_matrix
+      - prepare_matrix
     name: Check
     runs-on: ${{ matrix.os }}
     strategy:
@@ -29,7 +29,7 @@ jobs:
         os: [ubuntu-latest, windows-latest, macos-latest]
     steps:
       - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7.0.0
         with:
           node-version: ${{ matrix.node-version }}
       - name: Install Appium

.github/workflows/docs.yml

@@ -37,9 +37,9 @@ jobs:
     name: Docs
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Install dependencies (Node.js)
-        uses: bahmutov/npm-install@v1
+        uses: bahmutov/npm-install@v1.12.1
         with:
           useRollingCache: true
           install-command: npm ci

.github/workflows/fossa.yml

@@ -13,11 +13,11 @@ jobs:
     env:
       FOSSA_API_KEY: ${{secrets.FOSSA_API_KEY}}
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
         with:
           ref: master
       - name: Install dependencies
-        uses: bahmutov/npm-install@v1
+        uses: bahmutov/npm-install@v1.12.1
       - name: Install fossa-cli
         run: |
           curl -H 'Cache-Control: no-cache' https://raw.githubusercontent.com/fossas/fossa-cli/master/install-latest.sh | bash

.github/workflows/github-contrib-stats.yml

@@ -14,9 +14,9 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Use Node.js LTS
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7.0.0
         with:
           node-version: lts/*
           cache: 'npm'
@@ -29,7 +29,7 @@ jobs:
           # GITHUB_TOKEN is optional - if not provided, uses unauthenticated requests (rate limited)
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       - name: Post to Slack
-        uses: slackapi/slack-github-action@v2.1.1
+        uses: slackapi/slack-github-action@v4.0.0
         with:
           errors: true
           webhook: ${{ secrets.SLACK_WEBHOOK_URL }}

.github/workflows/manual-release.yml

@@ -0,0 +1,137 @@
+name: Appium Server Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: 'Dry run (no publishing or tagging)'
+        required: true
+        type: boolean
+        default: true
+
+permissions:
+  contents: write
+  pull-requests: write
+  issues: write
+  id-token: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/master' && contains(fromJSON('["mykola-mokhnach", "jlipps", "eglitise", "KazuCocoa"]'), github.actor)
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v7.0.1
+        with:
+          fetch-depth: 0
+
+      - name: Configure git user
+        run: |
+          git config user.name "github-actions"
+          git config user.email "github-actions@github.com"
+
+      - name: Setup Node and install deps (LTS)
+        uses: ./.github/actions/setup-build
+        with:
+          node-version: lts/*
+          install-command: npm ci
+          run-build: 'true'
+
+      - name: Run Lerna publish
+        env:
+          # for lerna createRelease
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          DRY_RUN: ${{ inputs.dry_run }}
+        run: |
+          set -euo pipefail
+          if [ "$DRY_RUN" = "true" ]; then
+            echo "Running lerna publish in dry-run mode"
+            printf "n\n" | npx lerna version --exact --no-git-tag-version --no-push
+          else
+            echo "Running lerna publish for real"
+            set +e
+            release_output="$(npm run release -- --yes 2>&1)"
+            release_exit_code=$?
+            set -e
+            printf '%s\n' "$release_output"
+
+            if [ $release_exit_code -eq 0 ]; then
+              exit 0
+            fi
+
+            if [[ "$release_output" == *"fatal: tag '"*"' already exists"* ]]; then
+              existing_tag="$(printf '%s\n' "$release_output" | sed -n "s/.*fatal: tag '\\([^']*\\)' already exists.*/\\1/p" | head -n 1)"
+              if [ -z "$existing_tag" ]; then
+                echo "Detected existing tag failure, but could not parse tag name"
+                exit $release_exit_code
+              fi
+
+              echo "Detected existing tag failure for ${existing_tag}; attempting scoped publish recovery from tagged commit"
+              git fetch --tags --force origin
+              tagged_commit="$(git rev-list -n 1 "$existing_tag")"
+              if [ -z "$tagged_commit" ]; then
+                echo "Tag ${existing_tag} was not found after fetching tags"
+                exit $release_exit_code
+              fi
+
+              git checkout "$tagged_commit"
+              missing=()
+              for pkg_json in packages/*/package.json; do
+                if [ ! -f "$pkg_json" ]; then
+                  continue
+                fi
+
+                if [ "$(jq -r '.private // false' "$pkg_json")" = "true" ]; then
+                  continue
+                fi
+
+                pkg_name="$(jq -r '.name // empty' "$pkg_json")"
+                pkg_version="$(jq -r '.version // empty' "$pkg_json")"
+                if [ -z "$pkg_name" ] || [ -z "$pkg_version" ]; then
+                  echo "Skipping malformed package manifest: $pkg_json"
+                  continue
+                fi
+
+                pkg_spec="${pkg_name}@${pkg_version}"
+                if ! npm view "$pkg_spec" version >/dev/null 2>&1; then
+                  missing+=("$pkg_spec")
+                fi
+              done
+
+              if [ ${#missing[@]} -gt 0 ]; then
+                echo "Missing package versions on npm before scoped recovery:"
+                printf ' - %s\n' "${missing[@]}"
+                echo "Publishing missing packages one-by-one with scope"
+                for pkg_spec in "${missing[@]}"; do
+                  pkg_name="${pkg_spec%@*}"
+                  echo "Publishing ${pkg_name}"
+                  set +e
+                  npx lerna publish from-package --yes --scope "$pkg_name"
+                  scoped_exit_code=$?
+                  set -e
+                  if [ $scoped_exit_code -ne 0 ]; then
+                    echo "Scoped publish exited non-zero for ${pkg_name}; will verify on npm"
+                  fi
+                done
+
+                final_missing=()
+                for pkg_spec in "${missing[@]}"; do
+                  if ! npm view "$pkg_spec" version >/dev/null 2>&1; then
+                    final_missing+=("$pkg_spec")
+                  fi
+                done
+
+                if [ ${#final_missing[@]} -gt 0 ]; then
+                  echo "Recovery incomplete after scoped retries. Still missing:"
+                  printf ' - %s\n' "${final_missing[@]}"
+                  exit $release_exit_code
+                fi
+              fi
+
+              echo "All publishable workspace package versions are present on npm; treating recovery as successful."
+            else
+              echo "Release failed and no known recovery condition matched"
+              exit $release_exit_code
+            fi
+          fi

.github/workflows/manual-version.yml

@@ -0,0 +1,41 @@
+# This job only publishes new releases on GitHub and updates the changelog, without publishing to NPM.
+# It can be used if the standard release workflow failed and *only* published to NPM.
+
+name: Appium Server Version (Without NPM Publish)
+
+on:
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pull-requests: write
+  issues: write
+  id-token: write
+
+jobs:
+  version:
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/master' && contains(fromJSON('["mykola-mokhnach", "jlipps", "eglitise", "KazuCocoa"]'), github.actor)
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v7.0.1
+        with:
+          fetch-depth: 0
+
+      - name: Configure git user
+        run: |
+          git config user.name "github-actions"
+          git config user.email "github-actions@github.com"
+
+      - name: Setup Node and install deps (LTS)
+        uses: ./.github/actions/setup-build
+        with:
+          node-version: lts/*
+          install-command: npm ci
+          run-build: 'true'
+
+      - name: Run Lerna version
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: npx lerna version --exact --yes

.github/workflows/on-hold.yml

@@ -9,7 +9,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check for "On Hold" label
-        uses: egmacke/action-check-label@v4
+        uses: egmacke/action-check-label@v5
         with:
           label: On Hold
           state: absent

.github/workflows/publish-doc.yml

@@ -1,38 +1,32 @@
-# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
-# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs
-
 name: Publish docs
 
 on:
   workflow_dispatch:
+  workflow_run:
+    workflows: ['Appium Server Release']
+    types:
+      - completed
 
 jobs:
   build:
-
     runs-on: ubuntu-latest
 
-    strategy:
-      matrix:
-        node-version: [18.x]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-
     steps:
-    - uses: actions/checkout@v6
-    - run: |
-        git config user.name github-actions
-        git config user.email github-actions@github.com
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v6
-      with:
-        node-version: ${{ matrix.node-version }}
-    - name: Install dependencies (Node.js)
-      uses: bahmutov/npm-install@v1
-      with:
-        useRollingCache: true
-        install-command: npm ci
-    - name: Install dependencies (Python)
-      run: PIP_BREAK_SYSTEM_PACKAGES=1 pip install -r packages/docutils/requirements.txt
-    - name: Publish docs
-      run: |
-        cd packages/appium
-        npm run publish:docs
+      - uses: actions/checkout@v7.0.1
+      - run: |
+          git config user.name github-actions
+          git config user.email github-actions@github.com
+      - name: Setup Node and install deps (LTS)
+        uses: ./.github/actions/setup-build
+        with:
+          node-version: lts/*
+          install-command: npm ci
+          run-build: 'true'
+      - name: Install dependencies (Python)
+        run: npm run install-docs-deps
+      - name: Fetch gh-pages
+        run: |
+          git fetch origin gh-pages:gh-pages || true
+      - name: Publish docs
+        run: |
+          npm run docs:publish

.github/workflows/renovate.yml

@@ -23,8 +23,8 @@ jobs:
     name: Check Renovate Configs
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7.0.1
       - name: Validate Renovate Config
-        uses: rinchsan/renovate-config-validator@v0.2.0
+        uses: rinchsan/renovate-config-validator@v0.2.1
         with:
           pattern: '{.renovaterc.json,renovate/default.json}'

.lintstagedrc.js

@@ -1,10 +0,0 @@
-module.exports = {
-  '*.(js|ts)': ['eslint --fix', 'prettier --write'],
-  'appium-config-schema.js': () => [
-    'npm run --workspace=./packages/schema build',
-    'git add -A packages/schema/lib/appium-config.schema.json',
-    'npm run --workspace=./packages/types build',
-    'git add -A packages/types/lib/appium-config.ts',
-  ],
-  '!(package|package-lock)*.json': ['prettier --write'],
-};

.mcp.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "codegraph": {
+      "type": "stdio",
+      "command": "codegraph",
+      "args": ["serve", "--mcp"]
+    }
+  }
+}

.mocharc.js

@@ -1,11 +0,0 @@
-// @ts-check
-
-'use strict';
-
-module.exports = {
-  require: ['ts-node/register'],
-  // forbids use of .only() in CI
-  forbidOnly: Boolean(process.env.CI),
-  color: true,
-  timeout: '5s',
-};

.prettierignore

@@ -1,15 +0,0 @@
-**/node_modules/**
-**/build/**
-**/fixtures/**
-**/*.min.*
-**/*.md
-package-lock.json
-package.json
-**/.vscode/**
-**/*.html
-**/generated/**
-# generated
-packages/types/lib/appium-config.ts
-**/*.hbs
-
-/.nx/workspace-data

.renovaterc.json

@@ -1,9 +1,6 @@
 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
   "extends": ["github>appium/appium//renovate/default"],
-  "schedule": [
-    "after 10pm",
-    "before 5:00am"
-  ],
+  "schedule": ["after 10pm", "before 5:00am"],
   "timezone": "America/Vancouver"
 }

CHANGELOG.md

@@ -33,7 +33,6 @@ to driver/client documentation
 * [schema](packages/schema/CHANGELOG.md)
 * [strongbox](packages/strongbox/CHANGELOG.md)
 * [support](packages/support/CHANGELOG.md)
-* [test-support](packages/test-support/CHANGELOG.md)
 * [tsconfig](packages/tsconfig/CHANGELOG.md)
 * [types](packages/types/CHANGELOG.md)
 
@@ -42,4 +41,5 @@ The changelog links used for these modules lead to the last version of their cha
 * [doctor](https://github.com/appium/appium/blob/8daf5e123ac14c8325acf504fb33eb28e1a3dd78/packages/doctor/CHANGELOG.md) ([removal PR](https://github.com/appium/appium/pull/20805))
 * [eslint-config-appium](https://github.com/appium/appium/blob/4b3a8c2197a587ec5a2606b662e4e7667a7852cb/packages/eslint-config-appium/CHANGELOG.md) ([removal PR](https://github.com/appium/appium/pull/20856))
 * [gulp-plugins](https://github.com/appium/appium/blob/0823f0b60e40395cd1dc3b72cfa3c0092bc81302/packages/gulp-plugins/CHANGELOG.md) ([removal PR](https://github.com/appium/appium/pull/17943))
+* [test-support](https://github.com/appium/appium/blob/1a46d7d61ee49c7e82a63687c5647c42ab69513d/packages/test-support/CHANGELOG.md) ([removal PR](https://github.com/appium/appium/pull/22351))
 * [typedoc-plugin-appium](https://github.com/appium/appium/blob/d6204b6902074210943d7bbbf72d139b9b170a20/packages/typedoc-plugin-appium/CHANGELOG.md) ([removal PR](https://github.com/appium/appium/pull/19465))

CONDUCT.md

@@ -1,48 +0,0 @@
-## Code of Conduct
-
-### What is this code of conduct for?
-
-Appium is a piece of technology, but **the core of the Appium community is the people in it**. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, gender identity and expression, sexual orientation, ability, physical appearance, body size, race, age, socioeconomic status, religion (or lack thereof), or other marginalized aspect of community members. We expect all members of the Appium community to abide by this Code of Conduct whenever interacting in Appium venues (pull requests, GitHub issues, 1-1 or group chat, meetups, conferences, etc...)
-
-### Examples of inappropriate behavior
-
-Because we come from a variety of backgrounds, we don't want to assume that everyone has the same assumptions about what is and isn't appropriate. Here are some examples of inappropriate behavior that are incompatible with our community's ethos:
-
-* Spamming, trolling, intentionally disrupting conversations, or irrelevant solicitation or advertisement
-* Making demeaning or discriminatory comments
-* Making negative assumptions about someone's background, abilities, or intentions
-* Harassing or stalking individuals (online or in person)
-* Giving someone unwelcome sexual attention or making unwelcome physical contact (in the case of an IRL event)
-* Sharing sexual images or using sexually explicit language
-
-In general: treat others how you would like to be treated, were you in their place. Don't be a jerk. _Do_ ask questions. _Do_ keep conflicts productively focused on technical issues. _Do_ think before you speak; remember that what is perceived as a funny witticism in your group of friends might be hurtful or reinforce hurtful stereotypes in the context of our diverse online community. _Do_ remember that we are all people, not robots, and all equally deserving of sensitivity and respect. (If and when robots join our community, let's treat them with respect too!)
-
-
-### What will organizers do about inappropriate behavior?
-
-If we notice you doing or saying something inappropriate, an organizer will explain why it's inappropriate and ask you to stop. We won't demonize or vilify you. But please do stop the inappropriate behavior so we can get back to writing and discussing code in a safe environment. If you have philosophical disagreements about what's actually inappropriate, please take them to a separate public or private conversation with an Appium maintainer so we don't turn pull requests into an ethics debate.
-
-If you keep doing unacceptable things, we'll likely ban you, report you to GitHub, or take other appropriate action.
-
-### What if I see or am subject to what feels like inappropriate behavior?
-
-Let us know! Please notify a community organizer as soon as possible. Full contact information is listed in the [Contact Info](#contact-info) section of this document. All communications will be kept strictly confidential, unless otherwise required by law. No issue will be considered too inconsequential or unimportant for us to have a conversation about.
-
-### Contact Info
-
-If you need to report an incident, please contact any of the following organizers directly:
-
-* Isaac Murchie [email](mailto:isaac@saucelabs.com) [twitter](https://twitter.com/imurchie)
-* Jonathan Lipps [email](mailto:jlipps@saucelabs.com) [twitter](https://twitter.com/jlipps)
-
-### Credit, License, and Attribution
-
-This Code of Conduct is distributed under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).
-
-It's inspired among other things by:
-* [Citizen Code of Conduct](http://citizencodeofconduct.org/)
-* [npmjs](https://www.npmjs.com/policies/conduct)
-* [Geek Feminism](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy)
-* [Ashe Dryden](http://www.ashedryden.com/blog/codes-of-conduct-101-faq)
-* [Model View Culture](https://modelviewculture.com/issues/events)
-* [Open Source & Feelings](http://osfeels.com/conduct).

GOVERNANCE.md

@@ -50,18 +50,22 @@ The current committers are (along with their primary areas(s) of ownership or ma
 
 * [@dan-maor](https://github.com/Dan-Maor) - XCUITest driver and iOS internals
 * [@dor-bl](https://github.com/Dor-bl) - DotNet client
+* [@Delta456](https://github.com/Delta456) - appium-mcp, iOS support libraries
 * [@eglitise](https://github.com/eglitise) - Appium server, Inspector
+* [@harsha509](https://github.com/harsha509) - appium-ios-tuntap
 * [@jlipps](https://github.com/jlipps) - Appium server, Inspector
 * [@kazucocoa](https://github.com/KazuCocoa) - all Appium projects
 * [@laolubenson](https://github.com/laolubenson) - DotNet client
 * [@mwakizaka](https://github.com/mwakizaka) - XCUITest driver
 * [@mykola-mokhnach](https://github.com/mykola-mokhnach) - all Appium projects
+* [@navin772](https://github.com/navin772) - appium-mcp, iOS support libraries
 * [@rerorero](https://github.com/rerorero) - XCUITest/UIA2 driver
 * [@saikrishna321](https://github.com/saikrishna321) - Java client
 * [@srinivasantarget](https://github.com/SrinivasanTarget) - Java client
 * [@tomriddly](https://github.com/tomriddly) - appium-ios-device
 * [@valfirst](https://github.com/valfirst) - Java client
 
+
 See [Emeritus Contributors](#emeritus-contributors) below for a list of people who formerly made
 significant contributions to the project but are no longer actively committing.
 

IDEAS.md

@@ -1,16 +0,0 @@
-Google Summer of Code Ideas
-=====
-
-Appium is excited to participate as a [Google Summer of Code](https://summerofcode.withgoogle.com/) sponsor project. Here's a fun list of ideas that a Summer of Code student participant can use as a foundation for thinking about what to contribute to Appium!
-
-|Idea|Description|
-|----|-----------|
-|Apple tvOS Support|Our users have been asking for an Appium driver for Apple tvOS apps. Is this possible? We're not entirely sure! Why not be awesome and build it?|
-|Test App revamp|Appium uses a number of poorly-designed mobile applications in its own testing. We have to use a variety of apps because we need to test that Appium can automate all the various controls and platform features that mobile vendors provide. Really what we need is one cross-platform app (or one app per platform) that exhibit all and only the features we need to test. This would be a fun project to build some mobile apps used for testing and also demoing Appium at events and in training videos, etc...|
-|Tooling and Performance|We haven't instrumented Appium with very many performance metrics, and don't really know if we're missing some low-hanging fruit in terms of performance. Maybe you can help us do that?|
-|Babel|We have a lot of repos, and they're all on a really old version of Babel. They all need to stay in sync. How can we make this situation better, and upgrade to the latest and greatest?|
-|Unity3d Driver|Historically, Appium hasn't been great at automating games. We don't have any particular support for the frameworks used to create games. Unity is a popular one, for example. What if we could write an Appium driver that talked to an embedded process in a test version of a Unity game, that allowed us to find and interact with 3d elements? It would be amazing! You can also be amazing and lead Appium into this new world.|
-|Testing the Internet of Things|Appium's architecture makes it dead simple to integrate drivers for automating new technologies. What about _really_ new technologies like IoT devices? Help to redefine the semantics of the WebDriver protocol for use with IoT, and build a driver for an IoT device to prove it out.|
-|Driver for X|Have an idea of something else Appium could automate that it doesn't already? Build a driver for it! This would involve some awesome Node.js code, plus whatever else is needed to integrate with the platform you have in mind.|
-
-Hopefully this gives you some ideas of fun projects that would be substantial and long-lasting contributions to the Appium community.

README.md

@@ -199,11 +199,11 @@ contribution of project development and leadership!
 </p>
 
 <p align="center">
-  <a href="https://lambdatest.com/?utm_source=appium.io&utm_medium=organic&utm_campaign=june_25&utm_term=sk&utm_content=webpage">
+  <a href="https://www.testmuai.com">
     <picture>
-      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-lambdatest-dark.png" media="(prefers-color-scheme: dark)"/>
-      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-lambdatest-light.png" media="(prefers-color-scheme: light)"/>
-      <img src="packages/appium/docs/overrides/assets/images/sponsor-logo-lambdatest-dark.png" width="300" alt="LambdaTest"/>
+      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-testmuai-dark.png" media="(prefers-color-scheme: dark)"/>
+      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-testmuai-light.png" media="(prefers-color-scheme: light)"/>
+      <img src="packages/appium/docs/overrides/assets/images/sponsor-logo-testmuai-dark.png" width="300" alt="TestMu AI (formerly LambdaTest)"/>
     </picture>
   </a>
 </p>

eslint.config.mjs

@@ -1,24 +1,38 @@
-import tsConfig from '@appium/eslint-config-appium-ts';
+import appiumConfig from '@appium/eslint-config-appium-ts';
+import {defineConfig, globalIgnores} from 'eslint/config';
 
-export default [
-  ...tsConfig,
+// Create a modified config subset for test support files:
+// Extract the test file related configs (Mocha plugin and custom rules),
+// then override their 'files' property (match by name — resilient to new config entries).
+const testFileConfigItems = appiumConfig.filter(
+  (item) => typeof item?.name === 'string' && item.name.startsWith('Test Files'),
+);
+const testSupportFiles = ['packages/driver-test-support/lib/**', 'packages/plugin-test-support/lib/**'];
+const testSupportConfig = testFileConfigItems.map((item) => ({...item, files: testSupportFiles}));
+
+export default defineConfig([
+  {
+    name: 'Base Config',
+    extends: [appiumConfig],
+  },
   {
-    ...tsConfig.find(({name}) => name === 'Test Files'),
     name: 'Test Support',
-    files: [
-      'packages/test-support/lib/**',
-      'packages/driver-test-support/lib/**',
-      'packages/plugin-test-support/lib/**',
-    ],
+    extends: [testSupportConfig],
   },
   {
-    name: 'Ignores',
-    ignores: [
-      '**/build-fixtures/**',
-      'packages/appium/docs/**/assets/**',
-      'packages/appium/docs/**/js/**',
-      'packages/appium/sample-code/**',
-    ],
+    name: 'Consistent type-only imports (all packages)',
+    files: ['**/*.{ts,tsx,mtsx}'],
+    rules: {
+      '@typescript-eslint/consistent-type-imports': [
+        'error',
+        {fixStyle: 'separate-type-imports', prefer: 'type-imports'},
+      ],
+    },
   },
-];
-
+  globalIgnores([
+    '**/build-fixtures/**',
+    'packages/appium/docs/**/assets/**',
+    'packages/appium/docs/**/js/**',
+    'packages/appium/sample-code/**',
+  ]),
+]);

lerna.json

@@ -14,7 +14,8 @@
     "version": {
       "conventionalCommits": true,
       "createRelease": "github",
-      "allowBranch": ["master", "appium3"]
+      "allowBranch": ["master", "appium3"],
+      "exact": true
     }
   },
   "ignoreChanges": ["**/test/**", "**/*.md"],

oxfmt.config.mjs

@@ -0,0 +1,11 @@
+import appiumConfig, {defineConfig, ignorePatterns as appiumIgnorePatterns} from '@appium/oxc-config/oxfmt';
+
+export default defineConfig({
+  ...appiumConfig,
+  ignorePatterns: [
+    ...appiumIgnorePatterns,
+    'packages/appium/docs/**',
+    'packages/schema/lib/appium-config.schema.json',
+    'packages/types/lib/appium-config.ts',
+  ],
+});

oxlint.config.mjs

@@ -0,0 +1,11 @@
+import appiumConfig, {defineConfig, ignorePatterns as appiumIgnorePatterns} from '@appium/oxc-config/oxlint';
+
+export default defineConfig({
+  extends: [appiumConfig],
+  ignorePatterns: [
+    ...appiumIgnorePatterns,
+    'packages/appium/docs/**/assets/**',
+    'packages/appium/docs/**/js/**',
+    'packages/appium/sample-code/**',
+  ],
+});

package.json

@@ -4,28 +4,31 @@
   "private": true,
   "description": "Automation for Apps.",
   "keywords": [
+    "android",
     "automation",
+    "firefoxos",
+    "ios",
     "javascript",
     "selenium",
-    "webdriver",
-    "ios",
-    "android",
-    "firefoxos",
-    "testing"
+    "testing",
+    "webdriver"
   ],
   "homepage": "https://appium.io",
   "bugs": {
     "url": "https://github.com/appium/appium/issues"
   },
+  "license": "Apache-2.0",
+  "author": "https://github.com/appium",
   "repository": {
     "type": "git",
     "url": "https://github.com/appium/appium.git"
   },
-  "license": "Apache-2.0",
-  "author": "https://github.com/appium",
   "workspaces": [
     "packages/*"
   ],
+  "publishConfig": {
+    "access": "public"
+  },
   "scripts": {
     "build": "run-s build:*",
     "build:compile": "tsc -b",
@@ -47,9 +50,11 @@
     "docs:publish": "npm run -w packages/appium publish:docs",
     "doctor": "node ./scripts/doctor-stub.mjs",
     "install-docs-deps": "npm run -w packages/appium install-docs-deps",
-    "lint": "eslint .",
-    "lint:ci": "eslint --quiet .",
-    "lint:fix": "run-s \"lint -- --fix\"",
+    "format": "oxfmt -c oxfmt.config.mjs .",
+    "format:check": "oxfmt -c oxfmt.config.mjs --check .",
+    "lint": "oxlint -c oxlint.config.mjs .",
+    "lint:ci": "oxlint -c oxlint.config.mjs --quiet .",
+    "lint:fix": "oxlint -c oxlint.config.mjs --fix .",
     "prepare": "run-p rebuild",
     "prepublishOnly": "run-s rebuild",
     "preversion": "run-s rebuild",
@@ -57,119 +62,96 @@
     "rebuild": "run-s clean build",
     "reinstall": "run-s clean clean:deps ci",
     "reinstall:angry": "npm run clean:dangerously && npm ci",
-    "release": "lerna publish",
+    "release": "lerna publish --exact",
     "stage-synced-pkgs": "git add -A packages/appium/README.md \"packages/*/package.json\"",
     "start": "appium",
-    "sync-pkgs": "run-p sync-pkgs:*",
-    "sync-pkgs:appium-readme": "sync-monorepo-packages --force --no-package-json --packages=packages/appium README.md",
-    "sync-pkgs:common-fields:default": "sync-monorepo-packages --packages=\"!packages/logger\" --fields=author,license,bugs,homepage",
-    "sync-pkgs:common-fields:logger": "sync-monorepo-packages --packages=\"packages/logger\" --fields=author,bugs,homepage",
-    "sync-pkgs:keywords": "sync-monorepo-packages --field=keywords --packages=\"packages/*\" --packages=\"!packages/types\" --packages=\"!packages/eslint-config-appium-ts\" ",
-    "sync-pkgs:license": "sync-monorepo-packages --force --no-package-json --packages=\"!packages/logger\" LICENSE",
+    "sync-pkgs": "node ./scripts/sync-monorepo-packages.mjs",
     "test": "run-s test:quick",
     "test:ci": "run-s test:smoke test:unit test:types test:e2e",
     "test:e2e": "lerna run test:e2e",
     "test:quick": "run-s lint test:unit test:types",
     "test:slow": "run-s test:quick test:smoke test:e2e",
-    "test:smoke": "smoker --all test:smoke",
+    "test:smoke": "lerna run test:smoke",
     "test:types": "lerna run test:types",
     "test:unit": "lerna run test",
     "upload": "gulp github-upload",
     "zip": "zip -qr ./appium.zip ./packages/appium",
     "zip-and-upload": "run-s zip upload"
   },
-  "prettier": {
-    "bracketSpacing": false,
-    "printWidth": 100,
-    "singleQuote": true
-  },
   "devDependencies": {
-    "@colors/colors": "1.6.0",
-    "@eslint/js": "9.39.1",
-    "@tsconfig/node20": "20.1.8",
-    "@types/argparse": "2.0.17",
-    "@types/archiver": "7.0.0",
+    "@appium/oxc-config": "1.0.0",
+    "@eslint/js": "10.0.1",
+    "@stylistic/eslint-plugin": "5.10.0",
+    "@tsconfig/node20": "20.1.9",
     "@types/async-lock": "1.4.2",
-    "@types/base64-stream": "1.0.5",
     "@types/bluebird": "3.5.42",
     "@types/chai": "5.2.3",
     "@types/chai-as-promised": "8.0.2",
+    "@types/content-disposition": "0.5.9",
     "@types/express": "5.0.6",
+    "@types/finalhandler": "1.2.4",
     "@types/jsftp": "2.1.5",
     "@types/json-schema": "7.0.15",
     "@types/klaw": "3.0.7",
     "@types/lockfile": "1.0.4",
-    "@types/lodash": "4.17.21",
+    "@types/lodash": "4.17.24",
     "@types/method-override": "3.0.0",
-    "@types/mocha": "10.0.10",
+    "@types/morgan": "1.9.10",
     "@types/mv": "2.1.4",
-    "@types/ncp": "2.0.8",
-    "@types/node": "24.10.1",
+    "@types/node": "24.13.3",
+    "@types/plist": "3.0.5",
     "@types/pluralize": "0.0.33",
     "@types/semver": "7.7.1",
     "@types/serve-favicon": "2.5.7",
     "@types/shell-quote": "1.7.5",
-    "@types/sinon": "21.0.0",
+    "@types/sinon": "22.0.0",
     "@types/sinon-chai": "4.0.0",
-    "@types/source-map-support": "0.5.10",
-    "@types/supports-color": "8.1.3",
-    "@types/teen_process": "2.0.4",
     "@types/which": "3.0.4",
-    "@types/wrap-ansi": "3.0.0",
     "@types/ws": "8.18.1",
     "@types/xmldom": "0.1.34",
     "@types/yargs": "17.0.35",
-    "asyncbox": "3.0.0",
-    "chai": "6.2.1",
+    "asyncbox": "6.3.5",
+    "chai": "6.2.2",
     "chai-as-promised": "8.0.2",
     "conventional-changelog-conventionalcommits": "7.0.2",
-    "cpy-cli": "6.0.0",
+    "cpy-cli": "7.0.0",
     "cross-env": "10.1.0",
-    "eslint": "9.39.1",
+    "eslint": "10.7.0",
     "eslint-config-prettier": "10.1.8",
-    "eslint-import-resolver-typescript": "4.4.4",
-    "eslint-plugin-import": "2.32.0",
-    "eslint-plugin-mocha": "11.2.0",
-    "eslint-plugin-promise": "7.2.1",
+    "eslint-import-resolver-typescript": "4.4.5",
+    "eslint-plugin-import-x": "4.17.1",
+    "eslint-plugin-mocha": "11.3.0",
+    "eslint-plugin-n": "18.2.2",
+    "eslint-plugin-promise": "7.3.0",
     "finalhandler": "2.1.1",
-    "get-port": "5.1.1",
     "json-schema-to-typescript": "15.0.4",
-    "lerna": "9.0.3",
-    "log-symbols": "4.1.0",
-    "midnight-smoker": "8.0.0",
+    "lerna": "9.0.7",
     "mjpeg-consumer": "2.0.0",
     "mjpeg-server": "0.3.1",
-    "mocha": "11.7.5",
-    "npm-run-all2": "8.0.4",
-    "prettier": "3.7.4",
+    "npm-run-all2": "9.0.2",
     "rewiremock": "3.14.6",
-    "rimraf": "6.1.2",
-    "serve-static": "2.2.0",
-    "sinon": "21.0.0",
-    "sync-monorepo-packages": "1.0.2",
-    "teen_process": "3.0.4",
-    "ts-node": "10.9.2",
+    "rimraf": "6.1.3",
+    "serve-static": "2.2.1",
+    "sinon": "22.1.0",
+    "sinon-chai": "4.0.1",
+    "teen_process": "4.1.9",
     "tsd": "0.33.0",
-    "typescript": "5.9.3",
-    "typescript-eslint": "8.48.1",
-    "webdriverio": "9.21.0",
-    "ws": "8.18.3",
-    "yaml-js": "0.3.1"
+    "typescript": "6.0.3",
+    "typescript-eslint": "8.65.0",
+    "webdriverio": "9.29.1",
+    "ws": "8.21.1"
+  },
+  "overrides": {
+    "@sidvind/better-ajv-errors": {
+      "ajv": "8.20.0"
+    },
+    "ajv-formats": {
+      "ajv": "8.20.0"
+    },
+    "http-cache-semantics": "4.2.0"
   },
   "engines": {
     "node": "^20.19.0 || ^22.12.0 || >=24.0.0",
     "npm": ">=10"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "overrides": {
-    "@sidvind/better-ajv-errors": {
-      "ajv": "8.17.1"
-    },
-    "ajv-formats": {
-      "ajv": "8.17.1"
-    },
-    "http-cache-semantics": "4.2.0"
   }
 }

packages/appium/CHANGELOG.md

@@ -3,6 +3,132 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [3.6.0](https://github.com/appium/appium/compare/appium@3.5.2...appium@3.6.0) (2026-07-25)
+
+
+### Features
+
+* **appium:** add --allow-unknown-args to tolerate unrecognized server CLI arguments ([#22477](https://github.com/appium/appium/issues/22477)) ([f943fab](https://github.com/appium/appium/commit/f943fab1411826212cfb174e3847e610c25f37b7))
+
+
+### Bug Fixes
+
+* **appium:** Duplicated module import ([#22519](https://github.com/appium/appium/issues/22519)) ([154ea18](https://github.com/appium/appium/commit/154ea1825281335569f0d6952db527135c75e153))
+* typescript config ([#22540](https://github.com/appium/appium/issues/22540)) ([ea6a2e1](https://github.com/appium/appium/commit/ea6a2e117f56c1d7ff459378700494407c51608e))
+* Typescript references ([#22458](https://github.com/appium/appium/issues/22458)) ([fd70da7](https://github.com/appium/appium/commit/fd70da7ab407bf1f6fec8a3576b9a33f0aef9b69))
+
+
+
+## [3.5.2](https://github.com/appium/appium/compare/appium@3.5.1...appium@3.5.2) (2026-06-18)
+
+**Note:** Version bump only for package appium
+
+
+
+
+
+## [3.5.1](https://github.com/appium/appium/compare/appium@3.5.0...appium@3.5.1) (2026-06-18)
+
+
+### Bug Fixes
+
+* **storage-plugin:** add fs.sanitizeName for the delete request as well ([#22362](https://github.com/appium/appium/issues/22362)) ([5fee017](https://github.com/appium/appium/commit/5fee01752f2782e96fbe64fd13520b433d4a7535))
+
+
+
+## [3.5.0](https://github.com/appium/appium/compare/appium@3.4.2...appium@3.5.0) (2026-05-31)
+
+
+### Features
+
+* add IPC channels per session for drivers and plugins to communicate ([#22211](https://github.com/appium/appium/issues/22211)) ([97c879c](https://github.com/appium/appium/commit/97c879cdd02e6fcccaaea45a8d1a7088bed4ae66)), closes [#22206](https://github.com/appium/appium/issues/22206)
+* **appium:** Ditch bluebird ([#22301](https://github.com/appium/appium/issues/22301)) ([abb83bd](https://github.com/appium/appium/commit/abb83bde62e8beefdd9483a276ef2aa888722245))
+* Limit the maximum count of topics per session and make it configurable ([#22279](https://github.com/appium/appium/issues/22279)) ([0264775](https://github.com/appium/appium/commit/0264775ecb8ecaca9dac2eae47784da02a653255))
+* make assignIpc internal ([#22278](https://github.com/appium/appium/issues/22278)) ([25d922b](https://github.com/appium/appium/commit/25d922b7d3062c306c1631d6f5c227600ddd226a))
+
+
+
+## [3.4.2](https://github.com/appium/appium/compare/appium@3.4.1...appium@3.4.2) (2026-05-07)
+
+**Note:** Version bump only for package appium
+
+
+
+
+
+## [3.4.1](https://github.com/appium/appium/compare/appium@3.4.0...appium@3.4.1) (2026-05-06)
+
+**Note:** Version bump only for package appium
+
+
+
+
+
+## [3.4.0](https://github.com/appium/appium/compare/appium@3.3.1...appium@3.4.0) (2026-05-06)
+
+
+### Features
+
+* add 3 WebDriver extension endpoints ([#22237](https://github.com/appium/appium/issues/22237)) ([787571d](https://github.com/appium/appium/commit/787571d33836c06bb1332d7bc6cc2f9800bbdd82))
+
+
+
+## [3.3.1](https://github.com/appium/appium/compare/appium@3.3.0...appium@3.3.1) (2026-04-23)
+
+
+### Bug Fixes
+
+* **appium:** lint warnings ([#22171](https://github.com/appium/appium/issues/22171)) ([8e68b3e](https://github.com/appium/appium/commit/8e68b3e2c9c7b6238e0ffc241adbd4d9991ead7a))
+* **appium:** plugins caching per session ([#22203](https://github.com/appium/appium/issues/22203)) ([622f199](https://github.com/appium/appium/commit/622f1999d72d2f7ebc7cc279879ea0fcefe29a54))
+
+
+
+## [3.3.0](https://github.com/appium/appium/compare/appium@3.2.2...appium@3.3.0) (2026-04-09)
+
+
+### Features
+
+* use exact version for dependencies in monorepo packages instead of ^ ([#22090](https://github.com/appium/appium/issues/22090)) ([86c8f23](https://github.com/appium/appium/commit/86c8f23a670d0bbc2d359a8235828606bd36e6aa))
+
+
+
+## [3.2.2](https://github.com/appium/appium/compare/appium@3.2.1...appium@3.2.2) (2026-03-09)
+
+
+### Bug Fixes
+
+* **appium:** Exclude package.json from tsconfig ([#22052](https://github.com/appium/appium/issues/22052)) ([1d89e2a](https://github.com/appium/appium/commit/1d89e2a5f8e478f3331666d3c308427ab834471a))
+
+
+
+## [3.2.1](https://github.com/appium/appium/compare/appium@3.2.0...appium@3.2.1) (2026-03-08)
+
+
+### Bug Fixes
+
+* **appium:** Fix CLI arguments normalization ([#21945](https://github.com/appium/appium/issues/21945)) ([9ea601c](https://github.com/appium/appium/commit/9ea601c8330d35f45f0712e41867544d925a0f6b))
+* Avoid attaching plugins to a non-existing session ([#21964](https://github.com/appium/appium/issues/21964)) ([9f5faf5](https://github.com/appium/appium/commit/9f5faf5bedffe6196742c09c6793a6450af48ac9))
+* **logger:** Make sure we always have single logger instance per process ([#21991](https://github.com/appium/appium/issues/21991)) ([4daaa14](https://github.com/appium/appium/commit/4daaa14c29bed129d329d0881a93ecdb9de77676))
+* Type imports ([#22025](https://github.com/appium/appium/issues/22025)) ([2f27425](https://github.com/appium/appium/commit/2f27425ea300ca1af1c1da6e4be68d48e7a94346))
+
+
+
+## [3.2.0](https://github.com/appium/appium/compare/appium@3.1.2...appium@3.2.0) (2026-01-26)
+
+
+### Features
+
+* **appium:** Add repository links to verbose extensions list ([#21813](https://github.com/appium/appium/issues/21813)) ([ce91686](https://github.com/appium/appium/commit/ce91686852b0baab5f46990f5d40db4747922924))
+
+
+### Bug Fixes
+
+* **appium:** appium symlink behavior across drivers/plugins installations ([#21837](https://github.com/appium/appium/issues/21837)) ([529aeb4](https://github.com/appium/appium/commit/529aeb48f10419e21555cec05835ff07bb0e2e51))
+* apply npm run lint:fix ([#21867](https://github.com/appium/appium/issues/21867)) ([5e28714](https://github.com/appium/appium/commit/5e28714442cf59ee35b085e01e82c3f5483891fd))
+* **docs:** add missing verbose flag for CLI list command ([#21814](https://github.com/appium/appium/issues/21814)) ([dcfaa88](https://github.com/appium/appium/commit/dcfaa88830f6a5c608c92f5ae72445e065261d38))
+
+
+
 ## [3.1.2](https://github.com/appium/appium/compare/appium@3.1.1...appium@3.1.2) (2025-12-04)
 
 **Note:** Version bump only for package appium

packages/appium/README.md

@@ -199,11 +199,11 @@ contribution of project development and leadership!
 </p>
 
 <p align="center">
-  <a href="https://lambdatest.com/?utm_source=appium.io&utm_medium=organic&utm_campaign=june_25&utm_term=sk&utm_content=webpage">
+  <a href="https://www.testmuai.com">
     <picture>
-      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-lambdatest-dark.png" media="(prefers-color-scheme: dark)"/>
-      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-lambdatest-light.png" media="(prefers-color-scheme: light)"/>
-      <img src="packages/appium/docs/overrides/assets/images/sponsor-logo-lambdatest-dark.png" width="300" alt="LambdaTest"/>
+      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-testmuai-dark.png" media="(prefers-color-scheme: dark)"/>
+      <source srcset="packages/appium/docs/overrides/assets/images/sponsor-logo-testmuai-light.png" media="(prefers-color-scheme: light)"/>
+      <img src="packages/appium/docs/overrides/assets/images/sponsor-logo-testmuai-dark.png" width="300" alt="TestMu AI (formerly LambdaTest)"/>
     </picture>
   </a>
 </p>

packages/appium/docs/base-mkdocs.yml

@@ -3,7 +3,9 @@ site_name: Appium Documentation
 repo_url: https://github.com/appium/appium
 repo_name: appium/appium
 edit_uri: edit/master/packages/appium/docs
-copyright: Copyright &copy; 2012 OpenJS Foundation - <a href="#__consent">Change cookie settings</a>
+copyright: |
+  <p>Copyright <a href="https://openjsf.org">OpenJS Foundation</a> and Appium contributors. All rights reserved. The <a href="https://openjsf.org">OpenJS Foundation</a> has registered trademarks and uses trademarks.  For a list of trademarks of the <a href="https://openjsf.org">OpenJS Foundation</a>, please see our <a href="https://trademark-policy.openjsf.org">Trademark Policy</a> and <a href="https://trademark-list.openjsf.org">Trademark List</a>. Trademarks and logos not indicated on the <a href="https://trademark-list.openjsf.org">list of OpenJS Foundation trademarks</a> are trademarks&trade; or registered&reg; trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.</p>
+  <p><a href="https://openjsf.org">The OpenJS Foundation</a> | <a href="https://terms-of-use.openjsf.org">Terms of Use</a> | <a href="https://privacy-policy.openjsf.org">Privacy Policy</a> | <a href="https://bylaws.openjsf.org">Bylaws</a> | <a href="https://code-of-conduct.openjsf.org">Code of Conduct</a> | <a href="https://trademark-policy.openjsf.org">Trademark Policy</a> | <a href="https://trademark-list.openjsf.org">Trademark List</a> | <a href="https://www.linuxfoundation.org/cookies">Cookie Policy</a></p><a href="#__consent">Change cookie settings</a>
 
 theme:
   logo: assets/images/appium-logo-white.png

packages/appium/docs/en/contributing/index.md

@@ -10,7 +10,7 @@ maintenance, and support from companies and volunteers. As such, we welcome cont
 
 There are a lot of different ways to help the project - see below for everything you can do and the
 processes to follow for each contribution method. Note that no matter how you contribute, your
-participation is governed by our [Code of Conduct](https://github.com/appium/appium/blob/master/CONDUCT.md).
+participation is governed by our [Code of Conduct](https://github.com/appium/.github/blob/master/CODE_OF_CONDUCT.md).
 
 ## Join the Discussion Forum
 

packages/appium/docs/en/developing/build-drivers.md

@@ -568,6 +568,33 @@ capability), and then to set an internal field to that value, so that it can be
 bidiProxyUrl`. Once all this is in place, Appium will proxy BiDi commands from the client straight
 to the upstream connection.
 
+### Understand server-assigned driver properties and security flags
+
+When your driver is running under the main Appium server, Appium assigns a small set of
+server-related properties on your driver instance when a session is created:
+
+- `cliArgs`: Driver-specific configuration derived from the Appium server’s CLI flags and/or
+  configuration files (for example via the `server.driver.<your-driver-name>` section). These
+  options are **not** user capabilities and cannot be influenced directly by test code.
+- `server`, `serverHost`, `serverPort`, `serverPath`: Information about the HTTP server that is
+  hosting your driver. These values reflect how the Appium server was started (for example the
+  `--address`, `--port`, and `--base-path` flags) and are useful when your driver needs to construct
+  URLs that point back to the Appium server itself (for example when setting up proxies, webhooks,
+  or other callbacks).
+
+`BaseDriver` and `AppiumDriver` also cooperate to expose security-related flags on your driver
+instance:
+
+- `relaxedSecurityEnabled`: Indicates whether the server is running with relaxed security enabled
+  (for example via `--relaxed-security`).
+- `allowInsecure`: A list of insecure features which are explicitly allowed for this driver (derived
+  from server-level options like `--allow-insecure`).
+- `denyInsecure`: A list of insecure features which are explicitly disabled for this driver (derived
+  from server-level options like `--deny-insecure`).
+
+See [Hide behaviour behind security flags](#hide-behaviour-behind-security-flags) for how to use
+these flags in your driver (e.g. via `isFeatureEnabled` and `assertFeatureEnabled`).
+
 ### Extend the existing protocol with new commands
 
 You may find that the existing commands don't cut it for your driver. If you want to expose
@@ -858,3 +885,118 @@ this.onUnexpectedShutdown(handler)
 
 `handler` should be a function which receives an error object (representing the reason for the
 unexpected shutdown).
+
+### Send messages to plugins running on the same session
+
+Appium's driver and plugin architecture means that a single driver and any number of plugins can be
+running together for a current session. The driver and plugins don't really know anything about
+each other though, which can make coordination potentially difficult. Without creating any kind of
+tight coupling between drivers or plugins, it's possible for drivers and plugins to communicate
+along a pub/sub style message bus. With Appium's IPC feature, "message" means a combination of
+"data" (the data intended to be published or received), and metadata (timestamp, the name of the
+publisher, etc...).
+
+Drivers and plugins can implement an instance method called `async onIpcInit`, in which they will
+know that the IPC channel for the session is now active. At this point, they have access to the
+following methods:
+
+#### `ipcSubscribe<T>(topic: string): IIpcSubscription`
+
+This method allows a driver or plugin to subscribe to a topic on the IPC channel for the session.
+Topics are simply strings. To coordinate effectively, drivers or plugins would use the same topic
+string (so this would be something advertised in the driver/plugin documentation).
+
+The result of this call is an `IpcSubscription` object that allows:
+- Looping through messages on the topic via an async generator
+- Hooking up an event handler for new messages
+- Getting the last message sent on the topic
+- Publishing a message to the topic
+- Unsubscribing from the topic
+
+#### `IpcSubscription` object
+
+Here is an example of how subscribing and use of these subscription methods might work:
+
+```ts
+async onIpcInit() {
+  // we know at this point in our driver/plugin lifecycle that we can use IPC methods
+  type MyMessageData = {myData: string}; // let's say the message data for this channel has this shape
+
+  const subscription = this.ipcSubscribe<MyMessageData>('coolTopic');
+
+  // listen for new messages on topic
+  subscription.on('message', (message) => {
+    console.log(message.data); // {myData: 'something'}
+  });
+
+  // publish data to the topic; might throw if the data is larger than configured max size, or we
+  // are no longer subscribed
+  await subscription.publish({myData: 'hi'});
+
+  // get last message sent to topic
+  const {data} = subscription.getMessage() ?? {data: null};
+  // data = {myData: 'hi'}
+
+  // unsubscribe
+  subscription.unsubscribe(); // returns true if we unsubscribed and false if no subscription existed
+}
+```
+
+With a subscription object, we can also iterate async over it to receive new messages:
+
+```ts
+for await (const message of subscription) {
+  // here we have a message and can unwrap its data
+}
+```
+
+Note that the iteration will stop when the subscription ends (i.e., when `unsubscribe` is called).
+
+You can also check whether the subscription is still active (if your subscribe and unsubscribe
+logic is not locally connected):
+
+```ts
+if (subscription.isActive) {
+  // we know we have not yet unsubscribed
+}
+```
+
+If the subscription is not active, attempts to call `subscription.publish` will throw an error.
+
+#### `IpcMessage` object
+
+When you get a message on a topic, it has the following shape:
+
+```ts
+export type IpcMessage<T> = {
+  publisher: string,   // the id of the publishing object (typically of the form <ClassName>@<uniqueObjectId>)
+  timestampMs: number, // when the message was published, in ms since epoch
+  topic: string,       // the topic the message was published on
+  data: T,             // the arbitrary message data. Must be serializable and a valid argument to 'structuredClone()'
+};
+```
+
+#### IPC Notes
+
+There are some important things to keep in mind when using Appium's IPC feature:
+- IPC is only available once `onIpcInit` has been called, at the end of the `createSession` flow.
+  It cannot be used statically or in `createSession` hooks
+- In sum, IPC is only for use during a session (this is also to prevent drivers/plugins from
+  accessing or reading data sent on IPC channels in other sessions.)
+- The default max size of an IPC message is 1MB. This can be configured by the server-admin by
+  using the `--max-ipc-data-size` arg (value is a number in bytes).
+- If a message exceeds the configured size, any call to `publish` methods will throw, so be
+  sure to cover this case in your error handling.
+- The default max number of IPC topics per session is 1000. This can be configured by the
+  server-admin using the `--max-ipc-topics` arg.
+- If the topic limit is reached, calls to `subscribe` or `publish` on a new topic will throw, so
+  be sure to cover this case in your error handling.
+- Topic names exist within a global namespace per session. So if you don't want to clash with other
+  drivers or plugins, make sure you prefix your topic names with something unique, akin to vendor
+  prefixes in the WebDriver standard (for example: `fake-driver:some-topic`). We recommend the
+  format `<namespace>:<topic>`.
+
+To see examples of IPC in action, check out Appium's own
+[FakeDriver](https://github.com/appium/appium/blob/master/packages/fake-driver/lib/driver.ts) and
+[FakePlugin](https://github.com/appium/appium/blob/master/packages/fake-plugin/lib/plugin.ts)
+extensions, which showcase several ways of using IPC messages.

packages/appium/docs/en/developing/build-plugins.md

@@ -512,3 +512,12 @@ async onUnexpectedShutdown(driver, cause) {
   }
 }
 ```
+
+### Send messages to the driver or other plugins running on the same session
+
+Even though drivers and plugins don't know anything about each other, it's possible for them to
+send messages that other drivers or plugins can listen for, within the context of the same session,
+using an IPC channel. Given that the developer instructions for this feature are the same for
+drivers and plugins, please head over to the [IPC development docs for
+drivers](./build-drivers.md#send-messages-to-plugins-running-on-the-same-session) at the driver
+development guide.

packages/appium/docs/en/developing/config-system.md

@@ -30,7 +30,7 @@ In lieu of a separate file, configuration can be embedded in a project's `packag
 ```
 
 When an Appium server is started via the `appium` executable, the `init` function in `lib/main.js`
-will call into `lib/config-file.js` to load and/or search for a configuration file and in
+will call into `lib/bootstrap/config-file.js` to load and/or search for a configuration file and in
 `package.json`.
 
 !!! note
@@ -69,7 +69,7 @@ It is more straightforward to explain how config files are validated, so we'll s
 
 ### Validating Config Files
 
-When a config file is found (`lib/config-file.js`), it will call the `validate` function exported
+When a config file is found (`lib/bootstrap/config-file.js`), it will call the `validate` function exported
 from `lib/schema/schema.js` with the contents of the config file. In turn, this asks `ajv` to
 validate the data against the schema that Appium has provided it.
 

packages/appium/docs/en/ecosystem/tools.md

@@ -19,6 +19,43 @@ Appium has a graphical client which can be used to inspect application screensho
 application hierarchy, search for elements, run Appium commands, record app interactions, and more.
 It can be very useful for Appium test development.
 
+=== "Install as an Appium Plugin"
+
+    ```bash
+    appium plugin install inspector
+    ```
+=== "Install Standalone"
+
+    Download the app from the Appium Inspector repo's [GitHub Releases section](https://github.com/appium/appium-inspector/releases).
+
+### [Appium MCP](https://github.com/appium/appium-mcp)
+
+Appium MCP is a Model Context Protocol (MCP) server that provides mobile test development and
+automation capabilities using Appium.
+
+```json title="Install This Tool"
+// Add the following to your MCP client configuration
+{
+  "appium-mcp": {
+    "disabled": false,
+    "timeout": 100,
+    "type": "stdio",
+    "command": "npx",
+    "args": ["appium-mcp@latest"],
+    "env": {
+      "ANDROID_HOME": "/path/to/android/sdk"
+    }
+  }
+}
+```
+
+### [Skills](https://github.com/appium/skills)
+
+A set of AI Agent skills to support Appium automation, for example:
+
+- Help preparing Appium test environment from scratch, including common driver setup
+- Help preparing XCUITest driver and WebDriverAgent for real device automation
+
 ## Extension Tools
 
 Appium driver or plugin developers can choose to include these tools in their driver/plugin:
@@ -33,7 +70,7 @@ details needed for the driver/plugin have been set up correctly. The tool can be
 appium {driver|plugin} doctor <extension-name>
 ```
 
-It shows no results if the driver/plugin author did not implement Doctor support.
+It shows no results if the driver/plugin does not have such validation checks.
 
 !!! note
 
@@ -44,6 +81,18 @@ It shows no results if the driver/plugin author did not implement Doctor support
 
 These tools are not maintained by the Appium team:
 
+### [AppClaw](https://github.com/AppiumTestDistribution/AppClaw)
+
+AppClaw is a CLI-based agentic AI layer for mobile automation, powered by [Appium MCP](#appium-mcp).
+Agent instructions can be passed directly via CLI, or defined as YAML flows in either structured
+or natural language syntax.
+
+Supported by: `@AppiumTestDistribution`
+
+```sh title="Install This Tool"
+npm install -g appclaw
+```
+
 ### [Appium Installer](https://github.com/AppiumTestDistribution/appium-installer)
 
 Appium Installer is a command-line tool for simplifying setups of new Appium test environments.
@@ -55,29 +104,3 @@ Supported by: `@AppiumTestDistribution`
 ```sh title="Install This Tool"
 npm install -g appium-installer
 ```
-
-### [Jarvis Appium](https://github.com/AppiumTestDistribution/mcp-appium)
-
-Jarvis Appium is a Model Context Protocol (MCP) server that provides mobile test development and
-automation capabilities using Appium.
-
-Supported by: `@AppiumTestDistribution`
-
-```json title="Install This Tool"
-// Add the following to your MCP client configuration
-{
-  "mcpServers": {
-    "jarvis-appium": {
-      "disabled": false,
-      "timeout": 100,
-      "type": "stdio",
-      "command": "npx",
-      "args": ["jarvis-appium"],
-      "env": {
-        "ANDROID_HOME": "/path/to/android/sdk",
-        "CAPABILITIES_CONFIG": "/path/to/your/capabilities.json"
-      }
-    }
-  }
-}
-```

packages/appium/docs/en/guides/caps.md

@@ -2,14 +2,14 @@
 title: Session Capabilities
 ---
 
-"Capabilities" is the name given to the set of parameters used to start an Appium session. The
-information in the set describes what sort of "capabilities" you want your session to have, for
-example, a certain mobile operating system or a certain version of a device. Capabilities are
-represented as key-value pairs, with values allowed to be any valid JSON type, including
-other objects.
+Capabilities are the core parameters used to start an Appium session. They describe various
+features that you want your session to have, for example, a certain mobile operating system or a
+certain version of a device. Capabilities are represented as key-value pairs, with values allowed
+to be any valid JSON type, including other objects. Most importantly, they cannot be changed
+during the lifecycle of the session.
 
-The W3C WebDriver spec's [section on Capabilities](https://w3c.github.io/webdriver/#capabilities)
-identifies a small set of 10 standard capabilities, including the following:
+The capabilities used in Appium follow [the W3C WebDriver specification of the same name](https://w3c.github.io/webdriver/#capabilities).
+The WebDriver spec defines a small set of standard capabilities, including the following:
 
 | Capability Name  | Type     | Description                                    |
 |------------------|----------|------------------------------------------------|
@@ -17,65 +17,62 @@ identifies a small set of 10 standard capabilities, including the following:
 | `browserVersion` | `string` | The specific version of the browser            |
 | `platformName`   | `string` | The type of platform hosting the browser       |
 
+While the above capabilities are commonly used by Appium drivers, they are not sufficient for
+describing Appium-specific features, such as the name of the driver to use, or the name of the app
+to launch. In order to achieve this, Appium defines its own [extension capabilities](https://w3c.github.io/webdriver/#dfn-extension-capability).
+
 ## Common Appium Capabilities
 
-Appium understands these browser-focused capabilities, but introduces a number of additional
-capabilities. According to the WebDriver spec, any
-non-standard "extension capabilities" must include a namespace prefix (signifying the vendor
-introducing the capability), ending in a `:`. Appium's vendor prefix is
-`appium:`, and so any Appium-specific capabilities must include this prefix. Depending on which
-client you are using, the prefix may be added automatically or in conjunction with certain
-interfaces, but it is always a good practice to explicitly include it for clarity.
+According to the WebDriver spec, extension capabilities must include a namespace prefix (signifying
+the vendor introducing the capability), and the namespace must end a colon (`:`). Appium's vendor
+prefix is `appium:`, and so any Appium-specific capabilities must include this prefix. Depending on
+your Appium client, the prefix may be added automatically or in conjunction with certain interfaces,
+but it is always a good practice to explicitly include it for clarity.
 
-Here is a list of all the globally-recognized Appium capabilities:
+Here are a few commonly (but not universally!) used Appium-specific capabilities:
 
-!!! info
+| Capability Name         | Type     | Description                                                     |
+|-------------------------|----------|-----------------------------------------------------------------|
+| `appium:automationName` | `string` | The name of the Appium driver to use                            |
+| `appium:udid`           | `string` | The unique device identifier of a particular device to automate |
+| `appium:app`            | `string` | The path to an installable application                          |
 
-    Individual drivers and plugins can support other capabilities, so refer to their documentation
-    for lists of specific capability names. Some drivers may also not support all of these capabilities
+All capabilities recognized by the Appium base driver (inherited by all drivers) can be found in the
+[Capabilities Reference document](../reference/session/caps.md). While this common capability set
+is fairly small, it can be greatly extended by Appium drivers and plugins, who can (and should)
+define their own capabilities. Make sure to reference their documentation to learn more about the
+capabilities they support. You can find a list of known drivers in the [Ecosystem Drivers](../ecosystem/drivers.md) document.
 
-| <div style="width:12em">Capability</div>   | Type      | Required? | Description  |
-|--------------------------------------------|-----------|-----------|----------------------------|
-| `platformName`                             | `string`  | yes       | The type of platform hosting the app or browser |
-| `appium:automationName`                    | `string`  | yes       | The name of the Appium driver to use |
-| `browserName`                              | `string`  | no        | The name of the browser to launch and automate, if the driver supports web browsers as a special case |
-| `appium:app`                               | `string`  | no        | The path to an installable application |
-| `appium:deviceName`                        | `string`  | no        | The name of a particular device to automate, e.g., `iPhone 14` (currently only actually useful for specifying iOS simulators, since in other situations it's typically recommended to use a specific device id via the `appium:udid` capability). |
-| `appium:platformVersion`                   | `string`  | no        | The version of a platform, e.g., for iOS, `16.0` |
-| `appium:newCommandTimeout`                 | `number`  | no        | The number of seconds the Appium server should wait for clients to send commands before deciding that the client has gone away and the session should shut down. `60` seconds by default. Setting it to zero disables the timer. |
-| `appium:noReset`                           | `boolean` | no        | If true, instruct an Appium driver to avoid its usual reset logic during session start and cleanup (default `false`) |
-| `appium:fullReset`                         | `boolean` | no        | If true, instruct an Appium driver to augment its usual reset logic with additional steps to ensure maximum environmental reproducibility (default `false`) |
-| `appium:eventTimings`                      | `boolean` | no        | If true, instruct an Appium driver to collect [Event Timings](./event-timing.md) (default `false`) |
-| `appium:printPageSourceOnFindFailure`      | `boolean` | no        | If true, collect the page source and print it to the Appium log whenever a request to find an element fails (default `false`) |
+Drivers are also able to place more complex constraints on capabilities as a group. For example,
+the XCUITest driver recommends that at least one of `browserName`, `appium:app`, or `appium:bundleId`
+is included in the capabilities, otherwise it will not be able to auto-install or auto-launch any
+application. Each driver will document how it interprets these capabilities and any other
+platform-specific requirements.
 
-
-Some drivers place more complex constraints on capabilities as a group. For example, while the
-`appium:app` and `browserName` capabilities are listed above as optional, if you want to launch
-a session with a specific app, the XCUITest driver requires that at least one of `appium:app`,
-`browserName`, or `appium:bundleId` are included in the capabilities (otherwise it will not know
-what app to install and/or launch and will simply open a session on the home screen). Each driver
-will document how it interprets these capabilities and any other platform-specific requirements.
+The way to construct capabilities and start a session will likely differ depending on your Appium
+client. For examples of doing this in each client library, head to the [Ecosystem Clients](../ecosystem/clients.md)
+page and click through to the appropriate client documentation.
 
 !!! note
 
-    Capabilities are like parameters used when starting a session. After the capabilities are sent
-    and the session is started, they cannot be changed. If a driver supports updating aspects of
-    its behaviour in the course of a session, it will provide a [Setting](./settings.md) for this
-    purpose instead of, or in addition to, a capability.
-
-Each Appium client has its own way of constructing capabilities and starting a session. For
-examples of doing this in each client library, head to the [Ecosystem](../ecosystem/index.md) page
-and click through to the appropriate client documentation.
+    Once your capabilities are sent to the server and the session is started, they cannot be
+    changed. If a driver supports updating its behaviour during a session, it will use the
+    [Settings API](./settings.md) for this purpose.
 
 ## BiDi Protocol Support
 
-Appium supports [WebDriver BiDi](https://w3c.github.io/webdriver-bidi/) protocol since base–driver 9.5.0.
-The actual behavior depends on individual drivers while the Appium and the baseｰdriver support the protocol.
-Please make sure if a driver supports the protocol and what kind of commands/events it supports in the documentation.
+In addition to the standard WebDriver protocol (now known as WebDriver Classic), Appium supports the
+[WebDriver BiDi](https://w3c.github.io/webdriver-bidi/) protocol. Support for this protocol is
+opt-in, and requires the use of the standard `webSocketUrl` capability. 
 
-| Capability Name | Type      | Description                             |
-|-----------------|-----------|-----------------------------------------|
-| `webSocketUrl`  | `boolean` | To enable BiDi protocol in the session. |
+| Capability Name | Type      | Description                                      |
+|-----------------|-----------|--------------------------------------------------|
+| `webSocketUrl`  | `boolean` | Whether BiDi protocol is enabled in the session |
+
+All BiDi commands supported by the Appium base driver (inherited by all drivers) can be found in the
+[BiDi Protocol API Reference document](../reference/api/bidi.md). Similarly to WebDriver Classic
+commands, individual Appium drivers and plugins can define their own supported standard and custom
+BiDi commands, so make sure to reference their documentation.
 
 ## Using `appium:options` to Group Capabilities
 
@@ -118,8 +115,7 @@ creates in response to a new session request. This is through the concept of "al
 
 !!! note
 
-    Check out the [spec itself](https://w3c.github.io/webdriver/#processing-capabilities) or
-    a [summarized version](https://github.com/jlipps/simple-wd-spec#processing-capabilities) for
+    Check out the [spec itself](https://w3c.github.io/webdriver/#processing-capabilities) for
     a more in-depth description of how capabilities are processed.
 
 In practice, use of first-match capabilities is not necessary or recommended for use with Appium.

packages/appium/docs/en/guides/security.md

@@ -3,27 +3,27 @@ title: Appium Server Security
 ---
 
 The Appium team makes every effort to ensure the security of the Appium server. This is especially
-important when Appium is run in a multitenant environment, or when multiple users are running
-sessions on the same Appium server. In general, you can only safely enable all of Appium's features if
-all the following are true:
+important when Appium is run in a multi-tenant environment, or when multiple users are running
+sessions on the same Appium server. To ensure a safe environment for Appium's purposes, all of the
+following should be true:
 
 - You're running your own Appium server locally or within a protected internal network
 - You're not sharing it with any untrusted parties
 - You don't expose Appium's port(s) to the wider internet
 
-But because many Appium users might not be able to guarantee such a safe environment, the Appium
-team puts many features behind a security protection mechanism, which forces system admins (the
-people who are in charge of starting the Appium server) to _explicitly opt-in_ to these features.
-(Third-party driver and plugin authors can also [hide behaviour behind security
-flags](../developing/build-drivers.md).)
+But because not all Appium hosts can guarantee such a safe environment, certain insecure Appium
+features are disabled by default, and require explicit opt-in in order to enable them. Most
+importantly, this can _only_ be done by the Appium server _host_, and Appium _client_ sessions are
+not allowed to change this.
 
-For security reasons, Appium client sessions can _not_ request feature enablement via capabilities.
-This is the responsibility of the server admin who configures and launches the Appium server.
+While it is possible for an Appium host to simply enable all insecure features at once, each
+feature also has a unique name, which can be used for granular control over the server state.
 
 ## Security Server Args
 
-The [Server CLI](../reference/cli/server.md) doc outlines three relevant arguments which may be passed to
-Appium, when starting it from the command line:
+Enabling or disabling insecure features is done via [Appium server launch arguments](../reference/cli/server.md)
+or [configuration file](./config.md). The former document outlines three relevant arguments for
+achieving this:
 
 |<div style="width:10em">Parameter</div>|Description|
 |---------------------------------------|-----------|
@@ -31,36 +31,28 @@ Appium, when starting it from the command line:
 |`--allow-insecure`|Turns on _only_ specified features, except those blocked by `--deny-insecure`. Has no effect when used in combination with `--relaxed-security`|
 |`--deny-insecure`|Explicitly turns _off_ specified features, overriding `--relaxed-security` and `--allow-insecure`|
 
-All of the above arguments can also be specified in the [Appium Configuration file](./config.md).
-
 Features passed to `--allow-insecure`/`--deny-insecure` must be specified as a comma-separated list,
-and each feature in the list must additionally include a prefix, indicating the driver to which the
-feature should apply. The prefix can be either the driver's `automationName`, or the wildcard (`*`)
-symbol, if the feature should be applied to all drivers. The prefix and feature name are separated
-using the colon character (`:`).
+and each feature in the list must additionally include a prefix, indicating the driver to whose
+sessions the feature should apply. The prefix can be either the driver's `automationName`, or the
+wildcard (`*`) symbol, if the feature should be applied to all drivers. The prefix and feature name
+are separated using the colon character (`:`).
 
 For example, `first:foo` refers to the `foo` feature for the `first` driver, whereas `*:bar` refers
 to the `bar` feature for all drivers.
 
 ## Insecure Features
 
-Each Appium driver is responsible for its own security, and can create its own feature names. Thus,
-you should read through the documentation for a particular driver to know which feature names it
-might use. Here is an incomplete list of examples from some of Appium's official drivers:
+Almost all insecure features are defined on a per-driver or plugin basis, so make sure to read the
+documentation for a particular driver/plugin to know which feature names it might use.
 
-|<div style="width:12em">Feature Name</div>|Description|Supported Extension(s)|
-|------------|-----------|-------|
-|`get_server_logs`|Allows retrieving of Appium server logs via the Webdriver log interface|IOS, XCUITest, Android, UiAutomator2, Espresso|
-|`adb_shell`|Allows execution of arbitrary shell commands via ADB, using the `mobile: shell` command|Android, UiAutomator2, Espresso|
-|`record_audio`|Allow recording of host machine audio inputs|XCUITest|
-|`execute_driver_script`| Allows sending a request that has multiple Appium commands.|Execute Driver Plugin|
+Certain insecure features are also defined on the Appium server itself. For a list of these
+features, as well as the features defined in official plugins, see
+[the Insecure Features CLI Reference](../reference/cli/insecure-features.md) doc.
 
-Some insecure features operate on the server level and do not require a driver session. Enabling
-these features require using the wildcard prefix:
+!!! note
 
-|<div style="width:12em">Feature Name</div>|Description|
-|------------|-----------|
-|`session_discovery`|Allows retrieving the list of active server sessions via `GET /appium/sessions`|
+    If you are a driver or plugin author and want to implement insecure features of your own, check
+    out the [Building Drivers documentation](../developing/build-drivers.md#understand-server-assigned-driver-properties-and-security-flags).
 
 ## Examples
 

packages/appium/docs/en/index.md

@@ -34,9 +34,9 @@ Android TV, Samsung), and more!
       </a>
     </div>
     <div class="homepageSponsor">
-      <a href="https://lambdatest.com/?utm_source=appium.io&utm_medium=organic&utm_campaign=june_25&utm_term=sk&utm_content=webpage">
-        <img src="assets/images/sponsor-logo-lambdatest-dark.png#only-dark" style="width: 220px;" />
-        <img src="assets/images/sponsor-logo-lambdatest-light.png#only-light" style="width: 220px;" />
+      <a href="https://www.testmuai.com">
+        <img src="assets/images/sponsor-logo-testmuai-dark.png#only-dark" style="width: 220px;" />
+        <img src="assets/images/sponsor-logo-testmuai-light.png#only-light" style="width: 220px;" />
       </a>
     </div>
   </div>

packages/appium/docs/en/reference/api/others.md

@@ -396,6 +396,45 @@ Deletes the virtual sensor with the type identified by `:sensorType`.
 
 `null`
 
+## Global Privacy Control Protocol
+
+The [Global Privacy Control protocol](https://www.w3.org/TR/gpc) (GPC) is an extension of the W3C
+WebDriver protocol.
+
+### setGlobalPrivacyControl
+
+```
+POST /session/:sessionId/privacy
+```
+
+> GPC documentation: [Set Global Privacy Control](https://www.w3.org/TR/gpc/#set-global-privacy-control)
+
+Sets the value of the do-not-sell-or-share preference for the current session.
+
+#### Parameters
+
+|Name|Description|Type|
+|--|--|--|
+|`gpc`|Whether the browser should perform do-not-sell-or-share interactions|boolean|
+
+#### Response
+
+`null`
+
+### getGlobalPrivacyControl
+
+```
+GET /session/:sessionId/privacy
+```
+
+> GPC documentation: [Get Global Privacy Control](https://www.w3.org/TR/gpc/#get-global-privacy-control)
+
+Retrieves the value of the do-not-sell-or-share preference for the current session.
+
+#### Response
+
+`boolean` - the preference value
+
 ## Permissions Protocol
 
 The [Permissions protocol](https://www.w3.org/TR/permissions/) is an extension of the W3C WebDriver
@@ -523,6 +562,32 @@ Retrieves the available log types that can be used to call the [`getLog`](#getlo
 
 `string[]` - an array of log types
 
+## Storage Access Protocol
+
+The [Storage Access protocol](https://privacycg.github.io/storage-access/) is an extension of the
+W3C WebDriver protocol.
+
+### setStorageAccess
+
+```
+POST /session/:sessionId/storageaccess
+```
+
+> Storage Access documentation: [Set Storage Access](https://privacycg.github.io/storage-access/#set-storage-access-command)
+
+Sets the storage access policy of the current browsing context.
+
+#### Parameters
+
+|Name|Description|Type|
+|--|--|--|
+|`blocked`|Whether storage access should be blocked (`true`) or allowed (`false`)|boolean|
+|`origin`|The origin to which the policy should be applied. Must be either a valid URL, or an asterisk (`*`) if the policy should apply to all origins.|string|
+
+#### Response
+
+`null`
+
 ## Web Authentication Protocol
 
 The [Web Authentication protocol](https://w3c.github.io/webauthn/) (WebAuthn) is an extension of

packages/appium/docs/en/reference/api/plugins.md

@@ -222,7 +222,7 @@ Deletes a file in the storage.
 #### Response
 
 `boolean` - `true` upon successful file deletion, or `false` if the file does not exist in
-the storage 
+the storage, or if the delete request is invalid.
 
 ### listStorageItems
 

packages/appium/docs/en/reference/cli/extensions.md

@@ -117,6 +117,12 @@ appium {driver|plugin} install <install-spec>
     appium driver install git://github.com/appium/appium-xcuitest-driver.git --source=git --package=appium-xcuitest-driver
     ```
 
+- Install a branch of XCUITest driver repository using a Git URL:
+
+    ```
+    appium driver install git://github.com/appium/appium-xcuitest-driver.git#specific-branch --source=git --package=appium-xcuitest-driver
+    ```
+
 ## `list`
 
 Lists all installed extensions, plus all official extensions that are not installed.
@@ -134,6 +140,7 @@ appium {driver|plugin} list
 |`--installed`|Only list all installed extensions|boolean|
 |`--json`|Return the result in JSON format|boolean|
 |`--updates`|List all extensions along with information on whether newer versions are available. Only supported for extensions installed via `npm`.|boolean|
+|`--verbose`|Show additional details for each extension|boolean|
 
 #### Example
 

packages/appium/docs/en/reference/cli/index.md

@@ -31,5 +31,6 @@ The executable has four main subcommands: `server`, `driver`, `plugin`, and `set
 
 </div>
 
-Appium also recognizes several [environment variables](./env-vars.md), which may be used for
-advanced configuration.
+The Appium server also recognizes several [environment variables](./env-vars.md) and
+[insecure feature names](./insecure-features.md), though drivers and plugins can also define
+variables and features of their own.

packages/appium/docs/en/reference/cli/insecure-features.md

@@ -0,0 +1,24 @@
+---
+hide:
+  - toc
+
+title: Insecure Features
+---
+
+The Appium server implements [a security protection mechanism](../../guides/security.md) that
+allows the management of various insecure features.
+
+The following features are defined on the server level and can be used even without drivers, but
+they can only be enabled using the wildcard (`*`) prefix:
+
+| Feature Name      | Description                                                                   |
+|-------------------|-------------------------------------------------------------------------------|
+|`session_discovery`|Allows retrieving the list of active server sessions via `GET /appium/sessions`|
+
+
+Of course, Appium drivers and plugins are free to define additional insecure features of their own.
+The following features are defined by official plugins:
+
+| Feature Name          | Plugin         | Description                                              |
+|-----------------------|----------------|----------------------------------------------------------|
+|`execute_driver_script`|`execute_driver`|Allows sending a request that has multiple Appium commands|

packages/appium/docs/en/reference/cli/server.md

@@ -29,6 +29,7 @@ appium
 |`--address`, `-a`|IPv4/IPv6 address to listen on|string|`0.0.0.0`|
 |`--allow-cors`|Allow web browser connections from any host|boolean|`false`|
 |`--allow-insecure`|List of [insecure features](../../guides/security.md) that should be allowed in this server's sessions. Individual features can be overridden by `--deny-insecure`. Has no effect in combination with `--relaxed-security`.|array<string>|`[]`|
+|`--allow-unknown-args`|Do not exit if unrecognized command-line arguments are passed to the server; ignore them instead. Useful when the Appium CLI is wrapped by external tooling that appends extra flags.|boolean|`false`|
 |`--base-path`, `-pa`|Base path to use as the prefix for all webdriver routes running on the server|string|`""`|
 |`--callback-address`, `-ca`|Callback IP address|string|`0.0.0.0`|
 |`--callback-port`, `-cp`|Callback port|integer|`4723`|
@@ -48,6 +49,8 @@ appium
 |`--log-no-colors`|Disable colors in the server log|boolean|`false`|
 |`--log-timestamp`|Show timestamps in the server log|boolean|`false`|
 |`--long-stacktrace`|Add long stack traces to log entries. Recommended for debugging only.|boolean|`false`|
+|`--max-ipc-data-size`|Maximum byte size of IPC message objects.|integer|`1048576` (1MB)|
+|`--max-ipc-topics`|Maximum number of IPC topics per session.|integer|`1000`|
 |`--no-perms-check`|Skip various permission checks on the server startup|boolean|`false`|
 |`--nodeconfig`|JSON configuration for registering Appium as a node with Selenium Grid 3|object||
 |`--plugin`|Plugin-specific configuration. Keys should correspond to plugin package names|object||

packages/appium/docs/en/reference/index.md

@@ -5,8 +5,8 @@ hide:
 title: Reference
 ---
 
-This section of the Appium documentation provides a reference to the two main interfaces within the
-Appium server: the command-line executable, and the supported API endpoints.
+This section of the Appium documentation provides a reference to the core interfaces supported within the
+Appium server:
 
 <div class="grid cards" markdown>
 
@@ -16,10 +16,16 @@ Appium server: the command-line executable, and the supported API endpoints.
 
     Learn how to use the Appium command-line executable
 
+-   :material-lan-connect: [__Session Properties__](./session/index.md)
+
+    ---
+
+    See the values of global Appium session properties 
+
 -   :material-cloud-braces: [__API Endpoints__](./api/index.md)
 
     ---
 
-    View endpoints supported by the Appium server
+    View endpoints supported by the core Appium server
 
 </div>

packages/appium/docs/en/reference/session/caps.md

@@ -0,0 +1,56 @@
+---
+hide:
+  - toc
+
+title: Capabilities
+---
+
+The following [capabilities](../../guides/caps.md) are recognized by the Appium server/base driver,
+and are therefore supported by all drivers as well. Some capabilities are directly handled by the
+server/base driver, while others are only validated before being passed to the actual driver.
+
+!!! note
+
+    Capabilities not listed here will _not_ be rejected by Appium: they will simply be forwarded
+    directly to the active driver/plugin.
+
+### Required Capabilities
+
+These capabilities are used in the Appium server/base driver, and are explicitly required in all
+Appium sessions.
+
+| Capability              | Description                                 | Type      |
+|-------------------------|---------------------------------------------|-----------|
+| `platformName`          | Type of platform hosting the app or browser | `string`  |
+| `appium:automationName` | Name of the Appium driver to use            | `string`  |
+
+### Optional Capabilities
+
+These capabilities are used in the Appium server/base driver, but are optional, and may have a
+default value.
+
+| <div style="width:19em">Capability</div> | Description | Type | Default |
+|--|--|--|--|
+| `webSocketUrl` | Toggle support of the WebDriver BiDi protocol | `boolean` ||
+| `appium:eventTimings` (deprecated) | Toggle collection of [Event Timings](../../guides/event-timing.md). This capability is deprecated - please use the [`getLogEvents`](../api/appium.md#getlogevents) endpoint instead. | `boolean` ||
+| `appium:newCommandTimeout` | Number of seconds the Appium server should wait for clients to send commands before stopping the session. A value of `0` disables the timeout. | `number` | `60` |
+| `appium:printPageSourceOnFindFailure` | Toggle retrieval of the the page source and its printing to the Appium log, whenever a request to find an element fails | `boolean` ||
+
+### Validated Capabilities
+
+These capabilities are not directly used in the Appium server/base driver, but are still subject to
+validation checks due to their relevance in other drivers. The actual handling of these
+capabilities is optional and entirely driver-dependent.
+
+| Capability                        | Validation                                                    |
+|-----------------------------------|---------------------------------------------------------------|
+| `platformVersion`                 | Must be `string`                                              |
+| `appium:app`                      | Must be `string`; empty values are ignored                    |
+| `appium:autoLaunch` (deprecated)  | Must be `boolean`                                             |
+| `appium:autoWebview`              | Must be `boolean`                                             |
+| `appium:fullReset`                | Must be `boolean`; mutually exclusive with `appium:noReset`   |
+| `appium:language`                 | Must be `string`                                              |
+| `appium:locale`                   | Must be `string`                                              |
+| `appium:orientation`              | Must be either `LANDSCAPE` or `PORTRAIT`                      |
+| `appium:noReset`                  | Must be `boolean`; mutually exclusive with `appium:fullReset` |
+| `appium:udid`                     | Must be `string`                                              |

packages/appium/docs/en/reference/session/index.md

@@ -0,0 +1,23 @@
+---
+hide:
+  - toc
+
+title: Session Properties
+---
+
+An Appium session has several key properties, each with its own set of supported values:
+capabilities, execute methods, settings, locator strategies, and others. The supported values for
+each property are primarily defined by the active driver and plugins, but some properties also have
+common values provided by the Appium server and its base driver:
+
+<div class="grid cards" markdown>
+
+-   [__Capabilities__](./caps.md)
+
+    A small set of basic capabilities
+
+-   [__Command Endpoints__](../api/index.md)
+
+    The core set of API endpoints
+
+</div>

packages/appium/docs/en/resources/index.md

@@ -8,11 +8,6 @@ title: Additional Resources
 
 Here you can find links to additional Appium resources around the web:
 
-## Websites
-
-- [Appium Pro](https://appiumpro.com) - a blog and newsletter written by one of Appium's
-maintainers, Jonathan Lipps, with lots of useful guides
-
 ## Online Courses
 
 - [Appium and Selenium Fundamentals](https://ui.headspin.io/university/learn/appium-selenium-fundamentals-2020) - a comprehensive video course on learning Python, Selenium, and Appium by Jonathan Lipps
@@ -26,3 +21,4 @@ maintainers, Jonathan Lipps, with lots of useful guides
 - [AppiumConf 2021](https://www.youtube.com/playlist?list=PL9Z-JgiTsOYRCcJhDfmKAah9XmAp2b903)
 - [AppiumConf 2024](https://www.youtube.com/playlist?list=PL9Z-JgiTsOYQaU5i5LJtAWlh5WVZPi3If)
 - [SeleniumConf & AppiumConf 2025](https://www.youtube.com/playlist?list=PLRdSclUtJDYV2R92TLbmwxws6clruuTjH)
+- [SeleniumConf & AppiumConf 2026](https://www.youtube.com/playlist?list=PLRdSclUtJDYVgVqdKnSyBLBmFdA0KE_Dk)

packages/appium/docs/en/sponsors/index.md

@@ -22,6 +22,11 @@ Hub](https://opencollective.com/appium).
 We are very grateful for the support of our Development Partners, who donate Appium development and
 maintenance as part of their employees' core job duties!
 
+<a href="https://www.testmuai.com">
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-dark.png#only-dark" width="250" alt="TestMu AI (formerly LambdaTest)" />
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-light.png#only-light" width="250" alt="TestMu AI (formerly LambdaTest)" />
+</a>
+
 ## Strategic Partners
 
 We are very grateful for the financial and marketing support of our exclusive Strategic Partners,
@@ -33,9 +38,9 @@ contributors!
   <img src="/docs/en/latest/assets/images/sponsor-logo-browserstack-light.png#only-light" width="250" alt="BrowserStack" />
 </a>
 
-<a href="https://lambdatest.com/?utm_source=appium.io&utm_medium=organic&utm_campaign=june_25&utm_term=sk&utm_content=webpage">
-  <img src="/docs/en/latest/assets/images/sponsor-logo-lambdatest-dark.png#only-dark" width="250" alt="LambdaTest" />
-  <img src="/docs/en/latest/assets/images/sponsor-logo-lambdatest-light.png#only-light" width="250" alt="LambdaTest" />
+<a href="https://www.testmuai.com">
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-dark.png#only-dark" width="250" alt="TestMu AI (formerly LambdaTest)" />
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-light.png#only-light" width="250" alt="TestMu AI (formerly LambdaTest)" />
 </a>
 
 ## Gold Sponsors

packages/appium/docs/ja/contributing/index.md

@@ -10,7 +10,7 @@ maintenance, and support from companies and volunteers. As such, we welcome cont
 
 There are a lot of different ways to help the project - see below for everything you can do and the
 processes to follow for each contribution method. Note that no matter how you contribute, your
-participation is governed by our [Code of Conduct](https://github.com/appium/appium/blob/master/CONDUCT.md).
+participation is governed by our [Code of Conduct](https://github.com/appium/.github/blob/master/CODE_OF_CONDUCT.md).
 
 ## Join the Discussion Forum
 

packages/appium/docs/ja/developing/build-drivers.md

@@ -570,6 +570,33 @@ capability), and then to set an internal field to that value, so that it can be
 bidiProxyUrl`. Once all this is in place, Appium will proxy BiDi commands from the client straight
 to the upstream connection.
 
+### Understand server-assigned driver properties and security flags
+
+When your driver is running under the main Appium server, Appium assigns a small set of
+server-related properties on your driver instance when a session is created:
+
+- `cliArgs`: Driver-specific configuration derived from the Appium server’s CLI flags and/or
+  configuration files (for example via the `server.driver.<your-driver-name>` section). These
+  options are **not** user capabilities and cannot be influenced directly by test code.
+- `server`, `serverHost`, `serverPort`, `serverPath`: Information about the HTTP server that is
+  hosting your driver. These values reflect how the Appium server was started (for example the
+  `--address`, `--port`, and `--base-path` flags) and are useful when your driver needs to construct
+  URLs that point back to the Appium server itself (for example when setting up proxies, webhooks,
+  or other callbacks).
+
+`BaseDriver` and `AppiumDriver` also cooperate to expose security-related flags on your driver
+instance:
+
+- `relaxedSecurityEnabled`: Indicates whether the server is running with relaxed security enabled
+  (for example via `--relaxed-security`).
+- `allowInsecure`: A list of insecure features which are explicitly allowed for this driver (derived
+  from server-level options like `--allow-insecure`).
+- `denyInsecure`: A list of insecure features which are explicitly disabled for this driver (derived
+  from server-level options like `--deny-insecure`).
+
+See [Hide behaviour behind security flags](#hide-behaviour-behind-security-flags) for how to use
+these flags in your driver (e.g. via `isFeatureEnabled` and `assertFeatureEnabled`).
+
 ### Extend the existing protocol with new commands
 
 You may find that the existing commands don't cut it for your driver. If you want to expose
@@ -579,7 +606,7 @@ three ways:
 1. Extending the classic WebDriver protocol and creating client-side plugins to access the extensions via the classic HTTP interface
 2. Extending the WebDriver BiDi protocol with new modules and methods, accessed from a client via the BiDi interface
 3. Overloading the Execute Script command by defining Execute
-  Methods
+   Methods
 
 If you want to follow the first path, you can direct Appium to recognize new methods and add them
 to its set of allowed HTTP routes and command names. You do this by assigning the `newMethodMap`
@@ -685,17 +712,17 @@ async execute(script, args) {
 A couple notes about this system:
 
 1. The arguments array sent via the call to Execute Script must contain only zero or one element(s). The
-  first item in the list is considered to be the parameters object for your method. These parameters
-  will be parsed, validated, and then applied to your overload method in the order specified in
-  `executeMethodMap` (the order specified in the `required` parameters list, followed by the
-  `optional` parameters list). I.e., this framework assumes only a single actual argument sent in via
-  Execute Script (and this argument should be an object with keys/values representing the
-  parameters your execute method expects).
+   first item in the list is considered to be the parameters object for your method. These parameters
+   will be parsed, validated, and then applied to your overload method in the order specified in
+   `executeMethodMap` (the order specified in the `required` parameters list, followed by the
+   `optional` parameters list). I.e., this framework assumes only a single actual argument sent in via
+   Execute Script (and this argument should be an object with keys/values representing the
+   parameters your execute method expects).
 2. Appium does not automatically implement `execute` (the Execute Script handler) for you. You may
-  wish, for example, to only call the `executeMethod` helper function when you're not in proxy
-  mode!
+   wish, for example, to only call the `executeMethod` helper function when you're not in proxy
+   mode!
 3. The `executeMethod` helper will reject with an error if a script name doesn't match one of the
-  script names defined as a command in `executeMethodMap`, or if there are missing parameters.
+   script names defined as a command in `executeMethodMap`, or if there are missing parameters.
 
 One of the nice things about the Execute Method strategy is that methods implemented in this way
 will be available via the classic or BiDi interfaces (since they will result in the same Appium
@@ -770,7 +797,7 @@ that multiple simultaneous sessions don't use the same resources:
 1. Have your users specify resource IDs via capabilities (`appium:driverPort` etc)
 2. Just always use free resources (find a new random port for each session)
 3. Have each driver express what resources it is using, then examine currently-used resources from
-  other drivers when a new session begins.
+   other drivers when a new session begins.
 
 To support this third strategy, you can implement `get driverData` in your driver to return what
 sorts of resources your driver is currently using, for example:
@@ -864,3 +891,120 @@ this.onUnexpectedShutdown(handler)
 
 `handler` should be a function which receives an error object (representing the reason for the
 unexpected shutdown).
+
+### Send messages to plugins running on the same session
+
+Appium's driver and plugin architecture means that a single driver and any number of plugins can be
+running together for a current session. The driver and plugins don't really know anything about
+each other though, which can make coordination potentially difficult. Without creating any kind of
+tight coupling between drivers or plugins, it's possible for drivers and plugins to communicate
+along a pub/sub style message bus. With Appium's IPC feature, "message" means a combination of
+"data" (the data intended to be published or received), and metadata (timestamp, the name of the
+publisher, etc...).
+
+Drivers and plugins can implement an instance method called `async onIpcInit`, in which they will
+know that the IPC channel for the session is now active. At this point, they have access to the
+following methods:
+
+#### `ipcSubscribe<T>(topic: string): IIpcSubscription`
+
+This method allows a driver or plugin to subscribe to a topic on the IPC channel for the session.
+Topics are simply strings. To coordinate effectively, drivers or plugins would use the same topic
+string (so this would be something advertised in the driver/plugin documentation).
+
+The result of this call is an `IpcSubscription` object that allows:
+
+- Looping through messages on the topic via an async generator
+- Hooking up an event handler for new messages
+- Getting the last message sent on the topic
+- Publishing a message to the topic
+- Unsubscribing from the topic
+
+#### `IpcSubscription` object
+
+Here is an example of how subscribing and use of these subscription methods might work:
+
+```ts
+async onIpcInit() {
+  // we know at this point in our driver/plugin lifecycle that we can use IPC methods
+  type MyMessageData = {myData: string}; // let's say the message data for this channel has this shape
+
+  const subscription = this.ipcSubscribe<MyMessageData>('coolTopic');
+
+  // listen for new messages on topic
+  subscription.on('message', (message) => {
+    console.log(message.data); // {myData: 'something'}
+  });
+
+  // publish data to the topic; might throw if the data is larger than configured max size, or we
+  // are no longer subscribed
+  await subscription.publish({myData: 'hi'});
+
+  // get last message sent to topic
+  const {data} = subscription.getMessage() ?? {data: null};
+  // data = {myData: 'hi'}
+
+  // unsubscribe
+  subscription.unsubscribe(); // returns true if we unsubscribed and false if no subscription existed
+}
+```
+
+With a subscription object, we can also iterate async over it to receive new messages:
+
+```ts
+for await (const message of subscription) {
+  // here we have a message and can unwrap its data
+}
+```
+
+Note that the iteration will stop when the subscription ends (i.e., when `unsubscribe` is called).
+
+You can also check whether the subscription is still active (if your subscribe and unsubscribe
+logic is not locally connected):
+
+```ts
+if (subscription.isActive) {
+  // we know we have not yet unsubscribed
+}
+```
+
+If the subscription is not active, attempts to call `subscription.publish` will throw an error.
+
+#### `IpcMessage` object
+
+When you get a message on a topic, it has the following shape:
+
+```ts
+export type IpcMessage<T> = {
+  publisher: string,   // the id of the publishing object (typically of the form <ClassName>@<uniqueObjectId>)
+  timestampMs: number, // when the message was published, in ms since epoch
+  topic: string,       // the topic the message was published on
+  data: T,             // the arbitrary message data. Must be serializable and a valid argument to 'structuredClone()'
+};
+```
+
+#### IPC Notes
+
+There are some important things to keep in mind when using Appium's IPC feature:
+
+- IPC is only available once `onIpcInit` has been called, at the end of the `createSession` flow.
+  It cannot be used statically or in `createSession` hooks
+- In sum, IPC is only for use during a session (this is also to prevent drivers/plugins from
+  accessing or reading data sent on IPC channels in other sessions.)
+- The default max size of an IPC message is 1MB. This can be configured by the server-admin by
+  using the `--max-ipc-data-size` arg (value is a number in bytes).
+- If a message exceeds the configured size, any call to `publish` methods will throw, so be
+  sure to cover this case in your error handling.
+- The default max number of IPC topics per session is 1000. This can be configured by the
+  server-admin using the `--max-ipc-topics` arg.
+- If the topic limit is reached, calls to `subscribe` or `publish` on a new topic will throw, so
+  be sure to cover this case in your error handling.
+- Topic names exist within a global namespace per session. So if you don't want to clash with other
+  drivers or plugins, make sure you prefix your topic names with something unique, akin to vendor
+  prefixes in the WebDriver standard (for example: `fake-driver:some-topic`). We recommend the
+  format `<namespace>:<topic>`.
+
+To see examples of IPC in action, check out Appium's own
+[FakeDriver](https://github.com/appium/appium/blob/master/packages/fake-driver/lib/driver.ts) and
+[FakePlugin](https://github.com/appium/appium/blob/master/packages/fake-plugin/lib/plugin.ts)
+extensions, which showcase several ways of using IPC messages.

packages/appium/docs/ja/developing/build-plugins.md

@@ -236,13 +236,13 @@ upstream server. In this case, we might run into a problem, because the plugin n
 handle that command! The way Appium handles this is as follows:
 
 1. When a command comes in, before deciding whether to proxy the command, the main protocol handler
-  checks to see whether a plugin would handle the command.
+   checks to see whether a plugin would handle the command.
 2. If a plugin would _not_ handle the command--all proceeds as normal, and the request is either
-  proxied or not, based on the driver's proxy mode.
+   proxied or not, based on the driver's proxy mode.
 3. If a plugin _would_ handle the command, then the proxy behavior is skipped for the time being,
-  and wrapped up as the `next` function sent to the plugin. So if you have a command handler in
-  your plugin, and you want to be sure that the default driver proxying _does_ take place, then
-  simply `await next()` instead of (or in addition to) whatever your plugin handler is doing.
+   and wrapped up as the `next` function sent to the plugin. So if you have a command handler in
+   your plugin, and you want to be sure that the default driver proxying _does_ take place, then
+   simply `await next()` instead of (or in addition to) whatever your plugin handler is doing.
 
 ### Throw WebDriver-specific errors
 
@@ -331,7 +331,7 @@ drivers, you can create new commands in one of two ways, just as is possible for
 1. Extending the WebDriver protocol and creating client-side plugins to access the extensions
 2. Extending the WebDriver BiDi protocol with new modules and methods, accessed from a client via the BiDi interface
 3. Overloading the Execute Script command by defining Execute
-  Methods
+   Methods
 
 #### Extending the HTTP Protocol
 
@@ -458,10 +458,10 @@ inside the plugin class:
 
 1. The `executeMethodMap`, defined in just the same way as for drivers
 2. The implementation of the command method as defined in `executeMethodMap` (in this case,
-  `plugMeIn`)
+   `plugMeIn`)
 3. The overriding/handling of the `execute` command. Just like any plugin command handlers, the
-  first two arguments are `next` and `driver`, followed by the script name and args. `BasePlugin`
-  implements a helper method which we can simply call with all of these arguments.
+   first two arguments are `next` and `driver`, followed by the script name and args. `BasePlugin`
+   implements a helper method which we can simply call with all of these arguments.
 
 Overriding Execute Methods from drivers works as you'd expect: if your plugin defines an Execute
 Method with the same name as that of a driver, your command (in this case `plugMeIn`) will be
@@ -518,3 +518,12 @@ async onUnexpectedShutdown(driver, cause) {
   }
 }
 ```
+
+### Send messages to the driver or other plugins running on the same session
+
+Even though drivers and plugins don't know anything about each other, it's possible for them to
+send messages that other drivers or plugins can listen for, within the context of the same session,
+using an IPC channel. Given that the developer instructions for this feature are the same for
+drivers and plugins, please head over to the IPC development docs for
+drivers at the driver
+development guide.

packages/appium/docs/ja/developing/config-system.md

@@ -29,7 +29,7 @@ In lieu of a separate file, configuration can be embedded in a project's `packag
 ```
 
 When an Appium server is started via the `appium` executable, the `init` function in `lib/main.js`
-will call into `lib/config-file.js` to load and/or search for a configuration file and in
+will call into `lib/bootstrap/config-file.js` to load and/or search for a configuration file and in
 `package.json`.
 
 !!! note
@@ -72,7 +72,7 @@ It is more straightforward to explain how config files are validated, so we'll s
 
 ### Validating Config Files
 
-When a config file is found (`lib/config-file.js`), it will call the `validate` function exported
+When a config file is found (`lib/bootstrap/config-file.js`), it will call the `validate` function exported
 from `lib/schema/schema.js` with the contents of the config file. In turn, this asks `ajv` to
 validate the data against the schema that Appium has provided it.
 

packages/appium/docs/ja/ecosystem/tools.md

@@ -21,6 +21,48 @@ Appium has a graphical client which can be used to inspect application screensho
 application hierarchy, search for elements, run Appium commands, record app interactions, and more.
 It can be very useful for Appium test development.
 
+\=== "Install as an Appium Plugin"
+
+````
+```bash
+appium plugin install inspector
+```
+````
+
+\=== "Install Standalone"
+
+```
+Download the app from the Appium Inspector repo's [GitHub Releases section](https://github.com/appium/appium-inspector/releases).
+```
+
+### [Appium MCP](https://github.com/appium/appium-mcp)
+
+Appium MCP is a Model Context Protocol (MCP) server that provides mobile test development and
+automation capabilities using Appium.
+
+```json title="Install This Tool"
+// Add the following to your MCP client configuration
+{
+  "appium-mcp": {
+    "disabled": false,
+    "timeout": 100,
+    "type": "stdio",
+    "command": "npx",
+    "args": ["appium-mcp@latest"],
+    "env": {
+      "ANDROID_HOME": "/path/to/android/sdk"
+    }
+  }
+}
+```
+
+### [Skills](https://github.com/appium/skills)
+
+A set of AI Agent skills to support Appium automation, for example:
+
+- Help preparing Appium test environment from scratch, including common driver setup
+- Help preparing XCUITest driver and WebDriverAgent for real device automation
+
 ## Extension Tools
 
 Appium driver or plugin developers can choose to include these tools in their driver/plugin:
@@ -35,7 +77,7 @@ details needed for the driver/plugin have been set up correctly. The tool can be
 appium {driver|plugin} doctor <extension-name>
 ```
 
-It shows no results if the driver/plugin author did not implement Doctor support.
+It shows no results if the driver/plugin does not have such validation checks.
 
 !!! note
 
@@ -48,6 +90,18 @@ out the documentation on [Building Doctor Checks](../developing/build-doctor-che
 
 These tools are not maintained by the Appium team:
 
+### [AppClaw](https://github.com/AppiumTestDistribution/AppClaw)
+
+AppClaw is a CLI-based agentic AI layer for mobile automation, powered by [Appium MCP](#appium-mcp).
+Agent instructions can be passed directly via CLI, or defined as YAML flows in either structured
+or natural language syntax.
+
+Supported by: `@AppiumTestDistribution`
+
+```sh title="Install This Tool"
+npm install -g appclaw
+```
+
 ### [Appium Installer](https://github.com/AppiumTestDistribution/appium-installer)
 
 Appium Installer is a command-line tool for simplifying setups of new Appium test environments.
@@ -59,29 +113,3 @@ Supported by: `@AppiumTestDistribution`
 ```sh title="Install This Tool"
 npm install -g appium-installer
 ```
-
-### [Jarvis Appium](https://github.com/AppiumTestDistribution/mcp-appium)
-
-Jarvis Appium is a Model Context Protocol (MCP) server that provides mobile test development and
-automation capabilities using Appium.
-
-Supported by: `@AppiumTestDistribution`
-
-```json title="Install This Tool"
-// Add the following to your MCP client configuration
-{
-  "mcpServers": {
-    "jarvis-appium": {
-      "disabled": false,
-      "timeout": 100,
-      "type": "stdio",
-      "command": "npx",
-      "args": ["jarvis-appium"],
-      "env": {
-        "ANDROID_HOME": "/path/to/android/sdk",
-        "CAPABILITIES_CONFIG": "/path/to/your/capabilities.json"
-      }
-    }
-  }
-}
-```

packages/appium/docs/ja/guides/caps.md

@@ -2,9 +2,14 @@
 title: Session Capabilities
 ---
 
-「Capabilities」は、Appiumセッションを開始するために使用されるパラメータセットに付けられた名前です。 セット内の情報は、セッションにどのような「Capabilities」を持たせたいかを表します。たとえば、特定のモバイルオペレーティングシステムや特定のデバイスバージョンなどです。 Capabilities はキーと値のペアとして表され、値には他のオブジェクトを含む任意の有効な JSON 型を使用できます。
+Capabilities are the core parameters used to start an Appium session. They describe various
+features that you want your session to have, for example, a certain mobile operating system or a
+certain version of a device. Capabilities are represented as key-value pairs, with values allowed
+to be any valid JSON type, including other objects. Most importantly, they cannot be changed
+during the lifecycle of the session.
 
-W3C WebDriver 仕様の [Capabilities に関するセクション](https://w3c.github.io/webdriver/#capabilities) では、以下の機能を含む 10 個の標準機能のセットが定義されています：
+The capabilities used in Appium follow [the W3C WebDriver specification of the same name](https://w3c.github.io/webdriver/#capabilities).
+The WebDriver spec defines a small set of standard capabilities, including the following:
 
 | Capability 名     | 型        | 説明                    |
 | ---------------- | -------- | --------------------- |
@@ -12,51 +17,64 @@ W3C WebDriver 仕様の [Capabilities に関するセクション](https://w3c.g
 | `browserVersion` | `string` | ブラウザのバージョン            |
 | `platformName`   | `string` | ブラウザをホストするプラットフォームの種類 |
 
+While the above capabilities are commonly used by Appium drivers, they are not sufficient for
+describing Appium-specific features, such as the name of the driver to use, or the name of the app
+to launch. In order to achieve this, Appium defines its own [extension capabilities](https://w3c.github.io/webdriver/#dfn-extension-capability).
+
 ## 一般的なAppiumのCapabilities
 
-Appium はこれらのブラウザに焦点を当てた capabilities を理解しますが、いくつかの capabilities も追加導入しています。 WebDriver 仕様によれば、非標準の「拡張 capabilities」には、capabilities を導入したベンダーを示す名前空間となる接頭辞（末尾に「:」）を含める必要があります。 Appium の接頭辞は「appium:」であるため、Appium 固有の capabilities には必ずこの接頭辞を含める必要があります。 使用しているクライアントによっては接頭辞が自動的に追加される場合もあれば、特定のインターフェースと組み合わせて追加される場合もありますが、明確にするために明示的に追加することをお勧めします。
+According to the WebDriver spec, extension capabilities must include a namespace prefix (signifying
+the vendor introducing the capability), and the namespace must end a colon (`:`). Appium's vendor
+prefix is `appium:`, and so any Appium-specific capabilities must include this prefix. Depending on
+your Appium client, the prefix may be added automatically or in conjunction with certain interfaces,
+but it is always a good practice to explicitly include it for clarity.
 
-以下は様々なドライバーで認識される Appium の capabilities の一覧です：
+Here are a few commonly (but not universally!) used Appium-specific capabilities:
 
-!!! info
+| Capability 名            | 型        | Description                                                     |
+| ----------------------- | -------- | --------------------------------------------------------------- |
+| `appium:automationName` | `string` | 使用するAppiumドライバの名前                                               |
+| `appium:udid`           | `string` | The unique device identifier of a particular device to automate |
+| `appium:app`            | `string` | インストール可能なアプリケーションへのパス                                           |
 
-```
-個々のドライバやプラグインは独自の capabilities をサポートしている場合があるため、具体的な capability 名のリストについては、それぞれのドキュメントを参照してください。また、一部のドライバはこれらの capabilities をすべてサポートしていない場合があります
-```
+All capabilities recognized by the Appium base driver (inherited by all drivers) can be found in the
+[Capabilities Reference document](../reference/session/caps.md). While this common capability set
+is fairly small, it can be greatly extended by Appium drivers and plugins, who can (and should)
+define their own capabilities. Make sure to reference their documentation to learn more about the
+capabilities they support. You can find a list of known drivers in the [Ecosystem Drivers](../ecosystem/drivers.md) document.
 
-| <div style="width:12em">Capability 名</div> | 型         | 必須か | 説明                                                                                                                        |
-| ------------------------------------------ | --------- | --- | ------------------------------------------------------------------------------------------------------------------------- |
-| `platformName`                             | `string`  | はい  | アプリまたはブラウザをホストするプラットフォームの種類                                                                                               |
-| `appium:automationName`                    | `string`  | はい  | 使用するAppiumドライバの名前                                                                                                         |
-| `browserName`                              | `string`  | いいえ | ドライバーが特別なケースとしてWebブラウザーをサポートしている場合、起動して自動化するブラウザーの名前                                                                      |
-| `appium:app`                               | `string`  | いいえ | インストール可能なアプリケーションへのパス                                                                                                     |
-| `appium:deviceName`                        | `string`  | いいえ | 自動化する特定のデバイスの名前、例：`iPhone 14`（現在のところ、iOS シミュレーターを指定する場合にのみ役立ちます。他の状況では通常、`appium:udid` 機能を使用して特定のデバイス Id を使用することをお勧めします）。 |
-| `appium:platformVersion`                   | `string`  | いいえ | プラットフォームのバージョン（例：iOS の場合は `16.0`）                                                                                         |
-| `appium:newCommandTimeout`                 | `number`  | いいえ | クライアントがこれ以上コマンドを送信してこないと判断しセッションを終了する前に、Appium サーバーがクライアントからのコマンド送信を待機する秒数。 デフォルトは `60` 秒。 ゼロに設定するとタイマーが無効になります。          |
-| `appium:noReset`                           | `boolean` | いいえ | true の場合、セッションの開始とクリーンアップ中に通常のリセット処理を回避するように Appium ドライバーに指示します (デフォルトは `false`)                       |
-| `appium:fullReset`                         | `boolean` | いいえ | true の場合、Appium ドライバーに通常のリセット処理に追加の手順を追加して、環境の再現性を最大限に高めるように指示します (デフォルトは `false`)                     |
-| `appium:eventTimings`                      | `boolean` | いいえ | true の場合、Appium ドライバーに [Event Timings](./event-timing.md) を収集するように指示します (デフォルトは `false`)               |
-| `appium:printPageSourceOnFindFailure`      | `boolean` | いいえ | true の場合、要素の検索リクエストが失敗するたびにページソースを収集し、Appium ログに出力します (デフォルトは `false`)                                 |
+Drivers are also able to place more complex constraints on capabilities as a group. For example,
+the XCUITest driver recommends that at least one of `browserName`, `appium:app`, or `appium:bundleId`
+is included in the capabilities, otherwise it will not be able to auto-install or auto-launch any
+application. Each driver will document how it interprets these capabilities and any other
+platform-specific requirements.
 
-ドライバーの中には、capabilitiesのより複雑な制約をグループとして設定しているものもあります。 たとえば、`appium:app` および `browserName`  capabilities は上記では必須ではないと記載していますが、特定のアプリでセッションを開始する場合、XCUITest ドライバーは、`appium:app`、`browserName`、または `appium:bundleId` の少なくとも1 つが capabilities に含まれていることが必要です (含まれていない場合、どのアプリをインストールまたは起動すればよいか判断できないため、ホーム画面からセッションが開かれます)。 各ドライバーは、これらの capabilities やその他のプラットフォーム固有の要件をどのように解釈するかを記述しています。
+The way to construct capabilities and start a session will likely differ depending on your Appium
+client. For examples of doing this in each client library, head to the [Ecosystem Clients](../ecosystem/clients.md)
+page and click through to the appropriate client documentation.
 
 !!! note
 
 ```
-Capabilitiesは、セッション開始時に使用されるパラメータのようなものです。Capabilitiesが送信され、セッションが開始された後変更できません。ドライバーがセッション中に動作の一部を更新する場合、capabilitiesの代わりに、またはcapabilitiesに加えて、[Settings](./settings.md)も利用可能です。
+Once your capabilities are sent to the server and the session is started, they cannot be
+changed. If a driver supports updating its behaviour during a session, it will use the
+[Settings API](./settings.md) for this purpose.
 ```
 
-各 Appium クライアントには、capabilities を構築し、セッションを開始する独自の方法があります。 各クライアントライブラリでこれを行う例については、[エコシステム](../ecosystem/index.md) ページにアクセスし、適切なクライアントドキュメントをクリックしてください。
-
 ## BiDi プロトコルのサポート
 
-Appiumは、base-driver 9.5.0以降で[WebDriver BiDi](https://w3c.github.io/webdriver-bidi/)プロトコルをサポートしています。
-実際の動作は個々のドライバーによって異なりますが、Appium と base-driver はプロトコルをサポートしています。
-ドライバーが BiDi プロトコルをサポートしているかどうか、また、どのようなコマンド/イベントをサポートしているかはドキュメントで確認してください。
+In addition to the standard WebDriver protocol (now known as WebDriver Classic), Appium supports the
+[WebDriver BiDi](https://w3c.github.io/webdriver-bidi/) protocol. Support for this protocol is
+opt-in, and requires the use of the standard `webSocketUrl` capability.
 
-| Capability 名   | 型         | 説明                        |
-| -------------- | --------- | ------------------------- |
-| `webSocketUrl` | `boolean` | セッションで BiDi プロトコルを有効にします。 |
+| Capability Name | 型         | 説明                                              |
+| --------------- | --------- | ----------------------------------------------- |
+| `webSocketUrl`  | `boolean` | Whether BiDi protocol is enabled in the session |
+
+All BiDi commands supported by the Appium base driver (inherited by all drivers) can be found in the
+[BiDi Protocol API Reference document](../reference/api/bidi.md). Similarly to WebDriver Classic
+commands, individual Appium drivers and plugins can define their own supported standard and custom
+BiDi commands, so make sure to reference their documentation.
 
 ## `appium:options` を使用して機能をグループ化する
 
@@ -99,8 +117,7 @@ creates in response to a new session request. This is through the concept of "al
 !!! note
 
 ```
-Check out the [spec itself](https://w3c.github.io/webdriver/#processing-capabilities) or
-a [summarized version](https://github.com/jlipps/simple-wd-spec#processing-capabilities) for
+Check out the [spec itself](https://w3c.github.io/webdriver/#processing-capabilities) for
 a more in-depth description of how capabilities are processed.
 ```
 

packages/appium/docs/ja/guides/security.md

@@ -3,27 +3,27 @@ title: Appium Server Security
 ---
 
 The Appium team makes every effort to ensure the security of the Appium server. This is especially
-important when Appium is run in a multitenant environment, or when multiple users are running
-sessions on the same Appium server. In general, you can only safely enable all of Appium's features if
-all the following are true:
+important when Appium is run in a multi-tenant environment, or when multiple users are running
+sessions on the same Appium server. To ensure a safe environment for Appium's purposes, all of the
+following should be true:
 
 - You're running your own Appium server locally or within a protected internal network
 - You're not sharing it with any untrusted parties
 - You don't expose Appium's port(s) to the wider internet
 
-But because many Appium users might not be able to guarantee such a safe environment, the Appium
-team puts many features behind a security protection mechanism, which forces system admins (the
-people who are in charge of starting the Appium server) to _explicitly opt-in_ to these features.
-(Third-party driver and plugin authors can also hide behaviour behind security
-flags.)
+But because not all Appium hosts can guarantee such a safe environment, certain insecure Appium
+features are disabled by default, and require explicit opt-in in order to enable them. Most
+importantly, this can _only_ be done by the Appium server _host_, and Appium _client_ sessions are
+not allowed to change this.
 
-For security reasons, Appium client sessions can _not_ request feature enablement via capabilities.
-This is the responsibility of the server admin who configures and launches the Appium server.
+While it is possible for an Appium host to simply enable all insecure features at once, each
+feature also has a unique name, which can be used for granular control over the server state.
 
 ## Security Server Args
 
-The [Server CLI](../reference/cli/server.md) doc outlines three relevant arguments which may be passed to
-Appium, when starting it from the command line:
+Enabling or disabling insecure features is done via [Appium server launch arguments](../reference/cli/server.md)
+or [configuration file](./config.md). The former document outlines three relevant arguments for
+achieving this:
 
 | <div style="width:10em">Parameter</div> | Description                                                                                                                                                     |
 | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -31,36 +31,30 @@ Appium, when starting it from the command line:
 | `--allow-insecure`                      | Turns on _only_ specified features, except those blocked by `--deny-insecure`. Has no effect when used in combination with `--relaxed-security` |
 | `--deny-insecure`                       | Explicitly turns _off_ specified features, overriding `--relaxed-security` and `--allow-insecure`                                                               |
 
-All of the above arguments can also be specified in the [Appium Configuration file](./config.md).
-
 Features passed to `--allow-insecure`/`--deny-insecure` must be specified as a comma-separated list,
-and each feature in the list must additionally include a prefix, indicating the driver to which the
-feature should apply. The prefix can be either the driver's `automationName`, or the wildcard (`*`)
-symbol, if the feature should be applied to all drivers. The prefix and feature name are separated
-using the colon character (`:`).
+and each feature in the list must additionally include a prefix, indicating the driver to whose
+sessions the feature should apply. The prefix can be either the driver's `automationName`, or the
+wildcard (`*`) symbol, if the feature should be applied to all drivers. The prefix and feature name
+are separated using the colon character (`:`).
 
 For example, `first:foo` refers to the `foo` feature for the `first` driver, whereas `*:bar` refers
 to the `bar` feature for all drivers.
 
 ## Insecure Features
 
-Each Appium driver is responsible for its own security, and can create its own feature names. Thus,
-you should read through the documentation for a particular driver to know which feature names it
-might use. Here is an incomplete list of examples from some of Appium's official drivers:
+Almost all insecure features are defined on a per-driver or plugin basis, so make sure to read the
+documentation for a particular driver/plugin to know which feature names it might use.
 
-| <div style="width:12em">Feature Name</div> | Description                                                                             | Supported Extension(s)      |
-| ------------------------------------------ | --------------------------------------------------------------------------------------- | ---------------------------------------------- |
-| `get_server_logs`                          | Allows retrieving of Appium server logs via the Webdriver log interface                 | IOS, XCUITest, Android, UiAutomator2, Espresso |
-| `adb_shell`                                | Allows execution of arbitrary shell commands via ADB, using the `mobile: shell` command | Android, UiAutomator2, Espresso                |
-| `record_audio`                             | Allow recording of host machine audio inputs                                            | XCUITest                                       |
-| `execute_driver_script`                    | Allows sending a request that has multiple Appium commands.             | Execute Driver Plugin                          |
+Certain insecure features are also defined on the Appium server itself. For a list of these
+features, as well as the features defined in official plugins, see
+[the Insecure Features CLI Reference](../reference/cli/insecure-features.md) doc.
 
-Some insecure features operate on the server level and do not require a driver session. Enabling
-these features require using the wildcard prefix:
+!!! note
 
-| <div style="width:12em">Feature Name</div> | Description                                                                     |
-| ------------------------------------------ | ------------------------------------------------------------------------------- |
-| `session_discovery`                        | Allows retrieving the list of active server sessions via `GET /appium/sessions` |
+```
+If you are a driver or plugin author and want to implement insecure features of your own, check
+out the [Building Drivers documentation](../developing/build-drivers.md#understand-server-assigned-driver-properties-and-security-flags).
+```
 
 ## Examples
 

packages/appium/docs/ja/index.md

@@ -30,9 +30,9 @@ Appiumのドキュメントにようこそ！ Appiumはオープンソースプ
       </a>
     </div>
     <div class="homepageSponsor">
-      <a href="https://lambdatest.com/?utm_source=appium.io&utm_medium=organic&utm_campaign=june_25&utm_term=sk&utm_content=webpage">
-        <img src="assets/images/sponsor-logo-lambdatest-dark.png#only-dark" style="width: 220px;" />
-        <img src="assets/images/sponsor-logo-lambdatest-light.png#only-light" style="width: 220px;" />
+      <a href="https://www.testmuai.com">
+        <img src="assets/images/sponsor-logo-testmuai-dark.png#only-dark" style="width: 220px;" />
+        <img src="assets/images/sponsor-logo-testmuai-light.png#only-light" style="width: 220px;" />
       </a>
     </div>
   </div>

packages/appium/docs/ja/reference/api/others.md

@@ -397,6 +397,45 @@ Deletes the virtual sensor with the type identified by `:sensorType`.
 
 `null`
 
+## Global Privacy Control Protocol
+
+The [Global Privacy Control protocol](https://www.w3.org/TR/gpc) (GPC) is an extension of the W3C
+WebDriver protocol.
+
+### setGlobalPrivacyControl
+
+```
+POST /session/:sessionId/privacy
+```
+
+> GPC documentation: [Set Global Privacy Control](https://www.w3.org/TR/gpc/#set-global-privacy-control)
+
+Sets the value of the do-not-sell-or-share preference for the current session.
+
+#### Parameters
+
+| Name  | Description                                                          | Type    |
+| ----- | -------------------------------------------------------------------- | ------- |
+| `gpc` | Whether the browser should perform do-not-sell-or-share interactions | boolean |
+
+#### Response
+
+`null`
+
+### getGlobalPrivacyControl
+
+```
+GET /session/:sessionId/privacy
+```
+
+> GPC documentation: [Get Global Privacy Control](https://www.w3.org/TR/gpc/#get-global-privacy-control)
+
+Retrieves the value of the do-not-sell-or-share preference for the current session.
+
+#### Response
+
+`boolean` - the preference value
+
 ## Permissions Protocol
 
 The [Permissions protocol](https://www.w3.org/TR/permissions/) is an extension of the W3C WebDriver
@@ -524,6 +563,32 @@ Retrieves the available log types that can be used to call the [`getLog`](#getlo
 
 `string[]` - an array of log types
 
+## Storage Access Protocol
+
+The [Storage Access protocol](https://privacycg.github.io/storage-access/) is an extension of the
+W3C WebDriver protocol.
+
+### setStorageAccess
+
+```
+POST /session/:sessionId/storageaccess
+```
+
+> Storage Access documentation: [Set Storage Access](https://privacycg.github.io/storage-access/#set-storage-access-command)
+
+Sets the storage access policy of the current browsing context.
+
+#### Parameters
+
+| Name      | Description                                                                                                                                                                                      | Type    |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------- |
+| `blocked` | Whether storage access should be blocked (`true`) or allowed (`false`)                                                                                     | boolean |
+| `origin`  | The origin to which the policy should be applied. Must be either a valid URL, or an asterisk (`*`) if the policy should apply to all origins. | string  |
+
+#### Response
+
+`null`
+
 ## Web Authentication Protocol
 
 The [Web Authentication protocol](https://w3c.github.io/webauthn/) (WebAuthn) is an extension of

packages/appium/docs/ja/reference/api/plugins.md

@@ -224,7 +224,7 @@ Deletes a file in the storage.
 #### Response
 
 `boolean` - `true` upon successful file deletion, or `false` if the file does not exist in
-the storage
+the storage, or if the delete request is invalid.
 
 ### listStorageItems
 

packages/appium/docs/ja/reference/cli/extensions.md

@@ -118,6 +118,12 @@ appium {driver|plugin} install <install-spec>
     appium driver install git://github.com/appium/appium-xcuitest-driver.git --source=git --package=appium-xcuitest-driver
     ```
 
+- Install a branch of XCUITest driver repository using a Git URL:
+
+    ```
+    appium driver install git://github.com/appium/appium-xcuitest-driver.git#specific-branch --source=git --package=appium-xcuitest-driver
+    ```
+
 ## `list`
 
 Lists all installed extensions, plus all official extensions that are not installed.
@@ -135,6 +141,7 @@ appium {driver|plugin} list
 | `--installed`                         | Only list all installed extensions                                                                                                                                     | boolean |
 | `--json`                              | Return the result in JSON format                                                                                                                                       | boolean |
 | `--updates`                           | List all extensions along with information on whether newer versions are available. Only supported for extensions installed via `npm`. | boolean |
+| `--verbose`                           | Show additional details for each extension                                                                                                                             | boolean |
 
 #### Example
 

packages/appium/docs/ja/reference/cli/index.md

@@ -31,5 +31,6 @@ The executable has four main subcommands: `server`, `driver`, `plugin`, and `set
 
 </div>
 
-Appium also recognizes several [environment variables](./env-vars.md), which may be used for
-advanced configuration.
+The Appium server also recognizes several [environment variables](./env-vars.md) and
+[insecure feature names](./insecure-features.md), though drivers and plugins can also define
+variables and features of their own.

packages/appium/docs/ja/reference/cli/insecure-features.md

@@ -0,0 +1,23 @@
+---
+hide:
+  - toc
+
+title: Insecure Features
+---
+
+The Appium server implements [a security protection mechanism](../../guides/security.md) that
+allows the management of various insecure features.
+
+The following features are defined on the server level and can be used even without drivers, but
+they can only be enabled using the wildcard (`*`) prefix:
+
+| Feature Name        | Description                                                                     |
+| ------------------- | ------------------------------------------------------------------------------- |
+| `session_discovery` | Allows retrieving the list of active server sessions via `GET /appium/sessions` |
+
+Of course, Appium drivers and plugins are free to define additional insecure features of their own.
+The following features are defined by official plugins:
+
+| Feature Name            | Plugin           | Description                                                |
+| ----------------------- | ---------------- | ---------------------------------------------------------- |
+| `execute_driver_script` | `execute_driver` | Allows sending a request that has multiple Appium commands |

packages/appium/docs/ja/reference/cli/server.md

@@ -29,6 +29,7 @@ appium
 | `--address`, `-a`                      | IPv4/IPv6 address to listen on                                                                                                                                                                                                                                                                                                                     | string        | `0.0.0.0`                                                |
 | `--allow-cors`                         | Allow web browser connections from any host                                                                                                                                                                                                                                                                                                        | boolean       | `false`                                                  |
 | `--allow-insecure`                     | List of [insecure features](../../guides/security.md) that should be allowed in this server's sessions. Individual features can be overridden by `--deny-insecure`. Has no effect in combination with `--relaxed-security`.                                                                        | array<string> | `[]`                                                     |
+| `--allow-unknown-args`                 | Do not exit if unrecognized command-line arguments are passed to the server; ignore them instead. Useful when the Appium CLI is wrapped by external tooling that appends extra flags.                                                                                                                              | boolean       | `false`                                                  |
 | `--base-path`, `-pa`                   | Base path to use as the prefix for all webdriver routes running on the server                                                                                                                                                                                                                                                                      | string        | `""`                                                     |
 | `--callback-address`, `-ca`            | Callback IP address                                                                                                                                                                                                                                                                                                                                | string        | `0.0.0.0`                                                |
 | `--callback-port`, `-cp`               | Callback port                                                                                                                                                                                                                                                                                                                                      | integer       | `4723`                                                   |
@@ -48,6 +49,8 @@ appium
 | `--log-no-colors`                      | Disable colors in the server log                                                                                                                                                                                                                                                                                                                   | boolean       | `false`                                                  |
 | `--log-timestamp`                      | Show timestamps in the server log                                                                                                                                                                                                                                                                                                                  | boolean       | `false`                                                  |
 | `--long-stacktrace`                    | Add long stack traces to log entries. Recommended for debugging only.                                                                                                                                                                                                                                              | boolean       | `false`                                                  |
+| `--max-ipc-data-size`                  | Maximum byte size of IPC message objects.                                                                                                                                                                                                                                                                                          | integer       | `1048576` (1MB)                       |
+| `--max-ipc-topics`                     | Maximum number of IPC topics per session.                                                                                                                                                                                                                                                                                          | integer       | `1000`                                                   |
 | `--no-perms-check`                     | Skip various permission checks on the server startup                                                                                                                                                                                                                                                                                               | boolean       | `false`                                                  |
 | `--nodeconfig`                         | JSON configuration for registering Appium as a node with Selenium Grid 3                                                                                                                                                                                                                                                                           | object        |                                                          |
 | `--plugin`                             | Plugin-specific configuration. Keys should correspond to plugin package names                                                                                                                                                                                                                                                      | object        |                                                          |

packages/appium/docs/ja/reference/index.md

@@ -5,8 +5,8 @@ hide:
 title: Reference
 ---
 
-This section of the Appium documentation provides a reference to the two main interfaces within the
-Appium server: the command-line executable, and the supported API endpoints.
+This section of the Appium documentation provides a reference to the core interfaces supported within the
+Appium server:
 
 <div class="grid cards" markdown>
 
@@ -16,10 +16,16 @@ Appium server: the command-line executable, and the supported API endpoints.
 
   Learn how to use the Appium command-line executable
 
+- :material-lan-connect: [**Session Properties**](./session/index.md)
+
+  ---
+
+  See the values of global Appium session properties
+
 - :material-cloud-braces: [**API Endpoints**](./api/index.md)
 
   ---
 
-  View endpoints supported by the Appium server
+  View endpoints supported by the core Appium server
 
 </div>

packages/appium/docs/ja/reference/session/caps.md

@@ -0,0 +1,56 @@
+---
+hide:
+  - toc
+
+title: Capabilities
+---
+
+The following [capabilities](../../guides/caps.md) are recognized by the Appium server/base driver,
+and are therefore supported by all drivers as well. Some capabilities are directly handled by the
+server/base driver, while others are only validated before being passed to the actual driver.
+
+!!! note
+
+    Capabilities not listed here will _not_ be rejected by Appium: they will simply be forwarded
+    directly to the active driver/plugin.
+
+### Required Capabilities
+
+These capabilities are used in the Appium server/base driver, and are explicitly required in all
+Appium sessions.
+
+| Capability              | Description                                 | Type     |
+| ----------------------- | ------------------------------------------- | -------- |
+| `platformName`          | Type of platform hosting the app or browser | `string` |
+| `appium:automationName` | Name of the Appium driver to use            | `string` |
+
+### Optional Capabilities
+
+These capabilities are used in the Appium server/base driver, but are optional, and may have a
+default value.
+
+| <div style="width:19em">Capability</div>              | Description                                                                                                                                                                                                          | Type      | Default |
+| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------- |
+| `webSocketUrl`                                        | Toggle support of the WebDriver BiDi protocol                                                                                                                                                                        | `boolean` |         |
+| `appium:eventTimings` (deprecated) | Toggle collection of [Event Timings](../../guides/event-timing.md). This capability is deprecated - please use the [`getLogEvents`](../api/appium.md#getlogevents) endpoint instead. | `boolean` |         |
+| `appium:newCommandTimeout`                            | Number of seconds the Appium server should wait for clients to send commands before stopping the session. A value of `0` disables the timeout.                                       | `number`  | `60`    |
+| `appium:printPageSourceOnFindFailure`                 | Toggle retrieval of the the page source and its printing to the Appium log, whenever a request to find an element fails                                                                                              | `boolean` |         |
+
+### Validated Capabilities
+
+These capabilities are not directly used in the Appium server/base driver, but are still subject to
+validation checks due to their relevance in other drivers. The actual handling of these
+capabilities is optional and entirely driver-dependent.
+
+| Capability                                          | Validation                                                    |
+| --------------------------------------------------- | ------------------------------------------------------------- |
+| `platformVersion`                                   | Must be `string`                                              |
+| `appium:app`                                        | Must be `string`; empty values are ignored                    |
+| `appium:autoLaunch` (deprecated) | Must be `boolean`                                             |
+| `appium:autoWebview`                                | Must be `boolean`                                             |
+| `appium:fullReset`                                  | Must be `boolean`; mutually exclusive with `appium:noReset`   |
+| `appium:language`                                   | Must be `string`                                              |
+| `appium:locale`                                     | Must be `string`                                              |
+| `appium:orientation`                                | Must be either `LANDSCAPE` or `PORTRAIT`                      |
+| `appium:noReset`                                    | Must be `boolean`; mutually exclusive with `appium:fullReset` |
+| `appium:udid`                                       | Must be `string`                                              |

packages/appium/docs/ja/reference/session/index.md

@@ -0,0 +1,23 @@
+---
+hide:
+  - toc
+
+title: Session Properties
+---
+
+An Appium session has several key properties, each with its own set of supported values:
+capabilities, execute methods, settings, locator strategies, and others. The supported values for
+each property are primarily defined by the active driver and plugins, but some properties also have
+common values provided by the Appium server and its base driver:
+
+<div class="grid cards" markdown>
+
+- [**Capabilities**](./caps.md)
+
+  A small set of basic capabilities
+
+- [**Command Endpoints**](../api/index.md)
+
+  The core set of API endpoints
+
+</div>

packages/appium/docs/ja/resources/index.md

@@ -8,11 +8,6 @@ title: Additional Resources
 
 Here you can find links to additional Appium resources around the web:
 
-## Websites
-
-- [Appium Pro](https://appiumpro.com) - a blog and newsletter written by one of Appium's
-  maintainers, Jonathan Lipps, with lots of useful guides
-
 ## Online Courses
 
 - [Appium and Selenium Fundamentals](https://ui.headspin.io/university/learn/appium-selenium-fundamentals-2020) - a comprehensive video course on learning Python, Selenium, and Appium by Jonathan Lipps
@@ -26,3 +21,4 @@ Here you can find links to additional Appium resources around the web:
 - [AppiumConf 2021](https://www.youtube.com/playlist?list=PL9Z-JgiTsOYRCcJhDfmKAah9XmAp2b903)
 - [AppiumConf 2024](https://www.youtube.com/playlist?list=PL9Z-JgiTsOYQaU5i5LJtAWlh5WVZPi3If)
 - [SeleniumConf & AppiumConf 2025](https://www.youtube.com/playlist?list=PLRdSclUtJDYV2R92TLbmwxws6clruuTjH)
+- [SeleniumConf & AppiumConf 2026](https://www.youtube.com/playlist?list=PLRdSclUtJDYVgVqdKnSyBLBmFdA0KE_Dk)

packages/appium/docs/ja/sponsors/index.md

@@ -22,6 +22,11 @@ Hub.
 We are very grateful for the support of our Development Partners, who donate Appium development and
 maintenance as part of their employees' core job duties!
 
+<a href="https://www.testmuai.com">
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-dark.png#only-dark" width="250" alt="TestMu AI (formerly LambdaTest)" />
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-light.png#only-light" width="250" alt="TestMu AI (formerly LambdaTest)" />
+</a>
+
 ## Strategic Partners
 
 We are very grateful for the financial and marketing support of our exclusive Strategic Partners,
@@ -33,9 +38,9 @@ contributors!
   <img src="/docs/en/latest/assets/images/sponsor-logo-browserstack-light.png#only-light" width="250" alt="BrowserStack" />
 </a>
 
-<a href="https://lambdatest.com/?utm_source=appium.io&utm_medium=organic&utm_campaign=june_25&utm_term=sk&utm_content=webpage">
-  <img src="/docs/en/latest/assets/images/sponsor-logo-lambdatest-dark.png#only-dark" width="250" alt="LambdaTest" />
-  <img src="/docs/en/latest/assets/images/sponsor-logo-lambdatest-light.png#only-light" width="250" alt="LambdaTest" />
+<a href="https://www.testmuai.com">
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-dark.png#only-dark" width="250" alt="TestMu AI (formerly LambdaTest)" />
+  <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-light.png#only-light" width="250" alt="TestMu AI (formerly LambdaTest)" />
 </a>
 
 ## Gold Sponsors

packages/appium/docs/mkdocs-en.yml

@@ -42,6 +42,10 @@ nav:
           - reference/cli/extensions.md
           - reference/cli/setup.md
           - reference/cli/env-vars.md
+          - reference/cli/insecure-features.md
+      - Session Properties:
+          - reference/session/index.md
+          - reference/session/caps.md
       - API Endpoints:
           - reference/api/index.md
           - reference/api/webdriver.md

packages/appium/docs/mkdocs-ja.yml

@@ -42,6 +42,10 @@ nav:
           - reference/cli/extensions.md
           - reference/cli/setup.md
           - reference/cli/env-vars.md
+          - reference/cli/insecure-features.md
+      - Session Properties:
+          - reference/session/index.md
+          - reference/session/caps.md
       - API Endpoints:
           - reference/api/index.md
           - reference/api/webdriver.md

packages/appium/docs/mkdocs-zh.yml

@@ -9,40 +9,44 @@ theme:
 nav:
   - 欢迎使用: index.md
   - 博客: blog/index.md
-  - 简介：
+  - 简介:
       - intro/index.md
-      - 背景：
+      - 背景:
           - intro/appium.md
           - intro/drivers.md
           - intro/clients.md
           - intro/history.md
-  - 快速开始：
+  - 快速开始:
       - quickstart/index.md
       - quickstart/requirements.md
       - quickstart/install.md
       - quickstart/uiauto2-driver.md
-      - 写一个测试：
+      - 写一个测试:
           - quickstart/test-js.md
           - quickstart/test-py.md
           - quickstart/test-java.md
           - quickstart/test-rb.md
           - quickstart/test-dotnet.md
       - quickstart/next-steps.md
-  - 生态系统：
+  - 生态系统:
       - ecosystem/index.md
       - ecosystem/drivers.md
       - ecosystem/clients.md
       - ecosystem/plugins.md
       - ecosystem/tools.md
-  - 参考：
+  - 参考:
       - reference/index.md
-      - 命令行界面：
+      - 命令行界面:
           - reference/cli/index.md
           - reference/cli/server.md
           - reference/cli/extensions.md
           - reference/cli/setup.md
           - reference/cli/env-vars.md
-      - API 端点：
+          - reference/cli/insecure-features.md
+      - Session Properties:
+          - reference/session/index.md
+          - reference/session/caps.md
+      - API 端点:
           - reference/api/index.md
           - reference/api/webdriver.md
           - reference/api/bidi.md
@@ -51,11 +55,11 @@ nav:
           - reference/api/appium.md
           - reference/api/others.md
           - reference/api/plugins.md
-  - 指南：
-      - 迁移：
+  - 指南:
+      - 迁移:
           - guides/migrating-2-to-3.md
           - guides/migrating-1-to-2.md
-      - 服务器/驱动程序配置：
+      - 服务器/驱动程序配置:
           - guides/managing-exts.md
           - guides/branch-testing.md
           - guides/config.md
@@ -65,24 +69,24 @@ nav:
           - guides/grid.md
           - guides/caching.md
           - guides/tls.md
-      - 会话配置：
+      - 会话配置:
           - guides/caps.md
           - guides/settings.md
           - guides/execute-methods.md
           - guides/context.md
           - guides/event-timing.md
-  - 更多资源：
+  - 更多资源:
       - resources/index.md
-  - 开发：
+  - 开发:
       - developing/index.md
       - developing/build-drivers.md
       - developing/build-plugins.md
       - developing/build-docs.md
       - developing/build-doctor-checks.md
       - developing/sensitive.md
-      - 开发者参考：
+      - 开发者参考:
           - developing/config-system.md
-  - 贡献：
+  - 贡献:
       - contributing/index.md
-  - 赞助者：
+  - 赞助者:
       - sponsors/index.md

packages/appium/docs/overrides/partials/sponsors.html

@@ -5,7 +5,7 @@
     <img src="/docs/en/latest/assets/images/sponsor-logo-browserstack-dark.png" />
   </a>
 
-  <a href="https://lambdatest.com/?utm_source=appium.io&utm_medium=organic&utm_campaign=june_25&utm_term=sk&utm_content=webpage">
-    <img src="/docs/en/latest/assets/images/sponsor-logo-lambdatest-dark.png" />
+  <a href="https://www.testmuai.com">
+    <img src="/docs/en/latest/assets/images/sponsor-logo-testmuai-dark.png" />
   </a>
 </div>

packages/appium/docs/scripts/build-docs.js

@@ -20,7 +20,7 @@ const {
   DOCS_REMOTE,
   LATEST_ALIAS,
 } = require('./utils');
-const path = require('path');
+const path = require('node:path');
 const semver = require('semver');
 const {version} = require('../../package.json');
 
@@ -31,6 +31,9 @@ const preview = Boolean(process.env.APPIUM_DOCS_PREVIEW);
 
 const push = Boolean(process.env.APPIUM_DOCS_PUBLISH);
 
+/**
+ * Builds and optionally deploys docs for each supported language.
+ */
 async function main() {
   log.info(`Building Appium docs and committing to ${DOCS_BRANCH}`);
 

packages/appium/docs/scripts/gen-cli-args-docs.js

@@ -3,7 +3,7 @@
 /* eslint-disable promise/prefer-await-to-callbacks */
 /* eslint-disable promise/prefer-await-to-then */
 
-const path = require('path');
+const path = require('node:path');
 const {fs} = require('@appium/support');
 const {AppiumConfigJsonSchema} = require('@appium/schema');
 
@@ -12,6 +12,9 @@ const DOC_PATH = path.resolve(__dirname, '..', 'en', 'cli', 'args.md');
 const START_TAG = `<!-- AUTOGEN-START -->`;
 const STOP_TAG = `<!-- AUTOGEN-STOP -->`;
 
+/**
+ * Regenerates the CLI arguments table in docs.
+ */
 async function main() {
   console.log(`Gathering current cli doc file contents...`);
   const [preStart, postEnd] = await getDocParts();

packages/appium/docs/scripts/utils.js

@@ -3,7 +3,7 @@
 // for simplicity this file is not transpiled and is run directly via an npm script
 //
 const {logger} = require('@appium/support');
-const path = require('path');
+const path = require('node:path');
 
 const log = logger.getLogger('Docs');
 

packages/appium/docs/zh/blog/posts/announcing-appiumconf2024.md

@@ -5,9 +5,9 @@ authors:
 date: 2024-07-13
 ---
 
-# Appium Conf 2024: Call for Proposals Now Open!
+# Appium Conf 2024: 现在开始征集提案
 
-We're thrilled to announce that Appium Conf is back and going online for 2024! This is the official Appium conference where you can learn all about what's new in Appium 2.0 and explore the latest in automating tests for devices, mobile apps, and desktop applications.
+我们很兴奋地宣布，Appium Conf 已回归并在2024年上线！ 这是官方的Appium会议，您可以在会上了解Appium 2中的所有新内容。 并探索设备自动化测试、移动应用程序和桌面应用程序的最新版本。
 
 <!-- more -->
 
@@ -17,29 +17,29 @@ We're thrilled to announce that Appium Conf is back and going online for 2024! T
 </a>
 </div>
 
-## Mark Your Calendars: September 13, 2024
+## 标记您的日历：2024年9月13日
 
-Join us on September 13, 2024, for a full day of inspiring and practical talks from the Appium team and the world's top mobile testing and automation experts. With Appium 2.0 now well-established, this is your opportunity to dive deep and learn how to maximize its potential.
+2024年9月13日，请加入我们，参加Appium团队和世界顶级移动测试和自动化专家为期一天的鼓舞人心且实用的演讲。 随着Appium 2.0的成熟，这是您深入了解并学习如何最大限度地发挥其潜力的机会。
 
-## Why Attend Appium Conf 2024?
+## 为什么参加了2024年的Appium Conf ？
 
-1. **Gain Insights**: Hear interesting insights and inspiring case studies from global experts and the core Appium team.
-2. **Improve Your Strategy**: Gain valuable knowledge to enhance your own automation strategy.
-3. **Network**: Make connections with Appium users from around the globe.
-4. **Learn from Specialists**: Benefit from Appium specialists' expertise on a variety of topics.
+1. **获得见解**：听取全球专家和核心Appium团队的有趣见解和鼓舞人心的案例研究。
+2. **改进您的战略**：获得有价值的知识，以增强您自己的自动化战略。
+3. **网络**：与来自全球的Appium用户建立联系。
+4. **向专家学习**：从Appium专家在各种主题上的专业知识中受益。
 
-## Call for Proposals: Share Your Knowledge!
+## 征集提案：分享您的知识！
 
-We're looking for a diverse range of speakers from around the globe who are eager to share innovative ideas and use-cases of mobile test automation. If you have experience with Appium and insights that could benefit the community of test practitioners, we want to hear from you!
+我们正在寻找来自全球各地的各种演讲者，他们渴望分享移动测试自动化的创新想法和用例。 如果您有使用Appium的经验和见解，可以使测试从业者社区受益，我们想听听您的意见！
 
-Don't miss this chance to contribute to the Appium community and showcase your expertise on a global stage.
+不要错过这个机会，为Appium社区做出贡献，并在全球舞台上展示你的专业知识。
 
-## How to Submit Your Proposal
+## 如何提交您的提案
 
-Visit our website at [https://appiumconf.com/](https://appiumconf.com/) and [Submit a Proposal](https://confengine.com/conferences/appium-conf-2024/proposals?utm_medium=referal&utm_source=appium.io&utm_campaign=launch). We're excited to see your innovative ideas and experiences with Appium!
+访问我们的网站 [https://appiumconf.com/](https://appiumconf.com/) 并[提交提案](https://confengine.com/conferences/appium-conf-2024/proposals?utm_medium=referal&utm_source=appium.io&utm_campaign=launch)。 我们很高兴看到您在 Appium 中的创新想法和经验！
 
-## Stay Tuned
+## 敬请期待
 
-Keep an eye on our website and social media channels for updates on the conference schedule, keynote speakers, and more exciting details about Appium Conf 2024.
+关注我们的网站和社交媒体频道以了解会议日程安排的更新， 主旨演讲人和2024年Appium Conf 的更令人兴奋的细节。
 
-Join us in shaping the future of mobile and device test automation. Submit your proposal today and be part of this exciting event!
+加入我们来塑造移动设备测试自动化的未来。 立即提交您的提案，成为这一激动人心的活动的一部分！

packages/appium/docs/zh/contributing/index.md

@@ -7,7 +7,7 @@ title: 对Appium 的贡献
 
 Appium项目离不开来自公司和志愿者的代码、文档、维护和支持的众多贡献。 因此，我们欢迎贡献！
 
-有许多不同的方式可以帮助项目——请参阅下方了解您可以做的一切以及每个贡献方法的流程。 请注意，无论您如何贡献，您的参与都受我们的[行为准则](https://github.com/appium/appium/blob/master/CONDUCT.md)管辖。
+有许多不同的方式可以帮助项目——请参阅下方了解您可以做的一切以及每个贡献方法的流程。 请注意，无论您如何贡献，您的参与都受我们的[行为准则](https://github.com/appium/.github/blob/master/CODE_OF_CONDUCT.md)管辖。
 
 ## 加入讨论论坛
 

packages/appium/docs/zh/developing/build-docs.md

@@ -1,84 +1,66 @@
 ---
-title: Building Documentation
+title: 构建文档
 ---
 
-Once you've [built a driver](./build-drivers.md) or [built a plugin](./build-plugins.md) for Appium,
-you will hopefully want to document how that extension works for your users. The most basic way of
-doing this is to write up a quick `README.md` and keep it in the root of your project's repository.
-However, this can involve a lot of effort.
+一旦你为 Appium 构建了 [驱动](./build-drivers.md) 或 [插件](./build-plugins.md)，通常也会希望为用户说明这个扩展是如何工作的。 最基础的方式就是编写一个简短的 `README.md`，并将它放在项目仓库的根目录中。
+不过，这样做可能会耗费不少精力。
 
-The Appium project has built tools to help with this, and we've packaged up these tools so our
-ecosystem developers building drivers and plugins can _also_ use them. The best way to get going
-with these tools is probably to look at an existing Appium driver repo to see how it's done, for
-example the [XCUITest driver repo](https://github.com/appium/appium-xcuitest-driver). But this guide
-will outline the basic approach.
+Appium 项目已经提供了辅助工具，并且我们把这些工具打包好了，以便生态系统中的驱动和插件开发者也能使用。 这些工具最好的入门方式是查看一个现有的 Appium 驱动仓库，看看它是如何组织文档的，例如 [XCUITest 驱动仓库](https://github.com/appium/appium-xcuitest-driver)。 不过，本指南会先介绍基本的实现思路。
 
-### Conceptual architecture
+### 概念架构
 
-Appium settled on [MkDocs](https://www.mkdocs.org/) as a Markdown-based documentation site
-generator. It uses a Python toolchain (and not Node.js), but it turned out to be the best option
-for our purposes. You can adjust this, but by default Appium's utilities also assume that you'll be
-using the [mkdocs-material](https://squidfunk.github.io/mkdocs-material/) theme/extension for
-MkDocs.
+Appium 采用 [MkDocs](https://www.mkdocs.org/) 作为基于 Markdown 的文档站点的生成工具。 它使用 Python 工具链（而不是 Node.js），但这恰好是我们当前需求下最合适的选择。 你可以自行调整，不过默认情况下，Appium 的工具链也会假设你使用 [mkdocs-material](https://squidfunk.github.io/mkdocs-material/) 主题与扩展来搭建 MkDocs。
 
-In order to make different versions of your docs available (one for each minor release of your
-extension, typically), we also bundle [Mike](https://github.com/jimporter/mike).
+为了让你的文档能够支持不同版本（通常是每个小版本一个），我们还会捆绑 [Mike](https://github.com/jimporter/mike)。
 
-From here, building a basic docs site is as easy as collecting your Markdown files together and
-defining how you want them to be organized.
+从这里开始，构建一个基础文档站点其实很简单：把 Markdown 文件收集起来，再定义你希望它们如何组织即可。
 
-### Prerequisites
+### 前置条件
 
-To take advantage of Appium's documentation utilities, you'll need to install:
+要使用 Appium 的文档工具，你需要安装以下内容：
 
 - [Python v3+](https://www.python.org/downloads/)
-- [pip](https://pip.pypa.io/en/stable/installation/) (this may be installed automatically with Python)
-- The `@appium/docutils` package:
+- [pip](https://pip.pypa.io/en/stable/installation/)（通常 Python 会自动附带安装）
+- `@appium/docutils` 包：
 
   ```bash
   npm install --save-dev @appium/docutils
   ```
 
-### Initializing an Extension for Building Docs
+### 初始化用于构建文档的扩展
 
-To prepare your extension for generating documentation, run the following command:
+要为你的扩展准备文档生成环境，请运行下面的命令：
 
 ```bash
 npx appium-docs init
 ```
 
-This will:
+这一步会：
 
-1. Create a `tsconfig.json` if one does not already exist. This is necessary even if your extension
-   is not written in TypeScript.
-2. Create a `mkdocs.yml` with the necessary configuration for MkDocs.
+1. 创建一个 `tsconfig.json`（如果当前还没有的话）。 即使你的扩展并不是 TypeScript 编写的，这也是必需的。
+2. 创建一个 `mkdocs.yml`，其中包含 MkDocs 所需的配置。
 
-### Documenting Your Extension
+### 为你的扩展编写文档
 
-At this point, you can begin documenting your extension. By default, MkDocs will look for Markdown
-files in the `docs` directory. You can therefore create your Markdown documentation files, place
-them in `docs`, and add links to these files in `mkdocs.yml`.
+此时你就可以开始为扩展编写文档了。 默认情况下，MkDocs 会在 `docs` 目录中查找 Markdown 文件。 因此，你可以创建文档文件并放入 `docs`，然后在 `mkdocs.yml` 里添加相应链接。
 
-Refer to the [MkDocs documentation](https://www.mkdocs.org/user-guide/writing-your-docs/) for
-information on how to organize and structure your documentation.
+请参考 [MkDocs 文档](https://www.mkdocs.org/user-guide/writing-your-docs/) 来了解如何组织与构建你的文档结构。
 
-### Building the Docs
+### 构建文档
 
-At this point, you can use the `appium-docs` CLI tool. Run this tool with no arguments to get the
-full help output and see all the available subcommands and parameters. Here are a few usage
-examples:
+在这个阶段，你可以使用 `appium-docs` CLI 工具。 运行这个工具时不传任何参数，可以看到完整的帮助信息，以及所有可用的子命令与参数。 下面是几个常见用法示例：
 
 ```bash
-# Generate reference and build the mkdocs site into the site dir
+# 生成参考文档并将 mkdocs 站点构建到 site 目录
 npx appium-docs build
 
-# Same as build, but host the docs on a local dev server
-# and watch for changes and rebuild when files change
+# 与 build 相同，但会在本地启动开发服务器
+# 并监听文件变化，在内容变更时自动重建
 npx appium-docs build --serve
 
-# Build the docs and deploy them with mike versioning to the docs-site branch
-# using the included commit message.
-# This is particularly useful for pushing content to a GitHub pages branch!
+# 构建文档并使用 mike 进行版本化部署到 docs-site 分支
+# 其中包含内置提交信息。
+# 这对于把内容推送到 GitHub Pages 分支特别有用！
 npx appium-docs build \
   --deploy \
   -b docs-site \

packages/appium/docs/zh/developing/build-doctor-checks.md

@@ -1,45 +1,33 @@
 ---
-title: Building Doctor Checks
+title: 构建 Doctor Checks
 ---
 
-The idea of Appium Doctor is to assist users with driver or plugin preconditions setup. Sometimes such
-preconditions might be quite complicated and require non-trivial technical knowledge. Doctor checks,
-which are vanilla Node.js class instances written by extension authors, simplify
-the setup process by automating diagnostics and possible fixes for the found issues. These checks
-might also be interactive to ensure better usage experience.
+Appium Doctor 的目标，是帮助用户完成驱动或插件的前置条件配置。 有时这些前置条件可能相当复杂，需要一定的技术知识。 Doctor checks是由扩展作者编写的普通 Node.js 类实例，它可以自动完成诊断并尝试修复发现的问题。 为了提供更好的使用体验，这些检查项有时也会是交互式的。
 
-This tutorial is supposed to be used by plugin or driver authors that would like to help their users
-to deal with complicated setup or configuration steps.
+本教程适用于希望帮助用户处理复杂配置或设置步骤的插件或驱动作者。
 
-## Adding Doctor Checks
+## 添加 Doctor Checks
 
-### Typing Requirements
+### 类型要求
 
-The term `Doctor Check` literally describes a single javascript class instance that implements the
-[IDoctorCheck interface](https://github.com/appium/appium/blob/master/packages/types/lib/doctor.ts).
-The interface defines the following methods and properties:
+术语 `Doctor Check` 的字面含义，是指一个实现了 [IDoctorCheck 接口](https://github.com/appium/appium/blob/master/packages/types/lib/doctor.ts) 的 JavaScript 类实例。
+这个接口定义了以下方法和属性：
 
-- `diagnose(): Promise<DoctorCheckResult>`: Contains the code to diagnose a possible issue
-- `fix(): Promise<string|null>`: Either fixes the actual problem if `hasAutofix()` returns true or
-  returns a string description for possible manual fixes. If this method throws an exception named
-  `FixSkippedError` and `hasAutofix()` returns true then the result of the method invocation
-  is going to be ignored.
-- `hasAutofix(): boolean`: Whether calling `fix()` would resolve the found issue
-- `isOptional(): boolean`: Whether the found issue can be ignored and is not a showstopper
-- `log: AppiumLogger`: May be used for logging. This property may be assigned
-  by the instance itself or by the Appium server if it is left unassigned.
+- `diagnose(): Promise<DoctorCheckResult>`：包含诊断某个问题的代码
+- `fix(): Promise<string|null>`：如果 `hasAutofix()` 返回 true，则修复实际问题；否则返回一段手动修复的说明。 如果此方法抛出名为 `FixSkippedError` 的异常，并且 `hasAutofix()` 返回 true，那么该调用结果将被忽略。
+- `hasAutofix(): boolean`：表示调用 `fix()` 是否能解决发现的问题
+- `isOptional(): boolean`：表示发现的问题是否可以被忽略且不是阻塞性问题
+- `log: AppiumLogger`：可用于日志输出。 这个属性可以由实例自行赋值，也可以由 Appium 服务在未赋值时自动提供。
 
-The `DoctorCheckResult` object returned by the `diagnose()` method must contain the following properties:
+`diagnose()` 方法返回的 `DoctorCheckResult` 对象必须包含以下属性：
 
-- `ok: boolean`: Whether the diagnosis found no issues
-- `optional: boolean`: Whether the diagnosed issue is safe to ignore
-- `message: string`: The text message describing the diagnostic result
+- `ok: boolean`：诊断是否未发现任何问题。
+- `optional: boolean`：诊断出的问题是否可以安全忽略。
+- `message: string`：描述诊断结果的文本信息。
 
-### Manifest Requirements
+### 清单要求
 
-A single extension may export multiple Doctor checks to Appium. In order for these checks to be properly
-picked up by the server CLI after the corresponding extension is installed they might be listed in the
-package .json manifest under the `appium.doctor.checks` section similar to the definition below:
+一个扩展可以向 Appium 导出多个 Doctor checks。 为了让这些检查项在对应扩展安装后能够被服务端 CLI 正确识别，它们需要在package .json 清单文件中列在 `appium.doctor.checks` 部分，格式类似下面这样：
 
 ```json
   // ...
@@ -67,12 +55,11 @@ package .json manifest under the `appium.doctor.checks` section similar to the d
   // ...
 ```
 
-Also, it makes sense to include the [@appium/types](https://www.npmjs.com/package/@appium/types) import
-to the package dev dependencies.
+此外，建议将 [@appium/types](https://www.npmjs.com/package/@appium/types) 加入包的开发依赖中。
 
-### Implementation Example
+### 实现示例
 
-The below example is a "raw" Node.JS implementation that does not use any transpilation:
+下面是一个“原生”的 Node.js 实现示例，没有使用任何转译工具：
 
 ```js
 const {fs, doctor} = require('@appium/support');
@@ -123,8 +110,7 @@ module.exports = {androidHomeCheck};
  */
 ```
 
-This file could be saved as `doctor/android-home-check.js` and then added to the package.json manifest
-as
+这个文件可以保存为 `doctor/android-home-check.js`，然后再将其加入到 package.json 清单中，例如：
 
 ```json
   // ...

packages/appium/docs/zh/developing/build-drivers.md

@@ -570,6 +570,33 @@ capability), and then to set an internal field to that value, so that it can be
 bidiProxyUrl`. Once all this is in place, Appium will proxy BiDi commands from the client straight
 to the upstream connection.
 
+### Understand server-assigned driver properties and security flags
+
+When your driver is running under the main Appium server, Appium assigns a small set of
+server-related properties on your driver instance when a session is created:
+
+- `cliArgs`: Driver-specific configuration derived from the Appium server’s CLI flags and/or
+  configuration files (for example via the `server.driver.<your-driver-name>` section). These
+  options are **not** user capabilities and cannot be influenced directly by test code.
+- `server`, `serverHost`, `serverPort`, `serverPath`: Information about the HTTP server that is
+  hosting your driver. These values reflect how the Appium server was started (for example the
+  `--address`, `--port`, and `--base-path` flags) and are useful when your driver needs to construct
+  URLs that point back to the Appium server itself (for example when setting up proxies, webhooks,
+  or other callbacks).
+
+`BaseDriver` and `AppiumDriver` also cooperate to expose security-related flags on your driver
+instance:
+
+- `relaxedSecurityEnabled`: Indicates whether the server is running with relaxed security enabled
+  (for example via `--relaxed-security`).
+- `allowInsecure`: A list of insecure features which are explicitly allowed for this driver (derived
+  from server-level options like `--allow-insecure`).
+- `denyInsecure`: A list of insecure features which are explicitly disabled for this driver (derived
+  from server-level options like `--deny-insecure`).
+
+See [Hide behaviour behind security flags](#hide-behaviour-behind-security-flags) for how to use
+these flags in your driver (e.g. via `isFeatureEnabled` and `assertFeatureEnabled`).
+
 ### Extend the existing protocol with new commands
 
 You may find that the existing commands don't cut it for your driver. If you want to expose
@@ -864,3 +891,120 @@ this.onUnexpectedShutdown(handler)
 
 `handler` should be a function which receives an error object (representing the reason for the
 unexpected shutdown).
+
+### Send messages to plugins running on the same session
+
+Appium's driver and plugin architecture means that a single driver and any number of plugins can be
+running together for a current session. The driver and plugins don't really know anything about
+each other though, which can make coordination potentially difficult. Without creating any kind of
+tight coupling between drivers or plugins, it's possible for drivers and plugins to communicate
+along a pub/sub style message bus. With Appium's IPC feature, "message" means a combination of
+"data" (the data intended to be published or received), and metadata (timestamp, the name of the
+publisher, etc...).
+
+Drivers and plugins can implement an instance method called `async onIpcInit`, in which they will
+know that the IPC channel for the session is now active. At this point, they have access to the
+following methods:
+
+#### `ipcSubscribe<T>(topic: string): IIpcSubscription`
+
+This method allows a driver or plugin to subscribe to a topic on the IPC channel for the session.
+Topics are simply strings. To coordinate effectively, drivers or plugins would use the same topic
+string (so this would be something advertised in the driver/plugin documentation).
+
+The result of this call is an `IpcSubscription` object that allows:
+
+- Looping through messages on the topic via an async generator
+- Hooking up an event handler for new messages
+- Getting the last message sent on the topic
+- Publishing a message to the topic
+- Unsubscribing from the topic
+
+#### `IpcSubscription` object
+
+Here is an example of how subscribing and use of these subscription methods might work:
+
+```ts
+async onIpcInit() {
+  // we know at this point in our driver/plugin lifecycle that we can use IPC methods
+  type MyMessageData = {myData: string}; // let's say the message data for this channel has this shape
+
+  const subscription = this.ipcSubscribe<MyMessageData>('coolTopic');
+
+  // listen for new messages on topic
+  subscription.on('message', (message) => {
+    console.log(message.data); // {myData: 'something'}
+  });
+
+  // publish data to the topic; might throw if the data is larger than configured max size, or we
+  // are no longer subscribed
+  await subscription.publish({myData: 'hi'});
+
+  // get last message sent to topic
+  const {data} = subscription.getMessage() ?? {data: null};
+  // data = {myData: 'hi'}
+
+  // unsubscribe
+  subscription.unsubscribe(); // returns true if we unsubscribed and false if no subscription existed
+}
+```
+
+With a subscription object, we can also iterate async over it to receive new messages:
+
+```ts
+for await (const message of subscription) {
+  // here we have a message and can unwrap its data
+}
+```
+
+Note that the iteration will stop when the subscription ends (i.e., when `unsubscribe` is called).
+
+You can also check whether the subscription is still active (if your subscribe and unsubscribe
+logic is not locally connected):
+
+```ts
+if (subscription.isActive) {
+  // we know we have not yet unsubscribed
+}
+```
+
+If the subscription is not active, attempts to call `subscription.publish` will throw an error.
+
+#### `IpcMessage` object
+
+When you get a message on a topic, it has the following shape:
+
+```ts
+export type IpcMessage<T> = {
+  publisher: string,   // the id of the publishing object (typically of the form <ClassName>@<uniqueObjectId>)
+  timestampMs: number, // when the message was published, in ms since epoch
+  topic: string,       // the topic the message was published on
+  data: T,             // the arbitrary message data. Must be serializable and a valid argument to 'structuredClone()'
+};
+```
+
+#### IPC Notes
+
+There are some important things to keep in mind when using Appium's IPC feature:
+
+- IPC is only available once `onIpcInit` has been called, at the end of the `createSession` flow.
+  It cannot be used statically or in `createSession` hooks
+- In sum, IPC is only for use during a session (this is also to prevent drivers/plugins from
+  accessing or reading data sent on IPC channels in other sessions.)
+- The default max size of an IPC message is 1MB. This can be configured by the server-admin by
+  using the `--max-ipc-data-size` arg (value is a number in bytes).
+- If a message exceeds the configured size, any call to `publish` methods will throw, so be
+  sure to cover this case in your error handling.
+- The default max number of IPC topics per session is 1000. This can be configured by the
+  server-admin using the `--max-ipc-topics` arg.
+- If the topic limit is reached, calls to `subscribe` or `publish` on a new topic will throw, so
+  be sure to cover this case in your error handling.
+- Topic names exist within a global namespace per session. So if you don't want to clash with other
+  drivers or plugins, make sure you prefix your topic names with something unique, akin to vendor
+  prefixes in the WebDriver standard (for example: `fake-driver:some-topic`). We recommend the
+  format `<namespace>:<topic>`.
+
+To see examples of IPC in action, check out Appium's own
+[FakeDriver](https://github.com/appium/appium/blob/master/packages/fake-driver/lib/driver.ts) and
+[FakePlugin](https://github.com/appium/appium/blob/master/packages/fake-plugin/lib/plugin.ts)
+extensions, which showcase several ways of using IPC messages.

packages/appium/docs/zh/developing/build-plugins.md

@@ -518,3 +518,12 @@ async onUnexpectedShutdown(driver, cause) {
   }
 }
 ```
+
+### Send messages to the driver or other plugins running on the same session
+
+Even though drivers and plugins don't know anything about each other, it's possible for them to
+send messages that other drivers or plugins can listen for, within the context of the same session,
+using an IPC channel. Given that the developer instructions for this feature are the same for
+drivers and plugins, please head over to the IPC development docs for
+drivers at the driver
+development guide.

packages/appium/docs/zh/developing/config-system.md

@@ -29,7 +29,7 @@ In lieu of a separate file, configuration can be embedded in a project's `packag
 ```
 
 When an Appium server is started via the `appium` executable, the `init` function in `lib/main.js`
-will call into `lib/config-file.js` to load and/or search for a configuration file and in
+will call into `lib/bootstrap/config-file.js` to load and/or search for a configuration file and in
 `package.json`.
 
 !!! note
@@ -72,7 +72,7 @@ It is more straightforward to explain how config files are validated, so we'll s
 
 ### Validating Config Files
 
-When a config file is found (`lib/config-file.js`), it will call the `validate` function exported
+When a config file is found (`lib/bootstrap/config-file.js`), it will call the `validate` function exported
 from `lib/schema/schema.js` with the contents of the config file. In turn, this asks `ajv` to
 validate the data against the schema that Appium has provided it.