[ryanbarlow97]

Stage 6b gives the website wills and estates (design ~/stage6b/design.md, section W5 and Website; umbrella TF-Minecraft/RPCharacters#89).

The roster push now carries each character's death date, death id, will and estate. Wills are stored on the roster row and estates in a new character_estates table keyed by realm and death, which a roster push never deletes. An older will or estate revision never replaces a newer one; within one estate revision, the plugin's updated_at decides.

Profile can name an heir or revoke a will. The request goes into a new will_requests queue that RPCharacters pulls and acknowledges, like web creation. Both plugin routes require a realm and the ack is checked against the request's realm. A heir search lists living characters of the player's realm by name (three letters or more, ten results, rate-limited) with name, race and short id only, marking the player's own.

On Profile, living cards show "Heir: Kira" or "No will" with Change and Revoke, and a pending change until the server answers. Dead and missing cards open a read-only memorial: death date or "Before records began", heir, estate state and who received what. Wardrobe and kit pages, and their backend edits, refuse dead and missing characters.

Integrated the staff character cards and full sheets from #219 without changing will/estate routes or payloads. Profile alone passes the session token and will callbacks; staff cards and sheets stay read-only. Combined regressions cover Profile revoke/refresh, staff cards carrying living will data, staff full-sheet access checks, and historical portraits that remain available while wardrobe reads refuse dead/missing characters. The later AdminNav focus change from #220 combines cleanly and remains in main.

Routes and payloads are in the paired Docs guide: TF-Minecraft/Docs#216.

Validation on integration head 24cf8c4b: focused backend wills/roster/wardrobe-picture/staff tests 113 passed; focused frontend 118 passed; full frontend 192 files / 2199 passed + 1 skipped; formatting clean; lint passed with existing warnings; production Next build including TypeScript, static pages and search indexing passed. The earlier full backend 2282 passed + 1 skipped gate was on 64392171; no backend implementation conflict or new edit required repeating that whole suite. GitHub CI runs against the combined merge ref. Draft pending the coordinated stage 6b rollout; merging deploys Dev.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}