Move Blog to its own top-level nav tab

[alphdelta]

Summary

Blog is now a top-level section (content/blog/, /blog/) with its own "Blog" tab in both desktop and mobile nav, placed right after Resources. It is removed from the Resources page listing (which now only shows BMT→AIME and BmMT worksheets, still season-ordered).

Since posts moved from /resources/blog/* to /blog/*, the old /blog/* aliases became the canonical paths; they were swapped to /resources/blog/* (and /resources/blog on the section) so existing links keep redirecting.

Verified with zola build: public/blog/ and redirect stubs under public/resources/blog/ are both generated.

CI fix (unrelated to blog)

The deploy check failed because cloudflare/pages-action no longer exists (repo removed; GitHub returns 404). Both deploy.yaml and deploy-preview.yaml now use cloudflare/wrangler-action@v3 with command: pages deploy . --project-name=berkeley-mt [--branch=pr-N], Cloudflare's documented replacement. The preview deploy on this PR succeeded with the new action. Without this, the production deploy on the next push to main would also fail.

---

Requested by golden — per jeslyn, this was golden's fault. Merged at jeslyn's request.

Link to Devin session: https://app.devin.ai/sessions/b9c35144197b4077aa0472028302f733
Open in Devin Desktop: https://app.devin.ai/desktop/session/b9c35144197b4077aa0472028302f733?variant=devin
Requested by: @alphdelta

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[devin-ai-integration]

Browser test (fresh local build): Blog tab shows after Resources in desktop and mobile nav and highlights on /blog/; all five posts list and open; /resources/blog/ and /resources/blog/<slug> redirect to the new paths; Resources keeps BMT→AIME and BmMT worksheets without blog posts; at 768px all nine nav links fit with no horizontal overflow.

Desktop Blog listing	Active mobile menu

Deploy workflow changes were verified by the passing preview deploy, not by this browser test.