Home app-side state in the shared App Group container

Every edition declares group.dev.rzen.indie.Kanban and homes its
app-side state there from day one (12-editions.md ruling 2026-07-29):

- AppGroup namespace: container resolution with per-edition fallback
  when unprovisioned, shared UserDefaults suite, edition identity, and
  a unit-test-host redirect (the test host IS the app — its launch
  sweep and recents refresh must not touch the real shared container).
- BoardRecord: bookmark/isOpenNow replaced by per-edition grants and
  openNow keyed by bundle id; hand-written Codable keeps legacy keys
  decoding (adopted in memory as the running edition's slots, upgraded
  on first save); every other field stays common.
- RecentBoard gains needsReopen: no grant of ours but somebody's —
  first click runs an open panel pre-anchored at the recorded path,
  prompt "Grant"; recordOpen mints this edition's slot onto the
  matched shared record (path fallback only after identity fails and
  only against records holding no grant of ours, so re-granting never
  forks the record).
- Cross-edition freshness: stat-cheap mtime+size stamp re-reads the
  registry when the sibling edition wrote it, so one edition's save
  never erases the other's records wholesale.
- restorables() filters on this edition's open-now flags; the board
  popover gains BoardEditionPresence ("Also open in Lanework Pro"),
  pid-liveness-checked so crash residue never lies.
- Clipboard staging store moves to the group container; the sweep
  claims doomed trees by atomic rename into .sweeping/ then deletes,
  so the sibling's concurrent sweep is a non-event.
- Template store re-homed to the group container per the 09-templates
  re-ruling; scalars (quick-style recents, window size) move to the
  shared suite.
- verify-editions.sh: 30 checks (each edition carries exactly the
  family group). No pathfinder 1.x migrator: 1.x predates the
  registry; state starts fresh in the group container.

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

Kanban/App/RestoreBootstrapView.swift

@@ -92,6 +92,17 @@ struct RestoreBootstrapView: View {
                     path: record.lastKnownPath,
                     message: "This board is unavailable. Its volume may be offline, or it may have been moved or deleted."
                 )
+            case .needsReopen:
+                // Effectively unreachable — this edition can only have flagged a board open by having
+                // opened it, which needed a grant — and deliberately quiet if it ever happens.
+                //
+                // **No launch failure and no panel.** A modal grant panel at launch is exactly the
+                // "launch-time modal chain" 02 § Launch and window lifecycle rules out, and a failure
+                // row would put fail-fast's warning tone over a board that is *fine*: welcome appears
+                // (nothing restored), and this board's own row already carries the re-grant caption
+                // and the one click that resolves it (12-editions.md ▸ Distribution). That row is the
+                // surface, so nothing is silently dropped.
+                Self.logger.error("a flagged board is awaiting this edition's grant; left for its welcome row")
             }
         }