The standalone ghost_hunter binary defines its own on_init/on_frame/on_timer
WASM3 entry-points; the lib also exports those when default-pipeline is on.
A vanilla `cargo build -p wifi-densepose-wasm-edge --target wasm32-unknown-unknown
--release` would build both, producing a "Linking globals named 'on_frame':
symbol multiply defined!" error.
Fix: declare an explicit `[[bin]] required-features = ["standalone-bin"]`
gate so the bin only builds when the user opts in with
`--no-default-features --features standalone-bin`. The default feature
set continues to produce the combined-pipeline lib (15 KB wasm32).
Validation:
- cargo build -p wifi-densepose-wasm-edge --target wasm32-unknown-unknown
--release → 15 KB wifi_densepose_wasm_edge.wasm (default-pipeline lib)
- cargo build -p wifi-densepose-wasm-edge --bin ghost_hunter
--target wasm32-unknown-unknown --release
--no-default-features --features standalone-bin
→ 5.8 KB ghost_hunter.wasm (standalone module)
- cd v2/crates/wifi-densepose-wasm-edge && cargo test --features std
--no-default-features → 75/75 tests pass
Co-Authored-By: claude-flow <ruv@ruv.net>
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.
ruv