The board chooses where it lives — swipe-open settings move it between iCloud and this iPhone

A trailing swipe on a board row opens Board Settings, whose first setting is location: iCloud or Local, with a confirmed move to the other side — destructive-styled only outbound, because leaving iCloud is the direction that sheds protection. The move is setUbiquitous against the real container and a coordinated move under the DEBUG stand-in; evacuation sweeps materialization first and refuses honestly while content is still downloading. The local home is the sandbox Documents folder, published to the Files app, so a local board is still a folder the user owns.

With a second home the iCloud wall softens (user-ruled 2026-08-08): the index always reaches ready, cloud unavailability becomes an inline notice with a retry, creates land locally when there is no account, and LANEWORK_FORCE_NO_ICLOUD makes that state reproducible in tests regardless of the machine's sign-in. Known gap, now user-reachable: backup remains iCloud-only, so local boards sit outside it.

Claude-Session: https://claude.ai/code/session_01SR4XGjmBE16ZUYWpfFHXwY

KanbanMobile/Info.plist

@@ -33,6 +33,13 @@
 	     (MobileApp.swift) relies on. -->
 	<key>LSSupportsOpeningDocumentsInPlace</key>
 	<true/>
+	<!-- Publishes the sandbox's Documents/ as "On My iPhone ▸ Lanework" in the Files app — the
+	     device home (`DeviceHomeResolver`), which is where a board that is not in iCloud lives.
+	     Without this a local board would be a real board the user could not reach, back up by
+	     hand, or move off the phone any way except through this app, which is not what "local"
+	     is allowed to mean here. -->
+	<key>UIFileSharingEnabled</key>
+	<true/>
 	<!-- Same document-type + UTI declaration as the Mac app's Info.plist, and it must stay
 	     byte-identical in meaning: the package conformance is what makes NSMetadataQuery and the
 	     Files app treat a `.kanban` directory as one document instead of a folder of loose files.