The /forges and /forges/new pages fit a 390 px phone: no sideways scroll, the form's fields and long forge names wrap #9372

Intent: /forges and /forges/new reads on a 390 px phone without sideways scroll, in the same way the issues, pulls, waves and milestones pages now do (see test/issues-fit.test.ts and test/milestones-fit.test.ts for the shape).

Done:

• [x] A new test/forges-fit.test.ts seeds the page with long content: an unbroken 250-character word where the page shows a name or title, a long title, and many rows. It renders /forges and /forges/new and asserts no inline width/min-width over 390 px and no rule the page ships fixes a width over 390 px.
• [x] The containers holding long text carry overflow-wrap: anywhere (or break-word); the test asserts it. Wide content that must not wrap (code, a tree, a table) scrolls inside its own box (overflow-x: auto), never the page.
• [ ] Like test/milestones-fit.test.ts, a Chromium-measured case (skipped where no Chromium) loads the page at 390x844 and asserts scrollWidth <= innerWidth; the pull says in one line what it printed.
• [x] The test fails without the fix, or, if the page already fits, it pins that and the pull says so.
• [x] bun test and bun scripts/design-lint.ts pass.

Files: test/forges-fit.test.ts, src/web/pages/new-forge.ts, src/web/pages/forges.ts, src/web/style/ (only the rules the page needs).

This adds no preview look; the preview list of looks stays as it is.

Risks: a shared component rule changed for this page reaches other pages; prefer a rule scoped to this page's class, and run the other *-fit tests.

Fits: a builder's brief (scout or mason).

Parked by the crew: the check stayed red through 2 automatic tries (pull #9397 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Reviewed pull #9613 at its head: ticked A new test/forges-fit.test.ts seeds the page with long content: an unbroken 250-character word where the page shows a name or title, a long title, and many rows. It renders /forges and /forges/new and asserts no inline width/min-width over 390 px and no rule the page ships fixes a width over 390 px.; The containers holding long text carry overflow-wrap: anywhere (or break-word); the test asserts it. Wide content that must not wrap (code, a tree, a table) scrolls inside its own box (overflow-x: auto), never the page.; The test fails without the fix, or, if the page already fits, it pins that and the pull says so.; bun test and bun scripts/design-lint.ts pass.. left open: Like test/milestones-fit.test.ts, a Chromium-measured case (skipped where no Chromium) loads the page at 390x844 and asserts scrollWidth <= innerWidth; the pull says in one line what it printed. — The case exists but Chromium did not run in the builder sandbox, so the pull has no printed measurement..

Left open after pull #9613 landed: 1 unticked item remains (Like test/milestones-fit.test.ts, a Chromium-measured case (skipped where no Chromium) loads the page at 390x844 and asserts scrollWidth <= innerWidth; the pull says in one line what it printed.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

Already done on main in 10ef8b94d: test/forges-fit.test.ts measures /forges and /forges/new in Chromium at 390x844 and asserts scrollWidth <= innerWidth.