Skip to content

🚀 [Feature]: Module repositories share one auditable baseline - #525

Open
Marius Storhaug (MariusStorhaug) wants to merge 31 commits into
mainfrom
template-standardization
Open

Marius Storhaug (MariusStorhaug) wants to merge 31 commits into
mainfrom
template-standardization

Conversation

@MariusStorhaug

@MariusStorhaug Marius Storhaug (MariusStorhaug) commented Aug 29, 2026 •

Copy link
Copy Markdown
Member

Module maintainers and agents can audit repositories against one executable Template-PSModule baseline while preserving repository-owned code and content. Standard module sites use the shared MSX presentation profile, native folder-derived navigation, and no cookie-consent prompt.

Removed: PR-template files from the module baseline

Pull requests use canonical MSX PR Format guidance, not repository-local or centrally inherited automatic template files. Audits treat their absence as intentional and report existing files as stale drift for separate removal work. Upgrades must not add, recreate, copy, or generate a PR-template file from an older template snapshot or restore a central fallback.

Authors keep the complete release record in the PR body and follow the canonical release-range-first method for release-bound changes. This bounded correction needs no caller-input, TestData, Pester-dependency, module-asset, or documentation-configuration changes; the other standardization work below is preserved.

Technical details

The user-directed correction is committed at d2786d5e974e2430f756612cd66fe9dde6603756, based on the verified #525 candidate 9c41fb1cce0a846af994100ead738b2e2ed5a84f. Its scoped implementation comparison changes only these three files, with 44 insertions and two deleted baseline rows:

Changed surface Standards checked Framework contract Result
docs/content/reference/repository-standard.md MSX PR Format, Repository Standard, Markdown No PR-template requirements or central fallback Fixed in this PR
Read-only repository audit Canonical PR authoring and non-mutating audits No standard/scaffold classification or recreation prompt for PR-template files Fixed in this PR
v8 upgrade skill Canonical PR authoring and scoped migration No local/central PR-template creation or recovery from an older snapshot Fixed in this PR

Test-first assertions failed nine of 14 checks on the assigned candidate; physical-file absence and the four preservation/scope checks passed. All 14 pass after the correction. Exact content comparisons preserve every unrelated paragraph and every other tracked path, including CONTRIBUTING, legal/ownership/client routes, community-policy defaults, caller/TestData/Pester contracts, Zensical configuration, navigation, consent and assets. No consumer repository or other owner's workspace was edited.

Targeted Markdown lint passes all three files; both plugin manifests parse and their identity/version agrees; all four skill YAML headers and relative skill links validate. Site TOML parses, both JavaScript syntax checks pass, the repository analyzer reports zero regression-script diagnostics, and zensical build --clean --strict completes without issues. The generated authoring section and seven reference tables were checked before task-created build output was removed.

Immutable source correspondence: Template-PSModule default commit ff935a5745db222c5f28e59df45931b617c2c50b has a complete 20-file inventory and no PR-template file; this correction therefore needs no new template PR. The separately owned stale PSModule/Template-PSModule#42 removal remains separate. The canonical owner froze MSXOrg/docs#209 at bc03a5992615f65d1d5346dc48e7506e80b8b6ca. The complete description example, release-first procedure, no-file repository policy and defaults source guidance are the current correspondence; old template-scaffold links are not current evidence. The source's five hosted checks and automated approval 5725019918 were independently verified on that exact source head. This does not approve #525, merge the canonical source, or complete other owners' removals.

Actual #525 readiness hold: GitHub reports this producer head unmergeable against current main 64ffb1d87f86bd5d487891fdb140b78385a00531 (mergeable_state: dirty). Docs and Linter are active workflows but no PR runs/checks exist on this head; only dynamic CodeQL/Actions analysis and the reviewer checks succeeded. Copilot review 5725014128 is COMMENTED on d2786d5e974e2430f756612cd66fe9dde6603756, with zero new inline comments but an explicit keyboard-sorting human-assessment flag. The unchanged vendor source assigns lowercase tabindex, while the initializer assumes focusable headers. That wider Zensical concern is outside the bounded no-file correction. The review's "No open issues" line and successful reviewer check are not clean approval. Current-main composition and full actual-head checks/review remain required. Keep #525 draft; no merge/rebase or auto-merge was performed or is authorized by this revision.

Additional declared-schema checks expose unchanged composition gaps: the plugin's declared schema rejects its existing /skills property, and the marketplace's declared schema URL returns HTTP 404. Their manifest blobs exactly match the assigned candidate. The local Copilot command is an unavailable installation shim, so installed-plugin validation is also blocked. These were not repaired by widening the no-file revision.

Related references

New: Read-only module repository audits

The PSModule plugin gains psmodule-repository-audit, a read-only comparison skill for one repository or a fleet campaign. It records the template commit, classifies template-owned and repository-owned paths, reports drift, and leaves remediation to separate delivery work.

Changed: Migration skills consume the template

The v8 and Zensical migration skills use Template-PSModule rather than embedding another copy of standard files. The v8 upgrade now requires the dedicated Pester 6.1.0 procedure to inventory and validate every test set instead of treating a declared dependency or one green workflow as sufficient.

Changed: Documentation follows folders

Process-PSModule no longer maintains an explicit Zensical navigation array or hides the Dictionary from the generated tree. Zensical derives navigation from folders, places index pages first, and orders remaining pages alphabetically. The site uses the MSX vendored table sorter and keyboard-accessible initializer.

Changed: Community and release defaults follow their owners

Process-PSModule keeps its repository-specific contribution guide under .github/. The standard Code of Conduct, security policy, and support guidance are provided by PSModule/.github; local copies are needed only for repository-specific overrides. .github/release.yml is not part of the baseline because Process-PSModule does not use GitHub's built-in release configuration. The coordinated template update reflects the same contract for new module repositories.


Technical details
  • Documents that every Process-PSModule change evaluates its impact on Template-PSModule; the audit skill does not maintain or edit either repository.
  • Removes the duplicate generated-module .github/zensical.toml from Process-PSModule. The executable module profile lives in Template-PSModule; this repository's hand-authored site keeps docs/zensical.toml.
  • Uses MSXOrg/docs as the shared Zensical presentation source while preserving Process-specific identity, content, snippets, consent, and social links.
  • Declares that [project.extra.consent] is not part of the generated-module template because that profile enables no cookie-based measurement.
  • Excludes vendored minified assets from repository-authored JavaScript linting, matching the MSX documentation workflow.
  • Replaces duplicated caller-workflow examples with links to the executable template and documents the controlled @v8 major reference.
  • Keeps Process-PSModule's contribution guide under .github and points to organization-owned Code of Conduct and support guidance; the documentation standard records the inherited community-policy exception and excludes release.yml from the baseline.
  • Adds the required Claude and Copilot route files and corrects stale documentation links.
  • Preserves the historical managed-file anchor after clarifying that automated distribution is not operating today.
  • Local validation: plugin manifests parse, both JavaScript files pass node --check, docs/zensical.toml parses, explicit nav is absent, the vendored scripts match the pinned MSX sources after line-ending normalization, the local contribution path exists without root duplicates, the organization-owned policy files exist, and zensical build --clean completes without warnings.
  • Template impact evaluation: 🪲 [Fix]: New modules inherit the current repository baseline Template-PSModule#53 aligns the portable generated-module profile and removes redundant local community-policy and release configuration files.
Changed surface Standards checked Framework docs checked Result
.github/plugin/** MSX fleet orchestration and comparative review PSModule migration contracts Fixed in this PR
.github/workflows/Docs.yml MSX GitHub Actions Documentation lint contract Fixed in this PR
.github/*.md MSX repository and community health PSModule repository standard Fixed in this PR
docs/** MSX documentation, Markdown, and Zensical design PSModule repository and pipeline docs Fixed in this PR
Agent route files MSX agentic development PSModule onboarding contract Fixed in this PR
Relevant issues (or links)

Related work

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release:minor Publish a minor release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add template-backed audits and canonical repository defaults

2 participants