resume anchor: next-session order (phone federation test, auxo/chatty), fresh artifact note

STATE.md

@@ -14,9 +14,37 @@ Last updated: 2026-07-16 (evening — system tier / machined).
 ## Component repos
 
 ### souveraine (`~/Projects/souveraine`)
-Branch `experimental/session-trust-phase1` @ `8e540c7`.
-- Verified on archdev 2026-07-16: 295+8 tests, clippy `-D warnings`, aarch64
-  cross build (both `souveraine` and `souveraine-machined` ELF aarch64).
+Branch `experimental/session-trust-phase1` @ `c96f95b`.
+- Verified on archdev 2026-07-16: 295+8 tests, clippy `-D warnings`. Fresh
+  aarch64 cross build of `c96f95b` kicked on archdev end of session —
+  artifacts land in
+  `~/.cache/souveraine-ci-target/aarch64-unknown-linux-gnu/release/`
+  (`souveraine` + `souveraine-machined`); build tree
+  `~/builds/machined-verify/Souveraine`, log check: `file` output at the
+  end confirms both are ELF aarch64. The PREVIOUS staged artifact was
+  `116562a` — pre-`memory sync` — do not deploy that one for the
+  federation test.
+
+## NEXT SESSION (Casey's stated order, 2026-07-16 evening)
+1. **Souveraine phone-side test** — get phone AND laptop on the fresh
+   `c96f95b` build, then test agent transfer between them. The phone's
+   agent memfs is MORE UP TO DATE than the laptop's — phone is source of
+   truth; never clobber it. Sequence per FEDERATION.md: provision machined
+   on both (`sudo souveraine machine init --migrate-from
+   ~/.souveraine/seed-id` + enable `packaging/souveraine-machined.service`,
+   sysusers), provision one bare memfs remote on Gitea for the agent,
+   `git -C <memfs> remote add origin <url>` on both, `memory sync` both
+   sides, verify two `instance/*` branches on the remote. Merge policy
+   (step 3) is NOT built — first test is push/fetch + branch visibility,
+   not reconciliation.
+2. **Auxo tray + Chatty**. Auxo-style multitasking tray under the dock —
+   design first (talks only so far). Chatty: Casey says "the contacts app
+   is still needed to land so matrix can stay logged in" — the two open
+   pieces in that area are the qtpim contacts direction
+   (docs/qtpim-contacts-handoff.md, three paths, undecided) and
+   souveraine-secrets as the libsecret backend Chatty/libcmatrix need for
+   token persistence (committed, never build-verified). Confirm with Casey
+   which dependency he means before building.
 - Federation memory transport, first two steps landed (`8cfa992`,
   `a62379a`): `memfs_commit` presence signal on the bus after every memfs
   mutation (replaces the unconsumed `memory_*` events), and `memory sync` —