Repository navigation
Restore pre-Codex GERM main (M9 archived for future use) - #16
Merged
Merged
Conversation
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.
Restores GitHub main's complete tracked source tree to original commit
8789022415ffb44aca8ff88c4d1ba31f4ef994be, while retaining accepted M9, readiness documentation, existing feature branches, PRs, tests, evidence and all integration history. GitHub only: no SSH, Pi access, service operation, deployment, firmware, hardware or data changes./home/germ/germ-m9-testwas not accessed or changed.Preservation completed before rollback preparation
8027b9f5b424aa5fc226ea4c3897ee3e2fbfdab3.61aeed07f9eff3c70020f2f417fb2c3fb2257503.98d209517a47556de31b80e616f8ca93f4f81414, including readiness commit551ff294afff39c2237bb7a2bd9ca4addb5109f8. This documentation is additional to accepted M9 and remains separately recoverable.Reverse integration without rewriting history
Current main was checked against
713800931a5926abd8c9c5d57669c124c54dac42; no additional changes were found. This branch starts there and applies seven ordinarygit revert --no-edit -m 1 <merge>commits, newest integration first. Both parent identities of every original merge were verified. Each resulting intermediate tree matches the corresponding original first-parent checkpoint.713800931a5926abd8c9c5d57669c124c54dac42bfc645bbc98233a51beb35a45f72ff11c88b5f40b574f7e9ba0a95a6c3dbf1d55a721a46733edabedf6f7f50d5c4134b7f178a6a03ea117e670d90cf91447920fa052928190174307f55b59c6db14e2cddf5c6eb122022058eb179b4ab0ef4960a3a74645de81b195a683dc27e1858d26eb39af47870aa929227ba90d8b38879914155d6c31fc1b45de2c3da062bf256c6edda1922267643852841b9bb70a85f51344ca3ded1b3f09ac2c8c68b509b41032fd98e79927b18754c63e0b79d134e00d4fbdfb7d120342311c44d152f064d80e2faefb2605f86798c75815ee6228cd6b6c3c28847a9007ff2c27a47bc955ee80cca9d850f86a8eea3dcda404146f50554a12aFinal candidate:
e80cca9d850f86a8eea3dcda404146f50554a12a. Final and original tree IDs are bothf1516fe4c7bf3b164ced13f36fb0615902bbcd6a.git diff 8789022415ffb44aca8ff88c4d1ba31f4ef994be e80cca9d850f86a8eea3dcda404146f50554a12ais empty, covering every tracked path, Git blob, executable bit and directory. No extra documentation/test/CI file is added to the restored tree. The 42-file legacy baseline retains its original code as requested; M0–M9 files remain recoverable in the archive refs and Git history.No reset, force push, rebase, squash or branch deletion. Existing local checkouts/untracked files and the Pi installation are outside this source rollback.
Applicable original-baseline validation
Original host output:
C++/shell output:
Review and restoration instructions
git fetch originretrieves restored main; use a fresh local checkout if desired. Do not reset/clean existing workspaces or deploy from this PR. This GitHub operation does not replace software, switch databases, restart services or change hardware on the Pi.archive/germ-m9-codex-2026or the annotated tag. Readiness documentation is under its separate archive branch. Reintroducing M9 to main needs a new reviewed integration plan: already-merged-and-reverted commits are not automatically reapplied by simply merging the same archive ancestry.User authorization: explicit GitHub-only restoration request dated 2026-11-17 (America/Chicago). No physical, deployment, historical deletion or Pi operation is authorized or performed.
Actual restoration result
Merged and independently verified. New main commit
470963eb9da4ede6813c6872975a9897310c5c0ehas the verified original treef1516fe4c7bf3b164ced13f36fb0615902bbcd6a, exactly matching8789022415ffb44aca8ff88c4d1ba31f4ef994be. A fresh fetch and full Git diff confirmed equality.All 10 original host checks, actual-sketch C++, Python/Jinja/JavaScript/shell parsing and exact-tree checks passed. Live policy inspection found no configured protection/rulesets or required reviews/status checks; no candidate failures, pending checks or requested reviews were bypassed, and no policy was changed. The original tree has no hosted CI workflow; no hosted CI run is claimed.
All prior feature branches and PR #5-#15 heads/bases/states remain unchanged. Archive branch, annotated tag/peeled M9 target and documentation archive were reverified after merge. Rollback branch, original workspaces and 15 hashes are preserved. No SSH, Pi access, deployment, hardware operation or history rewrite occurred.