docs(phase-1/m4.3): M4.3 status + §1 gate output; plan handed to M4.4

Also two new §3 traps paid for during the gate re-run: daemon-surviving
desktop JVMs after a client kill (use pkill -9 before re-running against
the same data dir), and never parallelizing two --data-dir runs (leg B
against leg A's half-written library produces bogus FAILs).
This commit is contained in:
Incido Developer committed 2026-10-06 16:44:39 +13:00
1 parent 59bd6e106b
commit 31408172df
2 files changed
+77 -9

No files matched your search

+9
View File
@@ -98,6 +98,15 @@ app version `0.4.2.0` (code 38).
* PBKDF2 200k iterations ≈ **55 ms** on desktop versus ~2 s on the phone.
* The jpackage launcher prints `pure virtual method called` on stderr when the
app exits via `exitProcess`; harmless.
* Killing the gradle client of a wedged `:desktopApp:run` does NOT kill the
app — the JavaExec child runs under the daemon. `pkill -f org.incido.desktop.MainKt`
(TERM can be ignored by a wedged AWT JVM — use `-9`) before re-running against
the same data dir, or ObjectBox's single-writer lock and DataStore's file lock
will wedge the next run too.
* Never batch the crypto legs (or any two `--data-dir` runs) in one parallel
command group — leg B opening the library leg A is still writing produces
bogus FAIL lines and a corrupt-on-paper result. Sequential, separate processes,
fresh dir first.
## 4. M2 — the backup bridge (next up; the product's reason to exist)