Exclude entire samples/ folder from translation

samples/ is the code samples folder and should not be translated. Expand
the exclusion from samples/skills/** to all of samples/**: skip it in the
push trigger, delete translations/<lang>/samples and
translated_images/<lang>/samples before opening the PR, and ignore
samples/** in the co-op-review filter. Update translation-polisher.md docs
to match.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: DanWahlin

.github/scripts/filter-co-op-review.js

@@ -17,7 +17,7 @@ const { spawnSync } = require("child_process");
 // Source paths that are intentionally excluded from translation. Keep this in
 // sync with the excludes in .github/workflows/co-op-translator.yml and the
 // guidance in .github/workflows/translation-polisher.md.
-const EXCLUDED_PREFIXES = [".github/", "samples/skills/"];
+const EXCLUDED_PREFIXES = [".github/", "samples/"];
 
 const languages = process.argv
   .slice(2)

.github/workflows/co-op-translator.yml

@@ -14,7 +14,7 @@ on:
       - "!translations/**"
       - "!translated_images/**"
       - "!.github/**"
-      - "!samples/skills/**"
+      - "!samples/**"
 
 permissions:
   contents: write
@@ -94,9 +94,9 @@ jobs:
           for language in $TRANSLATION_LANGUAGES; do
             rm -rf \
               "translations/$language/.github" \
-              "translations/$language/samples/skills" \
+              "translations/$language/samples" \
               "translated_images/$language/.github" \
-              "translated_images/$language/samples/skills"
+              "translated_images/$language/samples"
           done
 
       - name: Upload Co-op Translator logs

.github/workflows/translation-polisher.md

@@ -93,7 +93,7 @@ You may edit only translated Markdown files:
 Exclude these generated translation paths from review, grading, and edits:
 
 - `translations/*/.github/**`
-- `translations/*/samples/skills/**`
+- `translations/*/samples/**`
 
 Leave skill definition Markdown in English.
 
@@ -111,7 +111,7 @@ Do not edit:
 2. Compare each changed translated Markdown file with its corresponding English source file.
    - Example: compare `translations/es/README.md` with `README.md`.
    - Example: compare `translations/es/03-development-workflows/README.md` with `03-development-workflows/README.md`.
-3. Focus on files changed by the pull request, not every translated file in the repository. Ignore excluded translation paths under `translations/*/.github/**` and `translations/*/samples/skills/**`.
+3. Focus on files changed by the pull request, not every translated file in the repository. Ignore excluded translation paths under `translations/*/.github/**` and `translations/*/samples/**`.
 4. If the pull request body already has a managed `## Translation Quality Review` section, identify files with grades below A- and repair those files first.
 5. Preserve Markdown structure exactly unless a link or heading fix is required.
 6. Apply the shared quality rules and the language quality profile for each target language present in the pull request.