Make Game Cloning Open an Editable Draft Before Publishing #775

New issue

Closed

opened 2026-06-28 12:27:28 -05:00 by Veilor · 1 comment

Veilor commented

2026-06-28 12:27:28 -05:00

Member

Copy link

Game DB admins need cloning to create an editable draft or prefilled edit step before the cloned game becomes visible as a live public entry.

The current admin clone flow confirms the source game, immediately replicates it into a live game record, and redirects to the edit page. That makes platform changes, title corrections, boxart changes, and other clone-specific edits race against members seeing an unfinished duplicate.

Scope

Admin game clone confirmation and submit flow.
Admin\GameController::storeClone behavior after an admin chooses to clone.
The edit experience for the newly cloned game.
Visibility of cloned records before an admin has reviewed and saved clone-specific changes.
Existing game edit form validation, authorization, and audit logging.

Acceptance Criteria

Cloning a game does not immediately publish an unfinished live duplicate to members.
Admins can review and edit the cloned game before it becomes publicly visible.
Admins can change platform, title, boxart, and other normal editable game fields before publication.
The source game remains unchanged during the clone preparation flow.
Clone authorization remains limited to existing game manager roles.
The admin UI clearly communicates whether the clone is still a draft/pre-publication record or has been published.
Existing edit validation and success/error feedback continue to work.

Test Coverage Required

Add feature coverage for starting a clone without exposing an unfinished live public game.
Add feature coverage that the cloned record can be edited before publication.
Add regression coverage that clone authorization remains restricted to game manager roles.
Preserve existing admin game edit validation coverage.
Run focused admin game clone/edit tests before closing the issue.
Run vendor/bin/pint --dirty --format agent before implementation closeout if PHP files change.

Progress Checklist

Decide the clone draft/pre-publication model or workflow
Update clone submission so unfinished clones are not immediately public
Route admins into the editable clone flow
Preserve source game data during clone preparation
Make clone publication state clear in the admin UI
Add focused clone workflow coverage
Run focused admin game tests
Run vendor/bin/pint --dirty --format agent if PHP files changed
Move the issue out of Codex review once verification is complete

Game DB admins need cloning to create an editable draft or prefilled edit step before the cloned game becomes visible as a live public entry. The current admin clone flow confirms the source game, immediately replicates it into a live game record, and redirects to the edit page. That makes platform changes, title corrections, boxart changes, and other clone-specific edits race against members seeing an unfinished duplicate. ## Scope - Admin game clone confirmation and submit flow. - `Admin\GameController::storeClone` behavior after an admin chooses to clone. - The edit experience for the newly cloned game. - Visibility of cloned records before an admin has reviewed and saved clone-specific changes. - Existing game edit form validation, authorization, and audit logging. ## Acceptance Criteria - Cloning a game does not immediately publish an unfinished live duplicate to members. - Admins can review and edit the cloned game before it becomes publicly visible. - Admins can change platform, title, boxart, and other normal editable game fields before publication. - The source game remains unchanged during the clone preparation flow. - Clone authorization remains limited to existing game manager roles. - The admin UI clearly communicates whether the clone is still a draft/pre-publication record or has been published. - Existing edit validation and success/error feedback continue to work. ## Test Coverage Required - Add feature coverage for starting a clone without exposing an unfinished live public game. - Add feature coverage that the cloned record can be edited before publication. - Add regression coverage that clone authorization remains restricted to game manager roles. - Preserve existing admin game edit validation coverage. - Run focused admin game clone/edit tests before closing the issue. - Run `vendor/bin/pint --dirty --format agent` before implementation closeout if PHP files change. ## Progress Checklist - [ ] Decide the clone draft/pre-publication model or workflow - [ ] Update clone submission so unfinished clones are not immediately public - [ ] Route admins into the editable clone flow - [ ] Preserve source game data during clone preparation - [ ] Make clone publication state clear in the admin UI - [ ] Add focused clone workflow coverage - [ ] Run focused admin game tests - [ ] Run `vendor/bin/pint --dirty --format agent` if PHP files changed - [ ] Move the issue out of Codex review once verification is complete

Veilor added the

Rows
Columns