chore(repo): rename rust-port/wifi-densepose-rs → v2/ (flatten to one level)#427
Merged
chore(repo): rename rust-port/wifi-densepose-rs → v2/ (flatten to one level)#427
Conversation
… level) The Rust port lived two directories deep (rust-port/wifi-densepose-rs/) without any sibling under rust-port/ that warranted the extra level. Move the whole workspace up to v2/ to match v1/ (Python) at the same depth and shorten every cd / build command across the repo. git mv preserves history for all tracked files. 60 files updated for path references (CI workflows, ADRs, docs, scripts, READMEs, internal .claude-flow state). Two manual fixes for relative-cd paths in CLAUDE.md and ADR-043 that became wrong after the depth change (cd ../.. → cd ..). Validated: - cargo check --workspace --no-default-features → clean (after target/ nuke; the gitignored target/ was carried by the OS rename and had hard-coded old paths in build scripts) - cargo test --workspace --no-default-features → 1,539 passed, 0 failed, 8 ignored (same totals as pre-rename) - ESP32-S3 on COM7 → still streaming live CSI (cb #40300, RSSI -64 dBm) After-merge follow-up: contributors should `rm -rf v2/target` once and let cargo regenerate from the new path. Co-Authored-By: claude-flow <ruv@ruv.net>
This was referenced Apr 26, 2026
ruvnet
added a commit
that referenced
this pull request
Apr 26, 2026
Two leftover references missed by the sed pass in #427 (which only matched the full `rust-port/wifi-densepose-rs` path). These are bare references to the workspace directory name, which is now v2/. Co-Authored-By: claude-flow <ruv@ruv.net>
This was referenced Apr 26, 2026
ruvnet
added a commit
that referenced
this pull request
Apr 26, 2026
The Rust port at v2/ has been the primary codebase since the rename in #427. The Python implementation at v1/ is no longer the active target; the only load-bearing path is the deterministic proof bundle at v1/data/proof/ (per ADR-011 / ADR-028 witness verification). Move the whole Python tree into archive/v1/ and document the policy in archive/README.md: no new features, bug fixes only when they affect a still-load-bearing path (currently just the proof), CI continues to verify the proof on every push and PR. Path references updated in 26 files via path-pattern sed (only matches v1/<known-child> patterns, never bare v1 or API URLs like /api/v1/). Two double-prefix typos (archive/archive/v1/) caught and hand-fixed in verify-pipeline.yml and ADR-011. Validated: - Python proof verify.py imports cleanly at archive/v1/data/proof/ (numpy/scipy still required; CI installs requirements-lock.txt from archive/v1/ now) - cargo test --workspace --no-default-features → 1,539 passed, 0 failed, 8 ignored (unaffected by Python tree relocation) - ESP32-S3 on COM7 untouched (no firmware paths changed) After-merge: contributors should re-run any local `python v1/...` commands as `python archive/v1/...` (CLAUDE.md and CHANGELOG already updated).
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.
Why
The Rust port lived two directories deep (
rust-port/wifi-densepose-rs/) with no sibling underrust-port/. The extra level had no justification and made every cd / build command longer than it needed to be. v1 (Python) sits atv1/— making the Rust portv2/matches that depth and is consistent with the existing v1/v2 framing in CLAUDE.md.Scope
git mv rust-port/wifi-densepose-rs v2— preserves full history (all 600+ files moved as renames; verify withgit log --follow v2/Cargo.tomlafter merge).rust-port/directory removed (was empty after the move).*.toml,*.yml,*.md,*.sh,*.py,*.json,*.rs, Dockerfile*).ci.yml,desktop-release.yml)gcloud-train.sh,generate-witness-bundle.sh,qemu-mesh-test.sh,qemu_swarm.py)install.sh,README.md,CLAUDE.md,Dockerfile.rust.claude-flow/JSON state, internal READMEs)cdpaths that became wrong after the depth change:CLAUDE.md—cd ../..→cd ..aftercd v2ADR-043—cd ../../ui/mobile→cd ../ui/mobileValidation
ESP32-S3 on COM7 was running unmodified firmware throughout — verified live CSI cb #40300, RSSI −64 dBm both before and after the rename. No firmware impact.
After-merge follow-up for contributors
Test plan
ci.yml,desktop-release.yml)v2/(19 ADRs touched)docker/Dockerfile.rust)🤖 Generated with claude-flow