Keep one-time and cooldown data per character by default

[ryanbarlow97]

Once-only flags and cooldowns now belong to the roleplay character being played, unless an event opts back to the account. Stacked on #1.

act1_exp_catchup:
  type: repetitive
  one_time: true
  data_scope: account   # character is the default

Why. Codex discoveries become per character in Codex #2. On Main, 87 Codex unlock events in codex.yml and codex_research.yml are one_time, and today those flags are per account. Without this change, a second character could never earn codex_die, a duchy title or a research entry the account already has.

What the default affects. Only events that keep data, meaning those with one_time or a cooldown, and only when a player is involved. Such an event runs only while a character is in play, so not at join before a character is chosen. Events without that data, and player-less events such as server_start or player_pre_join, have nothing to keep per character and run exactly as upstream. On Main that leaves 90 events affected:

• the 87 Codex unlocks, which should be per character, with no config change needed;
• the 10-second meditation cooldown in r_lore.yml, where per character is fine;
• act1_exp_catchup and act1_exp_catchup_retry, which should get data_scope: account at deployment so the one-off pre-split catch-up doesn't arm again for every character.

How it works.

• Storage: per-character data lives in the same player file, under characters.<character>.events, and loads with the account at login as before. Upstream files load unchanged.
• No inheritance: old account-level entries for events now per character stay in the file, unused, so every character starts these events fresh, because the old data doesn't record which character ran an event.
• Character tracking: a tracker records the character in play from TLibs session events in a thread-safe map, for events that run off the main thread.
• Delayed actions: a run is tied to the character it started for. If that character leaves before a delayed action (wait_ticks) or the hand-over from an async event, the rest is dropped and the run's one-time flag and cooldown are undone.
• Thread safety: player data is locked for every access. Saves write a snapshot and never clear changes made during the write.
• Resets: /ce reset <player> <event> and /ce reset * <event> clear the account and every character.
• Unrecognised values: an unknown data_scope value logs a warning and counts as character.

Tests. JUnit and Mockito cover scope rules, the data model and snapshots, the file format, the tracker and run abandonment. JaCoCo requires 100% line coverage of net.tfminecraft.conditionalevents.character. mvn clean verify passes (19 tests).

🤖 Generated with Claude Code

[ryanbarlow97]

Reviewed by Astra (GPT-6-Astra) over four read-only rounds (reports kept locally); every finding fixed, the last with tests for its exact scenario. Merging with admin bypass. Not released or deployed.