chore(openspec): archive fleet-env-target and neutral-engine-config - #221
Merged
Merged
Conversation
Both shipped without being archived: neutral-engine-config in 1b676e4 and fleet-env-target in 7ae4ca7. fleet-env-target carried a real fleet-config delta that was never synced, so the spec documented neither --env as a target nor what a fleet of one is, while the code had done both for two releases. Its modified resolution requirement and the fleet-of-one requirement are now in the main spec. neutral-engine-config declares skip_specs, so archiving it is a move with nothing to sync.
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.
Archives two changes that shipped without it, and syncs the delta spec one of them left behind.
Summary
fleet-env-target(shipped in7ae4ca7) carried afleet-configdelta that was never synced. The main spec documented neither--envas a target nor what a fleet of one is, while the code had done both since that merge. Its modified "Fleet file resolution" requirement (now covering--env,--fleetand the exclusivity rule, 11 scenarios) and the added "A registered environment is a fleet of one" requirement are now in the main spec.neutral-engine-config(shipped in1b676e4) declaresskip_specs, so archiving it is a move with nothing to sync.openspec listnow reports no active changes;openspec validate --specspasses 53/53.Implementation details
Both were left unarchived because the one-shot PR flow does not archive — it stops at the PR. Worth knowing for future changes: the archive step has to be run deliberately after a merge, and skipping it leaves the specs describing the previous release rather than the current one. The
fleet-configgap had been open across two merges.No code changes.