feat: implement auth, projects, and frontend foundation

2026-05-17 20:21:55 +00:00
parent e7819bfc82
commit 71d9fe6406
88 changed files with 10936 additions and 47 deletions
@@ -0,0 +1,10 @@
+## MODIFIED Requirements
+
+### Requirement: Repository Deletion
+The system SHALL remove repository records when their owning project is deleted through authorized project deletion flow.
+
+#### Scenario: Cascade repository cleanup
+- GIVEN a project with associated repositories
+- WHEN the project owner deletes the project
+- THEN repository records for that project are removed
+- AND repository listing no longer includes removed records
@@ -0,0 +1,69 @@
+## MODIFIED Requirements
+
+### Requirement: Project Creation
+The system SHALL allow authenticated users to create new projects and SHALL assign the creator as project owner.
+
+#### Scenario: Create project
+- GIVEN an authenticated user
+- WHEN they create a project with name and description
+- THEN a project record is created
+- AND the user is set as owner
+
+#### Scenario: Reject unauthenticated creation
+- GIVEN a request without a valid authenticated session
+- WHEN it attempts to create a project
+- THEN the system responds with unauthorized status
+
+### Requirement: Project Listing
+The system SHALL list projects owned by the authenticated user, including related repositories and default SSH key metadata.
+
+#### Scenario: List projects
+- GIVEN an authenticated user
+- WHEN they view the projects page
+- THEN all their projects are listed with associated repositories
+
+#### Scenario: Ownership-scoped listing
+- GIVEN multiple users with separate projects
+- WHEN one user requests their project list
+- THEN only that user's projects are returned
+
+### Requirement: Project Updates
+The system SHALL support updating project details for project owners only.
+
+#### Scenario: Update project
+- GIVEN a project owner
+- WHEN they update the name or description
+- THEN the changes are persisted
+
+#### Scenario: Non-owner update denied
+- GIVEN a user who is not the project owner
+- WHEN they attempt to update project details
+- THEN the system responds with forbidden status
+
+### Requirement: Project Deletion
+The system SHALL support cascading project deletion for project owners.
+
+#### Scenario: Delete project
+- GIVEN a project owner
+- WHEN they delete a project
+- THEN all associated repositories are deleted
+- AND all associated SSH keys are removed
+- AND the project record is deleted
+
+#### Scenario: Non-owner deletion denied
+- GIVEN a user who is not the project owner
+- WHEN they attempt to delete the project
+- THEN the system responds with forbidden status
+
+### Requirement: Default SSH Key
+The system SHALL allow project owners to set a default SSH key per project and SHALL validate ownership for selected keys.
+
+#### Scenario: Set default key
+- GIVEN a project with SSH keys
+- WHEN the owner selects a default key
+- THEN it's used for git operations in that project
+
+#### Scenario: Reject foreign key assignment
+- GIVEN a project owner
+- WHEN they try setting a default SSH key that does not belong to their allowed scope
+- THEN the system rejects the request with validation error
@@ -0,0 +1,14 @@
+## MODIFIED Requirements
+
+### Requirement: SSH Key Project Association
+The system SHALL only allow project default-key assignment using keys valid for the authenticated owner's project scope.
+
+#### Scenario: Valid default key assignment
+- GIVEN a project owner and an eligible SSH key
+- WHEN the owner sets the key as default for the project
+- THEN the project stores that key reference
+
+#### Scenario: Invalid default key assignment
+- GIVEN a project owner
+- WHEN the owner attempts to set an ineligible SSH key as project default
+- THEN the system responds with validation failure