Files
headquarter/openspec/changes/archive/2026-05-14-codeserver-spawn/specs/container-lifecycle/spec.md
T
alex 78aaddb2b5
CI / Web CI (push) Failing after 12s
CI / API CI (push) Failing after 1m1s
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

1.0 KiB

ADDED Requirements

Requirement: Tool instance status is tracked

The system SHALL track the lifecycle status of tool instances.

Scenario: Status transitions

  • WHEN a tool instance is created
  • THEN its status is "creating"
  • AND when the container starts, status becomes "running"
  • AND when stopped, status becomes "stopped"
  • AND on error, status becomes "error"

Scenario: Status polling

  • WHEN the user views a tool instance
  • THEN the frontend polls the status endpoint
  • AND updates the UI when status changes

Requirement: Tool instances can be stopped and restarted

The system SHALL allow stopping and restarting tool instances.

Scenario: Stop instance

  • WHEN the user clicks "Stop" on a running instance
  • THEN the system stops the Docker container
  • AND updates the status to "stopped"

Scenario: Restart instance

  • WHEN the user clicks "Start" on a stopped instance
  • THEN the system starts the existing container
  • AND updates the status to "running"