Require property assessor follow-through after preliminary helper

docs/property-assessor.md

@@ -60,6 +60,12 @@ Default operating sequence:
 7. Underwrite carry costs and risk factors.
 8. Render the final report as a fixed-template PDF.
 
+Operational rule:
+
+- The helper returning a preliminary payload is not the end of the job.
+- For a user request that clearly asks for a full assessment or PDF delivery, the agent is expected to continue the missing analysis after the helper returns.
+- Preliminary helper output should be treated as structured scaffolding for the remaining work, not as a reason to stop and wait for another user nudge.
+
 ### `assess`
 
 ```bash
@@ -82,6 +88,12 @@ Current behavior:
 - does not render/send the PDF from a preliminary helper payload with `decision: pending`
 - only renders the fixed-template PDF after a decision-grade verdict and fair-value range are actually present
 
+Expected agent behavior:
+
+- if the user asked for the full assessment, continue beyond the preliminary helper output
+- fill the remaining gaps with listing facts, comp work, condition interpretation, and valuation logic
+- only stop early when there is a real blocker, not merely because the helper stopped at a checkpoint
+
 Important limitation:
 
 - this implementation now wires the address-first intake, purpose-aware framing, public-record lookup, listing discovery, and photo-source extraction