Audit generated agent content before deployment

[PrzemyslawKlys]

Summary

• pin website CI and deployment to the landed agent-content scanner
• audit final LLMS artifacts before the normal doctor and SEO gates
• require exact owner-scoped NuGet publication evidence

Validation

• pipeline JSON parses successfully
• exact final-artifact audit smoke passes
• shared scanner and publication contracts pass

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[Copilot]

Pull request overview

This PR updates the website build/deploy pipeline to run a dedicated agent-content security audit step before the existing doctor/SEO gates, and pins the website CI/deploy reusable workflows to a newer PowerForge commit that contains the agent-content scanner.

Changes:

• Add an audit-agent-content pipeline step that enables checkAgentContentSecurity and blocks on agent-content findings, then make doctor-site depend on it.
• Update website-ci.yml and deploy-website.yml to use the newer pinned EvotecIT/PSPublishModule workflow ref/sha.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
Website/pipeline.json	Inserts an agent-content security audit step and wires it into the existing quality-gate chain before doctor/SEO.
.github/workflows/website-ci.yml	Pins website CI workflow to the updated PowerForge workflow commit.
.github/workflows/deploy-website.yml	Pins website deploy workflow to the updated PowerForge workflow commit.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.