llm-wiki-multiwiki-e2e-gate

To prevent infinite loops in a GitHub Actions wiki factory workflow, you can implement a raw-change gate that detects recursive triggers and stops the cycle before the Hermes webhook fires.

A multi-wiki factory flow automates isolated wiki creation, triggering incremental compiles via GitHub Actions and validating end-to-end push-back through a Hermes webhook to enforce schema and graph quality.

You validate schema and graph quality in an automated wiki build pipeline by enforcing predefined content standards during the incremental compile, ensuring the Hermes webhook only accepts builds that pass graph quality acceptance.

Yes, you need Telegram and Hermes to set up this automated wiki factory flow, as Telegram provides the required notification mechanism and Hermes handles the webhook integration for end-to-end validation.

Yes, you can use a raw-change gate to block recursive webhook triggers in a multi-wiki setup, preventing the pipeline from re-triggering itself during the automated push-back process.

Your Hermes webhook causes a loop because the push-back triggers a new GitHub Action, requiring a raw-change gate to detect and halt the recursive workflow before it starts.