fluxa-core/docs
KhooLy 603a94bf6c docs: mark §11 (desktop JSON tax) resolved after verifying fluxa-desktop
Per CLAUDE.md's rule to verify against fluxa-desktop/src-tauri call
sites before touching FluxaCore: the plan's premise for this section
no longer holds. dispatchAction/completeEffect/getSnapshot in
fluxa-desktop's src/core/engine.ts already go through dedicated Tauri
commands (engine_dispatch/engine_complete_effect/engine_snapshot) that
call FluxaCore::* directly in Rust, not through core_invoke. FluxaCore
itself has also grown from the "8 methods" this doc assumed to 21
(cast/AirPlay/Chromecast/Roku helpers), all with real call sites
verified via grep. The remaining core_invoke Tauri command is a
generic fallback for infrequent methods where a dedicated command
per method would be boilerplate with no measurable win, since Tauri
IPC serializes as JSON at the JS<->Rust boundary either way. No code
change needed; also corrected the stale "8 methods" claim in
CLAUDE.md's core_api description to reflect the current count.
2026-07-07 15:10:23 +03:00
..
building.md feat: update desktop core API support 2026-07-03 16:05:52 +03:00
effect-loop.md feat: companion server, FFI cleanup, and pre-release hardening 2026-06-17 20:01:42 +03:00
effects.md feat: companion server, FFI cleanup, and pre-release hardening 2026-06-17 20:01:42 +03:00
integrating.md feat: companion server, FFI cleanup, and pre-release hardening 2026-06-17 20:01:42 +03:00
overview.md feat: companion server, FFI cleanup, and pre-release hardening 2026-06-17 20:01:42 +03:00
robustness-plan.md docs: mark §11 (desktop JSON tax) resolved after verifying fluxa-desktop 2026-07-07 15:10:23 +03:00