[mobile] T054: Seam tests on real adapters: pull pipeline → SQLite rows → NoteContentStore round-trip; conformance suite (T023) green against the mobile adapters

[h4yfans]

Memry Mobile — Vault Parity Mobile App · task T054 · Phase 3 of 14 · gate G2 · story US1

Task

T054 — Seam tests on real adapters: pull pipeline → SQLite rows → NoteContentStore round-trip; conformance suite (T023) green against the mobile adapters

Files: apps/mobile/src/sync/__tests__/pull-pipeline.test.ts

Recorded state / notes from tasks.md

code landed: on-device harness src/sync/__harness__/us1-seam-harness.ts runs the shared conformance suite against the REAL mobile adapters (injected describe/it/expect, fresh scratch vault per test) plus a live pull→SQLite→NoteContentStore round-trip; dev runner screen (dev)/seam-tests.tsx. OPEN: the on-device run itself — needs the reference device

Phase context — Phase 3: User Story 1 — Open Your Vault on Your Phone (P1) 🎯 MVP — Train Phase 2 (Gate G2)

Goal: Existing user signs in, unlocks with password or recovery phrase,
browses their real vault read-only; production-safety kit verified end-to-end.

Independent Test (spec US1): on a phone that has never seen a real
desktop-created vault, sign in, unlock via password and separately via recovery
phrase, browse recent content. Standalone value: read-only companion.

Checkpoint — G2: all four drills green. This is the MVP: a trustworthy read-only companion on the developer's own device.

Ordering & dependencies

• Train gates are serial (Constitution): a phase does not start until the prior gate is green with evidence. Parallelism exists within a phase only.
• US1 depends on Phases 1–2 only. Within this phase: adapter tasks T037, T038, T039, T042 run in parallel after T033; T034 and T035 run in parallel.
• Feeds gate G2 — verification steps in quickstart.md §Phase 2 — G2.

Definition of done

• Constitution definition of done: pnpm lint, pnpm typecheck, tests, pnpm check:architecture, pnpm check:contracts, plus docs where the change is user-visible.
• No check-off without green evidence (Constitution III). Paste the evidence into this issue before closing.
• Backward compatibility is mandatory — real users run this on real data. Schema/contract/format changes need a stated migration + compat plan.

References

• tasks.md — full task list and the dependency graph
• spec.md · plan.md (§Release Train) · research.md
• data-model.md · contracts/ · quickstart.md
• .specify/memory/constitution.md

[h4yfans]

T054 evidence (Constitution III):

• On-device seam run, reference device iPhone 12 Pro against staging: conformance 26/26 PASS, pull round-trip 6/6 PASS, metadata-only items 0, corrupt-marked items 0 — seam-tests screen, clean table (2026-08-26 21:23 screenshot, also attached to the G2 evidence PR trail).
• First on-device green run 2026-08-24 (26/26 + 6/6) after the first-sync fixes fix(mobile): serialize sync pipelines; first sync resumes past unpullable items #1817 / fix(mobile): prepared statements for batch apply — 100-item chunks no longer crash expo-sqlite #1822 / fix(sync-client): hard 60s timeout on every pull request #1823 / fix(mobile): note_bodies.path is not unique — a title collision no longer kills the apply batch #1826; simulator closure evidence same day.
• Re-verified 2026-08-26/27 against the post-perf(sync): batch CRDT snapshot pushes so seeding stops paying per-note round trips #1858 server (batched CRDT snapshot push) after a full staging reset + device wipe + fresh first sync, including a 10,000-item vault first sync (list browsable ≤2 min, resumable across kill+relaunch, nothing stuck).

Full trail in draft PR #1827 (mobile-g2-evidence).