pvsyst_run_house_task
Runs an AI-authored residential PV project through PVsyst using a bound northern-site template, verifies mesh and PV regions, then performs annual simulation with guarded artifacts.
Instructions
[Simulation] Deliver one AI-authored residential project through existing native entries. Source must be the existing bounded fixed PV-only northern-site template, with identical bound workspace SIT/MET in PRJ/VC. Hardware/counts/angles/losses, source engineering defaults and weather remain inherited and disclosed, never sized or guessed. AI supplies a complete mesh house and one/two placed PV regions in spec; all module counts/source-PAN metadata and native8.1.6CN/DPI96 boundaries remain. Two source orientations require one explicitly named region per orientation1/2, the same PAN/OND, anchor azimuth zero and distinct source planes. Native table properties assign each plane and place its declared coordinates; SHD exports, saved VC and actual GUI reload verify every mesh/region before the annual run. Optional spec.shading_mode=module_layout invokes the native detailed electrical layout path for two landscape zero-spacing, single-string groups and exports ShdElec. Omitting it preserves the original request/checkpoint representation. Optional spec.scene_import_method="native" routes the SAME supported two-fixed-table recipe through the existing headless native importer (no GUI/INI/clipboard) and records the new variant as STORED-only: stored_geometry_verified (and stored_module_layout_verified for module_layout) may be true, while imported/native_geometry_verified/native_reload_verified and native_consumption_verified stay false until the normal CLI simulation consumes that VC. Omitting it keeps the original GUI import route and request/checkpoint shape; unsupported recipes stop with a concrete issue before writing and there is no silent GUI fallback. Preview writes nothing/does not activate or launch GUI; cold execution requires dry_run=false and confirm=true, configured DataPath and NO preexisting native GUI. It exclusively creates a working PRJ/VC0, PVC2 and SFI, opens one owned GUI, imports/ associates/checks/shading-tables/SavesAs one NEW native variant, then normally closes only its actual Popen. Unknown dialogs/unsaved-work questions are not dismissed. A NEW CLI process reloads the saved variant, recomputes native shading and generates the explicit full-year CSV/PDF. Completeness/context/finite columns/GlobShd and source preservation are checked using existing result validators; no replacement PV model. File creation, native save and simulation-consumption remain distinct checkpoints. Results/_house_task.json records the exact request and guarded files; existing artifacts are never overwritten/deleted. Resume requires the IDENTICAL spec and explicit resume=true; no checkpoint PID grants ownership. Partial unverified native saves need inspection, not blind reimport. A failed run keeps its outputs: explicit retry_simulation=true chooses NEW attempt names, without rebuilding the saved scene. A completed retry-free resume revalidates artifacts and runs no new GUI/simulation. Status/phase/issues matter, not just MCP is_error; any unexpected stop retains evidence. Process coordination is one server/workspace RLock, not a global desktop/task service.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| spec | Yes | ||
| resume | No | ||
| confirm | No | ||
| dry_run | No | ||
| retry_simulation | No |