budget-app/docs/STANDALONE_VALIDATION.md

23 lines
2.2 KiB
Markdown

> Historical revision record. For the current Cargo-only pipeline and test locations, see Readme, TESTING.md and GRADLE_FREE_VALIDATION.md.
> Historical three-member layout. The current two-member layout is validated in `TWO_CRATE_VALIDATION.md`.
# Standalone virtual workspace validation — 26 October 2026
The root manifest contains no `[package]`; its three members are inside `budget-app`: `budget-app`, `crates/budget-capture`, and `budget-capture`. No `nigig-org` member/dependency was added, and no files in that repository were changed by this correction.
Final checks after moving the application/resources/demos and renaming the capture/platform crates:
- **100 workspace Rust tests passed.**
- **93 independent model-harness tests passed** using the relocated application source files.
- Android Rust/JNI cross-check for `budget-capture` and `budget-capture`: passed.
- Native application compilation and linking: passed.
- `cargo run --locked` **from the virtual workspace root** launched the actual Budget binary, initialized its modules and OpenGL renderer, and remained alive for the 15-second Xvfb smoke window.
- **12 Java extraction tests passed** in the crate-owned Android library.
- Android validation harness APK assembly and offline/bundled-OCR checks: passed.
- Integrated application/platform Java and manifest/resource compilation: passed.
- **4 packaging/architecture tests passed**, including assertions that the root is virtual, the app is the default member, every member is within this repository, root `src/` is absent, and Java has a single owner under the platform crate.
- Shared Cargo.lock regenerated and exported after successful Rust validation.
- Temporary Rust, JDK/SDK/Gradle environments removed; source and packaging outputs retained separately from temporary tools.
Limits remain unchanged: Linux startup smoke is not interactive UI testing; Android compilation/harness assembly is not an installed final native APK or device test. Overlay/projection/permission behavior, OCR accuracy, persistence and signed upgrade acceptance need Android device testing. iOS does not have a cross-app floating-overlay backend; the optional Swift image OCR helper is source-only and not Xcode/host validated.