Projects list: follow-ups from the 1/0 count fix

Seen during the 1024px visual check for Task 7251 (Directory › Projects, local dev seed). 1. The over-max warning on the `active/max` slot ("1/— ⚠") is explained only by a native `title` hover, which touch and phone users cannot reach. Give it a second home there, e.g. a hung warning line on the phone band. 2. Sorting by Pool Max ranks a max of 0 above an unset max (0 vs -1 in `Projects.tsx` sort), although both now draw "—". Rank them as equal. 3. The dev seed's `org-a-probe-projects` row shows the Operator org, not org A. Confirm the seed assigns the intended org, or rename the probe. Out of scope: the count rendering itself (Task 7251), the name/org layout (Task 7229), the row hover (Task 7240). Done means: - Each item is fixed or explicitly declined with a reason; web tests in `apps/web/src/pages/Projects.test.tsx` cover 1–2; checked visually at 375px and 1024px.

Fixed Pool Max sort (0 ranks equal to unset) + test; item 3 declined (org A = Operator org by design); item 1 deferred to draft Task 7346 (its ⚠ is unmerged Task 7251's). Quick gate green, visual 375/1024 ok. PR #5946 merged; deploy superseded.