Skip to content

revert: destructive restore to 62f487e (2026-04-15 state)#94

Merged
KailasMahavarkar merged 1 commit intomainfrom
chore/restore-to-62f487e
Apr 22, 2026
Merged

revert: destructive restore to 62f487e (2026-04-15 state)#94
KailasMahavarkar merged 1 commit intomainfrom
chore/restore-to-62f487e

Conversation

@KailasMahavarkar
Copy link
Copy Markdown
Collaborator

Single-commit destructive revert of all changes merged to main after 62f487e. Tree equals 62f487e exactly.

Wipes PRs #63..#92 in one admin-merged commit. Force-push path was rejected by branch protection so this is expressed as a forward commit instead.

Diff vs main: 213 files, 6727 insertions, 5224 deletions.

Verified: bun install clean, bun run build exit 0.

Destructive reset of repo tree to 62f487e (feat: expand platform support to 12 IDEs/CLIs with format-aware patching) from 2026-04-15.

Wipes all work merged to main after 62f487e including PRs #63..#92: docker-primary fixes, topology manifest introduction, routing/artifact contracts, workspace-first routing, all corpus-backed slice PRs (#81..#90), corpus/tests removal (#91), MCP runtime deletion + topology enforcement (#92).

Tree equals 62f487e exactly. This is a destructive reset expressed as a single forward commit because branch protection on main forbids non-fast-forward push; the admin-merge path is used instead.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@KailasMahavarkar KailasMahavarkar merged commit 09d72a5 into main Apr 22, 2026
4 checks passed
@KailasMahavarkar KailasMahavarkar deleted the chore/restore-to-62f487e branch April 22, 2026 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant