docs: archive 17 stale planning docs to docs/historical/ (REQ-074 Phase 2a)#308
Merged
Conversation
…se 2a)
Wave 1 / PR-C of the cross-git investigation follow-ups. Acts on the
ARCHIVE verdicts from the docs audit (DOC-DOCS-AUDIT-2026-05-19):
roughly a third of the docs/ tree was dead-letter planning material
sitting next to active reference docs.
Moved to docs/historical/ (17 files, all `git mv` — history preserved):
- 15 docs/plans/2026-03-*.md — implementation plans for work that
has long since shipped (commit-traceability, cross-repo linking,
rowan/salsa, baseline-scoped validation, LSP, formal-verification
completion, the v0.1.0 release plan, ...).
- docs/audit-report.md — a 2026-03-09 doc-vs-reality snapshot that
still claimed fuzz/mutation testing "NOT IMPLEMENTED" while CI
runs both. Superseded by docs/research/2026-05-19-docs-audit.md.
- docs/design/rivet-cli-gaps-2026-04.md — a gap list with most
items now shipped.
Kept in docs/plans/: oslc-analysis.md (audit verdict KEEP — explains
a deliberate non-shipping decision still in force) and the two
vscode-lsp-rendering files (audit verdict INVESTIGATE — need a
maintainer triage, not archival).
doc_check change: `docs/historical/` joins `docs/plans/` and
`docs/design/` as an auto-`is_design_doc` directory. A frozen
archive snapshot legitimately references subcommands, artifact
counts, and IDs that have since changed; without the exemption the
moved files would trip the existence-based doc-check invariants
(SubcommandReferences / ArtifactCounts / ArtifactIdValidity). New
unit test `historical_dir_is_design_doc_without_marker`.
The one real inbound markdown link (what-is-rivet.md → audit-report)
is repointed to the new path and annotated as superseded.
Verified: `rivet docs check` PASS (57 files, 0 violations);
`cargo clippy -p rivet-core -- -D warnings` exit 0; the new unit
test passes.
Refs: FEAT-135, REQ-073, REQ-074
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
📐 Rivet artifact deltaNo artifact changes in this PR. Code-only changes (renderer, CLI wiring, tests) don't touch the artifact graph. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Rivet Criterion Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: db2ed75 | Previous: 9909beb | Ratio |
|---|---|---|---|
traceability_matrix/1000 |
62499 ns/iter (± 245) |
45259 ns/iter (± 4967) |
1.38 |
query/10000 |
132344 ns/iter (± 735) |
99824 ns/iter (± 437) |
1.33 |
This comment was automatically generated by workflow using github-action-benchmark.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
Wave 1 / PR-C of the cross-git investigation follow-ups (FEAT-135).
Acts on the ARCHIVE verdicts from
DOC-DOCS-AUDIT-2026-05-19— a thirdof the
docs/tree was dead-letter planning material next to activereference docs.
git mv'd todocs/historical/(history preserved):15
docs/plans/2026-03-*.mdimplementation plans for long-shippedwork,
docs/audit-report.md(a 2026-03-09 snapshot superseded bythe new audit), and
docs/design/rivet-cli-gaps-2026-04.md.docs/plans/:oslc-analysis.md(KEEP verdict) and thetwo
vscode-lsp-renderingfiles (INVESTIGATE — need triage).docs/historical/joinsplans//design/as anauto-
is_design_docdir, so frozen archive snapshots don't trip theexistence-based invariants. New unit test.
what-is-rivet.md) is repointedand annotated as superseded.
Test plan
rivet docs check— PASS (57 files, 0 violations).cargo clippy -p rivet-core -- -D warnings— exit 0.historical_dir_is_design_doc_without_markerunit test passes.Refs: FEAT-135, REQ-073, REQ-074
🤖 Generated with Claude Code