Self-deploy workflow points to @main
The self-deploy workflow was stuck on a broken pinned version of the publish-pages action, failing every run. It's now tracking @main for immediate fixes.
The self-deploy workflow was broken. It pinned to publish-pages.yaml@v0, which floats to v0.1.4 — a version containing a broken npx invocation. Worse, workflow file changes don't trigger releases, so v0 had no path forward without a separate cli commit.
This PR switches self-deploy to track @main instead. The fix lands immediately on the next push, and the workflow stays evergreen going forward. The team acknowledges the trade-off: self-deploy is no longer version-locked. But for gitpulse's own dogfood deployment, that's fine — they control main, and bleeding-edge is what they want for their own deploy. External consumers pinning @v0 or @v1 see no change.