mike-end-to-endlisted

# MIKE+ End-to-End (SOP) The other `mike-*` skills describe one tool group each. This one says how they fit together, what must be true before a number or figure is reported, and when to stop. ## 1. Pick an operating mode (state it in the first reply) | Mode | When | Chain | License | |---|---|---|---| | **A. Read / plot only** | a `.res1d` already exists, or no MIKE+ install | `mike-results` -> `mike-plot` -> `mike-audit` | none | | **B. Run an existing model** | a `.sqlite` and a goal ("run the 1-year storm") | copy -> `mike-model` -> (`mike_set_scenario`) -> `mike-runner` -> `mike-results` -> `mike-plot` -> `mike-audit` | yes | | **C. What-if / compare** | "what if the pipe were 0.5 m", "before vs after" | baseline copy + variant copy -> `mike-params` (variant only) -> `mike-runner` x2 -> `mike-compare` -> `mike-audit` | yes | | **D. Import from SWMM** | an EPA SWMM `.inp` (SWMMCanada, agentic-swmm) | `mike-import` -> then B or C | yes | | **E. New rainfall** | a CSV storm / gauge record to drive the model | `mike-rain` -> point the model's rainfall boundary at the `.dfs0` (`mike-params`) -> B | rain: none, run: yes | If the goal only needs Mode A, do not touch mikeplus at all: it is faster and needs no license. ## 2. Standard run directory (create it, use it everywhere) ``` runs/<case>/ 00_model/ COPY of the whole model folder (.sqlite, .mupp, .dfs0, hotstart .res1d ...) 01_inputs/ rain CSV/.dfs0 you produced, notes 02_results/ the engine wri