Activate proactive repository monitoring

[alexphillips-dev]

Summary

• add daily Unraid, PHP, plugin-manager, API, and Community Applications drift monitoring
• add weekly OSV SBOM scanning and security-workflow watchdog coverage
• keep live Unraid systems and credentials outside repository automation

Release impact

• monitoring, tests, and documentation only
• no plugin source, manifest, package archive, checksum, version, tag, or release change
• Release On Main is expected to take its non-release skip path

Validation

• tooling doctor passed
• full lint, tests, workflow tests/guards, and docs guards passed
• 1,074 tests passed; 1 intentionally skipped; 0 failed
• SBOM, actionlint, workflow self-check, and Wiki link/published-page validation passed

Wiki audit

Updated Security and Package Trust, Compatibility and Performance, Contributing Testing and Releases, and Development and Architecture. No screenshots or navigation changes were required.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c38d8fabff

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Paginate CodeQL runs before filtering by event

Because .github/workflows/codeql.yml also runs on every push and pull request, adding CodeQL here can produce false watchdog failures: fetchWorkflowRuns retrieves only the newest 100 runs and evaluateWorkflowRuns filters for schedule/workflow_dispatch afterward. If more than 100 push/PR runs occur after the weekly scheduled success, that success disappears from the fetched page and the watchdog reports no-successful-run, fails, and opens an alert despite CodeQL being healthy. Filter by event at the API or paginate until the relevant run window has been covered.

Useful? React with 👍 / 👎.