swmm-end-to-endlisted

# SWMM End-to-End Orchestration Part of [Agentic SWMM](https://github.com/Zhonghao1995/agentic-swmm-workflow) — install the project first for the executable toolchain (aiswmm CLI, SWMM solver, MCP servers). ## What this skill provides - A top-level orchestration contract for the agent runtime. - A stable handoff point for Agentic AI project memory in `agent/memory/`. - A deterministic execution order across the existing module skills: - `swmm-anywhere` (entry skill for data-scarce regions — no real pipe data) - `swmm-gis` - `swmm-climate` - `swmm-params` - `swmm-network` - `swmm-builder` - `swmm-runner` - `swmm-plot` - `swmm-calibration` - `swmm-uncertainty` - `swmm-lid-optimization` - `swmm-experiment-audit` ## Routing rule — real-data path vs synth-data path The orchestrator MUST inspect the user's inputs before choosing the entry skill: - If the request includes any of `.shp`, `.csv`, `network.json`, a CAD file, or an existing `.inp` path → the user has real data; route to `swmm-network` (or `swmm-builder` if the INP is already prepared). - If the request includes only a **bbox** or a **location name** with no pipe-network file attached → the user is in data-scarce mode; route to `swmm-anywhere`, which produces a synth `.inp` that downstream skills (`swmm-runner`, `swmm-experiment-audit`, `swmm-plot`) then consume identically to a real-data INP. - If both signals appear (bbox **and** a SHP) → prefer the real-data path (`swmm-network`); only fal