headquarter/openspec/changes/archive/2026-05-14-codeserver-spawn/specs/spawn-ui/spec.md at 09920c1ca1b31111fc3318231f000cf249e99e39

alex/headquarter

Fork 0

Files

T

alex 78aaddb2b5

CI / Web CI (push) Failing after 12s

Details

CI / API CI (push) Failing after 1m1s

Details

docs(openspec): add OpenSpec changes for FN-005, FN-006, FN-008, FN-009, FN-010

- Add frontend-foundation change (FN-005) with 46 tasks
- Add deployment-config change (FN-006) with 27 tasks
- Add runfusion-poc/opencode-poc change (FN-008) with 25 tasks
- Add config-secrets change (FN-009) with 31 tasks
- Add codeserver-spawn change (FN-010) with 38 tasks
- Include project specsheet and configuration
- Archive completed deployment-config change

2026-05-14 17:35:20 +02:00

754 B

Raw Blame History

ADDED Requirements

Requirement: User can spawn a tool from the UI

The system SHALL provide a user interface for spawning tools.

Scenario: Spawn form

WHEN the user navigates to /tools/spawn
THEN a form is displayed with tool selection
AND project selection dropdown
AND optional config override fields

Scenario: Tool selection

WHEN the user selects a tool from the dropdown
THEN the form shows tool-specific configuration options
AND a description of the tool

Scenario: Spawn submission

WHEN the user submits the spawn form
THEN the frontend calls POST /api/v1/tool-instances
AND displays a loading state
AND redirects to the tool instance detail page on success

754 B Raw Blame History