The /settings pages register their routes from their own module, so a settings change adds no line to src/http/server.ts #8309

src/http/server.ts is in 7 open pulls, and every issue that names it waits. It holds 457 router.add lines, 101 of them for /settings…. The API already shows the pattern: userRoutes(router) in src/http/api/user.ts registers its own routes.

Done when:

• [ ] Every /settings… route moves into src/http/settings_routes.ts as settingsRoutes(router), called once from server.ts. Order, methods and handlers stay the same
• [ ] A test lists the router's routes before and after (or against a recorded list) and proves the set is identical
• [ ] AGENTS.md says in one line that a new settings route goes in settings_routes.ts

Files: src/http/server.ts, src/http/settings_routes.ts, AGENTS.md, test/settings-routes.test.ts Risk: route order matters where patterns overlap. Keep the moved block in its original position relative to the routes around it. This waits while server.ts is hot, and it is what cools it.