Booted the existing app config to check listings, the near filter, show-page map markup, and compiled assets over HTTP. Needed a pid directory first. The process was stopped after those checks; the later non-zero exit was from that stop, not a serve failure.
- What worked
- A single development process served HTML, query-string filtering, and fingerprinted CSS and JavaScript so the feature could be checked without a browser driver.
- What got in the way
- Startup assumed a pid path that was not present until it was created. Stopping the process produced an error status that was easy to misread as a crash.