feat: implement repository clone mode with SSH key support

- Add clone_mode and branch fields to tool_instances - Add ssh_key_id to git_repositories for per-repo SSH key assignment - Implement host-side git cloning with branch selection (default: main) - Mount SSH keys into containers for git operations in clone mode - Add dirty state check on clone-mode instance deletion with confirmation - Update SessionsPage with mount/clone selector, branch input, SSH key display - Add SSH key selector to repository creation form - Add dirty delete confirmation modal with changed files list - Update API schemas and endpoints for new fields - Sync delta specs to main specs (git-repo, tool-instances, repo-clone-mode) - Archive completed OpenSpec change: repo-clone-mode-with-ssh - Document git requirement for custom tool types Quality gates: Frontend typecheck and build passed OpenSpec: repo-clone-mode-with-ssh archived with all tasks complete
2026-05-22 22:56:35 +02:00
parent 952a9f3234
commit 063a839790
95 changed files with 2002 additions and 392 deletions
@@ -0,0 +1,29 @@
+## ADDED Requirements
+
+### Requirement: Repository SSH key assignment
+The system SHALL allow associating an SSH key with a GitRepository for clone operations and container git access.
+
+#### Scenario: Assign SSH key at repository creation
+- **GIVEN** an authenticated user creating a repository
+- **WHEN** they provide an `ssh_key_id`
+- **THEN** the repository is associated with that SSH key
+
+#### Scenario: Update repository SSH key
+- **GIVEN** an authenticated user with an existing repository
+- **WHEN** they call `PATCH /repositories/{id}/ssh-key` with a new `ssh_key_id`
+- **THEN** the repository's SSH key association is updated
+
+## MODIFIED Requirements
+
+### Requirement: Repository Creation
+The system SHALL allow creating new bare git repositories with an optional SSH key association.
+
+#### Scenario: Create repository with SSH key
+- **GIVEN** an authenticated user with a project
+- **WHEN** they create a new repository with `ssh_key_id`
+- **THEN** a bare repo is initialized on disk
+- **AND** the SSH key association is stored in the database
+
+## REMOVED Requirements
+
+None.
@@ -0,0 +1,39 @@
+## ADDED Requirements
+
+### Requirement: Host-side repository cloning
+The system SHALL clone repositories on the host filesystem before container startup when clone mode is selected.
+
+#### Scenario: Clone repository with branch selection
+- **GIVEN** a repository with a remote URL and SSH key
+- **WHEN** an instance is created in clone mode with branch="feature-x"
+- **THEN** the system runs `git clone --branch feature-x <remote_url> <instance_dir>/repo-clone/`
+- **AND** the clone includes full history
+
+#### Scenario: Clone repository with default branch
+- **GIVEN** a repository with a remote URL and SSH key
+- **WHEN** an instance is created in clone mode without specifying a branch
+- **THEN** the system defaults to branch="main"
+- **AND** runs `git clone --branch main <remote_url> <instance_dir>/repo-clone/`
+
+### Requirement: SSH key preparation for containers
+The system SHALL decrypt and prepare SSH keys for container mounting.
+
+#### Scenario: Prepare SSH key files
+- **GIVEN** a repository with an associated SSH key
+- **WHEN** a clone-mode instance is started
+- **THEN** the private key is decrypted and written to `instance_dir/.ssh/id_ed25519` with mode 600
+- **AND** the public key is written to `instance_dir/.ssh/id_ed25519.pub`
+- **AND** an SSH config is written to `instance_dir/.ssh/config` with `StrictHostKeyChecking no`
+
+### Requirement: Repository dirty state detection
+The system SHALL detect uncommitted changes in cloned repositories.
+
+#### Scenario: Detect clean repository
+- **GIVEN** a cloned repository with no changes
+- **WHEN** dirty state is checked
+- **THEN** the result indicates no uncommitted changes
+
+#### Scenario: Detect dirty repository
+- **GIVEN** a cloned repository with modified files
+- **WHEN** dirty state is checked
+- **THEN** the result indicates uncommitted changes with file details
@@ -0,0 +1,54 @@
+## ADDED Requirements
+
+### Requirement: Clone mode instance creation
+The system SHALL support creating tool instances with a clone mode that clones the repository into the instance directory.
+
+#### Scenario: Create instance in clone mode
+- **GIVEN** an authenticated user with a repository that has an SSH key and remote URL
+- **WHEN** they create an instance with `clone_mode: "clone"` and `branch: "main"`
+- **THEN** the system clones the repository into the instance directory
+- **AND** the compose file uses the clone path as `REPO_PATH`
+- **AND** the instance record stores `clone_mode="clone"` and `branch="main"`
+
+#### Scenario: Create instance in mount mode
+- **GIVEN** an authenticated user with a repository
+- **WHEN** they create an instance with `clone_mode: "mount"` (or omit the field)
+- **THEN** the compose file uses the host repository path as `REPO_PATH`
+- **AND** the instance record stores `clone_mode="mount"`
+
+### Requirement: SSH key mounting for git operations
+The system SHALL mount the repository's SSH key into clone-mode containers for git operations.
+
+#### Scenario: Start clone-mode instance
+- **GIVEN** a clone-mode instance with an associated SSH key
+- **WHEN** the instance is started
+- **THEN** the SSH key is decrypted and written to `instance_dir/.ssh/`
+- **AND** the `.ssh` directory is mounted into the container
+- **AND** the container can perform git push/pull operations
+
+### Requirement: Dirty check on clone deletion
+The system SHALL check for uncommitted changes before deleting a clone-mode instance.
+
+#### Scenario: Delete clean clone
+- **GIVEN** a clone-mode instance with no uncommitted changes
+- **WHEN** the user requests deletion
+- **THEN** the instance is deleted successfully
+
+#### Scenario: Delete dirty clone with confirmation
+- **GIVEN** a clone-mode instance with uncommitted changes
+- **WHEN** the user requests deletion
+- **THEN** the system returns a warning with change details
+- **AND** the user must confirm deletion
+
+#### Scenario: Force delete dirty clone
+- **GIVEN** a clone-mode instance with uncommitted changes
+- **WHEN** the user requests deletion with `force=true`
+- **THEN** the instance is deleted regardless of uncommitted changes
+
+## MODIFIED Requirements
+
+None.
+
+## REMOVED Requirements
+
+None.