openai/gpt-chat-latest → A (4:1)

Side A substantially improves the developer workflow by replacing a one-shot release build with a persistent cargo-watch server, reusing seeded fixture data across runs, preferring a stable port with fallback, and rebasing saved URLs so the fixture remains usable after restarts. Side B adds a useful regression test for rank centrality on a random spanning-tree input, but it only increases test coverage and does not change the project's runtime behavior or architecture.