[Chore] Release reminder: replace Navad with James in weekly rotation

[zoomote]

Related GitHub Issue

Closes: #1698

Description

Replaces Navad with James in the owner rotation of the weekly release reminder workflow (.github/workflows/release-reminder.yml). The rotation is index-based over the owners array (owners=("Elliott" "James" "Toray")), so this is a straight name swap — the rotation cadence and anchor date are unchanged, and whoever is on deck this week stays on deck.

Test Procedure

• Verified the workflow file on main contains owners=("Elliott" "Navad" "Toray") and that the only change is the single name swap (full file otherwise byte-identical).
• Rotation logic is unchanged: weeks_since_anchor % 3 still selects from a 3-person list anchored at 2026-07-17.
• The workflow is scheduled (Fridays 09:00 UTC) plus workflow_dispatch; it can be manually dispatched after merge to verify the Discord post names the expected owner.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable). — N/A: workflow content change, no test harness for this workflow.
• Visual Snapshot (UI changes only): N/A — no UI change.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Visual Snapshots

N/A — no UI change.

Videos (interaction / animation only)

N/A.

Documentation Updates

• No documentation updates are required. (The reminder text and release process steps are unchanged; only the rotation name changed.)

Additional Notes

Requested by Elliott via Discord.

Get in Touch

Discord: elliott.delaunay (requester)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: Zoo-Code-Org/Zoo-Code/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 10b76cf9-7123-4ab7-b048-abaf7f0e82a5

📥 Commits

Reviewing files that changed from the base of the PR and between c5b5855 and 414bd83.

📒 Files selected for processing (1)

• .github/workflows/release-reminder.yml

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (1)

Require full commit SHA pins, least-privilege permissions, safe expression and shell interpolation, and trusted metadata handling.

⚙️ CodeRabbit configuration file

Files:

• .github/workflows/release-reminder.yml

🔇 Additional comments (1)

.github/workflows/release-reminder.yml (1)

29-29: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated the rotating release-reminder assignment to replace Navad with James.

Walkthrough

The release reminder workflow now rotates ownership among Elliott, James, and Toray instead of Elliott, Navad, and Toray. The schedule, concurrency settings, rotation logic, and Discord notifications are unchanged.

Changes

Release reminder owner rotation

Layer / File(s)	Summary
Update release reminder owners .github/workflows/release-reminder.yml	The owners array replaces Navad with James.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other · Severity of issue fixed: Low

🚥 Pre-merge checks | ✅ 8

✅ Passed checks (8 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Issue #1698 requires replacing Navad with James in the owners array of .github/workflows/release-reminder.yml. The reviewed change makes that exact replacement. The summary also confirms that …
Out of Scope Changes check	✅ Passed	The reviewed change contains one addition and one deletion in .github/workflows/release-reminder.yml. Both changes implement Issue #1698. No unrelated change is identified.
Regression Evidence	✅ Passed	PASS. The pull request changes only one line in .github/workflows/release-reminder.yml: the mechanical configuration value owners changes from "Navad" to "James". The schedule, anchor date, ro…
Security Boundaries	✅ Passed	PASS. The pull request changes only .github/workflows/release-reminder.yml, replacing Navad with James in the static owners array. The base file becomes byte-identical to the head file after t…
Persistence Integrity	✅ Passed	PASS: The pull request changes only the owners array in .github/workflows/release-reminder.yml, replacing Navad with James. The array value is read to build the Discord reminder message. No ch…
Lifecycle Resource Cleanup	✅ Passed	PASS. The authoritative diff changes only the owners array value from "Navad" to "James" in .github/workflows/release-reminder.yml. It does not change listeners, watchers, providers, timers, t…
Title check	✅ Passed	The title clearly and concisely identifies the main change: replacing Navad with James in the release reminder rotation.
Description check	✅ Passed	The description includes the linked issue, change summary, implementation details, test procedure, completed checklist, and documentation impact. It matches the required template and provides sufficie…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Review status

This PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging.

Current step: Awaiting fresh human maintainer or CODEOWNER approval.

Review-state labels are managed by this workflow; do not edit them manually.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!