PvZ 2-10 house protection in conversations

The finale temporarily suppresses home-entry defeat. Previously its live AI context contained dialogue receipts but no current loss-rule observation. A past promise could therefore be mistaken for continuing protection after the house was repaired.

The game now reads the saved native homeLineEnabled flag as houseEntryProtected. The browser forwards it only for an active source 40159/level 20 board with matching epoch and the source210-house-v1 capability. Old hosts receive no new field; old clients and missing observations remain supported. The shared schema rejects other chapters, ended lawns and non-booleans.

Dave and living mushrooms receive the same current rule. Their context distinguishes temporary boundary protection from plant damage and victory, and does not supply or invent a remaining timer. A repaired house does not restore mowers. The observation is not persisted as a lasting memory and grants no action authority. Account models, saves, billing, combat, difficulty, dialogue pauses and artwork are unchanged.

Evidence

• 516 game-NPC tests pass, including the new current/old/malformed/ended/chapter-isolation and living-plant cases. The first test run had an incorrect test import; the next run reproduced schema/context rejection. A subsequent fixture needed its existing text-only species marker, and a wording assertion needed case-insensitive matching. All failures remain in output/finale-house-*.
• 743 game web/package checks pass.
• 66 compiled native checks pass, including actual scheduled house destruction, pause-frozen repair callbacks, save/reload before and after repair, no mower replacement, all 17 wave allocations, boss callbacks and the single trophy transition to level 21. Ordinary enemies are cleared in this native audit; it is not a natural victory or balance proof.
• Full hosted build/typecheck and OSS export verification pass. Compiled EN/ZH browser and publication receipts are retained in the game worktree under output/finale-house/. Public status is tracked there in docs/public-launch-current.md.

No fresh provider-writing evaluation or physical-phone result is claimed by these checks.