ci: add zizmor GitHub Actions security scanning

[kingchenc]

What

New workflow .github/workflows/zizmor.yml — static security analysis of the GitHub Actions workflows themselves (the surface CodeQL does not cover): template injection, overly broad GITHUB_TOKEN permissions, unpinned actions, cache poisoning, dangerous triggers. Covers this repo's ci.yml, links.yml, and refresh-badges.yml (the latter pushes via a token). Findings surface under Security → Code scanning.

Report-only (does not block CI)

zizmorcore/zizmor-action runs with advanced-security: true → SARIF mode → exits 0 regardless of findings, so the job uploads results but never blocks PRs.

Correctness

• Actions pinned to SHA (checkout v6.0.2, zizmor-action v0.5.6).
• Least privilege: top-level contents: read; job raises only security-events: write + contents: read + actions: read.
• persist-credentials: false on checkout.
• Identical to the workflow added in the wickra, webpage, and .github repos.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[cloudflare-workers-and-pages]

Deploying wickra-docs with    Cloudflare Pages

Latest commit:	246ffdb
Status:	✅  Deploy successful!
Preview URL:	https://98d36650.wickra-docs.pages.dev
Branch Preview URL:	https://ci-add-zizmor.wickra-docs.pages.dev

View logs