Skip to content

1/3 Relocate pre-v0.5 code into legacy/ - #44

Open
varunursekar wants to merge 1 commit into
mainfrom
pr1-legacy-relocate
Open

1/3 Relocate pre-v0.5 code into legacy/#44
varunursekar wants to merge 1 commit into
mainfrom
pr1-legacy-relocate

Conversation

@varunursekar

@varunursekar varunursekar commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

First of three stacked PRs that split #41 (v0.5) into reviewable pieces.

Moves the pre-v0.5 codebase (vero/, vero-agents/, vero-benchmarking/) under legacy/ — 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 add harness-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/, and vero-benchmarking/ into legacy/, and a brief legacy/README.md is added to explain the archive.

  • All file moves are renames with zero content changes, making this essentially a structural reorganisation with no logic impact.
  • The root README.md is 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 restores vero/ 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

Filename Overview
legacy/README.md New archive description file — accurately describes the legacy directory's purpose and its relationship to the future root-level code.

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:#004085
Loading

Reviews (1): Last reviewed commit: "Relocate pre-v0.5 code into legacy/ (ori..." | Re-trigger Greptile

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.
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.

2 participants