feat: surface open opportunity need on villager field note

docs/BUILD_IN_PUBLIC_PLAN.md

@@ -841,10 +841,20 @@ Next:
 
 1. Let an inspected villager who owns an open opportunity surface that exact
    village need plus the authoritative direct-help route, capable helper, or
-   honest unavailable state that currently exists.
+   honest unavailable state that currently exists. **Complete:** the quiet
+   `VillagerFieldNoteHud` now shows a restrained `Need` line for exactly that
+   note, derived from the existing player-response/helper queries and the real
+   storage state. It names the helper when one is capable, shows the direct
+   finite-resource-to-storage route when the player response derives it, or
+   honestly states why help is unavailable, and it re-derives from live facts
+   after restore without entering saves.
 2. Prove that the ordinary finite-resource-to-storage harvest resolves an
    available player route and updates the context without dialogue branching,
    acceptance state, rewards, a quest log, or saved presentation state.
+   **Complete:** a runtime scenario stages the real pantry crisis, surfaces the
+   need for its interested villager, and proves that one ordinary
+   `harvest_resource_node` extraction resolves the same open opportunity and
+   clears the need segment on the next refresh.
 
 Do not start with GIS data, a full city, a large asset pack, or more NPC
 mechanics. The next proof is a beautiful stage for the systems that already