Repository navigation
Add template-backed audits and canonical repository defaults #526
Description
Need
Process-PSModule guidance duplicates parts of the module template, permits Zensical and repository-layout drift, and does not make the dedicated Pester 6 migration a required v8 upgrade step. There is also no reusable read-only audit for comparing established module repositories with the current Template-PSModule baseline.
Expected outcome
Module repositories have one executable source for standard files, migration skills consume that source, and documentation sites use the shared MSX presentation profile with native folder-derived navigation.
Acceptance criteria
- A read-only skill audits a module repository against a resolved
Template-PSModulecommit without editing the template or consumer. - Process-PSModule guidance states that every framework change includes a template-impact evaluation; template changes remain normal work in the template repository.
- The v8 upgrade skill requires the dedicated Pester 6.1.0 migration procedure to inventory and validate every test set.
- The v8 and Zensical migration skills use
Template-PSModule/.github/zensical.tomlas the generated-module source instead of embedding a second template. - Shared Zensical presentation follows
MSXOrg/docswhere it differs from Process-PSModule, while repository-specific identity and content remain local. - Standard Zensical configuration omits explicit
navand[project.extra.consent]. - Repository-local community health files live under
.github/, with no root duplicates. - Caller-workflow guidance links to the template-owned file instead of duplicating its contents.
- Process-PSModule's documentation site builds successfully with the updated configuration.
- A coordinated Template-PSModule pull request carries the generated-module configuration and community-file changes.
Scope
This task does not build the future fleet agent or managed-file distribution runtime. It establishes the audit operation and canonical template contract they can consume.
References
- Track fleet alignment: remove Zensical navigation.indexes from existing repos #418
- Reconcile the Repository Defaults required-files tables with what Template-PSModule ships #484
- State the real status of managed file distribution on the Repository Standard #488
- 🪲 [Fix]: New modules inherit the current repository baseline Template-PSModule#53
Activity
[-]Add template-backed module audits and canonical Zensical guidance[/-][+]Add template-backed audits and canonical repository defaults[/+]MariusStorhaug commentedon Oct 31, 2026
The user-directed no-file correction is committed and pushed in existing draft #525 at
d2786d5e974e2430f756612cd66fe9dde6603756, from verified candidate9c41fb1cce0a846af994100ead738b2e2ed5a84f. Only the repository standard, read-only audit skill, and v8 upgrade skill change. Two required-file rows are removed; the guidance rejects local/central templates, missing-file drift, standard/scaffold classifications and recreation from older snapshots. Complete in-body release records and release-range-first authoring remain required. Every unrelated paragraph and every other tracked file matches the assigned candidate; no fleet repository or other owner's workspace was edited.Test-first checks failed nine of 14 assertions before the edit; all 14 pass now. Targeted Markdown lint, all four skill headers and local references, manifest parsing/version consistency, TOML/JavaScript checks, zero regression-script analyzer diagnostics, and the strict clean Zensical build pass. The rendered authoring section and seven tables were checked; task-created site/cache output was removed.
Immutable source correspondence is resolved. Template-PSModule default
ff935a5745db222c5f28e59df45931b617c2c50bhas no PR template in its complete 20-file inventory, so no new template PR is needed. The canonical owner froze MSXOrg/docs#209 atbc03a5992615f65d1d5346dc48e7506e80b8b6ca; its complete description example, release-first method and no-file policy agree with this producer revision. The source's five required hosted checks and APPROVED automated review 5725019918 were independently verified on that exact head. It remains unmerged; this correspondence does not approve #525 or complete other owners' removals. The stale PSModule/Template-PSModule#42 copy has a separate removal owner.Actual-head readiness is blocked. GitHub reports #525 unmergeable (
mergeable_state: dirty) against currentmain64ffb1d87f86bd5d487891fdb140b78385a00531. Docs and Linter are active workflows but no PR runs/checks exist on this head; only dynamic CodeQL/Actions analysis and the Copilot reviewer checks succeeded. Automated review 5725014128 is COMMENTED on this exact head and has zero new inline comments, but explicitly needs human assessment of keyboard sorting focus. The unchanged vendor source assigns lowercasetabindex, while the initializer assumes focusable headers; that wider Zensical concern was not repaired in this bounded contract revision. Do not treat the review's "No open issues" line or successful reviewer check as clean approval.Additional unchanged composition gaps remain: the declared plugin schema rejects existing
/skills, the declared marketplace schema URL returns HTTP 404, and the local Copilot executable is only an unavailable installation shim. The manifest blobs exactly match the assigned candidate. Keep #525 draft. No merge/rebase, auto-merge, live policy changes, historical backfill, or unrelated producer changes were performed; current-main composition, full actual-head checks/review and the remaining composition gaps need their owners before readiness.