Upgrade active GitHub Actions off the deprecated Node 20 runtime

[dajiaohuang]

Reproduction

Open a recent successful workflow run and inspect the annotations/log preamble. GitHub emits:

Node 20 is being deprecated. This workflow is running with Node 24 by default.

Confirmed examples:

• Organization profile sync: https://github.com/SagaSmithAI/.github/actions/runs/33042434182
• Narrative CI: https://github.com/SagaSmithAI/sagasmith-narrative/actions/runs/33064159250
• D&D CI: https://github.com/SagaSmithAI/Sagasmith-dnd/actions/runs/33064159161
• CoC CI: https://github.com/SagaSmithAI/Sagasmith-coc/actions/runs/33064158423
• Core CI: https://github.com/SagaSmithAI/Sagasmith-core/actions/runs/33062952530
• Website deploy: https://github.com/SagaSmithAI/SagaSmithAI.github.io/actions/runs/33063629813

Static inspection of all nine active repositories also finds Node-20-era action majors, including actions/checkout@v4, actions/setup-python@v5, actions/setup-node@v4, astral-sh/setup-uv@v4/@v6, actions/upload-pages-artifact@v3, and actions/deploy-pages@v4. GitHub is currently forcing those actions onto Node 24 compatibility mode; the latest upstream action releases now have newer supported majors.

Actual behavior

Every active repository has at least one workflow pinned to an action major that declares the deprecated Node 20 runtime. Successful runs contain compatibility warnings, so a green conclusion currently hides organization-wide runtime debt.

Expected behavior

All active workflows use current Node-24-compatible action majors (or an explicitly documented supported pin) and complete without the forced-runtime deprecation warning.

Impact

The current setup relies on GitHub's temporary compatibility behavior. It creates noisy logs and leaves workflows exposed to breakage when Node 20 actions stop being accepted or lose compatibility under the forced runtime.

Affected repositories

• SagaSmith-service (ci.yml, nightly-recovery.yml)
• SagaSmith-dnd-content-library (validate.yml)
• .github (sync-news.yml)
• sagasmith-narrative (ci.yml)
• Sagasmith-dnd (ci.yml)
• SagaSmith-agent (ci.yml)
• Sagasmith-coc (ci.yml)
• Sagasmith-core (ci.yml)
• SagaSmithAI.github.io (deploy.yml)

Suggested acceptance criteria

• Upgrade each affected action to a current upstream-supported major after reviewing its migration notes.
• Keep existing least-privilege workflow permissions and cache behavior.
• Re-run every affected workflow, including the scheduled recovery and profile-sync paths.
• Confirm the logs no longer contain the Node 20 forced-runtime warning.
• Do not add ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION as a workaround.

Audit de-duplication

At filing time, organization-wide searches found no open issue or pull request matching Node 20, Node.js 20, checkout@v5, setup-python@v6, or setup-node@v5.

[dajiaohuang]

The active-repository upgrade is split into one focused PR per repository:

• ci: upgrade profile sync to Node 24 actions #7
• ci: move workflows to Node 24 actions SagaSmith-Web#17
• ci: move validation to Node 24 actions SagaSmith-dnd-content-library#5
• ci: move workflow to Node 24 actions sagasmith-narrative#5
• ci: move workflow to Node 24 actions Sagasmith-dnd#7
• ci: move workflow to Node 24 actions SagaSmith-agent#12
• ci: move workflow to Node 24 actions Sagasmith-coc#6
• ci: move workflow to Node 24 actions Sagasmith-core#7
• ci: move Pages deployment to Node 24 actions SagaSmithAI.github.io#8

Each branch passes actionlint and git diff --check. The setup-uv consumers use the official immutable v10.0.1 release because setup-uv stopped publishing floating major tags, and they explicitly preserve the previous cache-pruning behavior.

I am keeping this organization-wide issue open until all nine PRs are merged and the affected push, Pages, profile-sync, and nightly-recovery paths have run successfully without the forced Node 20 runtime warning. At that point the checklist can be marked complete and the issue closed.

[dajiaohuang]

All nine active repositories now use the reviewed Node-24-compatible action releases. Post-merge validation is complete: Service CI and nightly backup/restore, the private content validation workflow, organization profile sync, Narrative/D&D/Agent/CoC/Core CI, and the Pages deployment all completed successfully. I also searched each selected run log for the prior Node 20 forced-runtime/deprecation warning; all nine were clean. The issue checklist is updated to reflect the verified state.