docs: capture player standing and quest system in plans and schema

docs/BUILD_IN_PUBLIC_PLAN.md

@@ -855,6 +855,15 @@ Next:
    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.
+3. Give the player a reason to keep helping: a persistent **Standing** loop.
+   **Complete:** resolving real village needs (pantry, wood, hungry animals)
+   now grants Standing (Stranger → Known Hand → Trusted → Village Steward →
+   Voice of Jajce) and raises the requester's gratitude. The world's quest
+   generator turns each open need into a named player quest in a quiet
+   `QuestJournalHud`, and villagers who personally trust the player start
+   asking them directly even when another helper could act. All of it flows
+   through the ordinary finite-resource harvest/feed contracts, survives
+   save/restore deterministically, and adds no quest-only state.
 
 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