The Nuxt and Rust modules run in isolated flatpak-builder sandboxes with
separate git clones. Tauri's compile-time frontendDist resolution requires
.output/ to exist at the repo root relative to src-tauri/Cargo.toml.
Without it, tauri::generate_context!() falls back to the dev URL
http://localhost:1432, causing 'Connection refused' at runtime.
Fix:
- Nuxt module persists .output/ to /app/share/drop-frontend/
- Rust module symlinks it into the checkout before cargo build
- org.droposs.client.yml
- scripts/verify-manifest-guards.sh
GSD context:
- Milestone: M001 - Fix Flatpak Build + CI Pipeline
- Slice: S01
- Task: T02 - Fixed vendored-source paths to use $PWD-based absolute paths, removed --manifest-path in favor of cd+build, added `set -eu` error guards to all three modules, and wrote scripts/verify-manifest-guards.sh with 9 checks all passing.
GSD-Task: S01/T02
- scripts/generate-manifest.py
- org.droposs.client.yml
- tests/verify-manifest-modules.py
GSD context:
- Milestone: M001 - Fix Flatpak Build + CI Pipeline
- Slice: S01
- Task: T01 - Created scripts/generate-manifest.py that splits the monolithic 15,573-line manifest into three Flatpak modules (bootstrap, Nuxt, Rust) preserving all checksums, and wrote tests/verify-manifest-modules.py which confirms 3 modules with correct names, checksums, and append-path configuration.
GSD-Task: S01/T01
GSD Bot