Require explicit property assessor purpose per request

docs/property-assessor.md

@@ -71,6 +71,7 @@ Current behavior:
 
 - starts from the address
 - requires an assessment purpose for decision-grade analysis
+- does not assume the assessment purpose from prior thread context unless the user explicitly says the purpose is unchanged
 - automatically runs public-record / appraisal-district lookup
 - automatically tries to discover Zillow and HAR listing URLs from the address when no listing URL is provided
 - runs Zillow photo extraction first, then HAR as fallback when available

skills/property-assessor/SKILL.md

@@ -16,6 +16,9 @@ Accept any of:
 
 The assessment purpose is required for a decision-grade result.
 If the user does not say why they want the property assessed, stop and ask before finalizing the analysis.
+Do not silently infer or reuse the assessment purpose from earlier turns just because the property address is the same.
+Only reuse a prior purpose when the user explicitly says it is the same purpose as before.
+If the current request includes only the property/address plus email or PDF instructions, treat the assessment purpose as missing and ask again.
 
 If the property has a unit / apartment / suite number, include it.
 Do not drop the unit when discovering listing sources. Unit-qualified condo/townhome addresses must be matched as the exact unit, while single-family addresses with no unit should still work normally.
@@ -89,6 +92,7 @@ scripts/property-assessor render-report --input "<report-payload-json>" --output
 
 `assess` is the address-first entrypoint. It should:
 - require the assessment purpose
+- treat the assessment purpose as missing unless it is present in the current request or explicitly confirmed as unchanged from earlier context
 - resolve official public-record jurisdiction automatically from the address
 - try to discover Zillow and HAR listing URLs from the address when no listing URL is provided
 - run the approval-safe Zillow/HAR photo extractor chain automatically