Currently, all runs of a multi-run event share the parent event's registration policy. This makes it impossible to have run-specific registration configurations (e.g., different bucket capacities per run, or a frozen state on one run but not another).
Proposed change
Add the ability for individual runs to override the parent event's registration policy — either partially (e.g., overriding bucket capacities) or completely (replacing the policy for that run). When no override is set, a run would continue to inherit the event's policy as it does today.
Depends on
Blocked by #11238 (Migrate registration policies from JSONB to database tables) — the JSONB→tables migration is a prerequisite for making per-run overrides practical to implement.
Currently, all runs of a multi-run event share the parent event's registration policy. This makes it impossible to have run-specific registration configurations (e.g., different bucket capacities per run, or a frozen state on one run but not another).
Proposed change
Add the ability for individual runs to override the parent event's registration policy — either partially (e.g., overriding bucket capacities) or completely (replacing the policy for that run). When no override is set, a run would continue to inherit the event's policy as it does today.
Depends on
Blocked by #11238 (Migrate registration policies from JSONB to database tables) — the JSONB→tables migration is a prerequisite for making per-run overrides practical to implement.