Restore root README

Keep GitHub App and publishing credential guidance in the canonical documentation tree instead of the repository root README.

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

Author: MariusStorhaug

README.md

@@ -11,27 +11,3 @@ The full documentation is published at:
 📖 **[Process-PSModule documentation](https://psmodule.io/docs/)**
 
 It covers getting started, the pipeline stages, usage, configuration, repository structure, and the principles behind the framework.
-
-## Reusable workflow secrets (GitHub App auth)
-
-When calling `./.github/workflows/workflow.yml`, pass the PowerShell Gallery credential as `PSGALLERY_API_KEY` and GitHub App credentials using these reusable-workflow secret names:
-
-- `PSGALLERY_API_KEY`
-- `GitHubAppClientId`
-- `GitHubAppPrivateKey`
-
-Consumer repositories can keep their own secret names and map them in the caller workflow, for example:
-
-```yaml
-jobs:
-  ProcessPSModule:
-    uses: ./.github/workflows/workflow.yml
-    secrets:
-      PSGALLERY_API_KEY: ${{ secrets.PSGALLERY_API_KEY }}
-      GitHubAppClientId: ${{ secrets.SHELLY_CLIENT_ID }}
-      GitHubAppPrivateKey: ${{ secrets.SHELLY_PRIVATE_KEY }}
-```
-
-This is a required contract. `PSGALLERY_API_KEY` publishes the module to the PowerShell Gallery; the GitHub App credentials mint an installation token for GitHub operations via `GH_TOKEN`, with no `github.token` fallback in that path.
-
-See the [GitHub App authentication guide](https://psmodule.io/docs/guides/github-app-authentication/) for the caller mapping, per-workflow permissions and repository scoping, and token injection details.