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

openspec/changes/config-secrets/specs/config-management/spec.md

@@ -0,0 +1,37 @@
+## ADDED Requirements
+
+### Requirement: User can create config values
+The system SHALL allow users to create configuration values at various scopes.
+
+#### Scenario: Create project config
+- **WHEN** the user navigates to project settings
+- **AND** clicks "Add Config"
+- **THEN** a form appears with key, value, and scope fields
+- **AND** submitting creates a config at the selected scope
+
+#### Scenario: Config scope validation
+- **WHEN** the user creates a config
+- **THEN** the scope must be one of: global, user, project, instance
+- **AND** the scope_id must match the selected scope type
+
+### Requirement: User can view and update configs
+The system SHALL display configs with scope-based filtering.
+
+#### Scenario: List configs
+- **WHEN** the user views configs for a project
+- **THEN** all configs visible at project scope or above are displayed
+- **AND** values are shown as formatted JSON
+
+#### Scenario: Update config
+- **WHEN** the user edits a config value
+- **THEN** the updated value is saved
+- **AND** the change takes effect on next tool spawn
+
+### Requirement: User can delete configs
+The system SHALL allow deletion of config values.
+
+#### Scenario: Delete config
+- **WHEN** the user clicks delete on a config
+- **THEN** a confirmation dialog appears
+- **AND** confirming removes the config
+- **AND** the config is no longer injected into containers

openspec/changes/config-secrets/specs/runtime-injection/spec.md

@@ -0,0 +1,40 @@
+## ADDED Requirements
+
+### Requirement: Configs are mounted into tool containers
+The system SHALL mount configuration values as files into spawned tool containers.
+
+#### Scenario: Config file mount
+- **WHEN** a tool instance is spawned
+- **THEN** all applicable configs are written to /app/config/
+- **AND** each config is a separate JSON file named by key
+- **AND** files have restrictive permissions (0400)
+
+#### Scenario: Config scope resolution
+- **WHEN** configs are resolved for a tool instance
+- **THEN** the system collects configs from all applicable scopes
+- **AND** instance scope overrides project scope
+- **AND** project scope overrides user scope
+- **AND** user scope overrides global scope
+
+### Requirement: Secrets are injected as environment variables
+The system SHALL inject secret values as environment variables into tool containers.
+
+#### Scenario: Secret env var injection
+- **WHEN** a tool instance is spawned
+- **THEN** all applicable secrets are decrypted
+- **AND** injected as environment variables with uppercase keys
+- **AND** the container process can access them
+
+#### Scenario: Secret scope resolution
+- **WHEN** secrets are resolved for a tool instance
+- **THEN** the same scope hierarchy applies as configs
+- **AND** closest scope wins on key collision
+
+### Requirement: Missing secrets fail spawn
+The system SHALL prevent spawning if referenced secrets are missing.
+
+#### Scenario: Validate secrets before spawn
+- **WHEN** a spawn request references a secret by key
+- **AND** the secret does not exist in any applicable scope
+- **THEN** the spawn fails with a clear error message
+- **AND** no container is created

openspec/changes/config-secrets/specs/secret-management/spec.md

@@ -0,0 +1,37 @@
+## ADDED Requirements
+
+### Requirement: User can create secrets
+The system SHALL allow users to store encrypted secret values.
+
+#### Scenario: Create secret
+- **WHEN** the user navigates to project secrets
+- **AND** clicks "Add Secret"
+- **THEN** a form appears with key and value fields
+- **AND** the value is encrypted with Fernet before storage
+- **AND** the user sees a masked value (e.g., ••••••) after creation
+
+#### Scenario: Secret scope
+- **WHEN** the user creates a secret
+- **THEN** the scope can be user, project, or instance
+- **AND** the secret is only visible within that scope hierarchy
+
+### Requirement: Secrets are never exposed decrypted
+The system SHALL prevent decrypted secret values from being sent to the frontend.
+
+#### Scenario: Secret list display
+- **WHEN** the user views the secrets list
+- **THEN** only secret keys and scopes are visible
+- **AND** values are always masked
+
+#### Scenario: Secret update
+- **WHEN** the user updates a secret
+- **THEN** only the new value is sent to the backend
+- **AND** the old value is replaced (not displayed)
+
+### Requirement: User can delete secrets
+The system SHALL allow deletion of secret values.
+
+#### Scenario: Delete secret
+- **WHEN** the user deletes a secret
+- **THEN** the encrypted value is permanently removed
+- **AND** the secret is no longer injected into containers