introduces a comprehensive bulk activation workflow for contest instances, improves entry editing logic to better support administrative corrections, and adds several supporting utilities and policy updates.

[rsmoke]

This pull request introduces a comprehensive bulk activation workflow for contest instances, improves entry editing logic to better support administrative corrections, and adds several supporting utilities and policy updates. The main themes are the addition of bulk contest instance activation, enhanced entry update handling, and supporting service and model changes.

Bulk Contest Instance Activation

• Added a new controller BulkContestInstanceActivationsController to handle the bulk activation flow, including form handling, validation, and reporting.
• Introduced BulkContestInstanceActivationForm for validating activation requests, including date parsing and confirmation logic.
• Implemented BulkContestInstanceActivator service to activate contest instances in bulk, with detailed reporting of activated, deactivated, skipped, failed, and unchanged instances.
• Added supporting scopes to ContestInstance for querying inactive, not archived, and date-specific instances.
• The bulk activation report is now shown on the container page after activation, using session and cache for temporary storage. [1] [2]

Bulk Creation and Activation Flow Improvements

• After bulk creation of contest instances, the user is redirected to the new bulk activation screen for the created season, streamlining the workflow. [1] [2] [3] [4]

Entry Editing and Profile Handling

• Entry updates now always target the entry owner's profile (not the editor's), ensuring that administrative users (like Axis Mundi) do not accidentally update their own profile when editing another user's entry. [1] [2] [3] [4]
• Entry update parameters are now restricted to prevent changing the contest instance after creation, maintaining contest integrity.
• The entry update policy has been clarified: owners can edit while the contest is open, and admins can always edit for corrections.

Supporting Service and Model Improvements

• Judging round date updates are now applied per-round in a single update to avoid validation errors from partial updates.

These changes collectively provide a robust and user-friendly workflow for managing contest instance activations and ensure data integrity and proper permission handling throughout the entry lifecycle.

[Copilot]

Copilot review overview

🟡 Changes recommended

Five moderate findings remain unresolved.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Show no-op notice when activation only skips instances · New

What changed in this PR

Adds bulk contest-instance activation, improved administrative entry editing, and safer judging-round date updates.

Changes:

• Adds activation form, service, controller, routes, views, and reporting.
• Redirects bulk creation into the activation workflow.
• Targets entry owners’ profiles and restricts contest reassignment.
• Updates entry policies and batches judging-round changes.

Open findings: Five moderate issues remain around no-op messaging, report scoping, deleted-entry authorization, and multiple active siblings.

File	Reviewed change
spec/​services/​judging_round_date_updater_spec.rb	Date updater coverage
spec/​services/​bulk_contest_instance_activator_spec.rb	Bulk activation coverage
spec/​policies/​entry_policy_update_spec.rb	Entry policy coverage
spec/​forms/​bulk_contest_instance_activation_form_spec.rb	Activation validation coverage
spec/​features/​bulk_contest_instance_activation_spec.rb	Activation workflow coverage
spec/​controllers/​entries_controller_spec.rb	Entry update coverage
spec/​controllers/​bulk_contest_instance_activations_controller_spec.rb	Activation controller coverage
config/​routes.rb	Activation routes
app/​views/​entries/​_form.html.erb	Owner profile selection
app/​views/​containers/​show.html.erb	Report display
app/​views/​containers/​_container_detail.html.erb	Activation navigation
app/​views/​containers/​_bulk_activation_report.html.erb	Activation report rendering
app/​views/​bulk_contest_instance_activations/​new.html.erb	Activation form UI
app/​services/​judging_round_date_updater.rb	Batched round updates
app/​services/​bulk_contest_instance_activator.rb	Bulk activation logic
app/​policies/​entry_policy.rb	Entry update authorization
app/​models/​contest_instance.rb	Activation scopes
app/​forms/​bulk_contest_instance_activation_form.rb	Activation request validation
app/​controllers/​entries_controller.rb	Owner-profile entry updates
app/​controllers/​containers_controller.rb	Activation report loading
app/​controllers/​bulk_contest_instances_controller.rb	Post-creation redirect
app/​controllers/​bulk_contest_instance_activations_controller.rb	Activation workflow and reporting

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🔵 Needs a closer look

Two unresolved moderate issues affect activation feedback and report isolation.

Review effort: Lite
Findings: 1

Open (1)

• Show no-op notice when activation only skips instances

Previously missed (1)

In code that hasn't changed since last review

Activation reports are not scoped to their container

app/​controllers/​containers_controller.rb:208

This loader consumes the session's single report key for whichever container is shown, without recording or checking the container that produced the report. If a user activates one collection and then opens another collection (for example in a second tab), the second page can display the first collection's activation report and the intended page loses it. Include the container id in the cached/session payload and only consume the report when it matches @container (or otherwise scope the key to the container).

[Copilot]

Copilot review overview

🟡 Changes recommended

Unresolved activation race-condition, entry-policy, and timestamp-consistency issues remain.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Recheck description activity after acquiring the row lock · New