ci: restrict publish-wiki to schedule and manual dispatch only

[Copilot]

Wiki publish was firing on every merge to develop (push trigger) and after every maintenance-docs run (workflow_run trigger), causing unnecessary rebuild cycles. Both triggers removed — wiki now only updates nightly (03:00 UTC) or on manual workflow_dispatch.

Description

.github/workflows/publish-wiki.yml

• Removed push (branches: develop, paths: ...) trigger
• Removed workflow_run (after "Maintenance: Docs") trigger
• Retained: schedule (nightly 03:00 UTC) + workflow_dispatch (with dry_run / AI enrichment / fail_on_broken_links inputs)

Linked Issues

N/A

Type of Change

• Bug fix (non-breaking)
• New feature (non-breaking)
• Refactoring (non-breaking)
• Documentation
• Breaking change (requires MAJOR version bump — see VERSIONING.md)
• Security fix
• Other: CI/workflow configuration

Breaking Change Checklist

N/A

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• Benchmarks run (if performance-sensitive change)

Security Tiering Impact (Required for Runtime Changes)

• Impacted tier(s):

  • N/A (docs-only / non-runtime)

• Trust-boundary crossings documented in PR description (example: T3 -> T2, T5 -> T4 brokered call)

• Boundary controls validated for affected T3/T4/T5 paths (AuthN/AuthZ, validation, rate limits, audit)

• Boundary-focused tests added/updated or explicit N/A rationale provided

• If trust level/privilege increased, security maintainer approval is attached

📚 Research & Knowledge (wenn applicable)

• Diese PR basiert auf wissenschaftlichen Paper(s) oder Best Practices?

Relevante Quellen:

• Paper:
• Best Practice:
• Architecture Decision:

AI-Generated Code (KI-generierter Code)

• Symbol-Referenzen mit GetSymbolReferences_CppTools geprüft
• Keine rohen Pointer und kein new/delete ohne explizites Review eingeführt
• RAII und Exception-Safety für neue/angepasste Pfade geprüft
• Keine unnötig komplexen KI-Abstraktionen eingeführt
• Performance-Metriken geprüft, falls Hotpath betroffen

N/A — workflow YAML change only.

AI Review Workflow (Required for AI-assisted PRs)

• Findings-first review performed with .github/prompts/pr-diff-findings-review.prompt.md
• Security hardening review performed for security-sensitive/runtime changes with .github/prompts/security-hardening-review.prompt.md (or N/A documented)
• API impact review performed for API/contract changes with .github/prompts/api-change-impact-review.prompt.md (or N/A documented)
• All Critical/High findings are resolved or explicitly accepted with rationale in PR description
• Residual risks and follow-up actions documented in PR description
• Severity policy applied according to .github/copilot/REVIEW_SEVERITY_POLICY.md

N/A — no code changes.

High-Finding Exception Record (only if High is accepted)

N/A

Release Readiness Gate (Required for release-scoped changes)

• Release readiness reviewed with .github/prompts/release-readiness-check.prompt.md for branch transition scope
• Branch governance validated against BRANCHING_STRATEGY.md and RELEASE_STRATEGY.md
• Versioning/changelog impact validated against VERSIONING.md and CHANGELOG.md

N/A — infrastructure-only change.

Checklist

• Code follows project style guidelines (clang-format / clang-tidy)
• Self-review completed
• Documentation updated (if needed)
• CHANGELOG.md updated under [Unreleased]
• No new warnings introduced
• Security-sensitive paths reviewed by security maintainer (if applicable)

Scanner and IntelliSense Gates

N/A — no source code changes.

• IntelliSense/Compiler: no new errors in changed files
• clang-tidy/cppcheck: no new high-risk findings in changed files
• Gap Scanner: no new critical findings in categories security, input_validation, query_correctness, distributed_consistency, concurrency, memory
• Gap Scanner: no new high findings in the same categories (or explicitly approved)
• Gap Scanner delta report attached (baseline vs current), not only absolute totals
• New unknown scanner findings triaged (fixed, re-categorized, or justified)

[Copilot]

🟡 Changes recommended

The workflow’s header documentation still describes the removed push/workflow_run interplay and should be updated to match the new trigger behavior.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR updates the GitHub Actions workflow responsible for publishing documentation to the GitHub Wiki so it no longer runs automatically on merges to develop or after the docs maintenance workflow; it now runs only on a nightly schedule or via manual dispatch to reduce unnecessary rebuild cycles.

Changes:

• Removed the push trigger (with path filters) from publish-wiki.yml.
• Removed the workflow_run trigger that fired after "Maintenance: Docs" completes.
• Left schedule (03:00 UTC) and workflow_dispatch as the only triggers.

File summaries

File	Description
.github/workflows/publish-wiki.yml	Restricts wiki publishing to scheduled and manual runs by removing push/workflow_run triggers.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

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