1/3 Relocate pre-v0.5 code into legacy/ - #44
Open
varunursekar wants to merge 1 commit into
Open
Conversation
Archive the old top-level packages (vero/, vero-agents/, vero-benchmarking/) under legacy/ ahead of adding the redesigned system at the repo root. Pure moves; see legacy/README.md.
shehabyasser-scale
approved these changes
Jul 24, 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.
First of three stacked PRs that split #41 (
v0.5) into reviewable pieces.Moves the pre-v0.5 codebase (
vero/,vero-agents/,vero-benchmarking/) underlegacy/— the code for the original VeRO paper, kept for reference/reproducibility. Pure renames (378 files) +legacy/README.md.Stack: 1/3 (this) → 2/3 add
vero/→ 3/3 addharness-engineering-bench/. Merge in order.🤖 Generated with Claude Code
Greptile Summary
This is the first of three stacked PRs converting the repository to the v0.5 layout. It is a pure rename: 378 files are moved from
vero/,vero-agents/, andvero-benchmarking/intolegacy/, and a brieflegacy/README.mdis added to explain the archive.README.mdis now stale: its directory tree, relative links (vero/README.md,vero-agents/README.md,vero-benchmarking/README.md), and shell commands (cd vero && uv sync) reference paths that no longer exist until PR 2/3 restoresvero/at the root.Confidence Score: 4/5
Safe to merge as an intermediate step in the stack, provided PRs 2/3 and 3/3 follow promptly.
Every changed file is a pure rename with no content modification. The one new file (legacy/README.md) is a short, accurate description. The only concern is that the root README.md is left with broken links and install commands pointing to paths that won't exist until PR 2/3 lands — an intermediate gap for anyone who clones between merges.
Root README.md — its directory tree, relative links, and shell install commands reference paths (vero/, vero-agents/, vero-benchmarking/) that have been moved under legacy/ and will only be valid again once PR 2/3 adds the new vero/ at root.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["PR 1/3 (this)\nMove vero/, vero-agents/,\nvero-benchmarking/ → legacy/"] --> B["PR 2/3\nAdd new vero/ at root\n(v0.5 core library)"] B --> C["PR 3/3\nAdd harness-engineering-bench/\nat root"] C --> D["Final state:\nvero/ + harness-engineering-bench/\n+ legacy/ at root"] style A fill:#f9e4b7,stroke:#e6a817 style B fill:#d4edda,stroke:#28a745 style C fill:#d4edda,stroke:#28a745 style D fill:#cce5ff,stroke:#004085Reviews (1): Last reviewed commit: "Relocate pre-v0.5 code into legacy/ (ori..." | Re-trigger Greptile