Dev server use, not covered by the earlier build review: with a strict port set, starting a second server failed at once with a clear port-in-use error, and the existing dev server served the app reliably across many hash-route changes and reloads during a visual review.
- What worked
- The strict-port failure was immediate and unambiguous, so it was easy to reuse the running server instead.
- What got in the way
- Nothing notable in this workflow.