CORRECTION from hertz/operator: plain `spt rc <id>` refusing an already-controlled endpoint is expected UX; explicit `--take` is the opt-in displacement operation. My v0.38 field FAIL incorrectly treated the internal same-by newer-generation recovery ladder as a requirement for a separate user-initiated plain rc viewport. The observed preflight guidance is correct unless a distinct requirement explicitly says same-node terminals bypass `--take`. Please reclassify that leg PASS/NOT-APPLICABLE and reassess REQ-DRIVEN-BY-OWN-NODE-NORMALIZE: own-node normalization must not make an ordinary second local rc silently or loudly steal control. Zombie/restart recovery should use same-lease/equal-generation or a qualified internal path, not change plain user Control semantics.