Repository navigation
Sutoriraita v0.0.1 pre-alpha
Pre-releaseSutōrīraitā v0.0.1 pre-alpha
This is an early pre-alpha. Expect bugs and keep independent backups, especially on macOS and iOS, which have not had interactive device testing in this release session.
- Android Open Folder now uses persisted Storage Access Framework grants and content-URI reads/writes, including recovery copies and portable export.
- Open Project uses the system picker for packed .sutoriraita ZIPs and creates independent editable library copies. The source archive is never rewritten by autosave.
- Native document launches are wired on Android, iOS and macOS; Windows/Linux accept system launch filenames and include registration scripts.
- Archive validation checks paths, duplicate names, sizes, format versions and checksums.
- Creation, save/reopen, recovery, import/export, and project-format behavior are covered by the regression suite.
Windows: extract the whole ZIP to a permanent folder and run register.ps1 to register the format for your user.
Linux: extract the tar.gz and run sh install.sh to register the bundle at that location.
Android: APK is signed with a development key for sideload testing, not Play Store distribution. Its key can differ from earlier/local builds, preventing an in-place upgrade. Back up projects before any uninstall, which removes app-private data.
macOS: app is unnotarized and has no Developer ID distribution signing.
iOS: unsigned .app archive only; Apple signing/provisioning is required to install it. This is not a signed IPA.
See BUILDING.md for prerequisites, signing requirements and the manual platform checklist. Native provider/picker UI flows still need device testing. Windows/Linux external opens use a new app instance; avoid simultaneous editing of one live folder.
Verification: CI run 33295809177 passed analysis, all 28 tests and native release builds for Windows, macOS, Linux, Android and unsigned iOS. These binaries were built from application commit 3f0c72b3528e954dd492ff26d70ba5bab7538c9f; later release preparation changes only documentation and the manual asset-staging workflow, not application code. SHA256SUMS accompanies the downloads.