feat: share village needs with helpers

docs/ARCHITECTURE_OVERVIEW.md

@@ -38,7 +38,8 @@ would otherwise obscure that lifecycle:
 - `simulation/knowledge/EventKnowledgeSystem.gd` owns per-NPC references to
   known objective events, immutable acquisition provenance, proximity witnesses
   at record time, one-hop direct fact transfer, and deterministic recent-fact
-  retention/importance ranking;
+  retention/importance ranking. It can place the active opportunity trigger
+  first without weakening its direct-source or one-hop checks;
 - `simulation/relationships/RelationshipSystem.gd` owns directed relationship
   queries, event-driven trust changes, and deterministic social tie-breaking;
 - `simulation/opportunities/VillageOpportunitySystem.gd` observes immutable
@@ -96,8 +97,10 @@ improving ownership.
   retained knowledge. Opportunity presentation is likewise query-only.
   Relationship cues, interested-villager concern, physical pantry stock, and
   refill feedback consume authoritative state or state-change signals and are
-  intentionally absent from saves and checksums. Stable visuals are rebuilt
-  from state after restore; transient reactions are not replayed.
+  intentionally absent from saves and checksums. The transient village-whisper
+  HUD likewise formats need, transfer, response, and resolution signals without
+  owning them. Stable visuals are rebuilt from state after restore; transient
+  reactions are not replayed.
 - Resource changes go through `ResourceStateRecord`, NPC inventory, and
   `VillageEconomy`; `village.food` and `village.wood` are synchronized views.
 - New mutable features define serialization and deterministic continuation at