Exclude cookie consent from module templates

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

Author: MariusStorhaug

.github/plugin/psmodule/skills/psmodule-repository-audit/SKILL.md

@@ -98,6 +98,9 @@ in `Template-PSModule`.
 - Do not add a `nav` setting. Zensical generates navigation from the staged
   folder structure, places index pages first, and sorts the remaining pages
   alphabetically.
+- Confirm the template does not define `[project.extra.consent]`. Cookie
+  consent is not a generated-module default and belongs only in a documented
+  repository-specific configuration that actually requires it.
 - Keep the template's theme, palette, typography, icons, plugins, Markdown
   extensions, and supported assets together as one baseline.
 - Do not copy path-specific settings from `MSXOrg/docs` or

.github/plugin/psmodule/skills/psmodule-zensical-migration/SKILL.md

@@ -62,6 +62,8 @@ For a standard PowerShell module built by Process-PSModule:
 - Copy it from the same path in `Template-PSModule` at the recorded commit.
 - Keep template placeholders that Process-PSModule resolves while staging the
   site.
+- Do not add `[project.extra.consent]`. The generated-module template does not
+  enable cookie-based measurement, so it must not display a consent prompt.
 - Use only includes, overrides, and assets that the template supplies and the
   Process-PSModule staging pipeline copies.
 - Do not create `docs/content/` merely to imitate a documentation repository.

docs/content/reference/repository-standard.md

@@ -429,6 +429,11 @@ sorts the remaining pages alphabetically. Organize generated function
 references through their source folders instead of maintaining a second
 navigation tree in TOML.
 
+The template does not define `[project.extra.consent]`. Standard generated
+module sites do not enable cookie-based measurement and must not display a
+consent prompt. A repository adds consent configuration only when its own
+documented functionality requires it.
+
 Repository-specific documentation content remains repository-owned. A module
 may depart from the template's site configuration only for a documented
 requirement that the shared generated-site profile cannot satisfy.