Update: hexo-generator-feed/index to v4, hexo-fs to v5

[Aetf]

Replaces #59, which GitHub auto-closed and refuses to reopen because it was stacked on chore/hexo-8 and I deleted that branch during post-merge cleanup. Same commit, now rebased directly onto develop — and unlike #59 this one actually gets CI, since ci-workflow.yml only triggers on PRs into develop.

hexo-generator-feed   3.0.0 -> 4.0.0
hexo-generator-index  3.0.0 -> 4.0.0
hexo-fs               4.1.3 -> 5.0.1

These are Hexo 8-era releases (hexo-generator-feed 4 depends on hexo-util 4, hexo-generator-index 4 on hexo-pagination 3), which is why they waited for #56 rather than riding along with #55.

Verification

Diffed a clean build against a clean pre-bump build. Every HTML page is identical once the random prism code-block ids are normalised. Only two outputs change, both from hexo-generator-feed 4's rewritten generator:

atom.xml — elements reordered, plus a feed-level <rights> and a per-entry <author>:

	feed children	entry children
v3	author, entry, generator, id, link, subtitle, title, updated	category, content, id, link, published, summary, title, updated
v4	... + rights	... + author

Parsed both with ElementTree — same 21 entries, same ids, same titles, all still carrying <content>. Strictly richer, nothing dropped.

search.xml — same 21 entries in a different order. Compared per-URL content hashes: identical URL set, identical content per URL, order only. It's a search corpus, so order carries no meaning.

Post listing order and pagination are unchanged (/blog/, /blog/page/2, /blog/page/3 all match). Re-verified after the rebase from a wiped node_modules: clean npm ci, clean build, 43/43 tests, and a headless render of /, /blog, /about, /projects, /research and a post with zero page errors.

Remaining

With this merged, katex is the only outdated dependency left in the tree, and it's deliberately pinned — see #55 for why 0.18 can't move until NexT's vendored KaTeX CSS does. Renovate's #53 is the PR for it and is currently failing for exactly that reason.

🤖 Generated with Claude Code

[Aetf]

CI hasn't reported here yet — GitHub Actions is in a major outage (githubstatus.com → Actions: major_outage), and no workflow runs have been created repo-wide since 10:31 UTC. Nothing wrong with this branch; it'll pick up a run once Actions recovers. If it still doesn't, a no-op push will re-trigger it.

Verified locally in the meantime, from a wiped node_modules: clean npm ci, clean npm run build, 43/43 tests, plus the build diff and headless render described above.