Adds step-security/harden-runner (audit, pinned to v2.22.4 like
craft-common-actions) as the first step of each job that did not have it,
so every workflow in the org's public repos reports its egress to
StepSecurity. Audit, not block: block-mode allow lists come from each
job's observed traffic.
* ci: SonarCloud analysis from CI instead of automatic analysis
* Publish the worker's node:test coverage to SonarCloud (test:coverage)
* ci: shared SonarCloud workflow back on @main (node coverage merged in craft-common-actions#194)
Chrome warns because Safe Browsing lists some craft.wiki pages as phishing, and
the Worker's sign-in page was a bare "Craft Wiki sign-in" title served from an
/api/ path with no branding, no explanation and no security headers. Give it the
wiki's branding, say that the password prompt belongs to discord.com, and send a
CSP with framing, referrer and content-type headers.
Add a script and a daily workflow that report Google's verdict for the domain,
so a listing is noticed without waiting for a browser to show it.
Save the session where Sveltia looks for it and open the editor when no editor window answers, and show text instead of a blank page. Run the Worker test file directly, because the directory form ran no tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add a Worker that signs editors in with Discord, checks the Senior Contributor role, and serves the editor's GitHub API with a server-side token limited to wiki content. GitHub tokens pass through unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>