⏪ Revert merged spike evidence - #364
Merged
Merged
Conversation
PR #364: ⏪ Revert merged spike evidence158 files, +4 / -22864 Scope🔴 PR has 22868 lines changed. Split into focused PRs. 🟡 22868 lines changed. PRs under 400 receive more thorough review. 🟡 158 files changed. Are all changes related? 🟡 PR mixes config and source changes. Structural✅ No structural bloat detected. Slop✅ Slop indicators look low. Static Analysis✅ Oxlint found no issues. CorrectnessNo extraneous code patterns detected. |
This was referenced Aug 7, 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
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
PRs #350 and #353 are evidence spikes, not production source. They were mistakenly squash-merged while collapsing their review stack. Their findings remain preserved in the PRs and issues, but their large vendored proof trees should not live on
main.What changes
Before:
maincontains the complete #349 DOFS/FUSE proof and #351 Worker backend proof, including their vendored experimental dependencies.After:
mainreturns exactly to the tree that existed before those two merges. PRs #350 and #353 remain the permanent reviewable evidence. PR #362 remains open and unmerged as the final stacked proof.How it works
The branch reverts the two squash commits in reverse dependency order:
Review guide
Start with: the commit-level tree comparison against
21d26bcThen review:
spikes/351-worker-backends/;spikes/349-dofs/;.gitignoreanddeno.json; andLook carefully at: whether the resulting tree differs at all from pre-merge main.
What must stay true
21d26bcis removed; no such commit landed between the two mistaken merges.How to verify it
git diff --checkreports no whitespace errors.git diff --quiet 21d26bc7dd17966c4a21c151772ea5524ef2d333 -- .exits zero, proving the resulting tree exactly matches pre-spike main.Scope
Included
d96f5bf).f3f7ad5).Intentionally unchanged
Risks and limitations
Scope confirmation