docs(specs): correct stale references, broken links, and formatting - #6629
Merged
Conversation
github-actions
Bot
added
documentation
This was referenced Jul 21, 2026
Closed
…cross /specs Audit all specification files under /specs/ for correctness against the current codebase, completeness of mandatory sections, and internal consistency, per the sdd skill's review checklist. - fix stale crate/module paths, type names, and enum variants across ~40 spec files that no longer matched crates/ (feature flags, MSRV, crate count, provider registry layout, TACO/orchestration descriptions) - add 24 missing rows to the MOC-specs.md status tracker and restore omitted child-spec entries in 004-memory/spec.md - fix ~90 broken [[wikilink]] cross-references (shifted spec numbers, links to nonexistent slugs) - repair a broken markdown code fence in 031-database-abstraction/spec.md that silently swallowed roughly 2500 lines of the document as an unclosed code block, plus duplicate heading numbers in three other files - reconcile 004-memory/ sub-specs on GitHub org, migration numbers, implementation status, and component naming - flag (without rewriting) seven MCP/security sub-specs whose types have no match anywhere in the codebase, and flag a 2900-line spec with an independent 900-line subsystem embedded that should be split out
bug-ops
force-pushed
the
fix/specs-quality-audit
branch
from
July 21, 2026 00:58
31574a8 to
79b6a28
Compare
bug-ops
enabled auto-merge (squash)
July 21, 2026 00:58
This was referenced Jul 22, 2026
Merged
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
Audit of the entire
/specs/tree against the sdd skill's own review checklist (correctness vs. current code, completeness of mandatory sections, internal consistency, formatting). No source code is touched, only files underspecs/.crates/(feature flags, MSRV, crate count, provider registry layout, TACO description in the agent-loop spec)MOC-specs.mdstatus tracker and restored omitted child-spec entries in004-memory/spec.md[[wikilink]]cross-references (shifted spec numbers, links to nonexistent slugs)031-database-abstraction/spec.mdthat silently swallowed roughly 2500 lines of the document as an unclosed code block, plus duplicate heading numbers in three other files004-memory/sub-specs on GitHub org, migration numbers, implementation status, and component namingFlagged, not executed (need follow-up)
008-mcp/008-1..3,010-security/010-1..4) reference types with no match anywhere in the codebase — need a dedicated rewrite session against real code, not a text patch031-database-abstraction/spec.md(2958 lines) has an independent ~900-line subsystem (agent identity data isolation) embedded with no external references — candidate for extraction to its own spec013-acp/spec.mdstill asserts an outdated protocol version in several current-state sectionsARCHITECTURE.md's dependency graph only covers specs 001-034; specs 035-081 are not represented004-16spec-number collision between two files (blocked on existing rustdoc citations in source, see issue specs/README.md spec-number index drifted from actual specs/ directory names #6308)Test plan
gitleaks protect --staged— no leaks found/specs/markdown files after the fence repairTEMPLATE.mdplaceholder as unresolved.rsfiles changed