A board has members, and the shared bands lose the esports vocabulary

[ExtraToast]

Two mechanical sweeps of the same kind, described together in .agents/RENAME_SPEC.md (surveyed against origin/main at eeb954acc).

Part A, the domain rename: a board has members, not seats.

This reverses a documented decision. docs/CONTEXT.md's ### Seat section does not merely use the word, it argues for it: "renaming either would cost more than the inconsistency does". The reversal has been asked for and is the decision to implement, so it is recorded rather than quietly performed, and rewriting that section is the first ticket.

The distinction that section protects has to survive the new word. A BoardMember row is one person's place on one board; one person may hold several across the years, and most have no account behind them. It is not a User.

Part B, the shared-component rename: the island's shared bands still carry the esports vocabulary they were born with. SliceBand is used by three pages and all 123 of its internal names say team. Timeline draws a board's years through 33 season-* classes.

docs/CONTEXT.md already states the rule, under Island: "the name has outlived the ownership". The components followed it when BannerSlices became SliceBand and the props were neutralised. The CSS did not.

Tickets

Wave 1, no file overlap, all parallel:

• The vocabulary document says board member, and records what a shared band's names describe #974 the vocabulary document, which is the premise for the rest
• The board module says member: identifiers, the refusal it raises and the file it seeds from #975 the board module: Kotlin identifiers, the refusal's Kotlin half, the seed file
• A slice band's slices are not team slices #976 a slice band's slices are not team slices
• A timeline's stops are not seasons #977 a timeline's stops are not seasons
• The theme pinning is the esports bands' own, and says so #978 the theme pinning says it is the esports bands' own (scope changed, see its comment; uncovered The band's pinned dark treatment does not reach the grounds it is meant to pin #984)
• The shared island comments stop naming one caller #979 the shared island comments stop naming one caller

Added during the sweep, once #977 showed the plan had a hole in it:

• A timeline's comments stop narrating seasons #983 a timeline's comments, which no ticket owned

Wave 2:

• The published spec and the generated types say member #980 the published spec and the generated types, blocked by The board module says member: identifiers, the refusal it raises and the file it seeds from #975
• The board page says member, down to the ids its specs select by #981 the board page and its ids, blocked by The board module says member: identifiers, the refusal it raises and the file it seeds from #975, sequenced after The shared island comments stop naming one caller #979

Not in scope

roster and players in esports, team proper, --color-game-*, committee seats, the board_members table, the routes and the DTOs, and the V86/V87 migration filenames. Each is a deliberate divergence or already correct, and .agents/RENAME_SPEC.md gives the reason per row.