Bind the undo provider to the board, not the tier

The 2026-07-31 re-ruling: gitless boards bind the native stack in every tier — a Pro upgrade no longer removes undo from mode-none boards — and Pro git boards bind the git provider; repo-nested stays the no-undo case under Pro, while the free tier (which never runs detection) binds native there too, per 12's inert posture. Add-git now swaps a live native substrate mid-session: the in-flight stack is cleared with the discarded provider, the git trail seeds from the root commit, and the same BoardUndoManager instance keeps nil-target menu validation fresh. 2405 tests in 413 suites green. Claude-Session: https://claude.ai/code/session_01CqjXB7ASoWtbyoGod68k97
2026-07-31 18:53:38 -04:00
parent 3bd6187b94
commit 2e4dde5655
9 changed files with 286 additions and 104 deletions
@@ -23,8 +23,11 @@ public enum Tier: String, Sendable, Equatable, Codable, CaseIterable {
    /// existing at all.
    case free

-    /// Lanework Pro — an active auto-renewable subscription. Binds the git history provider when
-    /// pro-m1 builds it (06-history-undo.md, 07-sync-collab.md).
+    /// Lanework Pro — an active auto-renewable subscription. It is what puts git on the table; which
+    /// substrate a given board then binds is the *board's* answer, not this case's (re-ruled
+    /// 2026-07-31 — `AppModel.makeHistoryProvider`): the git provider on a git board
+    /// (06-history-undo.md, 07-sync-collab.md), the same native stack the free tier uses on a gitless
+    /// one, nothing on a repo-nested one.
    case pro
 }