[Feature]: [P3] Condo stickiness design fork remainder (satisfaction as value vs flight risk)

Imported from the engineering backlog (_bmad-output/implementation-artifacts/backlog.md, story condo-eviction).
Priority P3 (do-first order) | Severity: n/a | Status: partial | Epic: Modern condos | Type: feature-request | Recorded: 2026-07-06

Problem / motivation

Flavor (b) SHIPPED (v1.12.0): household-aware condo departures. Spec: gdd-condo-household-departures-2026-07-08.md (party-ratified). A sold Modern condo's household can relocate on a monthly roll (GameRules.condoRelocationChance(residents), scaled up with family size; Classic returns 0 and never rolls, RNG stream byte-identical); it enters a non-rescindable "relocation" notice and rides the existing buy-back at householdPrice (a self-scaling anti-trivialization sink: you reclaim 4s/5s while re-sales regress toward the mean 3, and the vacant unit bleeds hold-tax + overhead). Party (Samus/Cloud/Winston, 2026-07-08) chose reuse-the-buy-back over free turnover (a faucet). STILL PARKED (own specs before build): (a) player-initiated evict/buy-out (owner pays to reclaim a sold condo; the 1994 game had no condo evict); (c) relocation offer (offer a departing household a different empty condo before the forced buy-back).

Start with _bmad-output/implementation-artifacts/backlog.md and the condo-eviction story, then read gdd-condo-household-departures-2026-07-08.md. The issue lists player-initiated evict/buy-out and relocation offer as parked alternatives, but does not identify an implementation entry point, tests, or a selected scope. Done criteria therefore need to be established before coding.