chore(openspec): archive opencode-server-lifecycle - #120
Merged
Merged
Conversation
The capability spec was synced in #119; this only moves the completed change into openspec/changes/archive/2026-09-15-fix-opencode-server-lifecycle/. All 25 tasks are complete.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Archives the completed
fix-opencode-server-lifecyclechange. The capability spec was already synced intoopenspec/specs/opencode-server-lifecycle/by #119, so this PR only moves the change into the archive.openspec/changes/fix-opencode-server-lifecycle/→openspec/changes/archive/2026-09-15-fix-opencode-server-lifecycle/(pure rename;.openspec.yamland all artifacts preserved).Verification
openspec list --json→ no active changesopenspec validate --specs→ 21 passed, 0 faileddone, 25/25 tasks complete, delta already syncedNotes
#119 squash-merged as
436fd30before this archive could be ordered ahead of it, so the archive lands as a follow-up rather than in the same change set.