docs: add Pester 6 migration skill

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

Author: MariusStorhaug

docs/content/guides/pester-migration.md

@@ -0,0 +1,44 @@
+---
+title: Migrating Pester tests
+description: A repository-wide checklist for migrating PSModule test sets to Pester 6.1.0.
+---
+
+# Migrating Pester tests
+
+Use the reusable [`pester-migration`](https://github.com/PSModule/Process-PSModule/tree/main/skills/pester-migration/SKILL.md)
+agent skill to migrate every Pester test set in a PSModule repository. It is
+written for Pester **6.1.0** and distinguishes required compatibility changes
+from optional v6 modernization.
+
+The migration covers repository and test-set inventory, supported PowerShell
+runtime and CI checks, per-file discovery and run isolation, hidden paths,
+data-driven tests, setup blocks, mocks, pending tests, name templates,
+coverage, `Invoke-Pester` configuration, reserved tags, and validation
+reporting. It does not migrate consumer repositories as part of this framework
+change.
+
+## Required before declaring a migration complete
+
+- Every test entry point is inventoried and runs on its supported runtime matrix.
+- Pester 6.1.0 is imported in local and CI acceptance runs.
+- Each test file is self-contained under per-file discovery and run.
+- Hidden paths, empty data, duplicate setup blocks, mocks, pending tests, name
+  templates, coverage settings, legacy invocation parameters, and `None` tags
+  have been reviewed.
+- Serial results, coverage, and test-result artifacts are recorded and compared
+  with the baseline.
+
+## Optional after compatibility
+
+`Should-*` assertions, `Run.Shuffle`, and experimental `Run.Parallel` are
+independent adoption choices. Enable them only with separate validation and
+document the choice.
+
+## Primary and secondary sources
+
+- [Official Pester v5-to-v6 migration](https://pester.dev/docs/migrations/v5-to-v6)
+- [Pester installation](https://pester.dev/docs/introduction/installation)
+- [Pester configuration](https://pester.dev/docs/usage/configuration)
+- [Pester parallel execution](https://pester.dev/docs/usage/parallel)
+- [Awesome Copilot pester-migration](https://github.com/github/awesome-copilot/tree/main/skills/pester-migration)
+- [Awesome Copilot pester-should-migration](https://github.com/github/awesome-copilot/tree/main/skills/pester-should-migration)

docs/content/index.md

@@ -40,6 +40,7 @@ Task-oriented deep dives into the pipeline's functionality.
 | [Configuring the pipeline](guides/configuring-the-pipeline.md) | Worked examples for coverage targets, rapid testing, linting, and PR-based release notes. |
 | [Structuring your module](guides/structuring-your-module.md) | The repository and module source layout the workflow expects, and how to declare dependencies. |
 | [Writing module tests](guides/writing-module-tests.md) | Test discovery, setup and teardown phases, and shared test infrastructure. |
+| [Migrating Pester tests](guides/pester-migration.md) | A repository-wide checklist for migrating every test set to Pester 6.1.0. |
 | [Skipping framework tests](guides/skipping-framework-tests.md) | Skip individual framework tests on a per-file basis. |
 | [Versioning and releases](guides/versioning-and-releases.md) | Label-driven versioning, prereleases, and what a release produces. |
 | [Validating before review](guides/validating-before-review.md) | The PSModule validation pass before a draft pull request is marked ready. |

docs/zensical.toml

@@ -30,6 +30,7 @@ nav = [
     {"Configuring the pipeline" = "guides/configuring-the-pipeline.md"},
     {"Structuring your module" = "guides/structuring-your-module.md"},
     {"Writing module tests" = "guides/writing-module-tests.md"},
+    {"Migrating Pester tests" = "guides/pester-migration.md"},
     {"Skipping framework tests" = "guides/skipping-framework-tests.md"},
     {"Versioning and releases" = "guides/versioning-and-releases.md"},
     {"Validating before review" = "guides/validating-before-review.md"},