Allow cloning projects

[manuelkiessling]

As a SiteBuilder user, I want to be able to "clone" any of my organization's projects, so that a new project is created with a different name (which I can set before launching the clone operation for good), and which ends up having 1:1 the exact same project settings as the original one (but of course its own workspaces etc.).

[manuelkiessling]

@cursoragent Please create a plan for this, in form of a comment on this issue.

[cursor]

Applying rules: 00-rule-acknowledgment.mdc, CLAUDE.md

Here’s a comment-ready plan you can post on the issue:

---

Plan: “Allow cloning projects”

Requirements

• R1: While the source project belongs to the currently active organization and is not deleted, when a user starts cloning, the Project Clone Flow shall allow entering a new project name before finalizing.
• R2: When a valid clone is submitted, the Project Clone Flow shall create a new project that copies the source project’s settings 1:1 (git URL, GitHub token, project type, agent image, content-editing LLM provider/key, PhotoBuilder provider/key, agent instructions, remote content manifest URLs, S3 settings, keys visibility).
• R3: The Project Clone Flow shall not copy runtime artifacts (project ID, timestamps, deleted state, workspace, conversations, branches/PR state).
• R4: Where active projects are listed, the Project List UI shall expose a “Clone” action for each project.
• R5: If the source project is missing, deleted, or outside the active organization, then the Project Clone Flow shall create no project and return not-found behavior.
• R6: If the submitted clone name is empty/invalid, then the Project Clone Flow shall create no project and show validation feedback.
• R7: When cloning succeeds, the Project Clone Flow shall redirect to the project list and show a success flash message.

Implementation

• S1: Add a clone use case in ProjectMgmt domain/service layer (based on existing ProjectService::create(...)) to ensure one canonical way to persist full project settings.
• S2: Add clone endpoints in ProjectController:
  • GET /projects/{id}/clone (show clone form with editable suggested name),
  • POST /projects/{id}/clone (CSRF + ownership/deleted checks + execute clone).
• S3: Add UI pieces:
  • “Clone” button in project_list.twig,
  • clone form view (minimal form: new name + submit/cancel),
  • translation keys for labels/errors/success flash.
• S4: Ensure clone path does not create/copy workspace data; cloned project starts with no workspace/runtime state.
• S5: Add tests:
  • unit test for clone-copy behavior in ProjectServiceTest,
  • integration test suite (new ProjectCloneTest) for happy path + org boundary + deleted source + invalid name + “no workspace copied”.
• S6 (USER checkpoint): Confirm desired default suggested name format (e.g. Copy of <name>) and whether duplicate names in one org are acceptable.

Verification

• V1 (R1–R3): New/updated unit tests verify all expected settings are copied and runtime artifacts are not.
• V2 (R5–R6): Integration tests verify unauthorized/deleted/invalid clone attempts fail safely.
• V3 (R4, R7): Manual UI validation confirms Clone action appears in project list and successful clone redirects with flash.
• V4 (R1–R7): Run project checks before merge:
  • mise run quality
  • mise run tests
  • mise run tests:frontend
  • mise run frontend

---

  

[manuelkiessling]

@cursoragent Please implement this plan as a new Pull Request.

[cursor]

Applying rules: 00-rule-acknowledgment.mdc, 01-architecture-boundaries.mdc, 02-code-standards.mdc, 03-type-safety.mdc, 05-frontend.mdc, 07-workflow.mdc, 08-e2e-test-selectors.mdc, 09-symfony-services.mdc, 10-cursor-cloud.mdc, CLAUDE.md.

I implemented the project cloning plan end-to-end and pushed it on branch cursor/project-cloning-feature-7b03 (commit 965ce64). I added a new clone flow in ProjectController (GET/POST /projects/{id}/clone) with org ownership/deleted checks, CSRF validation, name validation, success flash, and redirect to list; added ProjectService::cloneProject() to copy all project settings 1:1; added clone UI (project_clone_form.twig) and a “Clone project” action in project_list.twig; and added EN/DE translations for clone labels + flash messages. I also added comprehensive tests: tests/Unit/ProjectMgmt/ProjectServiceTest.php (clone-copy behavior) and new tests/Integration/ProjectMgmt/ProjectCloneTest.php (happy path, org boundary, deleted source, invalid name, no workspace copied).

I validated everything with required checks and manual walkthrough evidence: mise run quality ✅, mise run tests ✅, mise run tests:frontend ✅, mise run frontend ✅. I also ran a browser-based manual clone flow and recorded it:

One small additional fix was needed to make the repo’s TypeScript check pass during mise run quality: I replaced replaceAll(...) with regex-based .replace(...) in src/RemoteContentAssets/Presentation/Resources/assets/controllers/remote_asset_browser_controller.ts for compatibility with the configured TS target.