report-assemblylisted

# Report Assembly Turn the accumulated workfile into a report draft the appraiser finalizes in their form software. This produces **section-by-section content**, not the delivered XML — it's the writing layer. ## Preconditions Check the job folder. If `field-notes.md`, `discrepancies.md`, or `comps.md` are missing or have unresolved `MATERIAL` items, list them and ask whether to proceed with placeholders (each placeholder becomes a `VERIFY:` block in the draft). ## Steps 1. Load `references/urar-uad36-outline.md` for the section map (and legacy mapping if the client requires an old form during the transition window — confirm from `intake.md`). 2. Draft `report-draft.md` section by section, pulling only from job-folder sources and citing the source file for each fact (`[field-notes]`, `[tax-card]`, `[deed]`…). If a file tool refuses the `report-draft.md` filename on a content heuristic, write it via shell to the same path — do not rename the file; the job-folder convention is fixed. Sections: - Subject & assignment (from intake — client, intended use/users, effective date) - Contract analysis (purchase assignments) - Neighborhood / market area description and trends — **fair-housing-safe language only** - Site (from field notes + state module items: zoning & overlays, flood, well/septic, road/access, waterfront) - Improvements (room-by-room from field notes; C/Q ratings as confirmed; mechanicals ages and update timeframes from `mechani