openspec: archive 4 completed changes, sync main specs - #36
Merged
Conversation
add-claude-docker-help, container-git-config-overlay, add-tfe-support, and add-private-registry-support are all fully implemented; validated task-by-task and against live/static code behavior before archiving. Two of the four needed their delta specs refreshed before `openspec archive` would accept them, since main specs had drifted since the deltas were authored: - add-claude-docker-help reused a change-id that had already been archived once in May; its delta was still marked ADDED for requirements that already exist in the main cli-help spec. Changed to MODIFIED. - container-git-config-overlay's delta modeled the new container-only overlay as a MODIFIED requirement, but its scenarios fully replace the old host-opt-in workflow rather than amend it. Split into REMOVED (old behavior) + ADDED (new requirement, distinctly named) so the retraction is explicit instead of silently dropping scenarios. - add-tfe-support's Credentials opt-in / gh-login-persistence deltas were written before gh-auth-proxy-sidecar was archived and no longer matched the current --gh/--gh-direct sidecar behavior; refreshed to layer --tfe onto the current spec text instead of reverting it. add-claude-docker-openspec is intentionally left open: its spec still describes pinning OPENSPEC_VERSION via a Dockerfile ARG, which was superseded by the pins/openspec.env mechanism from automate-version-pins (already implemented on main, not yet archived). automate-version-pins itself is left alone as it's still being worked on.
dtump
force-pushed
the
archive/completed-openspec-changes
branch
from
August 25, 2026 13:48
bde1b64 to
495ab7b
Compare
sbp-bvanb
approved these changes
Aug 25, 2026
5 tasks
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
2 participants
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 four OpenSpec changes that are fully implemented, verified independently before archiving (task-by-task against the real code, and spec scenarios against live/static behavior where possible):
add-claude-docker-helpcontainer-git-config-overlayadd-tfe-supportadd-private-registry-supportNo
run.sh/Dockerfile/README.mdchanges — this is purely archiving + spec sync.automate-version-pins(in progress) andadd-claude-docker-openspecare deliberately left open. The latter's spec still describes pinningOPENSPEC_VERSIONvia a DockerfileARG, which was superseded by thepins/openspec.envmechanism introduced byautomate-version-pins(already implemented onmain, not yet archived). Tracked in a follow-up issue.Delta refreshes required before archiving
openspec archiverefused three of the four until their delta specs were brought back in sync withopenspec/specs/(it has a built-in guard against silently dropping scenarios):## ADDED Requirementsfor requirements that already exist in the maincli-helpspec (from the first archive). Changed to## MODIFIED Requirements..git/configoverlay that fully replaces the old host-opt-in workflow (per its own commit message: "Retracts the host opt-in instructions... in favour of this asymmetric approach"), not an amendment to it. Split into## REMOVED Requirements(old host-opt-in requirement) +## ADDED Requirements(new requirement, distinctly namedNested worktrees portable via a container-only git config overlay) so the retraction is explicit rather than silently dropping the old scenarios.Credentials opt-in/ gh-login-persistence deltas were authored beforegh-auth-proxy-sidecarwas archived, and still described the pre-sidecar--ghbehavior (direct token forwarding). Refreshed to layer--tfeonto the current sidecar-based spec text instead of reverting it.Also fixed a cosmetic formatting artifact (missing blank lines around
## Purpose/## Requirementsheaders) that the archive tool's rebuild introduced in the four touched main specs.Test plan
openspec validate <change> --strictpasses for all four archived changes (pre-archive)openspec spec validate <capability> --strictpasses for every touched main spec (cli-help,external-cli-tools,multi-workspace-mounts,package-managers) post-archiveopenspec validate automate-version-pins --strictandopenspec validate add-claude-docker-openspec --strictstill pass (untouched changes unaffected)git statusclean, onlyopenspec/files touched — no shellcheck/hadolint/docker-build/smoke run since no code changed