docs(phase-1): cold-start handoff plan for the desktop track
Adds tools/DESKTOP_PHASE_PLAN.md: everything a fresh session needs with no prior context — current module shape, the exact commands that must stay green, pinned versions, the invariants (tracked ObjectBox model file, the objectbox-android / objectbox-java classpath rule, kapt and Compose Desktop plugin quirks), the traps already paid for, and the M2/M3/M4/M5 milestones with exit criteria. Every claim is checked against the working tree rather than remembered: the coupling inventory (per-file android.* import counts), the 8 DataStore keys, AesGcmFieldCipher's single getOrCreateKey() call, the portability of BackupCodec/EncryptedBackupCodec, and the pinned versions (Kotlin 2.0.21, AGP 8.7.2, Compose Multiplatform 1.7.3, ObjectBox 4.0.3). Open questions are marked as such rather than guessed — the JVM EXIF decoder and OS-keyring libraries are unverified, and the AGP/KMP friction around the composeApp conversion is called out as the least-known part of M4, with a fallback shape and a time-boxed decision rule.
This commit is contained in:
1 parent
5f45b0921b
commit
b11c02e1b4
2 files changed
+246
No files matched your search
@@ -1,5 +1,8 @@
|
||||
# Desktop feasibility spike (Phase 0) — findings
|
||||
|
||||
> The forward plan — remaining Phase-1 milestones, invariants and traps —
|
||||
> lives in `tools/DESKTOP_PHASE_PLAN.md`, written as a cold-start handoff.
|
||||
|
||||
Branch `spike/desktop-feasibility`. Throwaway code lives in `spike/` and is
|
||||
**not** wired into the Android build: `settings.gradle.kts` only gained two
|
||||
`include()` lines and `gradle/libs.versions.toml` four entries. Nothing under
|
||||
|
||||
Reference in new issue
Block a user