Remove Pierce from /board and reassign his work to Chloe and Daryen

[getvindicated2day]

What changes

Pierce Kosobayashi is removed from /board.

• His member entry and the board chart card are gone.
• His round 2 assignment set, his round 1 archive row and any submissions he made are removed.
• The member files are down to 20 people. The committed example file is updated here; the uncommitted real one is updated separately.

His work is reassigned.

• Chloe gets three new round 2 tasks:
  • RSVP form for VINdiBasketball (Sat Oct 17), posted on @ucb_vindicated. Proof: form link and post link.
  • Send invites for every social on the calendar to the full member email list. Proof: screenshot of the sent email showing the recipients.
  • Keep the Socials calendar current. Proof: the updated calendar.
• Daryen gets one: book an RSF court for VINdiBasketball, Sat Oct 17, 2–4pm. Proof: booking confirmation.
• Social leads change from Pierce to Chloe on VINdiBasketball and Glade Night, and to "Chloe + UCSC lead" on UCSC × UCB basketball.
• Chloe is the default lead for new socials, and the note under the calendar says she leads socials.

Socials editor role.

• Roles come from the password used to sign in, not from an email address.
• roles.ts, .env.example and BOARD_SETUP.md now say Chloe holds BOARD_SOCIALS_PASSWORD.
• Rana needs to rotate the passwords before Pierce actually loses access (see below).

Live database.

• There's no direct access to Railway's database from here, so the same changes run once on the board's first load after deploy, in one transaction.
• The run is recorded in a new board_changes table so it never runs again.
• A fresh database gets the updated starter data and the change does nothing there.

Docs.

• docs/board-preview.html matches the new data.
• No mention of Pierce is left in the board code, seed data or docs.
• He is still on the public Team page (lib/team.ts, en.json, public/team/pierce.jpg), which this PR doesn't touch.

⚠️ Access

All three board passwords are currently the same, so Pierce can still sign in as admin. Removing his data doesn't remove his access. To do that:

1. Change BOARD_PASSWORD, BOARD_SOCIALS_PASSWORD and BOARD_ADMIN_PASSWORD in Railway to new, different values.
2. Give Chloe the new socials password.

Changing a password signs out everyone who used the old one.

Tested locally (production build)

• Copy of the live data (old seed, 21 imported members, one submission from Pierce):
  • Afterwards there are 20 members and no Pierce members, assignments or submissions.
  • Chloe has 6 round 2 tasks and Daryen has 2, all due Oct 12.
  • The three socials are led by Chloe, and the round 1 archive has 6 rows.
  • board_changes records the change.
• Restart: the change doesn't run again. A value I set by hand stayed as it was.
• Fresh database: the new starter data has no Pierce, and Chloe has 6 tasks.
• Rendered page: the /board HTML has no mention of Pierce.
• tsc, lint and build pass.

---

Generated by Claude Code

[getvindicated2day]

Replaced by #95, which leaves Pierce's tasks unassigned instead of giving them to Chloe.

---

Generated by Claude Code