PAF becomes saf/device (history kept), STATE.md dissolves
into saf/state.md with the dated era archived, the substrate
SAF moves up from souveraine, and every agreement points at
saf/INDEX.md and nowhere else. one map, nothing to remember
DEVICE-STATE-MACHINE §0: the audit, in the doc rather than a new task file.
Lock shadow copy found and fixed (doctrine §4). Two open: proximity has no
debounce and thrashed 69 transitions in 40min (§9.5 already specifies the fix),
and forensic.jsonl sits on tmpfs — RAM, wiped on reboot, unbounded.
TASK-26 was never written and no longer needs to be: the proximity second
authority is resolved, packaging is TASK-27. Dangling refs in STATE.md,
TASK-25 and TASK-27 now say that instead of pointing at a missing file.
Scoped from what was measured today. The finding that matters: rootfs-overlay
is not a package, so overlay fixes reach a running phone only via reprovision
— which costs Casey his live system. Two fixes are already stuck behind it.
Also recorded: there is no `primary` branch despite ci.yml triggering on it
(public is the de facto release branch, proven by the phone's installed
package matching public's head); kernel.yml's fourth blocker, the
config-blueline move that breaks PKGBUILD:53; and that the archdev aarch64
sysroot was half-updated and silently lies about which ABI a cross build
targeted, which makes every recent cross-built artifact suspect.
