Repository navigation
Support OpenSpec stores as a first-class spec root - #174
Merged
Merged
Conversation
…kout Captures uncommitted work found staged in the main checkout (spec store support, spec deltas, and the Verify phase) so it isn't lost while it gets reconciled against current main. Known issue at this checkpoint: pull.go and repo.go were reverted to an older version, dropping maxSlugLen/capSlug/ dirExists/nextAvailableSlug from already-merged main work — go test fails to build until that's reconciled.
…nspec-store-support rebase The staged openspec-store-support work reverted pull.go and sync.go to versions that predated two already-merged main features: slug-length capping/collision-avoidance (#167, dirExists/nextAvailableSlug/capSlug/ maxSlugLen) and wiring sync's -project flag to actually call ProjectOntoBoard (#165). Restores both so `go test ./...` builds and passes again.
Deploying specsync with
|
| Latest commit: |
933284c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a29ae41c.specsync.pages.dev |
| Branch Preview URL: | https://feat-173-openspec-store-supp.specsync.pages.dev |
The old branch's flat diff also carried three unrelated changes along for the ride (spec-issue-linker archival, warn-before-creating-a-duplicate-issue, and a missing tasks.md on commit-change-stage) that don't belong in this PR and broke CI's structural validate gate. Drops the two fully unrelated ones, and adds tasks.md to commit-change-stage — a legitimate follow-up spun off from this feature's own tasks.md, just not yet planned into tasks.
androidand
added a commit
that referenced
this pull request
Sep 30, 2026
…port merge (#177) ## Summary - PR #174's source branch predated the "See who's already working what" (`specsync topology`) feature card's addition to `site/features.json`, and its flat-diff reapplication silently deleted it during that merge — same shape of regression as the pull.go/sync.go issues already caught and fixed in that PR, just not covered by any test or the structural validator since it's a content file. - Restores the entry verbatim (still `status: soon`, issue #168 — the card's own status is a separate content decision, out of scope here). Found while verifying the #174 deploy is up to date on specsync.se. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This was referenced Oct 5, 2026
androidand
added a commit
that referenced
this pull request
Oct 6, 2026
## Summary - `specsync topology` was silently broken by PR #174's rebase (its source branch predated the command's dispatch wiring) — restores `"topology": true` in `knownSubcommands` and the `case "topology": runTopology(rest)` arm. - Drops the stale `"status": "soon"` badge from three feature cards on specsync.se whose features actually shipped weeks ago (design notes overflow #139, topology #168, adopt #160). Found while verifying the #174/#177 deploys were fully correct. Closes #179 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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
store:fromopenspec/config.yamlso bare specsync resolves an OpenSpec store's spec root, with-store <id>resolving through OpenSpec's machine registry.targetsto a committed per-changespecsync.yml, inserted into repo resolution ahead of git-remote auto-detection; fan out one change to several target repos.-allis passed.doctorwith store health checks: resolved, registered, behind remote, dirty, changes missing targets.specs/**/spec.mddeltas into the Change model, and add the Verify phase (specsync verify -change <slug>, with-json/-checklist).store:, notargets) is unchanged.Recovered from a stale, never-merged branch and reconciled onto current
main: restored slug-length capping/collision-avoidance (#167) and sync's board-projection wiring (#165), both of which the original branch predated.Remaining follow-ups, tracked in the change's
tasks.mdrather than blocking this PR: cross-linking multi-target issues, projecting the acceptance checklist into the issue body, aspecsync store migratecommand, and three items to report upstream to OpenSpec.Closes #173