Developer
caadd59441
Move the following audited-and-implemented changes into openspec/changes/archive/2026-06-12-completed-changes-archive/: - backend-frontend-refactoring - config-profile-git-mounts - config-profile-includes-ui - config-profile-multi-repo-mounts - container-monitoring-notifications - git-mount-url-validation - home-path-expansion - mobile-terminal-ux - mount-specificity-ordering - notification-center - persistent-terminal-sessions - session-list-overhaul - ssh-key-mounting - terminal-fullscreen-unified-header - tool-session-progress-and-updates Also regenerated .pi-map*.md files for openspec/changes so the remaining active changes (multi-session-terminal-ux, reorganize-long-files, working-copies, workspace-first-ui) reflect the new layout.
1.9 KiB
1.9 KiB
ADDED Requirements
Requirement: Instance startup processes git mounts from config profiles
The system SHALL process git repository mounts from resolved config profiles during instance startup.
Scenario: Instance startup with git mounts
- GIVEN a tool instance configured with a profile that has git mounts
- WHEN the instance starts
- THEN the startup pipeline:
- Resolves the config profile (including inherited profiles)
- Collects all git mounts from the resolved profile
- For each git mount, verifies the repository filesystem path exists
- Creates bind mount entries in the compose file for each valid git mount
- Logs warnings for any invalid or missing git mounts without failing startup
Scenario: Git mount bind mount creation
- GIVEN a resolved git mount with:
- repository filesystem path:
/data/repos/user/project/dotfiles - source path:
. - target path:
/home/user
- repository filesystem path:
- WHEN the instance compose file is generated
- THEN a volume entry is added:
volumes: - /data/repos/user/project/dotfiles:/home/user:ro - AND the mount is read-only by default
Scenario: Repository auto-clone on startup
- GIVEN a git mount referencing a repository that has not been cloned
- WHEN the instance starts
- THEN the system triggers a clone operation using the repository's remote URL and SSH key
- AND the system waits for clone completion before proceeding
- AND the bind mount is created from the cloned repository path
Scenario: Clone failure handling
- GIVEN a git mount referencing a repository with an invalid SSH key
- WHEN the instance attempts to clone during startup
- THEN the clone operation fails
- AND an error is logged with details
- AND the mount is skipped
- AND instance startup continues with remaining mounts
- AND the instance status is not affected