chore(phase-1/m4.5c): delete spike modules; record M4.4/M4.5 findings
6.6 executed: :spike:data-jvm and :spike:compose-jvm leave the build now that :desktopApp hosts the real screens (M4.5b) — everything they proved has a permanent home in :core:data-jvm, :composeApp (jvm) and :desktopApp; their findings already live in the feasibility log. tools/DESKTOP_FEASIBILITY.md gains the M4.4a-e + M4.5a-c entries: seam inventory (image decode, editor intake, voice slot, platform back, shared settings sections, JVM EXIF), the hide-not-fake §6.5 rulings applied, the harness note about cold-build run timeouts, the M4.4/M4.5 verification suite, and the M5 next-up. Verified post-deletion: assembleDebug :desktopApp:build SUCCESSFUL + run --self-test --settings-smoke --editor-smoke (SELFTEST id=1, SETTINGS shown, EDITOR shown, ST_EXIT=0) + :core:data-jvm:smoke (M1a PASS) + orientationSmoke (M4.4e PASS).
This commit is contained in:
1 parent
cce35587fc
commit
faab0cde98
19 files changed
+77
-1575
No files matched your search
+5
-7
@@ -49,10 +49,8 @@ include(":core:backup")
|
||||
// both producing the same `.preferences_pb` format, same keys.
|
||||
include(":core:settings")
|
||||
|
||||
// --- Desktop feasibility spike (Development Plan §6.3, throwaway) ---
|
||||
// Throwaway probes that answer "can the existing stack run on the JVM"
|
||||
// before any of Phases 1-6 are committed to. They are additive: no module
|
||||
// above is touched, and nothing outside `spike/` depends on them.
|
||||
// See tools/DESKTOP_FEASIBILITY.md for the findings + how to delete these.
|
||||
include(":spike:data-jvm")
|
||||
include(":spike:compose-jvm")
|
||||
// --- (Phase 1, M4.5) The Phase-0 spike modules :spike:data-jvm and
|
||||
// :spike:compose-jvm are GONE (§6.6): everything they proved now lives in
|
||||
// :core:data-jvm, :composeApp (jvm target) and :desktopApp, and the real
|
||||
// screens have been hosted since M4.5b — the spike's reason to exist
|
||||
// expired. Its findings live on in tools/DESKTOP_FEASIBILITY.md.
|
||||
Reference in new issue
Block a user