Constant FOREIGN_OWNER_PATIENCE 

pub const FOREIGN_OWNER_PATIENCE: Duration;

How long an owner of another PID namespace counts as alive, measured from when its record was written. A commit or a lock hold lasts seconds to minutes; a crashed foreign owner stops blocking after this long. Three kinds of record are judged by this age. A merge’s intent record (merge_isolation_journal.rs, write_merge_intent, written once and synced per merge) and a claim file (single_owner_claim.rs, write_private, written once) are not rewritten while the owner works, so the age is the owner’s whole hold; the item path of a worktree add is judged by its own modification time (worktree_copy_owner.rs, is_alive), which the add’s work can move, so its age is at most the add’s length. The patience must outlast the longest such hold. Basis: twice LOCK_CEILING (10 minutes, wait_ceilings.rs), the longest a merge waits for a foreign index.lock with its record already written, so 20 minutes. It is derived, not written as a number, so the two cannot drift apart again: it was an hour because it was twice the 30 minute live lock wait of wait_limit.rs, a file that no longer exists, and the owner’s rule (2026-11-03, “nothing should ever wait forever or indefinitely”) bounded that wait at LOCK_CEILING. Measured: the longest worktree add in the add timing log (79 adds, 2026-11-03T08:55:46Z to 2026-11-04T13:53:17Z, totalMs) took 539.7 s and the longest commit in the commit timing log (1,838 commits to 2026-11-04T14:08:47Z) 750.6 s, so the patience is 1.6 times the longest command measured and 2.2 times the longest add. The logs hold commands of the host’s own PID namespace, so no foreign-namespace hold was observed directly. If LOCK_CEILING changes, this value follows it; revisit the margin then (doc/planning/cli-git-shipped-limits-audit.md, “Foreign-owner patience”).