chore: archive 15 completed OpenSpec changes
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.
This commit is contained in:
+5
-5
@@ -1,14 +1,14 @@
|
||||
# openspec/changes/archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
dir: openspec/changes/archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
# archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
|
||||
index: openspec/changes/archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines specification requirements for validating tool types, managing default network ports, exposing ports in Docker Compose templates, and supporting multiple network interfaces in the OpenCode web terminal environment.
|
||||
Defines specifications for validating tool types, managing default network ports, exposing services through Docker Compose templates, and supporting multiple network interfaces in the OpenCode web terminal project.
|
||||
## files
|
||||
- spec.md | Defines requirements for tool type validation including default ports, compose template port exposure, and multiple interface support
|
||||
## arch
|
||||
Specification-driven requirements document using markdown-based technical specification pattern with structured sections covering validation rules, port configuration defaults, container orchestration integration, and multi-interface networking requirements.
|
||||
Specification-driven architecture using markdown-based requirements documents to define validation rules, port configuration schemas, and multi-interface networking patterns before implementation.
|
||||
## tags
|
||||
spec, defines, requirements, tool, type, validation, including, default
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user