2.7 KiB
2.7 KiB
Phase overview
Use this document as the top-level index for the current release-oriented recovery pipeline.
Repository model
- repo root is the canonical editable deobfuscated tree
runs/keeps local current and previous upstream snapshot artifactsstable/keeps long-lived metadata reused across snapshotsreleases/stores machine-readable manifests for published deobfuscated versions- upstream bundles are stored as release assets, not committed into git
Release model
- an upstream “release” is any snapshot you decide to ingest
- your published versions use your own versioning, e.g.
0.y.z ychanges when the upstream snapshot changeszchanges when only maintained transforms or packaging change- publish with both Git tags/Gitea Releases and the package registry
Cross-phase invariants
- do not rewrite semantics during relabeling
- do not depend on LLM output for splitting or diffing
- only send changed or new segments to the LLM on upgrade
- keep maintained changes replayable as transforms, preferably
jscodeshiftcodemods - keep normal git commits as the human audit log for maintained changes
- emit compact upstream summary manifests instead of line-by-line historical ledgers
- surface low-confidence transform replays as conflicts instead of auto-applying them
Phases
- Phase 1 — deterministic ingest
- Phase 2 — dependency identification and externalization
- Phase 3 — context extraction
- Phase 4 — run-to-run diffing and upstream summary
- Phase 5 — iterative relabel queue planning and batching
- Phase 6 — relabel API execution and wave scheduling
- Phase 7 — iterative relabel evaluation, application, and queue feedback
- Phase 8 — deterministic codebase regularization
- Phase 9 — derive and replay maintained transforms
- Phase 10 — build and publish release artifacts