From c43c36e1012859388d378a838c27e318893d933c Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Wed, 4 Nov 2026 14:46:36 +0100 Subject: [PATCH 1/2] State v8 migration framing as explicit conditions Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- .../psmodule/skills/psmodule-v8-upgrade/SKILL.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/.github/plugin/psmodule/skills/psmodule-v8-upgrade/SKILL.md b/.github/plugin/psmodule/skills/psmodule-v8-upgrade/SKILL.md index 0c27e026..be52d02d 100644 --- a/.github/plugin/psmodule/skills/psmodule-v8-upgrade/SKILL.md +++ b/.github/plugin/psmodule/skills/psmodule-v8-upgrade/SKILL.md @@ -54,7 +54,8 @@ the template's default files before adding, removing, or relocating anything. The template is a starting point, not a reason to overwrite module-specific content. -The current template's default repository anatomy is: +If the selected immutable template revision has this layout, its default +repository anatomy is: ```text / @@ -125,11 +126,13 @@ Treat files and directories as follows: Preserve the consumer's local onboarding contract while updating stale links. If the template revision and the consumer's existing layout disagree, record -the difference and migrate only the requested integration surface. In -particular, the current template uses `.github/zensical.toml`, while this v8 -upgrade request uses `docs/zensical.toml`, `docs/content/`, and -`docs/overrides/` (including `docs/overrides/assets/`) as its documentation -contract; a separate `docs/assets/` directory is optional. When that requested +the difference and migrate only the requested integration surface. + +If the selected immutable template revision uses `.github/zensical.toml`, +that file contains the template's Zensical settings. If the requested v8 +upgrade uses `docs/zensical.toml`, `docs/content/`, and `docs/overrides/` +(including `docs/overrides/assets/`) as its documentation contract, a separate +`docs/assets/` directory is optional. When that requested documentation migration is in scope, move the template's Zensical settings and custom assets into the `docs/` contract rather than maintaining both configurations. When it is not in scope, preserve the consumer's existing From 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4 Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Wed, 4 Nov 2026 14:49:29 +0100 Subject: [PATCH 2/2] State Zensical starter layout as a template revision condition Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- .../psmodule/skills/psmodule-zensical-migration/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/plugin/psmodule/skills/psmodule-zensical-migration/SKILL.md b/.github/plugin/psmodule/skills/psmodule-zensical-migration/SKILL.md index b6e19fef..c0f49052 100644 --- a/.github/plugin/psmodule/skills/psmodule-zensical-migration/SKILL.md +++ b/.github/plugin/psmodule/skills/psmodule-zensical-migration/SKILL.md @@ -76,8 +76,8 @@ Keep existing content under `docs/content/`, custom templates under `docs/assets/` directory is optional for static content assets. Do not create a parallel MkDocs theme or leave two active site configurations. -The current `PSModule/Template-PSModule` repository historically stores a -starter `.github/zensical.toml` and may not contain a `docs/` tree. When the +If the selected immutable `PSModule/Template-PSModule` revision contains a +starter `.github/zensical.toml`, it may not contain a `docs/` tree. When the consumer upgrade explicitly requires the Process-PSModule `docs/` contract, move the template settings and custom assets into `docs/` and remove the obsolete active configuration only after the site builds. When that contract