7.2 — Offline draft persistence (NARROW SCOPE)

[tessak22]

Summary

The completion form must survive poor rural signal — save a local draft as Jeff types, sync on reconnect. Nothing more.

Spec references

• §10b (Offline / poor-signal resilience) — binding, including the scope limit.

Acceptance criteria

• The completion form persists a local draft as Jeff types and syncs when connectivity returns.
• Scope limit (do NOT over-build): this form ONLY. No offline booking, no offline record browsing, no general offline mode, no sync-conflict resolution engine.
• The rest of the app assumes connectivity.

Mobile behavior

• Draft survives app backgrounding / connection drop mid-entry; clear "saved locally / synced" indicator.

Tests

• Draft restored after simulated reload with no network.
• Draft flushes to server on reconnect exactly once.

Definition of done

Local draft + sync for the completion form only; explicitly not offline-first architecture.

OPEN QUESTIONS

• Storage mechanism (IndexedDB/localStorage) is left to implementer; must be robust to reloads. Confirm none needed beyond that.