chore: sync main to dev after v1.0.37 notes fix - #497
Merged
Conversation
chore(release): sync dev to main for v1.0.37
The stable series notes described an earlier draft of the train: they covered only #469 (graphRev) and claimed it was the sole feature surface, while the shipped range also carries #435 (project-level /dag inspector discovery) and #433 (warn-only shell silence guard), the #488 harness refresh, and the #475/#474/#472 stability fixes. The test summary cited CI @ 29e876a instead of the released 818f47d. Closes #493
The CI 配置 section claimed specgit-accept.yml installs pinned specgit@1.0.1; the workflow actually installs globally via npm install -g specgit@^0.5.0 (workspace-local installs die on the bun catalog: protocol). Closes #494
docs(release): correct v1.0.37 notes scope
LeXwDeX
marked this pull request as ready for review
September 2, 2026 00:30
This was referenced Sep 3, 2026
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.
Why
Carry the post-release docs corrections on
mainback into the integration layer so the next release train starts from correct release notes and an accurate AGENTS.md.What changed
.github/releases/v1.0.37.mdscope (feat(dag): refresh nodes after topology replans #469/feat(dag): project-wide discovery fallback for /dag inspector #435/feat: engine-level guardrail for silent long-running shell commands #433 inventory, CI @ 818f47d) and the AGENTS.md specgit-accept.yml install-form fix (docs: correct v1.0.37 release notes scope #493/docs: fix specgit accept CLI version drift in AGENTS.md #494).Evidence
mainvia PR docs(release): correct v1.0.37 notes scope #495 (Typecheck / Unit Tests (linux) / E2E linux+windows / SpecGit Acceptance all green); this PR re-runs the dev-layer gates on the merge ref.Closes #496