Design Process-PSModule app model for docs preview and repo wiring

[MariusStorhaug]

Context

PSModule is moving toward a Process-PSModule GitHub App-based control plane that configures module/default repos.

PR preview/pages behavior should be implemented through Process-PSModule's own model, not by inheriting transitional PSModule/docs assumptions.

Goal

Define Process-PSModule's native approach for configuring repository docs preview/publish behavior (including module repos and default repos like .github).

Scope

• Define app-driven provisioning flow for target repos:
  • GitHub Pages settings (where applicable).
  • Branch/ruleset configuration.
  • Workflow/script wiring.
  • Secrets/app credential wiring model.
• Define policy boundaries:
  • Which repos get preview lifecycle automation.
  • How org-level and repo-level ownership/permissions are separated.
• Define rollout/migration path from transitional setups.

Constraints

• Must be compatible with Process-PSModule as source of truth.
• Must support least-privilege app permissions.
• Must keep repository-local workflows standards-compliant.

Deliverables

1. Design proposal for Process-PSModule app orchestration model.
2. Permission model and rationale.
3. Repository classification + provisioning matrix (module repos, defaults repos, docs locations).
4. Migration plan and verification strategy.

Acceptance criteria

• A documented, reproducible provisioning flow exists for new repos.
• Existing repos can be migrated without manual drift.
• Ownership boundaries between MSX enterprise app usage and PSModule org-owned app usage are explicit.