SHA256
Replace current wrapper claims with native architecture/security/build evidence, preserve historical documents, track all thirty pages and explicit release gates, correct brand attribution and provide the twelve-section delivery report without claiming completion. Native signing remains paused and Apple application/device validation outstanding.
23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
# Changelog
|
|
|
|
## [Unreleased]
|
|
|
|
- Begin the genuine native rebuild: Compose/SwiftUI screens, direct HTTPS API,
|
|
protected native session storage and initial auth/dashboard/task/note/shopping
|
|
flows. Archive the rejected WebView renderer and its tests. Full PWA parity is
|
|
explicitly incomplete; see `docs/native-parity.md`.
|
|
|
|
- Gitea workflows for the maintainer's Ubuntu pool and native M4 Pro runner,
|
|
explicit SDK/KVM prerequisites, SHA-256 checkout and unsigned-only CI release builds.
|
|
|
|
- Native Android HTTPS onboarding, origin-bound browsing, session persistence,
|
|
recovery, server erasure, camera/document selection, downloads and blob exports.
|
|
- SwiftUI/WKWebView iOS implementation, isolated web sign-in, native settings,
|
|
recovery, file export, and strict URL/metadata policies; Xcode validation pending.
|
|
- JVM, Android emulator, portable Swift, and real pinned-upstream HTTPS tests.
|
|
- Reproducible build configuration, CI and maintainer-controlled release procedures.
|
|
- MIT licensing, upstream audit, security model and release documentation.
|
|
|
|
No stable release has been published. No native push or browser-to-app session
|
|
handoff is claimed. See validation records for what has actually been executed.
|