Ghost FTP 0.99.24 — client-only cleanup (Preview)

Previous public edition: v0.99.23. This is a development Preview. It is not verified production/stable software.

Removed from active source and distribution

• Independent Ghost FTP Server (Windows and Linux daemon, Control Center, service installers and server workflow).
• Ghost FTP Demo application, bundled UI and package artifacts.
• Ghost CLI, separate installer, CLI Rust workspace member, related build, release and test packaging.
• Obsolete desktop shell PATH integration and standalone CLI-based sync-script export controls.

All historical releases/tags and existing users' files, credentials and installed external services remain untouched. Deleting active source does not itself uninstall old versions from any operating system. The graphical Ghost FTP client retains its existing Rust FTP/FTPS/SFTP engine and platform-specific transfer capabilities.

Packaging

• Require 25 nonempty public release artifacts, including Windows portable/NSIS/MSI and QA, Linux ELF/AppImage/DEB/RPM/tarball, Android Preview packages, macOS ARM64 and Intel packages, source and documentation archives, and SHA-256 sums.
• All files must come from the immutable merged source SHA, and the publish workflow must verify local and remote SHA-256 digests. Optional signed-updater assets must be complete if present.
• The previous public v0.99.23 tag and its contents remain immutable.

Acceptance restrictions

• The client is Tauri 2 on Windows/Linux (system WebView). The separate native SwiftUI macOS client still has unimplemented or deliberately blocked FTPS/SFTP transports pending identity-verification tests. Do not claim feature parity across OSs.
• CI code-quality, actual protocol E2E, Android, Windows hardening, macOS builds, installer lifecycle, conservative dead-code inventory and source security checks must complete on the exact final HEAD before merge/publication.
• Production readiness still requires verified Authenticode, Android Play signing and safe upgrade, macOS Developer ID notarization, credential persistence and recovery, real-device UI/UX/performance, and security acceptance. Until verified, the stable release channel intentionally remains blocked.