[Bill Schnurr (bschnurr)]

Summary

• Use the shared Python localization core and composite action rather than copying helper scripts into this extension.
• Keep GitHub English submission separate from pull-only DevDiv stable/pre-release imports.
• Use drop branch dev and canonical extension ID ms-python.debugpy; remove tracked generated locale snapshots where present and keep generated files in VSIX selection.
• Preserve existing runtime metadata, extraction sources, feeds, platform matrices, and version/validation behavior.
• Validate readiness independently in every required real-language manifest/runtime table; allow individual untranslated entries and reject missing/wholly untranslated tables before packaging.

Shared dependencies

• Share Python extension localization tooling and submission action vscode-common-python-lsp#125
• https://dev.azure.com/devdiv/DevDiv/_git/Pylance-Eng/pullrequest/801431
• Pilot: Test Pylance-Eng stable and pre-release pipeline templates vscode-isort#777

The GitHub action and Azure tooling checkout are pinned to d1877b84bb10ff7caa6bd12ab4e75498ba760790. Azure templates temporarily reference the shared feature branch for verification; switch to Pylance-Eng main after the dependency merges, before merging this caller.

Verification

Executable guards read the actual YAML and preserve existing triggers, build steps, publication defaults, validation contacts, version flags, and matrices. Both release YAMLs expanded with publishing explicitly disabled (environments used the enabled validation definition because its native definitions are disabled). Actual English export used the pinned CLI through the internal feed. Changed YAML/JSON formatting and whitespace checks passed.

Required setup and release blockers

Current drop passes the shared handback readiness guard; credential setup and actual release validation are still required.

No repository-level PYTHON_LOCALIZATION_APP_ID variable or PYTHON_LOCALIZATION_PRIVATE_KEY secret is currently visible here. Organization-level access could not be verified with current permissions. Configure or expose them through the owners; do not copy credentials between repositories. Authorize Github-Pylance for both release resources/pipelines.

Keep this PR draft while dependencies/setup/handbacks are pending. No merge or publication is requested.

[Bill Schnurr (bschnurr)]

Live release verification passed on the exact feature commit: https://dev.azure.com/devdiv/0bdbc590-a062-4c3f-b0f6-9383f67865ee/_build/results?buildId=15876009

Publishing was explicitly disabled, and the Publish Extension stage was skipped. The full eight-platform build succeeded. Both actual universal and win32-x64 VSIXs contain all 28 localization files (14 manifest and 14 runtime tables), with non-English German content in both tables. This confirms the authoritative translation import survives the debugger pre-built overlay and final packaging.

No extension was published. Shared PR dependencies remain unchanged.